Update sqlparser_derive to syn 3.0 - #2483
Merged
Merged
Conversation
Contributor
Author
|
If we merge this PR, we will have to release a new version of sqlparser_derive as well (which is fine) |
6 tasks
alamb
marked this pull request as ready for review
September 7, 2026 10:53
LucaCappelletti94
approved these changes
Sep 8, 2026
Contributor
Author
|
Since we don't release often, let's do this now |
Contributor
Author
|
Thank you for the review @LucaCappelletti94 |
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
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.
Which issue does this PR close?
N/A — dependency maintenance.
Rationale for this change
Keep dependencies current.
What changes are included in this PR?
synfrom2.0to3.0inderive/Cargo.tomlIs this a breaking API change?
No —
syndoes not appear in the public API.sqlparser_deriveis a proc-macro crateAre these changes tested?
By CI
Are there any user-facing changes?
No user-facing API changes. Downstream crates that enable the
visitororderive-dialectfeatures will buildsyn3.0 instead of 2.0 once a newsqlparser_deriveis published.