chore: bump version to 0.6.8-rc.4 - #77
Merged
Merged
Conversation
Fourth internal-tester pre-release. Adds on top of rc.3: - "Pre-Release" header line above the teal "Update Available" banner (#76) -- testers see the channel of the offered update at a glance without having to parse the version string. Cut quickly after rc.3 so testers on rc.1/rc.2 (Linux/macOS) can exercise the V2-237 + #73 install path twice: once upgrading to rc.3, then again from rc.3 to rc.4 (verifies the fix is sticky across multiple upgrade cycles). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Fourth internal-tester pre-release.
Adds on top of rc.3
PRE-RELEASE / UPDATE AVAILABLE / v0.6.8-rc.X. Testers can identify the channel at a glance.Test cadence
Cutting rc.4 immediately after rc.3 lets testers on rc.1/rc.2 exercise the V2-237 + #73 install path twice:
Two upgrades through the prerelease channel in one tester session — confirms the fix is sticky across cycles, not just on a fresh install.
Release process
Same as previous RC cycles:
git tag v0.6.8-rc.4 && git push origin v0.6.8-rc.4→ release.yml builds (~22 min)gh workflow run refresh-release-notes.yml -f tag=v0.6.8-rc.4