Allow exclude-newer to be missing from the lockfile when exclude-newer-span is present#19024
Merged
zanieb merged 2 commits intoastral-sh:mainfrom Apr 21, 2026
Merged
Conversation
abf2f77 to
787512d
Compare
787512d to
a1e4f70
Compare
zanieb
commented
Apr 21, 2026
zanieb
commented
Apr 21, 2026
zanieb
commented
Apr 21, 2026
zanieb
commented
Apr 21, 2026
a1e4f70 to
9560351
Compare
…ewer-span` is present
8759e5e to
dc8d7d6
Compare
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.
Following #19022 this is an incremental step towards removing
exclude-newertimestamps from lockfiles. We don't remove it here, but we ensure from this version onward, uv will not behave poorly when the value is missing. This includes substantial refactoring to better represent the desired end state in our exclude-newer types.