Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Update
poetry (changelog) 2.0.02.3.2 age confidence minor
poetry-plugin-export 1.8.01.10.0 age confidence minor
rust-lang/rust 1.92.01.93.0 age confidence minor
uv (source, changelog) 0.5.150.10.0 age confidence minor

Release Notes

python-poetry/poetry (poetry)

v2.3.2

Compare Source

Changed
poetry-core (2.3.1)
  • Fix an issue where platform_release could not be parsed on Windows Server (#​911).

v2.3.1

Compare Source

Fixed
  • Fix an issue where cached information about each package was always considered outdated (#​10699).
Docs
  • Document SHELL_VERBOSITY environment variable (#​10678).

v2.3.0

Compare Source

Added
  • Add support for exporting pylock.toml files with poetry-plugin-export (#​10677).
  • Add support for specifying build constraints for dependencies (#​10388).
  • Add support for publishing artifacts whose version is determined dynamically by the build-backend (#​10644).
  • Add support for editable project plugins (#​10661).
  • Check requires-poetry before any other validation (#​10593).
  • Validate the content of project.readme when running poetry check (#​10604).
  • Add the option to clear all caches by making the cache name in poetry cache clear optional (#​10627).
  • Automatically update the cache for packages where the locked files differ from cached files (#​10657).
  • Suggest to clear the cache if running a command with --no-cache solves an issue (#​10585).
  • Propose poetry init when trying poetry new for an existing directory (#​10563).
  • Add support for poetry publish --skip-existing for new Nexus OSS versions (#​10603).
  • Show Poetry's own Python's path in poetry debug info (#​10588).
Changed
  • Drop support for Python 3.9 (#​10634).
  • Change the default of installer.re-resolve from true to false (#​10622).
  • PEP 735 dependency groups are considered in the lock file hash (#​10621).
  • Deprecate poetry.utils._compat.metadata, which is sometimes used in plugins, in favor of importlib.metadata (#​10634).
  • Improve managing free-threaded Python versions with poetry python (#​10606).
  • Prefer JSON API to HTML API in legacy repositories (#​10672).
  • When running poetry init, only add the readme field in the pyproject.toml if the readme file exists (#​10679).
  • Raise an error if no hash can be determined for any distribution link of a package (#​10673).
  • Require dulwich>=0.25.0 (#​10674).
Fixed
  • Fix an issue where poetry remove did not work for PEP 735 dependency groups with include-group items (#​10587).
  • Fix an issue where poetry remove caused dangling include-group references in PEP 735 dependency groups (#​10590).
  • Fix an issue where poetry add did not work for PEP 735 dependency groups with include-group items (#​10636).
  • Fix an issue where PEP 735 dependency groups were not considered in the lock file hash (#​10621).
  • Fix an issue where wrong markers were locked for a dependency that was required by several groups with different markers (#​10613).
  • Fix an issue where non-deterministic markers were created in a method used by poetry-plugin-export (#​10667).
  • Fix an issue where wrong wheels were chosen for installation in free-threaded Python environments if Poetry itself was not installed with free-threaded Python (#​10614).
  • Fix an issue where poetry publish used the metadata of the project instead of the metadata of the build artifact (#​10624).
  • Fix an issue where poetry env use just used another Python version instead of failing when the requested version was not supported by the project (#​10685).
  • Fix an issue where poetry env activate returned the wrong command for dash (#​10696).
  • Fix an issue where data-dir and python.installation-dir could not be set (#​10595).
  • Fix an issue where Python and pip executables were not correctly detected on Windows (#​10645).
  • Fix an issue where invalid template variables in virtualenvs.prompt caused an incomprehensible error message (#​10648).
Docs
  • Add a warning about ~/.netrc for Poetry credential configuration (#​10630).
  • Clarify that the local configuration takes precedence over the global configuration (#​10676).
  • Add an explanation in which cases packages are automatically detected (#​10680).
poetry-core (2.3.0)
  • Normalize versions (#​893).
  • Fix an issue where unsatisfiable requirements did not raise an error (#​891).
  • Fix an issue where the implicit main group did not exist if it was explicitly declared as not having any dependencies (#​892).
  • Fix an issue where python_full_version markers with pre-release versions were parsed incorrectly (#​893).

v2.2.1

Compare Source

Fixed
  • Fix an issue where poetry self show failed with a message about an invalid output format (#​10560).
Docs
  • Remove outdated statements about dependency groups (#​10561).
poetry-core (2.2.1)
  • Fix an issue where it was not possible to declare a PEP 735 dependency group as optional (#​888).

v2.2.0

Compare Source

Added
  • Add support for nesting dependency groups (#​10166).
  • Add support for PEP 735 dependency groups (#​10130).
  • Add support for PEP 639 license clarity (#​10413).
  • Add a --format option to poetry show to alternatively output json format (#​10487).
  • Add official support for Python 3.14 (#​10514).
Changed
  • Normalize dependency group names (#​10387).
  • Change installer.no-binary and installer.only-binary so that explicit package names will take precedence over :all: (#​10278).
  • Improve log output during poetry install when a wheel is built from source (#​10404).
  • Improve error message in case a file lock could not be acquired while cloning a git repository (#​10535).
  • Require dulwich>=0.24.0 (#​10492).
  • Allow virtualenv>=20.33 again (#​10506).
  • Allow findpython>=0.7 (#​10510).
  • Allow importlib-metadata>=8.7 (#​10511).
Fixed
  • Fix an issue where poetry new did not create the project structure in an existing empty directory (#​10431).
  • Fix an issue where a dependency that was required for a specific Python version was not installed into an environment of a pre-release Python version (#​10516).
poetry-core (2.2.0)
  • Deprecate table values and values that are not valid SPDX expressions for [project.license] (#​870).
  • Fix an issue where explicitly included files that are in .gitignore were not included in the distribution (#​874).
  • Fix an issue where marker operations could result in invalid markers (#​875).

v2.1.4

Compare Source

Changed
  • Require virtualenv<20.33 to work around an issue where Poetry uses the wrong Python version (#​10491).
  • Improve the error messages for the validation of the pyproject.toml file (#​10471).
Fixed
  • Fix an issue where project plugins were installed even though poetry install was called with --no-plugins (#​10405).
  • Fix an issue where dependency resolution failed for self-referential extras with duplicate dependencies (#​10488).
Docs
  • Clarify how to include files that were automatically excluded via VCS ignore settings (#​10442).
  • Clarify the behavior of poetry add if no version constraint is explicitly specified (#​10445).

v2.1.3

Compare Source

Changed
  • Require importlib-metadata<8.7 for Python 3.9 because of a breaking change in importlib-metadata 8.7 (#​10374).
Fixed
  • Fix an issue where re-locking failed for incomplete multiple-constraints dependencies with explicit sources (#​10324).
  • Fix an issue where the --directory option did not work if a plugin, which accesses the poetry instance during its activation, was installed (#​10352).
  • Fix an issue where poetry env activate -v printed additional information to stdout instead of stderr so that the output could not be used as designed (#​10353).
  • Fix an issue where the original error was not printed if building a git dependency failed (#​10366).
  • Fix an issue where wheels for the wrong platform were installed in rare cases. (#​10361).
poetry-core (2.1.3)
  • Fix an issue where the union of specific inverse or partially inverse markers was not simplified (#​858).
  • Fix an issue where optional dependencies defined in the project section were treated as non-optional when a source was defined for them in the tool.poetry section (#​857).
  • Fix an issue where markers with === were not parsed correctly (#​860).
  • Fix an issue where local versions with upper case letters caused an error (#​859).
  • Fix an issue where extra markers with a value starting with "in" were not validated correctly (#​862).

v2.1.2

Compare Source

Changed
  • Improve performance of locking dependencies (#​10275).
Fixed
  • Fix an issue where markers were not locked correctly (#​10240).
  • Fix an issue where the result of poetry lock was not deterministic (#​10276).
  • Fix an issue where poetry env activate returned the wrong command for tcsh (#​10243).
  • Fix an issue where poetry env activate returned the wrong command for pwsh on Linux (#​10256).
Docs
  • Update basic usage section to reflect new default layout (#​10203).
poetry-core (2.1.2)
  • Improve performance of marker operations (#​851).
  • Fix an issue where incorrect markers were calculated when removing parts covered by the project's Python constraint (#​841,
    #​846).
  • Fix an issue where extra markers were not simplified (#​842,
    #​845,
    #​847).
  • Fix an issue where the intersection and union of markers was not deterministic (#​843).
  • Fix an issue where the intersection of python_version markers was not recognized as empty (#​849).
  • Fix an issue where python_version markers were not simplified (#​848,
    #​851).
  • Fix an issue where Python constraints on a package were converted into invalid markers (#​853).

v2.1.1

Compare Source

Fixed
  • Fix an issue where poetry env use python does not choose the Python from the PATH (#​10187).
poetry-core (2.1.1)
  • Fix an issue where simplifying a python_version marker resulted in an invalid marker (#​838).

v2.1.0

Compare Source

Added
Changed
Fixed
  • Fix an issue where global options were not handled correctly when positioned after command options (#​10021,
    #​10067,
    #​10128).
  • Fix an issue where building a dependency from source failed because of a conflict between build-system dependencies that were not required for the target environment (#​10048).
  • Fix an issue where poetry init was not able to find a package on PyPI while adding dependencies interactively (#​10055).
  • Fix an issue where the @latest descriptor was incorrectly passed to the core requirement parser (#​10069).
  • Fix an issue where Boolean environment variables set to True (in contrast to true) were interpreted as false (#​10080).
  • Fix an issue where poetry env activate reported a misleading error message (#​10087).
  • Fix an issue where adding an optional dependency with poetry add --optional would not correctly update the lock file (#​10076).
  • Fix an issue where pip was not installed/updated before other dependencies resulting in a race condition (#​10102).
  • Fix an issue where Poetry freezes when multiple threads attempt to unlock the keyring simultaneously (#​10062).
  • Fix an issue where markers with extras were not locked correctly (#​10119).
  • Fix an issue where self-referential extras were not resolved correctly (#​10106).
  • Fix an issue where Poetry could not be run from a zipapp (#​10074).
  • Fix an issue where installation failed with a permission error when using the system environment as a user without write access to system site packages (#​9014).
  • Fix an issue where a version of a dependency that is not compatible with the project's python constraint was locked. (#​10141).
  • Fix an issue where Poetry wrongly reported that the current project's supported Python range is not compatible with some of the required packages Python requirement (#​10157).
  • Fix an issue where the requested extras of a dependency were ignored if the same dependency (with same extras) was specified in multiple groups (#​10158).
Docs
  • Sort commands by name in the CLI reference (#​10035).
  • Add missing documentation for env commands (#​10027).
  • Clarify that the name and version fields are always required if the project section is specified (#​10033).
  • Add a note about restarting the shell for tab completion changes to take effect (#​10070).
  • Fix the example for project.gui-scripts #​10121.
  • Explain how to include files as scripts in the project configuration (#​9572,
    #​10133).
  • Add additional information on specifying required python versions (#​10104).
poetry-core (2.1.0)
  • Fix an issue where inclusive ordering with post releases was inconsistent with PEP 440 (#​379).
  • Fix an issue where invalid URI tokens in PEP 508 requirement strings were silently discarded (#​817).
  • Fix an issue where wrong markers were calculated when removing parts covered by the project's python constraint (#​824).
  • Fix an issue where optional dependencies that are not part of an extra were included in the wheel metadata (#​830).
  • Fix an issue where the __pycache__ directory and *.pyc files were included in sdists and wheels (#​835).

v2.0.1

Compare Source

Added
  • Add support for poetry search in legacy sources (#​9949).
  • Add a message in the poetry source show output when PyPI is implicitly enabled (#​9974).
Changed
  • Improve performance for merging markers from overrides at the end of dependency resolution (#​10018).
Fixed
  • Fix an issue where poetry sync did not remove packages that were not requested (#​9946).
  • Fix an issue where poetry check failed even though there were just warnings and add a --strict option to fail on warnings (#​9983).
  • Fix an issue where poetry update, poetry add and poetry remove with --only uninstalled packages from other groups (#​10014).
  • Fix an issue where poetry update, poetry add and poetry remove uninstalled all extra packages (#​10016).
  • Fix an issue where poetry self update did not recognize Poetry's own environment (#​9995).
  • Fix an issue where read-only system site-packages were not considered when loading an environment with system site-packages (#​9942).
  • Fix an issue where an error message in poetry install started with Warning: instead of Error: (#​9945).
  • Fix an issue where Command.set_poetry, which is used by plugins, was removed (#​9981).
  • Fix an issue where the help text of poetry build --clean showed a malformed short option instead of the description (#​9994).
Docs
  • Add a FAQ entry for the migration from Poetry-specific fields to the project section (#​9996).
  • Fix examples for project.readme and project.urls (#​9948).
  • Add a warning that package sources are a Poetry-specific feature that is not included in core metadata (#​9935).
  • Replace poetry install --sync with poetry sync in the section about synchronizing dependencies (#​9944).
  • Replace poetry shell with poetry env activate in the basic usage section (#​9963).
  • Mention that project.name is always required when the project section is used (#​9989).
  • Fix the constraint of poetry-plugin-export in the section about poetry export (#​9954).
poetry-core (2.0.1)
  • Replace the deprecated core metadata field Home-page with Project-URL: Homepage (#​807).
  • Fix an issue where includes from tool.poetry.packages without a specified format were not initialized with the default value resulting in a KeyError (#​805).
  • Fix an issue where some project.urls entries were not processed correctly resulting in a KeyError (#​807).
  • Fix an issue where dynamic project.dependencies via tool.poetry.dependencies were ignored if project.optional-dependencies were defined (#​811).
python-poetry/poetry-plugin-export (poetry-plugin-export)

v1.10.0

Compare Source

Added
  • Add support for exporting pylock.toml files (#​357).
Changed
  • Drop support for Python 3.9 (#​349).
Fixed
  • Fix an issue where a "dependency walk failed" error message gave an outdated advice (#​353).

v1.9.0

Compare Source

Added
  • Add an --all-groups option to export dependencies from all groups (#​294).
Changed
  • Drop support for Python 3.8 (#​300).
  • Clarify the help text of --with and --only and deprecate --without (#​212).
  • Fail if the poetry.lock file is not consistent with the pyproject.toml file (#​310).
Fixed
  • Fix an issue where the export failed with the message "dependency walk failed".
    This fix requires a poetry.lock file created with Poetry 2.x (#​286).
  • Fix an issue where the pre-commit hook regex matched wrong files (#​285).
rust-lang/rust (rust-lang/rust)

v1.93.0

Compare Source

==========================

Language

Compiler

Platform Support

Refer to Rust's platform support page
for more information on Rust's tiered platform support.

Libraries

Stabilized APIs

Cargo

Rustdoc

Compatibility Notes

astral-sh/uv (uv)

v0.10.0

Compare Source

Since we released uv 0.9.0 in October of 2025, 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.

This release also includes the stabilization of preview features. Python upgrades are now stable, including the uv python upgrade command, uv python install --upgrade, and automatically upgrading Python patch versions in virtual environments when a new version is installed. The add-bounds and extra-build-dependencies settings are now stable. Finally, the uv workspace dir and uv workspace list utilities for writing scripts against workspace members are now stable.

Breaking changes
  • Require --clear to remove existing virtual environments in uv venv (#​17757)

    Previously, uv venv would prompt for confirmation before removing an existing virtual environment in interactive contexts, and remove it without confirmation in non-interactive contexts. Now, uv venv requires the --clear flag to remove an existing virtual environment. A warning for this change was added in uv 0.8.

    You can opt out of this behavior by passing the --clear flag or setting UV_VENV_CLEAR=1.

  • Error if multiple indexes include default = true (#​17011)

    Previously, uv would silently accept multiple indexes with default = true and use the first one. Now, uv will error if multiple indexes are marked as the default.

    You cannot opt out of this behavior. Remove default = true from all but one index.

  • Error when an explicit index is unnamed (#​17777)

    Explicit indexes can only be used via the [tool.uv.sources] table, which requires referencing the index by name. Previously, uv would silently accept unnamed explicit indexes, which could never be referenced. Now, uv will error if an explicit index does not have a name.

    You cannot opt out of this behavior. Add a name to the explicit index or remove the entry.

  • Install alternative Python executables using their implementation name (#​17756, #​17760)

    Previously, uv python install would install PyPy, GraalPy, and Pyodide executables with names like python3.10 into the bin directory. Now, these executables will be named using their implementation name, e.g., pypy3.10, graalpy3.10, and pyodide3.12, to avoid conflicting with CPython installations.

    You cannot opt out of this behavior.

  • Respect global Python version pins in uv tool run and uv tool install (#​14112)

    Previously, uv tool run and uv tool install did not respect the global Python version pin (set via uv python pin --global). Now, these commands will use the global Python version when no explicit version is requested.

    For uv tool install, if the tool is already installed, the Python version will not change unless --reinstall or --python is provided. If the tool was previously installed with an explicit --python flag, the global pin will not override it.

    You can opt out of this behavior by providing an explicit --python flag.

  • Remove Debian Bookworm, Alpine 3.21, and Python 3.8 Docker images (#​17755)

    The Debian Bookworm and Alpine 3.21 images were replaced by Debian Trixie and Alpine 3.22 as defaults in uv 0.9. These older images are now removed. Python 3.8 images are also removed, as Python 3.8 is no longer supported in the Trixie or Alpine base images.

    The following image tags are no longer published:

    • uv:bookworm, uv:bookworm-slim
    • uv:alpine3.21
    • uv:python3.8-*

    Use uv:debian or uv:trixie instead of uv:bookworm, uv:alpine or uv:alpine3.22 instead of uv:alpine3.21, and a newer Python version instead of uv:python3.8-*.

  • Drop PPC64 (big endian) builds (#​17626)

    uv no longer provides pre-built binaries for PPC64 (big endian). This platform appears to be largely unused and is only supported on a single manylinux version. PPC64LE (little endian) builds are unaffected.

    Building uv from source is still supported for this platform.

  • Skip generating activate.csh for relocatable virtual environments (#​17759)

    Previously, uv venv --relocatable would generate an activate.csh script that contained hardcoded paths, making it incompatible with relocation. Now, the activate.csh script is not generated for relocatable virtual environments.

    You cannot opt out of this behavior.

  • Require username when multiple credentials match a URL (#​16983)

    When using uv auth login to store credentials, you can register multiple username and password combinations for the same host. Previously, when uv needed to authenticate and multiple credentials matched the URL (e.g., when retrieving a token with uv auth token), uv would pick the first match. Now, uv will error instead.

    You cannot opt out of this behavior. Include the username in the request, e.g., uv auth token --username foo example.com.

  • Avoid invalidating the lockfile versions after an exclude-newer change (#​17721)

    Previously, changing the exclude-newer setting would cause package versions to be upgraded, ignoring the lockfile entirely. Now, uv will only change package versions if they are no longer within the exclude-newer range.

    You can restore the previous behavior by using --upgrade or --upgrade-package to opt-in to package version changes.

  • Upgrade uv format to Ruff 0.15.0 (#​17838)

    uv format now uses Ruff 0.15.0, which uses the 2026 style guide. See the blog post for details.

    The formatting of code is likely to change. You can opt out of this behavior by requesting an older Ruff version, e.g., uv format --version 0.14.14.

  • Update uv crate test features to use test- as a prefix (#​17860)

    This change only affects redistributors of uv. The Cargo features used to gate test dependencies, e.g., pypi, have been renamed with a test- prefix for clarity, e.g., test-pypi.

Stabilizations
  • uv python upgrade and uv python install --upgrade (#​17766)

    When installing Python versions, an intermediary directory without the patch version attached will be created, and virtual environments will be transparently upgraded to new patch versions.

    See the Python version documentation for more details.

  • uv add --bounds and the add-bounds configuration option (#​17660)

    This does not come with any behavior changes. You will no longer see an experimental warning when using uv add --bounds or add-bounds in configuration.

  • uv workspace list and uv workspace dir (#​17768)

    This does not come with any behavior changes. You will no longer see an experimental warning when using these commands.

  • extra-build-dependencies (#​17767)

    This does not come with any behavior changes. You will no longer see an experimental warning when using extra-build-dependencies in configuration.

Enhancements
  • Improve ABI tag error message phrasing (#​17878)
  • Introduce a 10s connect timeout (#​17733)
  • Allow using pyx.dev as a target in uv auth commands despite PYX_API_URL differing (#​17856)
Bug fixes
  • Support all CPython ABI tag suffixes properly (#​17817)
  • Add support for detecting PowerShell on Linux and macOS (#​17870)
  • Retry timeout errors for streams (#​17875)

v0.9.30

Compare Source

Released on 2026-02-04.

Python
Enhancements
  • Allow comma-separated values for --extra option (#​17525)
  • Check all files during a dry-run publish instead of stopping at the first failure (#​17785)
  • Clarify UV_HTTP_TIMEOUT error message (#​17493)
Preview features
  • Use relocatable virtual environments by default (#​17770)
Bug fixes
  • Fix deadlock on token refresh in uv publish when using pyx (#​17832)
  • Ignore global Python pins when incompatible with project (#​15473)

v0.9.29

Compare Source

Released on 2026-02-03.

Python
Enhancements
  • Add wheel-tag-style aliases for manylinux platform names (#​17750)
  • Hint on uv version --bump dev similar to pre-release bumps (#​17796)
  • Improve display of RFC 9457 Problem Detail responses in uv publish server errors (#​17787)
  • Improve the wording of publish errors during dry-run (#​17782)
  • Set backoff to 10 retries (#​17816)
  • Add properties to synthentic and project roots in Cyclone DX exports (#​17820)
  • Identify the invidividual clients in uv publish trace logs (#​17784)
Preview features
  • Remove special casing for base and default conda environment names (#​17758)
Bug fixes
  • Fix PYTHONHOME inheritance when spawning different Python versions (#​17821)
  • Fix wheel rejections on freethreading+debug builds (#​17812)
  • Pad with zeros during comparisons in EqualStar and NotEqualStar operators (#​17751)
  • Reject unknown field names in conflict declarations (#​17727)
  • Fix panics in system-configuration in sandboxes (#​17829)
Documentation
  • Update pip pre-release compatibility information (#​17788)
Security
  • Hide a subset of environment variable values in --help (#​17745)

v0.9.28

Compare Source

Released on 2026-01-29.

Python
Enhancements
  • Add support for Pyodide interpreter on Windows (#​17658)

@renovate renovate bot added the not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes label Jan 20, 2026
@renovate renovate bot force-pushed the renovate/charmcraft.yaml-build-tools branch from 4276a84 to 1ed5b0f Compare January 27, 2026 02:07
@renovate renovate bot force-pushed the renovate/charmcraft.yaml-build-tools branch from 1ed5b0f to 80a7346 Compare February 3, 2026 02:16
@renovate renovate bot force-pushed the renovate/charmcraft.yaml-build-tools branch from 80a7346 to 8cbca2c Compare February 10, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

not bug or enhancement PR is not 'bug' or 'enhancement'. For release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants