release: 0.4.0 - #21
Merged
Merged
Conversation
Minor rather than patch: a history row gains two things it could not do before — transcribe its kept recording again, and hand you that recording as a file — on all four clients. Nothing about how a dictation is captured, sent or transcribed changes, so nothing an existing install already does behaves differently. VERSION plus the seven fields scripts/stamp-version.sh propagates it to. Both CLIs report `dnt 0.4.0 (9a795fc, 2026-08-28)`. The near-miss gate was not re-run: docs/RELEASING.md asks for it when the prompt, the model or the context encoder changed, and this release touches none of the three. The dictation-accuracy gate is likewise not implicated, because nothing here makes a quality claim. The manual checks in docs/MANUAL-CHECKS.md have NOT been run — they need a microphone, a focused window in another application, a paid request and somebody who knows what was said. That belongs in the draft release notes before publishing, as the checklist itself requires. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016jptSNBmsbgyPSf8FMpxpa
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.
Cuts 0.4.0 for the history redo and save-the-recording work merged in #20.
Minor rather than patch. A history row gains two things it could not do before —
transcribe its kept recording again, and hand you that recording as a file — on all four
clients. Nothing about how a dictation is captured, sent or transcribed changes, so
nothing an existing install already does behaves differently.
VERSIONplus the seven fieldsscripts/stamp-version.shpropagates it to, which is thesame ten files the 0.3.0 bump touched.
scripts/check-version.shagrees, and both CLIsreport
dnt 0.4.0 (9a795fc, 2026-08-28)— the date is UTC, from the stamper; theCHANGELOG heading is the repository's local date, as its own header specifies.
Pre-tagging gates
docs/RELEASING.mdasks for it when the prompt, the model or the context encoder changed. This release touches none of the three.docs/MANUAL-CHECKS.mdneeds a microphone, a focused window belonging to anotherapplication, a paid request, and somebody who knows what was said. No runner has any of
those and neither do I. The draft release notes must record that before publishing,
which is what the checklist asks for: a release that says "Android untested this cycle"
is worth more than one that says nothing.
The two new surfaces are worth a minute of that fifteen when you do run it, since neither
has any automated coverage above the core:
is typed into the window behind the settings panel.
donottype-<timestamp>.wav.Note
v0.3.0 is still an unpublished draft (tagged 2026-08-25). Tagging v0.4.0 will open a
second draft beside it.
🤖 Generated with Claude Code
https://claude.ai/code/session_016jptSNBmsbgyPSf8FMpxpa