Skip to content

chore: bump to v0.1.39 - #131

Merged
claude[bot] merged 1 commit into
mainfrom
release/v0.1.39
Aug 12, 2026
Merged

chore: bump to v0.1.39#131
claude[bot] merged 1 commit into
mainfrom
release/v0.1.39

Conversation

@claude

@claude claude Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

Requested by Alex Kroman · Slack thread

What & why

Version bump to 0.1.39 (CFBundleShortVersionString 0.1.38 → 0.1.39, CFBundleVersion 38 → 39). Generated by the release-bump workflow — run 31641116076, started from a pushed marker branch at main's tip.

Merging this starts the release: the changed version landing on main triggers release.yml, which builds, signs, and notarizes the DMG, then parks on the release-publish approval gate before anything ships.

How it was tested

  • scripts/check.sh passes (or CI will, if I'm not on a Mac) — generated bump only; the check workflow runs on this PR
  • I read AGENTS.md and this doesn't reintroduce anything deliberately removed
  • Docs updated if behavior changed — n/a, generated bump only

Generated by Claude Code

@claude
claude Bot enabled auto-merge August 12, 2026 21:10
@github-actions

Copy link
Copy Markdown
Contributor

Dev build

Download Blurt.app — built from 5e79c16, Debug-Local,
ad-hoc signed. Expires in 14 days.

Installing it
cd ~/Downloads
unzip -o blurt-dev-build-pr-131.zip   # GitHub wraps every artifact in a zip
unzip -o Blurt-dev-5e79c16.zip
find Blurt.app -exec xattr -c {} +   # clear quarantine: xattr lost -r in macOS 12.3
rm -rf /Applications/Blurt.app && cp -R Blurt.app /Applications/
open -a Blurt

It is ad-hoc signed and not notarized: Gatekeeper refuses to open it until
the quarantine flag is cleared, and macOS treats it as a different app from a
released Blurt, so you have to re-grant Microphone, Accessibility, and Input
Monitoring. Reinstall the release DMG
when you are done reviewing.

Expect that re-grant once per dev build, including a second build of this
same PR. TCC pins an Accessibility grant to the signature that took it, and an
ad-hoc signature is just a hash of the binary, so every build is a new app as far
as tccd is concerned. Blurt clears the orphaned grant at launch, which is what
keeps the Accessibility step from getting stuck on a Blurt row that is switched on
and still denied. If you are coming from a build old enough to predate that,
clear the grant yourself once:

tccutil reset Accessibility dev.alex.blurt

@claude
claude Bot added this pull request to the merge queue Aug 12, 2026
Merged via the queue into main with commit 8d01ed4 Aug 12, 2026
12 checks passed
@claude
claude Bot deleted the release/v0.1.39 branch August 12, 2026 21:32
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.

0 participants