Retain old python-build-standalone releases #8216
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
zanieb
force-pushed
the
zb/fix-old-dists
branch
from
b869d97
to
fd2bb9f
Compare
zanieb
force-pushed
the
zb/fix-old-dists
branch
from
fd2bb9f
to
e93c1fa
Compare
|
Struggling to validate that the changes here are "correct" |
Two things from my point of view: One, there is a strong use case for pinning against a patch version of Python, I have seen plenty of times where patch versions of Python breaks code, so I want to be able to control when a patch version is updated and test against it carefully. Two, I would not expect a tool that installs my Python versions to ever make certain versions unavailable without announcing it as a big breaking change. This will be particularly important for large organizations, but if I have an internal app running against Python 3.7.9, and everything is pinned, I would not expect that to suddenly not work even if that app is still running against that version of Python in 10 years. |
Definitely agree — this was an unintentionally removal due to the peculiarities of these old artifacts. Of course, this still works fine if you're using an old version of uv (and I think if you're going to be pinning and using things 10 years out you'll want to pin that!) |
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [astral-sh/uv](https://github.com/astral-sh/uv) | patch | `0.4.21` -> `0.4.22` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (astral-sh/uv)</summary> ### [`v0.4.22`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0422) [Compare Source](astral-sh/uv@0.4.21...0.4.22) ##### Enhancements - Respect `[tool.uv.sources]` in build requirements ([#​7172](astral-sh/uv#7172)) ##### Preview features - Add a dedicated `uv publish` error message for missing usernames ([#​8045](astral-sh/uv#8045)) - Support interactive input in `uv publish` ([#​8158](astral-sh/uv#8158)) - Use raw filenames in `uv publish` ([#​8204](astral-sh/uv#8204)) ##### Performance - Reuse the result of `which git` ([#​8224](astral-sh/uv#8224)) ##### Bug fixes - Avoid environment check optimization for `uv pip install --exact` ([#​8219](astral-sh/uv#8219)) - Do not use free-threaded interpreters without a free-threaded request ([#​8191](astral-sh/uv#8191)) - Don't recommend `--prerelease=allow` during build requirement resolution errors ([#​8192](astral-sh/uv#8192)) - Prefer optimized builds for free-threaded Python downloads ([#​8196](astral-sh/uv#8196)) - Retain old `python-build-standalone` releases ([#​8216](astral-sh/uv#8216)) - Run `uv build` builds in the source distribution bucket ([#​8220](astral-sh/uv#8220)) </details> --- ### 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 MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM3LjQ0MC43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJSZW5vdmF0ZSBCb3QiXX0=-->
Closes #8213
I didn't mean to remove these when updating the regular expression. Arguably, they shouldn't be used anymore, but we should make that choice with intention.