chore: release @zkp2p/cash 0.5.3 - #76
Merged
Merged
Conversation
Contributor
Author
|
Post-merge cascade complete for
Cascade receipt: |
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
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 the SDK 0.14.1 adoption from #75 as Cash 0.5.3. This changes only the package version, following the repository release contract; no public API changes.
Validation: #75 passed the full local gate and GitHub CI, including 338 tests and packed compatibility checks, with clean independent review. Release CI passed in run 34347984091 (full bun run ci). The diff was reviewed: only version 0.5.2 → 0.5.3. After merge, the clean release commit will be verified and published, then adopted by the CLI and affected consumers.
Published @zkp2p/cash 0.5.3 from merge commit 3bdbe01 after a clean frozen install and full release preflight. Registry latest is 0.5.3 and downloaded tarball integrity matches the immutable preflight artifact. The initial registry proof lagged publication; read-only reconciliation succeeded without a second publish.