Skip to content

[Backport] Add backport-aws-6.x entry for aws package#20114

Draft
mrodm wants to merge 1 commit into
elastic:mainfrom
mrodm:create-backport-aws-6.x
Draft

[Backport] Add backport-aws-6.x entry for aws package#20114
mrodm wants to merge 1 commit into
elastic:mainfrom
mrodm:create-backport-aws-6.x

Conversation

@mrodm

@mrodm mrodm commented Jul 14, 2026

Copy link
Copy Markdown
Collaborator

Proposed commit message

[Backport] Add backport-aws-6.x entry for aws package

Add a new entry in `.backports.yml` for the `aws` package backport branch
`backport-aws-6.x`, based on version 6.21.0 (commit 913b779a20).

This branch is active (`archived: false`) and configured to strip all
other packages (`remove_other_packages: true`), consistent with other
aws backport entries.

Author's Checklist

  • base_version matches the package version at the point the branch diverged from main.
  • base_commit is the exact commit SHA (or short SHA) on main that the branch is based on.
  • maintained_until is set to the date until which this branch will receive backports, or null if indefinite.
  • archived: false — branch is active and should receive backports.
  • remove_other_packages: true — only the aws package is kept on the branch.

How to test this PR locally

No local testing required. CI will validate the .backports.yml entry (inventory check) and dry-run the backport branch creation. After merge, the backport-aws-6.x branch will be created automatically by CI.

Related issues


This PR was generated with the assistance of Claude (claude-sonnet-4-6).

@mrodm mrodm self-assigned this Jul 14, 2026
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

cc @mrodm

Comment thread .backports.yml
branch: backport-aws-6.x
base_version: "6.21.0"
base_commit: "913b779a20"
maintained_until: null

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

Comment thread .backports.yml
base_commit: "913b779a20"
maintained_until: null
archived: false
remove_other_packages: true

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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.

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