Restore supported Python container runtime#13
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9d0951f48e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| ignore: | ||
| # PyTorch and this project currently support Python 3.10-3.12. | ||
| - dependency-name: python | ||
| update-types: ["version-update:semver-major"] |
There was a problem hiding this comment.
Block unsupported Python minor bumps
This ignore only excludes semver-major Docker tag updates; Dependabot treats versions as major.minor.patch, so python:3.11-slim -> python:3.13-slim or 3.14-slim is a semver-minor update and will still be proposed. Since pyproject.toml declares requires-python = ">=3.10,<3.13", the next Docker Dependabot run can recreate the unsupported container upgrade this commit is trying to prevent. Use an ignored version range such as >=3.13 (or also ignore semver-minor if that is acceptable) instead of only version-update:semver-major.
Useful? React with 👍 / 👎.
Summary
Restores the container to Python 3.11 after an automated Python 3.14 base-image upgrade broke the package/container job.
Root cause
The project declares Python
>=3.10,<3.13, and the current PyTorch/torchvision dependency set does not support the Python 3.14 container. Dependabot PR #8 upgraded both Docker stages beyond the supported runtime.Changes
python:3.11-slimValidation
The identical Python 3.11 container previously passed the package and container workflow. This PR's Actions run provides the authoritative rebuild verification.