Repository navigation
chore: bump to v0.1.59 - #216
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <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
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.
Bumps Blurt to v0.1.59 (build 58). No code changes since v0.1.58: this release exists to test the real Sparkle update path, from the shipped v0.1.58 on the
/latestfeed to a newer build.Release notes (shown in Sparkle's update window)
Test after the gate
In the installed v0.1.58, choose Check for Updates…. Check that:
The
bumpcheck fails because pushing the notes commit re-triggersrelease-bump's ancestor guard. That's expected, andbumpisn't a required check.🤖 Generated with Claude Code