Repository upgraded into Python3.13

[tmikula-dev]

Overview

Upgrading python version across all the QA tools and lambda current required runtime.

Release Notes:

• Updating python project version into python3.13

Closes #58

Summary by CodeRabbit

• Chores

  • Upgraded Python version to 3.13 across CI workflows and serverless runtime for consistency and future compatibility.
  • Expanded code ownership to include an additional maintainer for broader review coverage.
  • Added a commented dependency note; no change to active dependencies or runtime behavior.

• Documentation

  • Introduced prerequisites outlining Python 3.13 and a PostgreSQL client requirement.
  • Provided guidance for local development using psycopg2-binary as a temporary alternative.

[coderabbitai]

Walkthrough

Project-wide Python version updated from 3.11 to 3.13 across CI workflows, configuration, and Terraform Lambda runtime. Documentation now lists Python 3.13 and notes local psycopg2-binary option. Requirements gains a commented hint. CODEOWNERS adds @tmikula-dev. No functional logic or control-flow changes.

Changes

Cohort / File(s)	Summary
CI Workflows (Python 3.13) .github/workflows/check_pr_release_notes.yml, .github/workflows/release_draft.yml, .github/workflows/test.yml	Updated actions/setup-python inputs from 3.11 to 3.13; workflow steps otherwise unchanged.
Infrastructure (Lambda runtime) terraform/lambda.tf	aws_lambda_function runtime changed from python3.11 to python3.13.
Project Configuration pyproject.toml	Target/version fields updated: py311 → py313; python_version 3.11 → 3.13.
Documentation DEVELOPER.md	Added Prerequisites specifying Python 3.13 and PostgreSQL client dev package; note about optional local use of psycopg2-binary==2.9.10.
Dependencies Note requirements.txt	Added commented line suggesting psycopg2-binary==2.9.10 for local development; no active dependency change.
Governance .github/CODEOWNERS	Added @tmikula-dev to owners for all paths.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I hop through versions, light and keen,
From 3.11 to 3.13.
Pip prints paths, the Lambdas sing,
CI sets a shiny thing.
New paws in CODEOWNERS’ den—
We merge, we munch, we ship again. 🥕

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Out of Scope Changes Check	⚠️ Warning	The pull request includes a change to the CODEOWNERS file adding @tmikula-dev as a maintainer, which is unrelated to updating the Python version. This addition does not address the objectives in issue #58 and appears outside the scope of the Python version upgrade.	Please remove the CODEOWNERS modification from this pull request or split it into a separate change that does not pertain to the Python version upgrade.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title “Repository upgraded into Python3.13” succinctly captures the primary change of migrating to Python 3.13 across the repository. It is clear and specific enough that a teammate scanning the history can understand the main update.
Linked Issues Check	✅ Passed	The pull request updates the Python version in all CI workflows, project configuration files, Terraform Lambda runtime, and developer documentation, directly satisfying the objective of migrating to Python 3.13 as specified in issue #58. All code and configuration changes align with the requirement to keep the project Python version up to date.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/upgrading-to-python313

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1095a0b and e716883.

📒 Files selected for processing (8)

• .github/CODEOWNERS (1 hunks)
• .github/workflows/check_pr_release_notes.yml (1 hunks)
• .github/workflows/release_draft.yml (1 hunks)
• .github/workflows/test.yml (4 hunks)
• DEVELOPER.md (1 hunks)
• pyproject.toml (2 hunks)
• requirements.txt (1 hunks)
• terraform/lambda.tf (1 hunks)

🔇 Additional comments (4)

terraform/lambda.tf (1)

25-25: Confirm AWS Lambda support for Python 3.13 runtime.

Terraform will fail to deploy if python3.13 isn’t yet offered as a managed Lambda runtime. Please double-check the AWS Lambda release notes/console before merging.

.github/workflows/check_pr_release_notes.yml (1)

13-16: Validate GitHub Actions availability of Python 3.13.

If actions/setup-python doesn’t yet ship a 3.13 toolcache, this job will fail before running any checks. Please confirm the runner currently exposes Python 3.13.

.github/workflows/release_draft.yml (1)

21-24: Double-check Python 3.13 availability on GitHub runners.

Release workflow will halt if the toolcache lacks 3.13. Verify support before rollout.

.github/workflows/test.yml (1)

18-22: Ensure CI can provision Python 3.13 across all jobs.

Every job now depends on the runner supplying Python 3.13. Please confirm actions/setup-python currently offers this build; otherwise the workflow will fail before installs/tests run.

Also applies to: 52-56, 81-85, 102-106

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[oto-macenauer-absa]

lgtm