chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.4.27 #3322
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.
This PR contains the following updates:
0.4.25
->0.4.27
0.4.25
->0.4.27
Release Notes
astral-sh/uv (ghcr.io/astral-sh/uv)
v0.4.27
Compare Source
This release includes support for the
[dependency-groups]
table as recently standardized in PEP 735. The table allows for declaration of optional dependency groups that are not published as part of the package metadata, unlike[project.optional-dependencies]
. There are new--group
,--only-group
, and--no-group
options throughout the uv interface.Previously, uv used a single
tool.uv.dev-dependencies
list for declaration of development dependencies. Now, uv supports declaring development dependencies in a standardized format and allows splitting development dependencies into multiple groups.For compatibility, and to simplify usage for people that do not need multiple groups, uv special-cases the group named
dev
. Thedev
group is equivalent totool.uv.dev-dependencies
. The contents oftool.uv.dev-dependencies
will merged into thedev
group in uv's resolver. The--dev
,--only-dev
, and--no-dev
flags remain as aliases for the corresponding--group
options. Support fortool.uv.dev-dependencies
remains in this release, but will display warnings in a future release.uv syncs the
dev
group by default — this matches the exististing behavior fortool.uv.dev-dependencies
. The default groups can be changed with thetool.uv.default-groups
setting.Thank you to Stephen Rosen who authored PEP 735.
Enhancements
--dry-run
mode inuv lock
(#7783)Bug fixes
uv tree
(#8532)lto
overdebug
free-threaded managed Python builds (#8515)Documentation
tool.uv.sources
to the "Settings" reference (#8543)uv build
anduv publish
in the landing pages (#8542)[tool.uv]
header in TOML examples (#8545).netrc
environment variable and path (#8511).netrc
typo in authentication docs (#8521)--publish-url
to avoid duplication. (#8561)--strict
flag (#8513)v0.4.26
Compare Source
Enhancements
uv python install --reinstall
(#8487)uv.toml
configuration (#7851)Bug fixes
requires-python
narrowing with upper bounds (#8403)[[tool.uv.index]]
entries when credentials are provided (#8502)uv add
comment handling for empty arrays (#8504)--allow-insecure-host
inuv publish
(#8440)--package
includes inuv tree
(#8507)uv python install
(#8485)Documentation
[tool.uv.dependency-metadata]
(#8484)cache-keys
typo intags = true
(#8422)Error messages
--from
command when executable is available foruvx
(#8473)--with-editable
inuv tool install
(#8472)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.