Serialize dependency constraints in lock entries - #1220
Merged
Conversation
ericmj
force-pushed
the
serialize-any-requirement
branch
from
August 4, 2026 20:04
81d80da to
e94c6fa
Compare
ericmj
marked this pull request as ready for review
August 4, 2026 20:20
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.
Use the explicit solver requirement serializer when converting registry dependencies to lock tuples and legacy Mix dependency tuples. This prevents presentational
anyandemptystrings from being persisted and adds regression coverage for both serialization boundaries.Depends on hexpm/hex_solver#44.
Related to hexpm/hex_solver#43.