Repository navigation
ci(ra): pin the callers to @v1-rc2 and rename the pilot tag in the branching model - #519
Merged
hdamker merged 1 commit intoNov 2, 2026
Conversation
hdamker
merged commit Nov 2, 2026
e41b66c
into
camaraproject:release-automation-refactor
8 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
Renames the floating pilot tag of this branch from
ra-v1-rc2tov1-rc2, so pilots follow@v1-rc→@v1-rc2→@v1.release-automation-caller.yml,validation-caller.yml) pin@v1-rc2; the pin test follows.branching-model.mdnames the new tag.v1-rc2is not deleted with the branch: after the exit merge it followsmain, so callers pinned to it keep working untilv1takes over.The tag
v1-rc2exists at the branch head33ec9aa;ra-v1-rc2andra-v1-rcare deleted.Which issue(s) this PR fixes:
Part of #476
Special notes for reviewers:
The tag-move gates for
v1-rc2are unchanged; this change touches only workflow templates, a test and docs. No canary run goes through@v1-rc2: the ReleaseTest2 callers pin the branch head, so the first pilot switch is the first run through the tag.Changelog input
Additional documentation