chore(sdk): release the contract catch-up as 0.0.4, not 0.1.0 - #17
Merged
Merged
Conversation
Every release this SDK has made is a patch step -- 0.0.1, 0.0.2, 0.0.3 -- and the closest precedent is #9, which refreshed the contract snapshot and regenerated as 0.0.2 rather than taking a minor. The 0.1.0 in the catch-up came from semver reasoning about the breaking facade rename, not from this repository's practice, and nothing was published under it. Under npm's rules the choice costs a consumer nothing either way: `^0.0.3` pins exactly, so neither 0.0.4 nor 0.1.0 reaches an existing caller without an explicit bump. What differs is the signal, and a minor here would claim a milestone the package has not reached. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AiYiPkSwvRWDfthQUtx11Q
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.
Corrects the version on #16 before anything is published.
Every release this SDK has made is a patch step — 0.0.1, 0.0.2, 0.0.3 (
sdk/go/v0.0.1..3) — and the closest precedent is #9, which refreshed the contract snapshot and regenerated as 0.0.2, not a minor. The 0.1.0 came from semver reasoning about the breaking facade rename rather than from this repository's practice, and no policy in the repo says otherwise.Under npm's rules the choice costs a consumer nothing either way:
^0.0.3pins exactly, so neither 0.0.4 nor 0.1.0 reaches an existing caller without an explicit bump. What differs is the signal, and a minor would claim a milestone the package has not reached.All six version sites move together — both manifests, the lockfile,
agentdrive_sdk.__version__, the Go README, andgenerate-sdks.sh'sSDK_VERSIONdefault — with the clients regenerated so the generated metadata carries 0.0.4 too.Nothing was published at 0.1.0;
publish.ymlhas not been dispatched.Validation
python3 -m unittest discover -s tests— 28 passed (includes the version-consistency pin).check_contract_provenance/check_operation_coverage— both clean.check-generated-freshness.shafter committing — worktree clean, idempotent.🤖 Generated with Claude Code
https://claude.ai/code/session_01AiYiPkSwvRWDfthQUtx11Q