Skip to content

chore: bump to v0.1.59 - #216

Merged
alexkroman merged 2 commits into
mainfrom
release/v0.1.59
Sep 30, 2026
Merged

alexkroman merged 2 commits into
mainfrom
release/v0.1.59

Conversation

@alexkroman

Copy link
Copy Markdown
Collaborator

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 /latest feed to a newer build.

Release notes (shown in Sparkle's update window)

  • Check that automatic updates work: nothing else changes in this version

Test after the gate

In the installed v0.1.58, choose Check for Updates…. Check that:

  • it offers 0.1.59 with the note above
  • it installs and relaunches as 0.1.59 (Settings → Advanced → Updates)
  • dictating into another app still pastes (the Accessibility permission survives)

The bump check fails because pushing the notes commit re-triggers release-bump's ancestor guard. That's expected, and bump isn't a required check.

🤖 Generated with Claude Code

github-actions Bot and others added 2 commits September 30, 2026 03:54
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alexkroman
alexkroman enabled auto-merge (squash) September 30, 2026 03:59
@alexkroman
alexkroman merged commit b75bc99 into main Sep 30, 2026
10 of 12 checks passed
@alexkroman
alexkroman deleted the release/v0.1.59 branch September 30, 2026 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants