Repository navigation
Use Python 3.12 in CI and for the Lambda functions - #8
Merged
Merged
Conversation
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
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.
The scheduled CI run has failed since Oct 25 at the Setup Python step:
ubuntu-latestnow resolves to Ubuntu 26.04, and actions/python-versions has no Python 3.9 build for it. The oldest build available for 26.04 is 3.10.python3.9topython3.12.sam buildruns without a container here, so the function runtime has to match the Python on the runner. The handlers only use boto3 and the standard library.sam buildpasses locally with Python 3.12.