Skip to content

Update compatible runtimes for AWS Lambda layer#797

Open
Miqueasher wants to merge 1 commit into
mainfrom
Miqueasher-patch-1
Open

Update compatible runtimes for AWS Lambda layer#797
Miqueasher wants to merge 1 commit into
mainfrom
Miqueasher-patch-1

Conversation

@Miqueasher

Copy link
Copy Markdown
Contributor

Update compatible-runtimes to include v 3.14

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Update compatible-runtimes to include v 3.14
@Miqueasher Miqueasher requested a review from a team as a code owner June 24, 2026 17:09
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Claude finished @Miqueasher's task in 1m 9s —— View job


Claude Code Review

  • Read prior reviews/comments for dedup (none existed)
  • Review PR diff
  • Post review findings

Summary

The change adds python3.14 to --compatible-runtimes in .github/workflows/region-build-release.yml:182. This brings it in line with .github/workflows/release-build.yml:317, which already lists python3.14. The two workflows are now consistent.

Observations:

  • Single-line, low-risk change. Looks good.
  • One nit: the corresponding line in release-build.yml:317 has a trailing double space before the line-continuation backslash (python3.14 \). The line in this PR uses a single space (python3.14 \), which is the more conventional formatting — no action needed here, just flagging that the sibling file has slightly inconsistent whitespace if anyone wants to clean it up in a follow-up.
  • Worth confirming that AWS Lambda's publish-layer-version accepts python3.14 as a value for --compatible-runtimes at the time this workflow runs in your target regions. If the runtime isn't yet available in a region, the publish step will fail with a validation error.

No blocking issues from my side.

@Miqueasher Miqueasher added the skip changelog doesn't need a CHANGELOG entry label Jun 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip changelog doesn't need a CHANGELOG entry

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant