[Chore] bump version to 0.2.2 - #29
Merged
Merged
Conversation
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.
Motivation
Prepares the v0.2.2 release — the first to publish npm packages via trusted publishing (OIDC) with provenance attestation, following #26/#27/#28. No functional changes to the binary; the release itself is the end-to-end verification of the tokenless publish path.
Test Plan
Cargo.lockupdated in lockstep viacargo update --workspace(only thealeo-devnodeversion entry changed; all dependencies untouched).v0.2.2; the release workflow validates the tag againstCargo.toml, builds, publishes the GitHub release, and dispatches the npm publish, which should logpublishing with provenance. Post-release check:npm view @provablehq/aleo-devnode@0.2.2 dist.attestations.Related PRs