Skip to content

Release 0.17.3#3417

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release/v0.17.3
Open

Release 0.17.3#3417
github-actions[bot] wants to merge 1 commit into
mainfrom
release/v0.17.3

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Release PR for 0.17.3.

The release readiness report will be prepared manually.

@github-actions github-actions Bot added this to the 0.17.x milestone May 15, 2026
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread uv.lock
Comment on lines +12 to +13
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"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants