chore(release): v0.4.0 - #179
Merged
Merged
Conversation
The mechanical half of the release ritual, so the tag is the only thing left to do by hand. `version` goes to 0.4.0 in Cargo.toml and the lockfile, the unreleased section is retitled, and a fresh empty one opens above it. 0.4.0 rather than 0.3.1 was Amy's call on 2026-08-16, and the section earns it: three backend kinds arrived (bfl, gemini-images, dashscope), `write_cas` and `kaibo cas write` are new surfaces, telemetry gained the metrics signal, and backends stopped seeding their own key sources — a minor, not a patch. **The date reads 2026-09-03 and is a guess** — Amy expects to cut the tag in the morning. It has to match the day the tag is pushed, so change the line if that slips; it is the one thing here a later reader cannot infer. Every pre-tag gate in AGENTS.md was run in the session that produced this branch, rather than assumed: - kaish pinned at 0.17.1, current *and* carrying no known unfixed bug — the `readlink -f` break that held this release is fixed and measured. - turso still exact-pinned `=0.7.1`; 0.8.0-pre.7 is a prerelease, so the pin is current. - `cargo tree -i` empty for aws-lc-rs, aws-lc-sys, mimalloc and openssl-sys, on the musl target and with `ring` as the control that the query works at all. - The musl binary is `statically linked` / `not a dynamic executable`, runs, and the assertion was checked against a dynamic binary to confirm it discriminates. - The sandbox probe battery A-G was re-run against both kaish pins and diffed, which the kernel bump required. Co-Authored-By: Claude Opus 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.
The mechanical half of the release ritual, so the tag is the only thing left to do by
hand.
version→ 0.4.0 inCargo.tomland the lockfile, the unreleased section retitled,a fresh empty one opened above it.
0.4.0 rather than 0.3.1 was your call on 2026-08-16, and the section earns it: three
backend kinds arrived (
bfl,gemini-images,dashscope),write_casandkaibo cas writeare new surfaces, telemetry gained the metrics signal, and backends stopped seedingtheir own key sources. A minor, not a patch.
The date reads
2026-09-03and it is a guess — you said you'd likely pick this up inthe morning. It must match the day the tag is pushed:
sed -i 's/^## \[0.4.0\] — .*/## [0.4.0] — YYYY-MM-DD/' CHANGELOG.mdIt is the one thing in this PR a later reader cannot infer or correct from context.
Pre-tag gates — run, not assumed
Every item in AGENTS.md's Cutting a release, checked in the session that produced this
branch:
readlink -fbreak that held this release is fixed and measured=0.7.1holds; 0.8.0-pre.7 is a prereleasecargo tree -iemptyringas the control that the query worksstatically linked, stripped/not a dynamic executable, runs and reports its versionThe static assertion was also run against a dynamic binary to confirm it discriminates,
because a check nobody has seen fail is a check nobody has tested.
Suite 1329 passed / 0 failed.
kaibo --versionreportskaibo 0.4.0.After the tag
.github/workflows/release.ymlbuilds the matrix onv*. Then the ritual's last steps,both deliberately manual:
gh attestation verify, andcosign verify-blobwith the new tag's identity. Note the floor is now cosign ≥ 2.5,measured this session (2.4.0 genuinely cannot read the bundle).
scripts/bump-tap.sh v0.4.0to point the Homebrew tap at the new release.🤖 Generated with Claude Code