chore(agent): upgrade Python 3.13 → 3.14
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Half a day
- Newbie friendliness
- 68/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker, python
- Domain
- build-system, devops
Research direction
Update the four locations named in the issue: agent/Dockerfile, agent/pyproject.toml, and the uv.lock generated by uv lock. Start by reviewing those Python-version settings, then run uv lock and uv sync --frozen, build the Docker image, run the agent unit tests and Trivy scan, and perform the smoke test. Done means the Python 3.14 image builds and all listed checks pass.
Written by the indexing model from the issue text.
Description
Summary
Upgrade the agent container base image from python:3.13-slim to python:3.14-slim.
Related: #104 (toolchain monitoring RFC)
Risk Assessment: SAFE
Comprehensive codebase analysis shows zero code changes required:
| Check | Result |
|---|---|
requires-python constraint |
>=3.13 — already permits 3.14 |
| Removed stdlib modules (asyncore, cgi, etc.) | None used |
| Typing features | All stable since 3.11/3.12; PEP 649 compatible |
| Native extension wheels (cedarpy, pydantic-core, grpcio, cffi) | All have cp314 wheels in uv.lock |
| Major deps (boto3, fastapi, uvicorn, opentelemetry, claude-agent-sdk) | All pure-Python or have 3.14 wheels |
| C extensions in agent source | None — all pre-built wheels |
| asyncio event loop policy usage | Diagnostic only; no behavior change in 3.14 |
Changes Required
agent/Dockerfileline 11:python:3.13-slim→python:3.14-slimagent/pyproject.toml:target-version = "py313"→"py314"(ruff)agent/pyproject.toml:python-version = "3.13"→"3.14"(ty)- Re-lock:
uv lock(lockfile already has 3.14 resolution markers)
Testing Required
- Docker image builds
-
uv sync --frozenworks (or re-lock if needed) - Agent unit tests pass
- Trivy image scan passes
- Smoke test: full agent task execution
Notes
- Consider doing this separately from the Debian trixie upgrade (#106) to isolate variables
- Python 3.14 is stable with 5 patch releases as of May 2026
- The uv.lock already contains resolution markers for
python_full_version >= '3.14'
- Dominant language
- TypeScript
- Stars
- 146
- Forks
- 46
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 27
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws-samples/sample-autonomous-cloud-coding-agents
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug v1
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug v1
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
documentation P2 security
Difficulty 2/5 1-2 days Newbie friendliness 74/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws-samples/sample-autonomous-cloud-coding-agents#767 · 2 comments ·
All issues in aws-samples/sample-autonomous-cloud-coding-agents
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100