chore(deps): update dependency python to 3.14

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python	uses-with	minor	3.9 -> 3.14
python	final	minor	3.12 -> 3.14
python	stage	minor	3.12 -> 3.14
python	stage	minor	3.9 -> 3.14
python	final	minor	3.9 -> 3.14

---

Release Notes

actions/python-versions (python)

v3.14.2: 3.14.2

Compare Source

Python 3.14.2

v3.14.1: 3.14.1

Compare Source

Python 3.14.1

v3.14.0: 3.14.0

Compare Source

Python 3.14.0

v3.13.11: 3.13.11

Compare Source

Python 3.13.11

v3.13.10: 3.13.10

Compare Source

Python 3.13.10

v3.13.9: 3.13.9

Compare Source

Python 3.13.9

v3.13.8: 3.13.8

Compare Source

Python 3.13.8

v3.13.7: 3.13.7

Compare Source

Python 3.13.7

v3.13.6: 3.13.6

Compare Source

Python 3.13.6

v3.13.5: 3.13.5

Compare Source

Python 3.13.5

v3.13.4: 3.13.4

Compare Source

Python 3.13.4

v3.13.3: 3.13.3

Compare Source

Python 3.13.3

v3.13.2: 3.13.2

Compare Source

Python 3.13.2

v3.13.1: 3.13.1

Compare Source

Python 3.13.1

v3.13.0: 3.13.0

Compare Source

Python 3.13.0

v3.12.12: 3.12.12

Compare Source

Python 3.12.12

v3.12.11: 3.12.11

Compare Source

Python 3.12.11

v3.12.10: 3.12.10

Compare Source

Python 3.12.10

v3.12.9: 3.12.9

Compare Source

Python 3.12.9

v3.12.8: 3.12.8

Compare Source

Python 3.12.8

v3.12.7: 3.12.7

Compare Source

Python 3.12.7

v3.12.6: 3.12.6

Compare Source

Python 3.12.6

v3.12.5: 3.12.5

Compare Source

Python 3.12.5

v3.12.4: 3.12.4

Compare Source

Python 3.12.4

v3.12.3: 3.12.3

Compare Source

Python 3.12.3

v3.12.2: 3.12.2

Compare Source

Python 3.12.2

v3.12.1: 3.12.1

Compare Source

Python 3.12.1

v3.12.0: 3.12.0

Compare Source

Python 3.12.0

v3.11.14: 3.11.14

Compare Source

Python 3.11.14

v3.11.13: 3.11.13

Compare Source

Python 3.11.13

v3.11.12: 3.11.12

Compare Source

Python 3.11.12

v3.11.11: 3.11.11

Compare Source

Python 3.11.11

v3.11.10: 3.11.10

Compare Source

Python 3.11.10

v3.11.9: 3.11.9

Compare Source

Python 3.11.9

v3.11.8: 3.11.8

Compare Source

Python 3.11.8

v3.11.7: 3.11.7

Compare Source

Python 3.11.7

v3.11.6: 3.11.6

Compare Source

Python 3.11.6

v3.11.5: 3.11.5

Compare Source

Python 3.11.5

v3.11.4: 3.11.4

Compare Source

Python 3.11.4

v3.11.3: 3.11.3

Compare Source

Python 3.11.3

v3.11.2: 3.11.2

Compare Source

Python 3.11.2

v3.11.1: 3.11.1

Compare Source

Python 3.11.1

v3.11.0: 3.11.0

Compare Source

Python 3.11.0

v3.10.19: 3.10.19

Compare Source

Python 3.10.19

v3.10.18: 3.10.18

Compare Source

Python 3.10.18

v3.10.17: 3.10.17

Compare Source

Python 3.10.17

v3.10.16: 3.10.16

Compare Source

Python 3.10.16

v3.10.15: 3.10.15

Compare Source

Python 3.10.15

v3.10.14: 3.10.14

Compare Source

Python 3.10.14

v3.10.13: 3.10.13

Compare Source

Python 3.10.13

v3.10.12: 3.10.12

Compare Source

Python 3.10.12

v3.10.11: 3.10.11

Compare Source

Python 3.10.11

v3.10.10: 3.10.10

Compare Source

Python 3.10.10

v3.10.9: 3.10.9

Compare Source

Python 3.10.9

v3.10.8: 3.10.8

Compare Source

Python 3.10.8

v3.10.7: 3.10.7

Compare Source

Python 3.10.7

v3.10.6: 3.10.6

Compare Source

Python 3.10.6

v3.10.5: 3.10.5

Compare Source

Python 3.10.5

v3.10.4: 3.10.4

Compare Source

Python 3.10.4

v3.10.3: 3.10.3

Compare Source

Python 3.10.3

v3.10.2: 3.10.2

Compare Source

Python 3.10.2

v3.10.1: 3.10.1

Compare Source

Python 3.10.1

v3.10.0: 3.10.0

Compare Source

Python 3.10.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[github-actions]

Code Quality

1. Pin Python base image versions:
   Instead of using python:3.13, specify a patch version (e.g., python:3.13.0). This ensures consistent builds and avoids unexpected behavior from future minor changes in the image.

   Example:
   dockerfile
   FROM python:3.13.0

2. Use multi-stage builds where appropriate:
   Ensure unused artifacts from the builder stage are not carried into the final image to reduce bloat. However, since you do not show the complete multi-stage setup above, there might be missed opportunities for file clean-up in various stages.

Security

3. Add a signature check for base images:
   Use digest pinning or verify image integrity via SHA256 to mitigate risks of compromised base images.

   Example:

   FROM python@sha256:abcdef123456...

4. Reduce permissions and privileges:
   Add the following to run the application as a non-root user where applicable:

   RUN addgroup --system appgroup && adduser --system --ingroup appgroup appuser
   USER appuser

Best Practices

5. Layered caching optimization:
   Place RUN pip install after COPY . /app. Changes in source code will invalidate this cache less frequently, reducing rebuild times.

   Example:

   COPY requirements.txt /app/
   RUN pip install --no-cache-dir --upgrade -r /app/requirements.txt
   COPY . /app/

6. Using no-cache during build time:
   Add --no-cache during apt-get update commands (if applicable) to reduce outdated packages usage. Ensure all images stay lightweight.

Cost & Carbon Usage

• Analysis of Python 3.13 impact:
  While upgrading to Python 3.13 offers the latest features/bug fixes, it could lead to increased resource usage depending on package compatibility. This might marginally increase costs and energy use in cloud environments until optimizations stabilize with newer libraries.

  Mitigation: Use Python 3.13 only if required and consider staying on LTS versions (e.g., Python 3.12) for better resource optimization initially.

Estimated Price Changes

• Direct impact depends on your package dependencies and CPU/memory consumption. If using a managed container service, small cost hikes (~1-2%) may arise during migration to updated libraries, assuming minor inefficiencies.

Carbon Usage

• Minimal expected increase in carbon output due to updated libraries requiring adjustments. Regular monitoring of resource utilization post-upgrade can help identify regressions.