Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: update BPA to disable inactive CE backports #21214

Merged

Conversation

zalimeni
Copy link
Member

Follow-up to #21094, which temporarily downgraded BPA to allow for old CE backport labels to be used during Consul's most recent patch release.

Upgrading fully enforces the version manifest and prevents accidental backports to no-longer-active CE versions.

PR Checklist

  • updated test coverage
  • external facing docs updated
  • appropriate backport labels added
  • not a security concern

Follow-up to #21094, which temporarily downgraded BPA to allow for old
CE backport labels to be used during Consul's most recent patch release.

Upgrading fully enforces the version manifest and prevents accidental
backports to no-longer-active CE versions.
@zalimeni zalimeni added pr/no-changelog PR does not need a corresponding .changelog entry pr/no-backport labels May 23, 2024
@github-actions github-actions bot added type/ci Relating to continuous integration (CI) tooling for testing or releases theme/contributing Additions and enhancements to community contributing materials labels May 23, 2024
@zalimeni zalimeni merged commit d2b107f into main May 24, 2024
102 checks passed
@zalimeni zalimeni deleted the zalimeni/net-8953-update-bpa-ignore-ce-inactive-backports branch May 24, 2024 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/no-backport pr/no-changelog PR does not need a corresponding .changelog entry theme/contributing Additions and enhancements to community contributing materials type/ci Relating to continuous integration (CI) tooling for testing or releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants