Skip to content
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.

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

chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.6.0 #3354

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 6, 2025

This PR contains the following updates:

Package Type Update Change
ghcr.io/astral-sh/uv final minor 0.5.28 -> 0.6.0
ghcr.io/astral-sh/uv stage minor 0.5.28 -> 0.6.0

Release Notes

astral-sh/uv (ghcr.io/astral-sh/uv)

v0.6.0

Compare Source

There have been 31 releases and 1135 pull requests since 0.5.0, our last release with breaking changes. As before, we've accumulated various changes that improve correctness and user experience, but could break some workflows. This release contains those changes; many have been marked as breaking out of an abundance of caution. We expect most users to be able to upgrade without making changes.

Breaking changes
  • Create main.py instead of hello.py in uv init (#​10369)

    Previously, uv init created a hello.py sample file. Now, uv init will create main.py instead — which aligns with expectations from user feedback. The --bare option can be used to avoid creating the file altogether.

  • Respect UV_PYTHON in uv python install (#​11487)

    Previously, uv python install did not read this environment variable; now it does. We believe this matches user expectations, however, this will take priority over .python-version files which could be considered breaking.

  • Set UV to the uv executable path (#​11326)

    When uv spawns a subprocess, it will now have the UV environment variable set to the uv binary path. This change is breaking if you are setting the UV environment variable yourself, as we will overwrite its value.

    Additionally, this change requires marking the uv Rust entrypoint (uv::main) as unsafe to avoid unsoundness — this is only relevant if you are invoking uv using Rust. See the Rust documentation for details about the safety of updating a process' environment.

  • Error on non-existent extras, e.g., in uv sync (#​11426)

    Previously, uv would silently ignore non-existent extras requested on the command-line (e.g., via uv sync --extra foo). This is generally correct behavior when resolving requests for package extras, because an extra may be present on one compatible version of a package but not another. However, this flexibility doesn't need to apply to the local project and it's less surprising to error here.

  • Error on missing dependency groups when --frozen is provided (#​11499)

    Previously, uv would not validate that the requested dependency groups were present in the lockfile when the --frozen flag was used. Now, an error will be raised if a requested dependency group is not present.

  • Change -p to a --python alias in uv pip compile (#​11486)

    In uv pip compile, -p was an alias for --python-version while everywhere else in uv's interface it is an alias for --python. Additionally, uv pip compile did not respect the UV_PYTHON environment variable. Now, the semantics of this flag have been updated for parity with the rest of the CLI.

    However, --python-version is unique: if we cannot find an interpreter with the given version, we will not fail. Instead, we'll use an alternative interpreter and override its version tags with the requested version during package resolution. This behavior is retained here for backwards compatibility, --python <version> / -p <version> will not fail if the version cannot be found. However, if a specific interpreter is requested, e.g., with --python <path> or --python pypy, and cannot be found — uv will exit with an error.

    The breaking changes here are that UV_PYTHON is respected and --python <version> will no longer fail if the version cannot be found.

  • Bump alpine default tag to 3.21 for derived Docker images (#​11157)

    Alpine 3.21 was released in Dec 2024 and is used in the official Alpine-based Python images. Our uv:python3.x-alpine images have been using 3.21 since uv v0.5.8. However, now the the uv:alpine image will use 3.21 instead of 3.20 and uv:alpine3.20 will no longer be updated.

  • Use files instead of junctions on Windows (#​11269)

    Previously, we used junctions for atomic replacement of cache entries on Windows. Now, we use a file with a pointer to the cache entry instead. This resolves various edge-case behaviors with junctions. These files are only intended to be consumed by uv and the cache version has been bumped. We do not think this change will affect workflows.

Stabilizations
  • uv publish is no longer in preview (#​11032)

    This does not come with any behavior changes. You will no longer see an experimental warning when using uv publish. See the linked pull request for a report on the stabilization.

Enhancements
  • Support --active for PEP 723 script environments (#​11433)
  • Add revision to the lockfile to allow backwards-compatible metadata changes (#​11500)
Bug fixes
  • Avoid reading metadata from .egg-info files (#​11395)
  • Include archive bucket version in archive pointers (#​11306)
  • Omit lockfile version when additional fields are dynamic (#​11468)
  • Respect executable name in uvx --from tool@latest (#​11465)

v0.5.31

Compare Source

Enhancements
  • Add uv sync --script (#​11361)
  • Allow PEP 508 requirements in tool requests (#​11337)
  • Allow source distributions to produce wheels with +local suffixes (#​11429)
  • Bring parity to uvx and uv tool install requests (#​11345)
  • Use a stable directory for local, remote, and stdin script virtual environments (#​11347, #​11364)
  • Detect infinite recursion in uv run (#​11386)
Python

The managed Python distributions have been updated, including:

See the python-build-standalone release notes for more details.

Bug fixes
  • Fix cross-drive script installation (#​11167)
  • Add indexes in priority order (#​11451)
  • Allow --python <dir> requests to match existing environments if sys.executable is the same file (#​11290)
  • Avoid comparing to system site packages in --dry-run mode (#​11427)
  • Prefer running executables in the environment with <name> over <name>/__main__.py (#​11431)
  • Retry local clones without hardlinks if they fail (#​11421)
Documentation
  • Update alternative-indexes.md to use UV_INDEX instead of UV_EXTRA_INDEX_URL (#​11381)
  • Update scripts guide to include using package indexes (#​11443)

v0.5.30

Compare Source

Python

The managed PyPy distributions have been updated for PyPy v7.3.18, which includes:

  • PyPy3.10, which updates the standard library from Python 3.10.14 to 3.10.19
  • PyPy3.11, which adds beta support for Python 3.11.11

See the PyPy release for more details.

Enhancements
  • Add uv sync --dry-run (#​11299)
  • Ignore #egg fragment in HTML Simple API response (#​11340)
Configuration
  • Add NO_BINARY and NO_BINARY_PACKAGE environment variables (#​11399)
Performance
  • Avoid re-cloning name when populating ambiguous set (#​11401)
  • Optimize flattening in large workspaces (#​11313)
Bug fixes
  • Allow dynamic packages to be overloaded (#​11400)
  • Fix credential caching for index roots when URL ends in simple/ (#​11336)
  • Fix marker merging for requirements.txt for psycopg (#​11298)
  • Set 777 permissions on locked files (#​11328)
  • Support extras in @ requests for tools (#​11335)
  • Upgrade astral-tokio-tar to v0.5.1 (#​11359)
  • Avoid missing logging for no-op upgrade events (#​11301)
  • Use refined specifiers when logging narrowed Python range (#​11334)
  • Don't use popup-generating eprintln in trampoline warnings (#​11295)
  • Patch pkg-config files to be relocatable (#​11291)
  • Fix a case of duplicate torch packages when using conflicting extras (#​11323)
Documentation
  • Add docs for uv tool install --editable (#​11280)
  • Fix broken anchors in README and docs index (#​11338)

v0.5.29

Compare Source

Enhancements
  • Add --bare option to uv init (#​11192)
  • Add support for respecting VIRTUAL_ENV in project commands via --active (#​11189)
  • Allow the project VIRTUAL_ENV warning to be silenced with --no-active (#​11251)
Python

The managed Python distributions have been updated, including:

  • CPython 3.12.9
  • CPython 3.13.2
  • pkg-config files are now relocatable

See the python-build-standalone release notes for more details.

Bug fixes
  • Always use base Python discovery logic for cached environments (#​11254)
  • Use a flock to avoid concurrent initialization of project environments (#​11259)
  • Fix handling of --all-groups and --no-default-groups flags (#​11224)
Documentation
  • Minor touchups to the Docker provenance docs (#​11252)
  • Move content from the mkdocs.public.yml into the template (#​11246)

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch from 5ba867d to 24888b4 Compare February 11, 2025 01:41
@renovate renovate bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.5.29 chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.5.30 Feb 11, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch 2 times, most recently from 07e6508 to 89d11bb Compare February 12, 2025 22:23
@renovate renovate bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.5.30 chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.5.31 Feb 12, 2025
@renovate renovate bot force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch from 89d11bb to b1465fd Compare February 14, 2025 18:59
@renovate renovate bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.5.31 chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.6.0 Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants