chore(release): v0.4.0#83
Merged
Merged
Conversation
Bumps Cargo.toml/Cargo.lock to 0.4.0 and regenerates CHANGELOG.md with `git cliff --tag v0.4.0`. The subject is `chore(release)` rather than plain `chore` so cliff.toml's skip parser drops it: v0.3.0's release commit was named `chore: update CHANGELOG.md for v0.3.0`, so it now shows up as an entry under 0.3.0 on regeneration. Naming it this way keeps release plumbing out of the next section. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XocU6NjgZricrRWMLyLXDn
Codecov Report✅ All modified and coverable lines are covered by tests. 🚀 New features to boost your workflow:
|
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
1 participant
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.
Release prep for 0.4.0. This is the reversible half — merging this does not publish anything. Pushing the
v0.4.0tag is what triggersrelease.yml.Changes
Cargo.toml/Cargo.lock: 0.3.0 → 0.4.0 (viacargo set-version)CHANGELOG.md: regenerated withgit cliff --tag v0.4.035 entries since v0.3.0 (2026-04-08). One line is added to the 0.3.0 section: v0.3.0's own changelog commit, which didn't exist yet when cliff ran for that release. Regeneration is otherwise byte-identical for released sections —
cliff.tomlhasn't changed since v0.3.0.Commit naming
Subject is
chore(release):, not plainchore:.cliff.tomlhas{ message = "^chore\\(release\\)", skip = true }, so this commit won't appear in the 0.5.0 section. v0.3.0's was namedchore: update CHANGELOG.md for v0.3.0, which is exactly why it surfaces as an entry now.Two cosmetic warts, not fixed here
deps:andstyle:aren't types incliff.toml'scommit_parsers, so they produced ad-hoc Deps and Style groups instead of folding into Miscellaneous. Cosmetic only.chore:so it reads under Miscellaneous rather than CI/Build.What's different about this release
v0.3.0 shipped 5 targets. This one ships 7 — both musl targets were added in #79, and #80 verifies their static linkage on dispatch.
publishandgithub_releaseare now gated to tag pushes only, soworkflow_dispatchis a true dry run.🤖 Generated with Claude Code
https://claude.ai/code/session_01XocU6NjgZricrRWMLyLXDn