chore: release 0.4.1 - #15
Merged
Merged
Conversation
Ship the post-0.4.0 housekeeping on npm: the refreshed README (upgrading guide, file:.. copy semantics) which is part of the published tarball, and a lib/ rebuilt with builder-bob 0.43 / TypeScript 6. No feat/fix landed since 0.4.0, so release-please needs the version stated explicitly. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP Release-As: 0.4.1
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.
Everything on main since v0.4.0 is chore/docs/ci, which release-please doesn't treat as releasable — this empty commit forces a 0.4.1 release PR via its
Release-Asfooter, so the refreshed README (it ships in the npm tarball) and the bob 0.43 / TS 6 build get published.Merge #14 first (the npm 11 pin), or the 0.4.1 publish will hit the same npm 12
sigstorefailure as 0.4.0.Merging this PR: if you squash, keep the body's last line so release-please sees it. With a merge commit it's preserved automatically.
Release-As: 0.4.1
🤖 Generated with Claude Code
https://claude.ai/code/session_012rn1KYa8uH8ikwK3AaHaLP