Re-point beta-fw tag on every beta publish#106
Open
bharvey88 wants to merge 1 commit into
Open
Conversation
The rolling beta-fw release tag stays on the commit that was default-branch HEAD when the release was first created. gh release create without --target tags default-branch HEAD, and gh release upload never moves the tag, so the published assets track every beta build while the release source commit does not. Add a step to build-beta.yml that PATCHes the beta-fw tag ref to the built commit after each upload, so the tag always matches the assets. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
|
Caution Review failedFailed to post review comments. We encountered an issue with GitHub. Use ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
⏰ Context from checks skipped due to timeout. (9)
WalkthroughThe beta release workflow now force-updates the rolling ChangesBeta release publishing
Estimated code review effort: 2 (Simple) | ~5 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
1 participant
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.
Version: unchanged (workflow only)
What does this implement/fix?
The rolling
beta-fwrelease tag was stuck on the commit that was default-branch HEAD when the release was first created (gh release createwithout--targettags default-branch HEAD, andgh release uploadnever moves the tag). The published assets tracked every beta build while the release's source commit did not, so the release page and its source archives pointed at the wrong tree.Adds a step to
build-beta.ymlthat PATCHes thebeta-fwtag ref to the built commit after each upload, so the tag always matches the assets.Types of changes
Checklist / Checklijst:
If user-visible functionality or configuration variables are added/modified:
🤖 Generated with Claude Code
Summary by CodeRabbit