Set custom version for vendored crates - #77
Merged
Conversation
JukkaL
approved these changes
Aug 12, 2026
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.
The internal Ruff crates that are now vendored are not versioned which potentially makes bringing
ast-serializeas a dependency to projects that already depend on the Ruff crates difficult.cargowill reject multiple sources for the same version of crates but using the Ruff crates from a different source byast-serialize, or the other way around - using the crates fromast-serializeby other packages, might not be possible because of incompatibilities between Ruff versions.To resolve this, use a custom version for the vendored crates:
0.0.0-ast-serialize.0.8.0so thatast-serializecan always be built using them even if there are other Ruff crates available in project dependencies.