Skip to content

Conversation

aanm
Copy link
Member

@aanm aanm commented Aug 13, 2025

This will make the release process even more smooth for release managers.

Depends on cilium/release#348

@aanm aanm requested a review from joestringer August 13, 2025 11:17
@aanm aanm requested review from a team as code owners August 13, 2025 11:17
@aanm aanm requested a review from brlbil August 13, 2025 11:17
@aanm aanm added release-note/misc This PR makes changes that have no direct user impact. needs-backport/1.16 This PR / issue needs backporting to the v1.16 branch needs-backport/1.17 This PR / issue needs backporting to the v1.17 branch needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Aug 13, 2025
@aanm aanm enabled auto-merge August 13, 2025 11:17
@aanm
Copy link
Member Author

aanm commented Aug 13, 2025

/test

@aanm aanm force-pushed the pr/add-step-5-release branch from e3460a0 to 4036d47 Compare August 14, 2025 15:35
@aanm aanm requested a review from joestringer August 14, 2025 15:35
@aanm
Copy link
Member Author

aanm commented Aug 14, 2025

/test

@aanm aanm force-pushed the pr/add-step-5-release branch from 4036d47 to 3a5dcde Compare August 14, 2025 15:37
@aanm
Copy link
Member Author

aanm commented Aug 14, 2025

/test

Copy link
Member

@joestringer joestringer left a comment

Choose a reason for hiding this comment

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

I'm a bit on the fence about whether this repository is the right place to host the logic for managing the merge, but on the other hand if it's part of this workflow which (a) has environment: release-tool for appropriate approvals and (b) is tied into the same workflow we already monitor for progress, it's probably easier to track the status of the release through this workflow than to add more logic elsewhere.

Either way this seems like an improvement to the process that should simplify things moving forward. If we hit some problems with this approach we can always amend the process further. 👍

@aanm aanm force-pushed the pr/add-step-5-release branch from 3a5dcde to 22703ac Compare August 15, 2025 10:29
@aanm aanm added the backport/author The backport will be carried out by the author of the PR. label Aug 15, 2025
This will make the release process even more smooth for release
managers.

Signed-off-by: André Martins <andre@cilium.io>
@aanm aanm force-pushed the pr/add-step-5-release branch from 22703ac to e9a0771 Compare August 15, 2025 10:30
@aanm
Copy link
Member Author

aanm commented Aug 15, 2025

/test

@aanm aanm added this pull request to the merge queue Aug 15, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Aug 15, 2025
Merged via the queue into main with commit 08bb1a7 Aug 15, 2025
68 checks passed
@aanm aanm deleted the pr/add-step-5-release branch August 15, 2025 10:50
@aanm aanm mentioned this pull request Aug 15, 2025
3 tasks
@aanm aanm added the backport-pending/1.17 The backport for Cilium 1.17.x for this PR is in progress. label Aug 15, 2025
@aanm aanm removed the needs-backport/1.17 This PR / issue needs backporting to the v1.17 branch label Aug 15, 2025
@aanm aanm added backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. and removed needs-backport/1.16 This PR / issue needs backporting to the v1.16 branch needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Aug 15, 2025
@github-actions github-actions bot added backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. and removed backport-pending/1.16 The backport for Cilium 1.16.x for this PR is in progress. backport-pending/1.17 The backport for Cilium 1.17.x for this PR is in progress. backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. labels Sep 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/author The backport will be carried out by the author of the PR. backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants