Repository navigation
PYTHON-6152 Remove exclude-newer handling from uv-lock-update action - #144
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The focused implementation and documentation consistently remove the action-level override without leaving stale references.
0 open findings
What changed in this PR
Removes the action-level uv resolution cutoff so repositories control dependency age policy through their own uv configuration.
Changes:
- Removes the
exclude_newerinput andUV_EXCLUDE_NEWERoverride. - Documents repository-level
exclude-newerconfiguration.
| File | Description |
|---|---|
python/uv-lock-update/action.yml |
Removes cutoff input and environment handling. |
python/README.md |
Documents project-owned cutoff configuration. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
GromNaN
reviewed
Oct 14, 2026
GromNaN
approved these changes
Oct 14, 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
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.
Summary
Removes the
exclude_newerinput from thepython/uv-lock-updateaction. Each project's own uv configuration now solely decides the resolution cutoff.Required for mongodb/mongo-python-driver#3114.
Motivation
The action injected the cutoff as an environment variable only while running the upgrade. Lock generation then ran under a different configuration than the one consumer CI uses to check the lock, so freshly updated locks read as stale (PYTHON-6151 in mongo-python-driver). The input's default also outranked the
exclude-newera repository sets in its ownpyproject.toml.Changes
exclude-newerin its ownpyproject.tomloruv.toml.Testing
All three
python/uv-lock-update/test_*.shscripts pass, mirroring the repo's CI test job.Breaking changes
The input is gone along with its 7-day default. A repo that relied on either must set
exclude-newerin its ownpyproject.tomloruv.tomlbefore adopting the release with this change. The only known consumer, mongo-python-driver, already sets it and drops its override in PYTHON-6153.