Merged
Conversation
joehoyle
approved these changes
Sep 19, 2025
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.
There's a chicken-and-egg scenario here, where the tag, README recommended SHA and latest appropriate commit for the internal reference to the build-to-release-branch action will always be out of sync since they need to be real commit references. You can't do a "relative" path lookup when depending on an action via URL repo path, unfortunately, at least not per my testing.
The better approach long-term may be to fold the
build-to-release-branchaction into the workflow, rather than having it be standalone; but for now, we have a one-commit lag between the latestmainbranch commit that we want to reference for the new tag, and the commit that we'll actually merge and tag.