[CI] Add Python 3.13 to the test matrix

Open Beginner friendly
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions, python
Domain
ci-cd

Research direction

The change belongs in the Python version matrix of .github/workflows/ci.yml; read that file first and see how the existing 3.10–3.12 entries are listed. Add 3.13 next to them without removing anything, then check that the dependency install step and the Qt offscreen test command still apply to it. Done when the workflow runs the existing test suite on Python 3.13 and the older versions still pass.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Summary

The GitHub Actions test workflow currently runs on Python 3.10, 3.11, and 3.12, while the development documentation recommends Python 3.13 or newer. The supported development/runtime range should be exercised in CI.

Proposed solution

Extend the Python version matrix in .github/workflows/ci.yml to include Python 3.13. Keep the existing versions and verify that the dependency installation and test command continue to work on the new runner.

Acceptance criteria

  • CI runs the existing test suite on Python 3.13.
  • Python 3.10, 3.11, and 3.12 coverage remains unchanged.
  • The workflow stays compatible with the current Qt offscreen test configuration.

Security considerations

This changes only automated compatibility coverage; it does not change application security behavior or cryptographic parameters.

Additional context

Relevant file: .github/workflows/ci.yml; the documented recommendation is in docs/DEVELOPMENT.md.

Dominant language
Python
Stars
1
Forks
0
Avg merge
1h 50m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ANCORATE/EncryptHome

All issues in ANCORATE/EncryptHome

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.