Fix verification script for new sqlparser_derive version #2119
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
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.
0.60.0around 2025-11-15 #2045sqlparser_derive = "^0.4.0"#2118cargo publish --dry-rundoesn't work when there are multiple crates that are to be published in the same workspacecargo release publish --dry-run --workspacefails due to unpublished workspace dependencies crate-ci/cargo-release#691 (comment)Thus, if we change the version of sqlparser_derive,
cargo publish --dry-runfails with the 0.60.0 release, as reported in #2118.Let's remove the
cargo publish --dry-runcheck. I tested locally and verified that the verification procedure now passes with0.60.0rc1