Fix branch reference in stage-release-candidate.yml#2690
Merged
Conversation
Member
Author
|
I can test this as part of prepping the 1.5.0 release. Hard to test without actually running the workflow. |
He-Pin
approved these changes
Feb 27, 2026
pjfanning
force-pushed
the
pjfanning-patch-2
branch
from
74c7eb1 to
092855c
Compare
Member
Author
|
I'm going to merge this to 1.5.x branch because that is where I am testing for the upcoming 1.5.0 release. I can forward fit the changes to main branch when they look like they work ok. |
Updated the branch reference in the release candidate workflow to use the dynamic branch variable.
pjfanning
force-pushed
the
pjfanning-patch-2
branch
from
092855c to
0abfd02
Compare
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
2 participants
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.
Updated the branch reference in the release candidate workflow to use the dynamic branch variable.
Also, explicitly say 72hrs because the token does not seem to be replaced.