mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2025-12-26 11:51:42 +01:00
Code Issues Projects Releases Wiki Activity
vault/.github/pull_request_template.md
hc-github-team-secure-vault-core 6d6807204d
[VAULT-34830] actions: update CE workflows for unified enterprise repository (#31425) (#31457) 
Various small changes and tweaks to our CI/CD workflows to allow for running CE branches in the context of `hashicorp/vault-enterprise`.

Signed-off-by: Ryan Cragun <me@ryan.ec>

 Conflicts:
	.github/actionlint.yaml
	.github/workflows/benchmark-prevent-performance-degradations.yml
	.github/workflows/plugin-update.yml
	.github/workflows/test-go.yml

Co-authored-by: Ryan Cragun <me@ryan.ec>
2025-08-07 15:27:03 -06:00

2.0 KiB
Raw Blame History

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.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.