Release 0.17.3#3417
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4418c7b4d5
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| exclude-newer = "0001-01-01T00:00:00Z" # This has no effect and is included for backwards compatibility when using relative exclude-newer values. | ||
| exclude-newer-span = "P7D" |
There was a problem hiding this comment.
Keep the lockfile timestamp stable
When developers or hooks run make sync with a uv version that does not understand the relative exclude-newer setting in pyproject.toml, this new sentinel is treated as removing the previous cutoff, so uv ignores the committed lockfile and tries to re-resolve from PyPI instead of using the lock; the stop hook hit this path and failed while fetching packages. Keeping an absolute exclude-newer timestamp in the lockfile (as before) avoids turning routine sync/check commands into network-dependent relocks for those environments.
Useful? React with 👍 / 👎.
Release PR for 0.17.3.
The release readiness report will be prepared manually.