chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.4 - abandoned - #12081
Open
renovate[bot] wants to merge 3 commits into
Open
renovate[bot] wants to merge 3 commits into
renovate[bot] wants to merge 3 commits into
Conversation
renovate
Bot
force-pushed
the
renovate/ghcr.io-astral-sh-uv-0.x
branch
from
August 14, 2026 00:00
9280101 to
8f89bd5
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
deepyaman
force-pushed
the
renovate/ghcr.io-astral-sh-uv-0.x
branch
6 times, most recently
from
August 14, 2026 18:45
781d42c to
cf88a70
Compare
deepyaman
force-pushed
the
renovate/ghcr.io-astral-sh-uv-0.x
branch
from
August 26, 2026 05:05
cf88a70 to
9353baa
Compare
deepyaman
approved these changes
Aug 26, 2026
The `mcr.microsoft.com/vscode/devcontainers/python:3.13` base image moved
to Debian trixie, which does not package `openjdk-17-jdk`. Every dev
container build has failed since then:
E: Unable to locate package openjdk-17-jdk
Reported in #11715, where the fix was identified but never committed.
Take `default-jdk` rather than pinning a version, as suggested by
@JonAnCla in #12029, so this does not break again the next time the base
image moves to a new Debian release.
That also keeps the JDK usable. It is only in the image for pyspark
(6af1dbf), we lock pyspark 4.0.1, and Spark 4.0 supports Java 17 and
21. `default-jdk` is openjdk-21 on trixie; openjdk-25 builds fine but
fails at runtime, since JDK 24 dropped the Security Manager that Hadoop's
UserGroupInformation relies on:
java.lang.UnsupportedOperationException: getSubject is not supported
Assisted-by: Claude Opus 5
The script is dead code: `devcontainer.json` defines only a `postStartCommand`, there is no `postCreateCommand`, and nothing else in the repo references the file. It is also stale. It reads `.tool.poetry.version` out of `pyproject.toml` to set `POETRY_DYNAMIC_VERSIONING_BYPASS`, but poetry was dropped in dad2acc in favor of uv and hatchling, so that lookup now yields `null`. The `pip install -e` it guards duplicates the `just sync duckdb` the Dockerfile already runs. Assisted-by: Claude Opus 5
deepyaman
force-pushed
the
renovate/ghcr.io-astral-sh-uv-0.x
branch
from
August 26, 2026 17:14
9353baa to
c9b0081
Compare
Contributor
Author
Autoclosing SkippedThis PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error. |
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
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.
Important
This PR has been extended beyond the renovate bump. Please rebase-merge
rather than squash, so the three commits stay separate.
Why this grew
The dev container has not built at all since roughly October 2025. On
main:The
mcr.microsoft.com/vscode/devcontainers/python:3.13base image moved toDebian trixie, which no longer packages
openjdk-17-jdk. This was reported in#11715, where the reporter found the fix (
openjdk-25-jdk) and confirmed itworked — but it was never committed, and the issue was closed.
Nothing in CI builds
.devcontainer/, so there was no signal. In the ~10 monthssince, renovate merged ten uv tag bumps into this same Dockerfile, all of them
auto-approved, auto-merged, and inert.
Commits
chore(deps):uv0.12.1 → 0.12.4, untouched.build(devcontainer):openjdk-17-jdk→default-jdk. One line short of the whole thing working.chore(devcontainer):postCreate.sh. It is unreferenced (there is nopostCreateCommand) and reads.tool.poetry.version, which has beennullsince poetry was dropped in dad2acc.default-jdkrather than a pinned version is @JonAnCla's suggestion in#12029 — it means this does not
break again the next time the base image moves to a new Debian release.
It also matters for correctness, not just durability. The JDK is in the image
only for pyspark (6af1dbf), we lock pyspark 4.0.1, and Spark 4.0 supports Java
17 and 21.
default-jdkis openjdk-21 on trixie. Pinning openjdk-25 buildscleanly but leaves the JDK unusable, because JDK 24 dropped the Security Manager
that Hadoop's
UserGroupInformationdepends on:ibis.pysparkdefault-jdk)java.lang.UnsupportedOperationException: getSubject is not supportedbuildrather thanfix:.devcontainer/ships to nobody(
[tool.hatch.build.targets.wheel] packages = ["ibis"]), so this should not cuta patch release.
Verification
Built locally via
@devcontainers/cli upon a clean clone, and separately on anamd64 GitHub runner:
Follow-ups, deliberately not in this PR
Nothing exercises the dev container.
nix.ymlbuilds the Nix devShell andcheck-generated-files.ymlinstalls fromrequirements-dev.txt, so two of thefive paths in
docs/contribute/01_environment.qmdare covered in CI — thecontainer is not. A scheduled build is the only thing that would have caught this
particular breakage, since the trigger was the upstream base image rather than
anything in this repo. Worth its own PR and its own review.
The
featuresblock does not appear to install. In the built imagequarto,duckdbandyqare all missing, on amd64 and arm64 alike. The threefeature-install steps complete in ~0.2s each and print nothing — not even the
banner their generated wrapper opens with — yet the build succeeds. Running that
wrapper by hand inside the image does execute it. Not root-caused; worth an
issue. Relatedly,
quarto-cliis still pinned to1.5.13from early 2024,because renovate's
enabledManagersomits thedevcontainermanager.Original renovate description
This PR contains the following updates:
0.12.1→0.12.4Release Notes
astral-sh/uv (ghcr.io/astral-sh/uv)
v0.12.4Compare Source
Released on 2026-08-13.
Enhancements
Requires-Python: >= 3.5.*(#21012)Preview features
uv check --no-install-projectand respectUV_NO_INSTALL_PROJECTto install dependencies without building or installing the project (#21085)uv checkhonor uv's color and progress settings, including quiet mode (#21086)Performance
Bug fixes
pythonw.exelaunchers for virtual environments created from managed Python minor-version links (#19235)uv lockto proceed when.venvis an unusable project environment (#21068)fork-strategywhen ordering forks created fromenvironmentsor existing lockfileresolution-markers(#21000)!=3.11.*, !=3.12.*inuv.lock(#21045)uv addupdates it (#21008)PYTHONEXECUTABLEand__PYVENV_LAUNCHER__overrides (#21075)uv version --bumpvalues (#21076)v0.12.3Compare Source
Released on 2026-08-07.
Python
Preview features
--output-formatto select automatic, human-readable, or raw-byte output foruv cache size(#20992)uv workspace metadata --quietwhile suppressing diagnostics (#20991)uv workspace metadataJSON output (#20990)Performance
Documentation
--python-pinto--pin-pythonin theuv init --bareexample (#20876)v0.12.2Compare Source
Released on 2026-08-05.
Python
Enhancements
Preview features
uv tool audit(#20921)cache-physical-spacepreview feature (#20925)Configuration
UV_RUN_RLIMIT_NOFILEto set the open-file limit for commands launched byuv run(#20926)Performance
uv.lockparsing for wheel entries (#20881)uv.lockparsing for source distribution entries (#20882)Bug fixes
Documentation
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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 this update again.
This PR was generated by Mend Renovate. View the repository job log.