Skip to content

Move boilerplate to Python 3.12 base image - #9

Merged
m-messer merged 1 commit into
mainfrom
python-3.12
Nov 6, 2026
Merged

m-messer merged 1 commit into
mainfrom
python-3.12

Conversation

@m-messer

@m-messer m-messer commented Nov 6, 2026

Copy link
Copy Markdown
Member

Why

The base layer is stopping its 3.8 image builds (lambda-feedback/BaseEvalutionFunctionLayer#23), and Python 3.8 is out of support on AWS Lambda. New evaluation functions created from this template currently start on main-3.8, so they would never get base-layer updates.

Changes

  • app/Dockerfile: base image main-3.8 → main-3.12.
  • .github/workflows/staging-deploy.yml: staging test job runs on 3.12 instead of 3.8. test-lint.yml was already on 3.12.
  • README.md: prerequisite changed to Python 3.12.

This is the same change as lambda-feedback/ArraySymbolicEqual#20.

Testing

The template's tests pass on Python 3.12 (2 passed). The template has no dependencies beyond the standard library. I couldn't build the Docker image locally.

Note

Functions already created from this template aren't affected. They have their own app/Dockerfile and stay on the frozen main-3.8 image until each one is migrated.

🤖 Generated with Claude Code

The base layer is dropping the 3.8 image (BaseEvalutionFunctionLayer#23),
and new functions created from this template should not start on an
unsupported runtime.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@m-messer
m-messer merged commit 76150b5 into main Nov 6, 2026
1 check passed
@m-messer
m-messer deleted the python-3.12 branch November 6, 2026 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant