Skip to content

Vault 34895/backport for 1 20#30930

Closed
benashz wants to merge 2 commits into
release/1.20.xfrom
VAULT-34895/backport-for-1-20
Closed

Vault 34895/backport for 1 20#30930
benashz wants to merge 2 commits into
release/1.20.xfrom
VAULT-34895/backport-for-1-20

Conversation

@benashz
Copy link
Copy Markdown
Contributor

@benashz benashz commented Jun 10, 2025

Description

What does this PR do?

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

@benashz benashz requested review from a team as code owners June 10, 2025 18:53
@benashz benashz added this to the 1.20.0-rc milestone Jun 10, 2025
@github-actions
Copy link
Copy Markdown

CI Results:
All Go tests succeeded! ✅

@github-actions
Copy link
Copy Markdown

Build Results:
All builds succeeded! ✅

@helenfufu
Copy link
Copy Markdown
Contributor

Handled by #30929

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants