Skip to content

Backport of Update vault-plugin-auth-jwt to v0.24.1 into release/1.20.x#30902

Closed
hc-github-team-secure-vault-core wants to merge 1 commit into
release/1.20.xfrom
backport/VAULT-36390/update/vault-plugin-auth-jwt/v0.24.1/enormously-natural-macaque
Closed

Backport of Update vault-plugin-auth-jwt to v0.24.1 into release/1.20.x#30902
hc-github-team-secure-vault-core wants to merge 1 commit into
release/1.20.xfrom
backport/VAULT-36390/update/vault-plugin-auth-jwt/v0.24.1/enormously-natural-macaque

Conversation

@hc-github-team-secure-vault-core
Copy link
Copy Markdown
Collaborator

Backport

This PR is auto-generated from #30876 to be assessed for backporting due to the inclusion of the label backport/1.20.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@hashiblaum
This person should resolve the merge-conflict(s) by either:

  • Manually completing the cherry picks into this branch
  • Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.


This PR was generated by a GitHub Action. Full log: https://github.com/hashicorp/vault/actions/runs/15479712711


Overview of commits

@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jun 6, 2025
@hashicorp-cla-app
Copy link
Copy Markdown

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes


temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

Have you signed the CLA already but the status is still pending? Recheck it.

@blaumer blaumer added this to the 1.20.0-rc milestone Jun 6, 2025
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 6, 2025

CI Results:
All Go tests succeeded! ✅

@blaumer blaumer marked this pull request as ready for review June 6, 2025 19:59
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 6, 2025

Build Results:
All builds succeeded! ✅

@blaumer blaumer closed this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants