Skip to content

PYTHON-6152 Remove exclude-newer handling from uv-lock-update action #144

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
blink1073 merged 2 commits into from
Oct 15, 2026
Merged

PYTHON-6152 Remove exclude-newer handling from uv-lock-update action #144

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
50421d1
PYTHON-6152 Remove exclude-newer handling from uv-lock-update action
blink1073 Oct 9, 2026
dcf0c8e
Merge branch 'main' into PYTHON-6152
blink1073 Oct 14, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 3 additions & 16 deletions python/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,19 +158,6 @@ GitHub rejects a pull request that asks for an unknown one.
Set `dry_run: true` to log the branch and pull request the action would have
created, without pushing or opening anything.

The upgrade skips releases published within the last 7 days, so a broken or
compromised release has time to be yanked before it can land in the lock file.
Change the cutoff with `exclude_newer`, which takes anything uv's
`--exclude-newer` accepts: a date, an RFC 3339 timestamp, a duration such as
`30 days`, or `false` to upgrade to the newest releases with no cutoff at all.
It reaches uv as `UV_EXCLUDE_NEWER`, so it overrides an `exclude-newer` the
repository sets in `pyproject.toml` or `uv.toml`. Pass `exclude_newer: ""` to
leave that setting in charge instead.

```yaml
- uses: mongodb-labs/drivers-github-tools/python/uv-lock-update@v3
with:
app_id: ${{ vars.APP_ID }}
private_key: ${{ secrets.APP_PRIVATE_KEY }}
exclude_newer: 14 days
```
The action sets no resolution cutoff. A repo that wants to hold back newly
published packages configures `exclude-newer` in its own `pyproject.toml` or
`uv.toml`, exactly as for `python/setup`.
17 changes: 0 additions & 17 deletions python/uv-lock-update/action.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,13 +21,6 @@ inputs:
dry_run:
description: If 'true', report intended actions without pushing or modifying pull requests
default: "false"
exclude_newer:
Comment thread
GromNaN marked this conversation as resolved.
description: >-
Cutoff passed to uv as UV_EXCLUDE_NEWER, so the upgrade ignores releases
published after it. Accepts anything uv's --exclude-newer does: a date, an
RFC 3339 timestamp, a duration such as '30 days', or 'false' to disable the
cutoff. Pass "" to leave the cutoff to the project's own uv configuration.
default: 7 days

runs:
using: composite
Expand Down Expand Up @@ -64,17 +57,7 @@ runs:

- name: Upgrade the lock file
shell: bash
env:
EXCLUDE_NEWER: ${{ inputs.exclude_newer }}
run: |
# uv rejects an empty UV_EXCLUDE_NEWER, so an empty input unsets it
# rather than passing "" through. Unsetting also drops any the caller
# exported, so this input alone decides the cutoff.
if [ -n "$EXCLUDE_NEWER" ]; then
export UV_EXCLUDE_NEWER="$EXCLUDE_NEWER"
else
unset UV_EXCLUDE_NEWER
fi
uv lock --upgrade

- name: Commit and summarize the upgrade
Expand Down
Loading