workspace: Bump all crates for publish #31
Merged
+298
−298
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
|
|
#### Problem As mentioned at anza-xyz#27, the sdk crates were pinning their versions internally, which made them more difficult to use outside of the repo. Now that the version has been relaxed, we need to publish these crates, but they're almost all still on v2.2.0. #### Summary of changes Normally crate publishing will be done one-by-one through the GitHub Actions publish workflow, but with ~100 crates, we need to go faster. Bump all of the v2.2.0 crates to v2.2.1, bump address-lookup-table-interface to v2.2.2, and bump loader-v3-interface to v3.0.0 since it contains a breaking change. Once this lands, we can publish all of the crates in the repo.
willhickey
previously approved these changes
Feb 12, 2025
Cargo.lock
Outdated
| "hermit-abi 0.4.0", | ||
| "libc", | ||
| "windows-sys 0.59.0", | ||
| "windows-sys 0.52.0", |
There was a problem hiding this comment.
Is this change expected? There's a similar one at line 4651
There was a problem hiding this comment.
I was a bit surprised by those changes too.
I reverted them manually, and it doesn't look like cargo tries to downgrade it again, so committed up 97e3f6e -- thanks for noticing!
There was a problem hiding this comment.
Yeah cargo does something weird. We never did figure out the borsh dependency version change that was happening in the monorepo. Chido eventually added a step to the version bump that just manually reverts it 🙈
There was a problem hiding this comment.
Yikes, that's rough 😅
willhickey
approved these changes
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
As mentioned at #27, the sdk crates were pinning their versions internally, which made them more difficult to use outside of the repo. Now that the version has been relaxed, we need to publish these crates, but they're almost all still on v2.2.0.
Summary of changes
Normally crate publishing will be done one-by-one through the GitHub Actions publish workflow, but with ~100 crates, we need to go faster.
Bump all of the v2.2.0 crates to v2.2.1, bump address-lookup-table-interface to v2.2.2, and bump loader-v3-interface to v3.0.0 since it contains a breaking change.
Once this lands, we can publish all of the crates in the repo.