Skip to content

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
mainfrom
renovate/ghcr.io-astral-sh-uv-0.x
Open

renovate[bot] wants to merge 3 commits into
mainfrom
renovate/ghcr.io-astral-sh-uv-0.x

Conversation

@renovate

@renovate renovate Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

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:

E: Unable to locate package openjdk-17-jdk

The mcr.microsoft.com/vscode/devcontainers/python:3.13 base image moved to
Debian trixie, which no longer packages openjdk-17-jdk. This was reported in
#11715, where the reporter found the fix (openjdk-25-jdk) and confirmed it
worked — but it was never committed, and the issue was closed.

Nothing in CI builds .devcontainer/, so there was no signal. In the ~10 months
since, renovate merged ten uv tag bumps into this same Dockerfile, all of them
auto-approved, auto-merged, and inert.

Commits

Commit What
chore(deps): The original renovate bump, uv 0.12.1 → 0.12.4, untouched.
build(devcontainer): openjdk-17-jdkdefault-jdk. One line short of the whole thing working.
chore(devcontainer): Delete postCreate.sh. It is unreferenced (there is no postCreateCommand) and reads .tool.poetry.version, which has been null since poetry was dropped in dad2acc.

default-jdk rather 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-jdk is openjdk-21 on trixie. Pinning openjdk-25 builds
cleanly but leaves the JDK unusable, because JDK 24 dropped the Security Manager
that Hadoop's UserGroupInformation depends on:

JDK ibis.pyspark
21 (default-jdk) works
25 java.lang.UnsupportedOperationException: getSubject is not supported

build rather than fix: .devcontainer/ ships to nobody
([tool.hatch.build.targets.wheel] packages = ["ibis"]), so this should not cut
a patch release.

Verification

Built locally via @devcontainers/cli up on a clean clone, and separately on an
amd64 GitHub runner:

{"outcome":"success", "remoteUser":"vscode", "remoteWorkspaceFolder":"/app"}
ibis 12.0.0 · duckdb backend ok · 4403 passed, 17 skipped (pytest -m core)
java 21.0.12.1 · ibis.pyspark create_table + count → 3 rows

Follow-ups, deliberately not in this PR

Nothing exercises the dev container. nix.yml builds the Nix devShell and
check-generated-files.yml installs from requirements-dev.txt, so two of the
five paths in docs/contribute/01_environment.qmd are covered in CI — the
container 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 features block does not appear to install. In the built image quarto,
duckdb and yq are all missing, on amd64 and arm64 alike. The three
feature-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-cli is still pinned to 1.5.13 from early 2024,
because renovate's enabledManagers omits the devcontainer manager.


Original renovate description

This PR contains the following updates:

Package Type Update Change
ghcr.io/astral-sh/uv final patch 0.12.10.12.4

Release Notes

astral-sh/uv (ghcr.io/astral-sh/uv)

v0.12.4

Compare Source

Released on 2026-08-13.

