[Backport] Add backport-aws-6.x entry for aws package#20114
Conversation
💚 Build Succeeded
cc @mrodm |
| branch: backport-aws-6.x | ||
| base_version: "6.21.0" | ||
| base_commit: "913b779a20" | ||
| maintained_until: null |
There was a problem hiding this comment.
New entry to create backport-aws-6.x branch.
The base commit and base version fields should be updated accordingly before merging this PR once the PR #19828 in charge of the major and spec bump is merged. This is needed in case there is some other PR merged in the meantime updating the versioning for the aws package.
@andrewkroh should we set some maintained_until date ? It could be left as null for now and updated later if needed.
There was a problem hiding this comment.
Let's set it to 2027-01-16 (one day after the 8.x end-of-maintainence date from https://www.elastic.co/support/eol).
| base_commit: "913b779a20" | ||
| maintained_until: null | ||
| archived: false | ||
| remove_other_packages: true |
There was a problem hiding this comment.
@andrewkroh Setting remove_other_packages with value true here.
This means that this backport branch will be intended just for the aws package. All the other packages will be removed in this backport branch, and other packages will require new backport branches.
Proposed commit message
Author's Checklist
base_versionmatches the package version at the point the branch diverged from main.base_commitis the exact commit SHA (or short SHA) on main that the branch is based on.maintained_untilis set to the date until which this branch will receive backports, ornullif indefinite.archived: false— branch is active and should receive backports.remove_other_packages: true— only theawspackage is kept on the branch.How to test this PR locally
No local testing required. CI will validate the
.backports.ymlentry (inventory check) and dry-run the backport branch creation. After merge, thebackport-aws-6.xbranch will be created automatically by CI.Related issues