Repository navigation
Conversation
…stable 3.15 - Replace 'pip install uv' with astral-sh/setup-uv@v10 in both jobs (official action, cached, tracks latest uv) - Remove allow-prereleases from the test matrix: 3.15.0 final shipped 2026-10-09 and is in the setup-python manifest as stable - Dockerfile stays on python:3.14-slim: no official 3.15-slim image published yet (rc tags only as of 2026-10-12)
The official python:3.15-slim image is now published on Docker Hub.
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
1 participant
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.
Summary
pip install --upgrade pip uvwithastral-sh/setup-uv@v10.3.0in both jobs (lint + test) — the official astral action, cached, always the latest uv. (Pinned to the full semver because setup-uv no longer publishes a floatingv10tag.)allow-prereleases: truefrom the test matrix: Python 3.15.0 final was released 2026-10-09 and is markedstable=Truein the actions/setup-python manifest, so the3.15matrix entry now resolves to the stable release..github/dependabot.yml(weekly,github-actionsecosystem) so action pins stay fresh automatically.Dockerfiletopython:3.15-slimand.python-versionto3.15(kept in sync becauseuv syncresolves its interpreter from.python-version).Known limitation
pydantic-core==2.46.5(pinned by pydantic 2.13.5) ships no cp315 wheel yet, souv sync --frozeninside the slim image would have to compile it from source (needs a Rust toolchain the slim image lacks). Verified 2026-10-13 via a localuv sync --frozenon Python 3.15.0: 185/187 locked packages install from wheels; only pydantic-core was affected (aiohttp 3.14.3 had the same gap, fixed by bumping the lock to 3.14.5). The Docker build stays red until pydantic ships a release depending on a cp315-capable pydantic-core — the lock bump will follow then.Verification