Add details re: dependency version error when publishing packages #77
Conversation
This file contains 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
When publishing a package (with `sui client publish`) there might be an error if the revision of a dependency used to build the package does not match with the on-chain version. Add details about the error and information about the the revision (`rev`) field of a dependency that appears in a package's `Move.toml`.
|
Hey sir! Thanks for this! We recently switched to testnet being the default network and a mainnet / testnet binary has a high risk of not working with devnet at all given that the latter is always 1 version ahead of everything else. I'll look into the issue, but the solution you have here is not the one. |
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.
I noticed that when publishing a package (with
sui client publish) there might be an error if the revision of a dependency used to build the package does not match with the on-chain version.The PR adds details about the error and information about the the revision (
rev) field of a dependency thatappears in a package's
Move.toml.