chore(deps): update public.ecr.aws/lambda/python docker tag to v3.14

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
public.ecr.aws/lambda/python	final	minor	3.13-x86_64 → 3.14-x86_64
public.ecr.aws/lambda/python	final	minor	3.12-x86_64 → 3.14-x86_64

---

Configuration

📅 Schedule: Branch creation - At 06:00 PM through 11:59 PM and 12:00 AM through 09:59 AM ( * 18-23,0-9 * * * ) in timezone Europe/Kiev, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep python3.12 image on 3.12 runtime

The python3_12 Dockerfile now pulls public.ecr.aws/lambda/python:3.14-x86_64, so the image built and published as 25.2-python3.12-x86_64 will actually contain Python 3.14. That silently drops the Python 3.12 runtime variant described in the README and is likely to break consumers that rely on the 3.12 interpreter for compatibility testing or deployment. If the intent is to continue offering distinct 3.12 and 3.13 images, this line should remain on the 3.12 tag.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Retain python3.13 image on 3.13 base

Similarly, the python3_13 variant now also points to public.ecr.aws/lambda/python:3.14-x86_64. Publishing this image under a python3.13 tag will ship Python 3.14 instead, removing the genuine 3.13 variant and potentially breaking workloads that must stay on 3.13. Unless the plan is to rename the image to 3.14 everywhere, the base tag here should stay at 3.13-x86_64.

Useful? React with 👍 / 👎.