chore: cut 0.1.0 — first stable in the 0.1.x line#22
Merged
vvillait88 merged 1 commit intomainfrom May 7, 2026
Merged
Conversation
Drops the `-rc.19` prerelease suffix. No behavioral change vs rc.19; this is the same code, end-to-end verified against the live martin-estate API in the previous release cycle. After this, consumers can pin `"@agent-score/pay": "^0.1.0"` and get the 0.1.x line (npm's standard semver caret excludes prereleases by default; this cut unlocks that). Future minor changes: 0.1.1, 0.1.2, ... Breaking changes: 0.2.0 Marketing-launch milestone: 1.0.0 (deferred per the team's policy that 1.0 is a coordinated launch, not a tech milestone). 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.
Summary
Drops the
-rc.19prerelease suffix. No behavioral change vs rc.19 — this is the same code, end-to-end verified against the live martin-estate API in the previous release cycle (all 5 rails probe correctly, every wallet operation works, error envelope shape withextra+next_stepsis live, sync-throw fix is live, human-TTY rendering is preserved).Why now
After this cut, consumers can pin
"@agent-score/pay": "^0.1.0"inpackage.jsonand get the 0.1.x line. Standard semver caret excludes prereleases by default — that's why^0.1.0against any0.1.0-rc.Xversion errors withNo match found for version ^0.1.0. Cutting the unsuffixed0.1.0unlocks the conventional caret range.Global search confirmed nothing else needs updating
Every install instruction across all repos (Mintlify docs, store skill manifest, node-commerce
llms_txt+how_to_pay, Homebrew template, pay's owninstall.sh) references@agent-score/payversion-free. They auto-resolve to whateverlatestdist-tag points to after publish.Versioning policy ahead
Test plan
bun run typecheckcleanbun run lintcleanbunx vitest run— passes (no behavioral change since rc.19, same suite)v0.1.0after merge → publish workflow fires (non-prerelease branch setslatestdist-tag)🤖 Generated with Claude Code