chore: bump SDKs to 0.6.1 - #77
Merged
Merged
Conversation
The v0.6.1 tag and GitHub release went out on top of packages that still declared 0.6.0, so the tag-triggered PyPI publish collides with the existing 0.6.0 uploads. Bump aleo-sdk, aleo-contract-abi-generator, shield-swap-sdk and aleo-bridge-sdk to 0.6.1 in lockstep (manifests, lockfiles, docs conf, __version__ and the version tests). Dependency floors are unchanged.
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.
Bumps all four packages to 0.6.1 in lockstep:
aleo-sdk,aleo-contract-abi-generator,shield-swap-sdkandaleo-bridge-sdk(bothCargo.toml+Cargo.lock, the fourpyproject.toml,sdk/docs/source/conf.py, the two__version__strings and their version tests). Dependency floors such asaleo-sdk>=0.5.1are unchanged.Why
The v0.6.1 release was tagged on master while every package still declared 0.6.0, so the tag-triggered
SDK Wheelspublish jobs collide with the 0.6.0 files already on PyPI and nothing ships under 0.6.1.After merge
Move the tag to the merge commit so the publish re-runs with the right version:
The release notes reference the tag name only and need no edit.
Validation
bridge-sdk:tests/test_package.py+tests/test_client_lifecycle.py— 17 passed.shield-swap-sdk:tests/test_package.py— 3 passed.cargo metadatareports 0.6.1 for both crates with the edited lockfiles, no regeneration needed.