fix(ci): use main's tooling for release branch bumps#3663
Conversation
The bump-payload-on-releases workflow was failing on older release branches (e.g. release-v0.74.x) because the generate-bump-message.sh script does not exist on those branches. The workflow now checks out main first to build the operator tool binary and cache the script, then checks out the release branch for the actual bump. This ensures consistent tooling regardless of branch age. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Akshay Pant <akpant@redhat.com>
vdemeester
left a comment
There was a problem hiding this comment.
Ah interesting.. but won't the 2 checkout be conflicting ?
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No conflict, the second actions/checkout overwrites the workspace. When checkout runs against the same path (default $GITHUB_WORKSPACE), it does: before fetching the new ref. The flow is:
Verified locally with act, a file created after the first checkout is wiped by the second, while /tmp/ artifacts persist. |
|
The CI failure looks unrelated to the changes :/ |
|
/retest |
Changes
The bump-payload-on-releases workflow was failing on older release branches (e.g. release-v0.74.x) because the generate-bump-message.sh script does not exist on those branches. The workflow now checks out main first to build the operator tool binary and cache the script, then checks out the release branch for the actual bump. This ensures consistent tooling regardless of branch age.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make test lintbefore submitting a PRSee the contribution guide for more details.
Release Notes