Repository navigation
chore(deps): update all non-major dependencies #167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 3.13 | ||
| 3.15 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,4 @@ | ||
| FROM python:3.12-slim AS base | ||
| FROM python:3.15-slim@sha256:65a65fc7b30b06cb6df4930fd4650697cb23f4c2698ab81fc87e4b031bc36928 AS base | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Python 3.15 image cannot build locked cffi The lockfile has no CPython 3.15 wheel for cffi 2.0.0, so this base image falls back to building its source distribution, but the slim image lacks the compiler and libffi headers required for that build. I reproduced the install failure with Prompt To Fix With AIThis is a comment left during a code review.
Path: Dockerfile
Line: 1
Comment:
**Python 3.15 image cannot build locked cffi**
The lockfile has no CPython 3.15 wheel for cffi 2.0.0, so this base image falls back to building its source distribution, but the slim image lacks the compiler and libffi headers required for that build. I reproduced the install failure with `SETUPTOOLS_SCM_PRETEND_VERSION=0.0.0+ci uv sync --frozen --group dev`, which failed compiling cffi because `ffi.h` was missing; the Dockerfile's `uv sync --no-dev` includes the same runtime dependency and will block image builds.
---
For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.🟠 Major · bug · Reply if this doesn't apply. |
||
|
|
||
| ENV PYTHONUNBUFFERED=1 \ | ||
| UV_COMPILE_BYTECODE=1 \ | ||
|
|
@@ -9,7 +9,7 @@ WORKDIR /app | |
| ARG PACKAGE_VERSION=0.0.0+docker | ||
| ENV SETUPTOOLS_SCM_PRETEND_VERSION=${PACKAGE_VERSION} | ||
|
|
||
| COPY --from=ghcr.io/astral-sh/uv:0.11.22 /uv /usr/local/bin/uv | ||
| COPY --from=ghcr.io/astral-sh/uv:0.13.8@sha256:5cc1805e2426484abca4ad46ea783bab281fdb225fd82d8ce6d66a81254bac85 /uv /usr/local/bin/uv | ||
|
|
||
| COPY pyproject.toml uv.lock README.md ./ | ||
| COPY src ./src | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep CI coverage for the minimum supported Python
The workflows now test only Python 3.15, although the project supports Python >=3.12 and AGENTS.md records 3.12 as the CI target. This leaves regressions specific to the minimum supported runtime undetected; please retain 3.12 coverage or test both versions.
Prompt To Fix With AI
🟡 Minor · testing · Reply if this doesn't apply.