Update charmcraft.yaml build tools

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Update
poetry (changelog)	2.0.1 -> 2.1.1					minor
rust-lang/rust	1.84.1 -> 1.85.0					minor
uv (source, changelog)	0.5.30 -> 0.6.2					minor

---

Release Notes

python-poetry/poetry (poetry)

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

• Make build command build-system agnostic (#​10059,
  #​10092).
• Add a --config-settings option to poetry build (#​10059).
• Add support for defining config-settings when building dependencies (#​10129).
• Add (experimental) commands to manage Python installations (#​10112).
• Use findpython to find the Python interpreters (#​10097).
• Add a --no-truncate option to poetry show (#​9580).
• Re-add support for passwords with empty usernames (#​10088).
• Add better error messages (#​10053,
  #​10065,
  #​10126,
  #​10127,
  #​10132).

Changed

• poetry new defaults to "src" layout by default (#​10135).
• Improve performance of locking dependencies (#​10111,
  #​10114,
  #​10138,
  #​10146).
• Deprecate adding sources without specifying --priority (#​10134).

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).

rust-lang/rust (rust-lang/rust)

v1.85.0

Compare Source

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

Language

• The 2024 Edition is now stable.
  See the edition guide for more details.
• Stabilize async closures
  See RFC 3668 for more details.
• Stabilize #[diagnostic::do_not_recommend]
• Add unpredictable_function_pointer_comparisons lint to warn against function pointer comparisons
• Lint on combining #[no_mangle] and #[export_name] attributes.

Compiler

• The unstable flag -Zpolymorphize has been removed, see https://github.com/rust-lang/compiler-team/issues/810 for some background.

Platform Support

• Promote powerpc64le-unknown-linux-musl to tier 2 with host tools

Refer to Rust's [platform support page][platform-support-doc]
for more information on Rust's tiered platform support.

Libraries

• Panics in the standard library now have a leading library/ in their path

• std::env::home_dir() on Windows now ignores the non-standard $HOME environment variable

  It will be un-deprecated in a subsequent release.

• Add AsyncFn* to the prelude in all editions.

Stabilized APIs

• BuildHasherDefault::new
• ptr::fn_addr_eq
• io::ErrorKind::QuotaExceeded
• io::ErrorKind::CrossesDevices
• {float}::midpoint
• Unsigned {integer}::midpoint
• NonZeroU*::midpoint
• impl std::iter::Extend for tuples with arity 1 through 12
• FromIterator<(A, ...)> for tuples with arity 1 through 12
• std::task::Waker::noop

These APIs are now stable in const contexts:

• mem::size_of_val
• mem::align_of_val
• Layout::for_value
• Layout::align_to
• Layout::pad_to_align
• Layout::extend
• Layout::array
• std::mem::swap
• std::ptr::swap
• NonNull::new
• HashMap::with_hasher
• HashSet::with_hasher
• BuildHasherDefault::new
• <float>::recip
• <float>::to_degrees
• <float>::to_radians
• <float>::max
• <float>::min
• <float>::clamp
• <float>::abs
• <float>::signum
• <float>::copysign
• MaybeUninit::write

Cargo

• Add future-incompatibility warning against keywords in cfgs and add raw-idents
• Stabilize higher precedence trailing flags
• Pass CARGO_CFG_FEATURE to build scripts

Rustdoc

• Doc comment on impl blocks shows the first line, even when the impl block is collapsed

Compatibility Notes

• rustc no longer treats the test cfg as a well known check-cfg, instead it is up to the build systems and users of --check-cfg[^check-cfg] to set it as a well known cfg using --check-cfg=cfg(test).

  This is done to enable build systems like Cargo to set it conditionally, as not all source files are suitable for unit tests.
  Cargo (for now) unconditionally sets the test cfg as a well known cfg.
  [^check-cfg]: https://doc.rust-lang.org/nightly/rustc/check-cfg.html

• Disable potentially incorrect type inference if there are trivial and non-trivial where-clauses

• std::env::home_dir() has been deprecated for years, because it can give surprising results in some Windows configurations if the HOME environment variable is set (which is not the normal configuration on Windows). We had previously avoided changing its behavior, out of concern for compatibility with code depending on this non-standard configuration. Given how long this function has been deprecated, we're now fixing its behavior as a bugfix. A subsequent release will remove the deprecation for this function.

• Make core::ffi::c_char signedness more closely match that of the platform-default char

  This changed c_char from an i8 to u8 or vice versa on many Tier 2 and 3
  targets (mostly Arm and RISC-V embedded targets). The new definition may
  result in compilation failures but fixes compatibility issues with C.

  The libc crate matches this change as of its 0.2.169 release.

• When compiling a nested macro_rules macro from an external crate, the content of the inner macro_rules is now built with the edition of the external crate, not the local crate.

• Increase sparcv9-sun-solaris and x86_64-pc-solaris Solaris baseline to 11.4.

• Show abi_unsupported_vector_types lint in future breakage reports

• Error if multiple super-trait instantiations of dyn Trait need associated types to be specified but only one is provided

• Change powerpc64-ibm-aix default codemodel to large

Internal Changes

These changes do not affect any public interfaces of Rust, but they represent
significant improvements to the performance or internals of rustc and related
tools.

• Build x86_64-unknown-linux-gnu with LTO for C/C++ code (e.g., jemalloc)

astral-sh/uv (uv)

v0.6.2

Compare Source

Enhancements

• Add support for constraining build dependencies with tool.uv.build-constraint-dependencies (#​11585)
• Sort dependency group keys when adding new group (#​11591)

Performance

• Use an Arc for index URLs (#​11586)

Bug fixes

• Allow use of x86-64 Python on ARM Windows (#​11625)
• Fix an issue where conflict markers could instigate a very large lock file (#​11293)
• Fix duplicate packages with multiple conflicting extras declared (#​11513)
• Respect color settings for log messages (#​11604)
• Eagerly reject unsupported Git schemes (#​11514)

Documentation

• Add documentation for specifying Python versions in tool commands (#​11598)

v0.6.1

Compare Source

Enhancements

• Allow users to mark platforms as "required" for wheel coverage (#​10067)
• Warn for builds in non-build and workspace root pyproject.toml (#​11394)

Bug fixes

• Add --all to uvx --reinstall message (#​11535)
• Fallback to GET on HTTP 400 when attempting to use range requests for wheel download (#​11539)
• Prefer local variants in preference selection (#​11546)
• Respect verbatim executable name in uvx (#​11524)

Documentation

• Add documentation for required environments (#​11542)
• Note that main.py used to be hello.py (#​11519)

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)

Documentation

• The CHANGELOG.md is now split into separate files for each "major" version to fix rendering (#​11510)

v0.5.31

Compare Source

Release Notes

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:

• CPython 3.14.0a5, which includes a new tail calling interpreter for a significant performance improvement
• The bundled OpenSSL version was updated from 3.0.15 to 3.0.16 which fixes a security advisory

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)

Install uv 0.5.31

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.5.31/uv-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.5.31/uv-installer.ps1 | iex"

Download uv 0.5.31

File	Platform	Checksum
uv-aarch64-apple-darwin.tar.gz	Apple Silicon macOS	checksum
uv-x86_64-apple-darwin.tar.gz	Intel macOS	checksum
uv-aarch64-pc-windows-msvc.zip	ARM64 Windows	checksum
uv-i686-pc-windows-msvc.zip	x86 Windows	checksum
uv-x86_64-pc-windows-msvc.zip	x64 Windows	checksum
uv-aarch64-unknown-linux-gnu.tar.gz	ARM64 Linux	checksum
uv-i686-unknown-linux-gnu.tar.gz	x86 Linux	checksum
uv-powerpc64-unknown-linux-gnu.tar.gz	PPC64 Linux	checksum
uv-powerpc64le-unknown-linux-gnu.tar.gz	PPC64LE Linux	checksum
uv-s390x-unknown-linux-gnu.tar.gz	S390x Linux	checksum
uv-x86_64-unknown-linux-gnu.tar.gz	x64 Linux	checksum
uv-armv7-unknown-linux-gnueabihf.tar.gz	ARMv7 Linux	checksum
uv-aarch64-unknown-linux-musl.tar.gz	ARM64 MUSL Linux	checksum
uv-i686-unknown-linux-musl.tar.gz	x86 MUSL Linux	checksum
uv-x86_64-unknown-linux-musl.tar.gz	x64 MUSL Linux	checksum
uv-arm-unknown-linux-musleabihf.tar.gz	ARMv6 MUSL Linux (Hardfloat)	checksum
uv-armv7-unknown-linux-musleabihf.tar.gz	ARMv7 MUSL Linux	checksum

---

Configuration

📅 Schedule: Branch creation - "after 1am and before 3am every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.95%. Comparing base (32d33d4) to head (f1063fc).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #768   +/-   ##
=======================================
  Coverage   71.95%   71.95%           
=======================================
  Files          15       15           
  Lines        3476     3476           
  Branches      532      532           
=======================================
  Hits         2501     2501           
  Misses        846      846           
  Partials      129      129           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.