Enhancements
  • Prefer post-quantum key exchange and enable opt-in TLS diagnostics (#​21054)
  • Accept whitespace before versions in noncompliant wildcard comparisons such as Requires-Python: >= 3.5.* (#​21012)
  • Report a specific error when a PEP 723 closing tag contains trailing whitespace or other content (#​20944)
  • Omit source-span carets from diagnostics for empty PEP 508 requirements (#​21094)
Preview features
  • Add uv check --no-install-project and respect UV_NO_INSTALL_PROJECT to install dependencies without building or installing the project (#​21085)
  • Make the ty subprocess invoked by uv check honor uv's color and progress settings, including quiet mode (#​21086)
Performance
  • Speed up resolutions with long runs of unavailable package versions by coalescing gaps in the resolver's version ranges (#​20804)
  • Speed up Simple API parsing by deserializing PyPI and Pyx file metadata directly (#​21041)
Bug fixes
  • Use windowed pythonw.exe launchers for virtual environments created from managed Python minor-version links (#​19235)
  • Allow uv lock to proceed when .venv is an unusable project environment (#​21068)
  • Respect fork-strategy when ordering forks created from environments or existing lockfile resolution-markers (#​21000)
  • Preserve consecutive wildcard Python minor-version exclusions such as !=3.11.*, !=3.12.* in uv.lock (#​21045)
  • Preserve inline comments on the final item in dependency arrays when uv add updates it (#​21008)
  • Recover from stale base-interpreter cache metadata when an existing virtual environment exposes a version mismatch (#​21073)
  • Prevent interpreter cache reuse across different PYTHONEXECUTABLE and __PYVENV_LAUNCHER__ overrides (#​21075)
  • Show standard styling, usage guidance, and line termination for invalid uv version --bump values (#​21076)

v0.12.3

Compare Source

Released on 2026-08-07.

Python
Preview features
  • Add --output-format to select automatic, human-readable, or raw-byte output for uv cache size (#​20992)
  • Preserve JSON output from uv workspace metadata --quiet while suppressing diagnostics (#​20991)
  • Reduce memory usage for large workspaces by streaming uv workspace metadata JSON output (#​20990)
Performance
  • Reduce Linux startup latency by initializing the workspace cache before spawning another thread (#​20989)
  • Reuse compiled workspace exclusion patterns during workspace discovery (#​20988)
  • Speed up conflict-heavy resolutions by avoiding materialized range complements (#​20982)
  • Avoid slow procfs reads during Python interpreter discovery on Linux (#​20987)
Documentation
  • Add PEP 740 attestations to the GitHub Actions publishing example (#​20986)
  • Restrict the GitHub Actions publishing example to Python version tags (#​20973)
  • Correct --python-pin to --pin-python in the uv init --bare example (#​20876)

v0.12.2

Compare Source

Released on 2026-08-05.

Python
Enhancements
  • Ensure diagnostic hints end with a newline to prevent malformed terminal output (#​20959)
Preview features
  • Audit one or all installed tools with uv tool audit (#​20921)
  • Report physically reclaimed disk space during cache cleanup with the cache-physical-space preview feature (#​20925)
Configuration
  • Add UV_RUN_RLIMIT_NOFILE to set the open-file limit for commands launched by uv run (#​20926)
Performance
  • Speed up uv.lock parsing for wheel entries (#​20881)
  • Speed up uv.lock parsing for source distribution entries (#​20882)
  • Speed up filename extraction from distribution URLs (#​20879)
  • Reduce filesystem metadata lookups during bytecode compilation (#​20928)
  • Reuse file metadata when building source distributions (#​20927)
Bug fixes
  • Preserve compatibility with older uv versions when recording artifact sizes in cached wheels and source distributions (#​20963)
  • Avoid including workspace-root default dependency groups when syncing or exporting a selected workspace member unless explicitly requested (#​20930)
Documentation
  • Separate build and publish jobs in the GitHub Actions publishing guide (#​20946)
  • Ensure the GitHub Actions publishing example waits for the build job to finish (#​20957)
  • Correct typos in the Docker integration guide (#​20970)

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 10pm every weekday,every weekend,before 5am every weekday"
  • Automerge
    • At any time (no schedule defined)

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


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

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

@renovate renovate Bot added the dependencies Issues or PRs related to dependencies label Aug 10, 2026
@renovate renovate Bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.3 chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.3 - autoclosed Aug 13, 2026
@renovate renovate Bot closed this Aug 13, 2026
@renovate
renovate Bot deleted the renovate/ghcr.io-astral-sh-uv-0.x branch August 13, 2026 14:50
@renovate renovate Bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.3 - autoclosed chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.4 Aug 14, 2026
@renovate renovate Bot reopened this Aug 14, 2026
@renovate
renovate Bot force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch from 9280101 to 8f89bd5 Compare August 14, 2026 00:00
@github-actions github-actions Bot added the ci Continuous Integration issues or PRs label Aug 14, 2026
@renovate

renovate Bot commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

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

⚠️ Warning: custom changes will be lost.

@deepyaman
deepyaman force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch 6 times, most recently from 781d42c to cf88a70 Compare August 14, 2026 18:45
@deepyaman
deepyaman force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch from cf88a70 to 9353baa Compare August 26, 2026 05:05
renovate Bot and others added 3 commits August 26, 2026 11:14
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
deepyaman force-pushed the renovate/ghcr.io-astral-sh-uv-0.x branch from 9353baa to c9b0081 Compare August 26, 2026 17:14
@renovate renovate Bot changed the title chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.4 chore(deps): update ghcr.io/astral-sh/uv docker tag to v0.12.4 - abandoned Aug 28, 2026
@renovate

renovate Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor Author

Autoclosing Skipped

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Continuous Integration issues or PRs dependencies Issues or PRs related to dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant