Skip to content

Add regression test for package cutoff ordering - #971

Closed
zaniebot wants to merge 1 commit into
mainfrom
zb/reproduce-exclude-newer-package-order
Closed

zaniebot wants to merge 1 commit into
mainfrom
zb/reproduce-exclude-newer-package-order

Conversation

@zaniebot

@zaniebot zaniebot commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Package-specific exclude-newer cutoffs are emitted in hash-map order, causing noncanonical uv.lock output. Record the current order in a focused offline lockfile snapshot. The ordering fix is tracked in #969.

@astral-automations-bot astral-automations-bot Bot added internal A refactor or improvement that is not user-facing internal:testing Internal testing of behavior labels Sep 3, 2026
@zanieb
zanieb marked this pull request as ready for review September 3, 2026 21:10
@astral-automations-bot

Copy link
Copy Markdown

Promoted to #21451.

zanieb added a commit to astral-sh/uv that referenced this pull request Sep 3, 2026
Package-specific `exclude-newer` settings use an `FxHashMap`, so their
serialized order depends on insertion history. Store them in a
`BTreeMap` instead, making lockfiles and other serialized forms
deterministic by construction.

Stacked on astral-sh#971.

Co-authored-by: Zanie Blue <contact@zanie.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal:testing Internal testing of behavior internal A refactor or improvement that is not user-facing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants