chore(leadclaw): 0.2.1 — signed provenance + version sync with mcp#12
Merged
chore(leadclaw): 0.2.1 — signed provenance + version sync with mcp#12
Conversation
0.2.0 was the bootstrap release before the repo went public, so it shipped without sigstore provenance. 0.2.1 is a no-op bump whose only purpose is to get signed provenance on @leadbay/leadclaw and keep versions in sync with @leadbay/mcp@0.2.1. Also fix the contract test that hardcoded "0.2.0" — it now asserts manifest.version === package.json#version, so future bumps only need to edit those two files (enforced by the release workflow's version drift guard). Co-Authored-By: Claude Opus 4.7 (1M context) <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
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.
No functional changes. Bumps to 0.2.1 so leadclaw gets signed sigstore provenance (repo is public now) and matches @leadbay/mcp@0.2.1. Also de-hardcodes the version assertion in the contract test so future bumps don't break it.