Update charmcraft.yaml build tools #426
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
the
not bug or enhancement
renovate
bot
requested review from
a team,
paulomach,
taurus-forever,
shayancanonical,
carlcsaposs-canonical and
sinclert-canonical
and removed request for
a team
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
carlcsaposs-canonical
approved these changes
Apr 15, 2025
taurus-forever
approved these changes
Apr 21, 2025
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/charmcraft.yaml-build-tools
branch
2 times, most recently
from
dbd66bc to
92011bb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/charmcraft.yaml-build-tools
branch
from
92011bb to
d93dc02
Compare
renovate
bot
force-pushed
the
renovate/charmcraft.yaml-build-tools
branch
from
d93dc02 to
244a94b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
25.0.1->25.1.12.1.2->2.1.30.6.13->0.7.3Release Notes
pypa/pip (pip)
v25.1.1Compare Source
v25.1Compare Source
python-poetry/poetry (poetry)
v2.1.3Compare Source
Changed
importlib-metadata<8.7for Python 3.9 because of a breaking change in importlib-metadata 8.7 (#10374).Fixed
--directoryoption did not work if a plugin, which accesses the poetry instance during its activation, was installed (#10352).poetry env activate -vprinted additional information to stdout instead of stderr so that the output could not be used as designed (#10353).poetry-core (
2.1.3)projectsection were treated as non-optional when a source was defined for them in thetool.poetrysection (#857).===were not parsed correctly (#860).extramarkers with a value starting with "in" were not validated correctly (#862).astral-sh/uv (uv)
v0.7.3Compare Source
Enhancements
--dry-runsupport touv self update(#9829)--show-withtouv tool listto list packages included by--with(#13264)fs_errfor paths in symlinking errors (#13303)Preview features
Configuration
python-downloads-json-urloption foruv.tomlto configure custom Python installations via JSON URL (#12974)Bug fixes
musllinux_1_0as a valid platform tag (#13289)uv run --with(#13283)uv run --with(#13284)--no-sync(#13287)Documentation
v0.7.2Compare Source
Enhancements
uv versionis used with project-specific flags but no project is found (#13203)Bug fixes
clangin managed Python sysconfig (#13237)--projectinuv version(#13230)v0.7.1Compare Source
Enhancement
Bugfix
v0.7.0Compare Source
This release contains various changes that improve correctness and user experience, but could break some workflows; many changes 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
Update
uv versionto display and update project versions (#12349)Previously,
uv versiondisplayed uv's version. Now,uv versionwill display or update the project's version. This interface was heavily requested and, after much consideration, we decided that transitioning the top-level command was the best option.Here's a brief example:
If used outside of a project, uv will fallback to showing its own version still:
As described in the warning,
--previewcan be used to error instead:The previous functionality of
uv versionwas moved touv self version.Avoid fallback to subsequent indexes on authentication failure (#12805)
When using the
first-indexstrategy (the default), uv will stop searching indexes for a package once it is found on a single index. Previously, uv considered a package as "missing" from an index during authentication failures, such as an HTTP 401 or HTTP 403 (normally, missing packages are represented by an HTTP 404). This behavior was motivated by unusual responses from some package indexes, but reduces the safety of uv's index strategy when authentication fails. Now, uv will consider an authentication failure as a stop-point when searching for a package across indexes. Theindex.ignore-error-codesoption can be used to recover the existing behavior, e.g.:Since PyTorch's indexes always return a HTTP 403 for missing packages, uv special-cases indexes on the
pytorch.orgdomain to ignore that error code by default.Require the command in
uvx <name>to be available in the Python environment (#11603)Previously,
uvxwould attempt to execute a command even if it was not provided by a Python package. For example, if we presumefoois an empty Python package which provides no command,uvx foowould invoke thefoocommand on thePATH(if present). Now, uv will error early if thefooexecutable is not provided by the requested Python package. This check is not enforced when--fromis used, so patterns likeuvx --from foo bash -c "..."are still valid. uv also still allowsuvx foowhere thefooexecutable is provided by a dependency offooinstead offooitself, as this is fairly common for packages which depend on a dedicated package for their command-line interface.Use index URL instead of package URL for keyring credential lookups (#12651)
When determining credentials for querying a package URL, uv previously sent the full URL to the
keyringcommand. However, some keyring plugins expect to receive the index URL (which is usually a parent of the package URL). Now, uv requests credentials for the index URL instead. This behavior matchespip.Remove
--versionfrom subcommands (#13108)Previously, uv allowed the
--versionflag on arbitrary subcommands, e.g.,uv run --version. However, the--versionflag is useful for other operations since uv is a package manager. Consequently, we've removed the--versionflag from subcommands — it is only available asuv --version.Omit Python 3.7 downloads from managed versions (#13022)
Python 3.7 is EOL and not formally supported by uv; however, Python 3.7 was previously available for download on a subset of platforms.
Reject non-PEP 751 TOML files in install, compile, and export commands (#13120, #13119)
Previously, uv treated arbitrary
.tomlfiles passed to commands (e.g.,uv pip install -r foo.tomloruv pip compile -o foo.toml) asrequirements.txt-formatted files. Now, uv will error instead. If using PEP 751 lockfiles, use the standardized format for custom names instead, e.g.,pylock.foo.toml.Ignore arbitrary Python requests in version files (#12909)
uv allows arbitrary strings to be used for Python version requests, in which they are treated as an executable name to search for in the
PATH. However, using this form of request in.python-versionfiles is non-standard and conflicts withpyenv-virtualenvwhich writes environment names to.python-versionfiles. In this release, uv will now ignore requests that are arbitrary strings when found in.python-versionfiles.Error on unknown dependency object specifiers (12811)
The
[dependency-groups]entries can include "object specifiers", e.g.set-phasers-to = ...in:However, the only current spec-compliant object specifier is
include-group. Previously, uv would ignore unknown object specifiers. Now, uv will error.Make
--frozenand--no-sourcesconflicting options (#12671)Using
--no-sourcesalways requires a new resolution and--frozenwill always fail when used with it. Now, this conflict is encoded in the CLI options for clarity.Treat empty
UV_PYTHON_INSTALL_DIRandUV_TOOL_DIRas unset (#12907, #12905)Previously, these variables were treated as set to the current working directory when set to an empty string. Now, uv will ignore these variables when empty. This matches uv's behavior for other environment variables which configure directories.
Enhancements
poetry-coreas auv initbuild backend option (#12781)pylock.toml(#13136)pyvenv.cfgversion mismatch (#13027)Bug fixes
pylock.toml(#13132)uvx --version(#13109)--no-binaryet al) inpylock.toml(#13134)upload-timerather thanupload_timeinuv.lock(#13176)Documentation
fishcompletions append>>to overwrite>(#13130)pylock.tomlmentions where relevant (#13115)v0.6.17Compare Source
Release Notes
Preview features
Bug fixes
python(#13051)requires-pythoneven if not listed on the index page (#13086)Install uv 0.6.17
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.17/uv-installer.ps1 | iex"Download uv 0.6.17
v0.6.16Compare Source
Release Notes
Bug fixes
Install uv 0.6.16
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.16/uv-installer.ps1 | iex"Download uv 0.6.16
v0.6.15Compare Source
Release Notes
This release includes preliminary support for the
pylock.tomlfile format, as standardized in PEP 751.pylock.tomlis an alternative resolution output format intended to replacerequirements.txt(e.g., in the context ofuv pip compile, whereby a "locked"requirements.txtfile is generated from a set of input requirements).pylock.tomlis standardized and tool-agnostic, such that in the future,pylock.tomlfiles generated by uv could be installed by other tools, and vice versa.As of this release,
pylock.tomlis supported in the following commands:uv.lockto thepylock.tomlformat, run:uv export -o pylock.tomlpylock.tomlfile from a set of requirements, run:uv pip compile -o pylock.toml requirements.inpylock.tomlfile, run:uv pip sync pylock.tomloruv pip install -r pylock.tomlEnhancements
uv pip compile(#13019)uv exportsupport for PEP 751 (#12955)requirements.txt(verbatim) as a format on the CLI (#12957)UV_NO_EDITABLEenvironment variable to set--no-editableon all invocations (#12773)pylock.tomltouv pip installanduv pip sync(#12992)SIGINTto child processes (#13018)uv.lock(#12968)which gitinuv init(#12893)--dry-runwith--locked/--frozenforuv sync(#12778)uv export(#12958)uv initresilient against broken git (#12895)uv run --withdependencies (#12882)uv tooland PEP723 scripts. (#12842)uvxbinary when searching for uv binary (#12923)SourceNotAllowederror message during Python discovery (#13012)Preview features
Bug fixes
config-settingswith example in docs (#12947)PythonDownloadRequestparsing for partial keys (#12925)uv-pep440(#12836)uv run(#13017)CCandCCXentries in sysconfig for cross-compiledaarch64Python distributions (#12239)UV_STACK_SIZE(#12839)uv python list(#12915)subdirectoryto Direct URL for local directories (#12971)uv python install(#12194)uv init(#12870)Documentation
uv python list --only-downloadsand--only-installed(#12916)--lockedtouv syncin GitHub Actions guide (#12819)"all"default-groupssetting documentation (#12963)--frozenwith--lockedin Docker integration guide (#12818)Install uv 0.6.15
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.15/uv-installer.ps1 | iex"Download uv 0.6.15
v0.6.14Compare Source
Release Notes
Python versions
The following Python versions have been added:
See the
python-build-standalonerelease notes for more details.Enhancements
uv-buildanduv_buildaliases touv init --build-backend(#12776)environment.ymlfiles (#12669)Preview features
Performance
Bug fixes
tool.uv.sourcesis set in system-level configuration file (#12757)uv init(#12756)Documentation
uv pip sync(#12683)uv 0.6.14
Install uv 0.6.14
Install prebuilt binaries via shell script
Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/astral-sh/uv/releases/download/0.6.14/uv-installer.ps1 | iex"Download uv 0.6.14
Configuration
📅 Schedule: Branch creation - Between 01:00 AM and 05:59 AM, only on Tuesday ( * 1-5 * * 2 ) 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.
This PR was generated by Mend Renovate. View the repository job log.