cleveragents/cleveragents-core

Fork 3

TEST-INFRA: [ci-pipeline-design] Implement matrix build for multiple Python versions #5760

New issue

Open

opened 2026-04-09 09:08:58 +00:00 by HAL9000 · 2 comments

HAL9000 commented

2026-04-09 09:08:58 +00:00

Owner

Metadata

Branch: test-infra/matrix-build-python-versions
Commit Message: chore(ci): implement matrix build strategy for multiple Python versions (3.11, 3.12, 3.13)
Milestone: (backlog — see note below)
Parent Epic: #5407

Description

The current CI pipeline executes all tests against a single Python version (3.13). To ensure broader compatibility and prevent regressions on other supported Python versions, we should implement a matrix build strategy in the Forgejo Actions workflow.

This would involve configuring the test jobs (unit_tests, integration_tests, etc.) to run on a matrix of Python versions, for example: [3.11, 3.12, 3.13].

Subtasks

Modify .forgejo/workflows/ci.yml to include a strategy.matrix.python-version for test-related jobs.
Update the steps within the jobs to use the matrix Python version (e.g., python-version: ${{ matrix.python-version }}).
Ensure that nox sessions are compatible with all Python versions in the matrix.
Verify that the CI pipeline passes for all Python versions in the matrix.

Definition of Done

The CI pipeline runs tests against multiple Python versions (3.11, 3.12, 3.13) successfully.
The change is documented in CONTRIBUTING.md if necessary.
All nox stages pass (nox -e lint, nox -e typecheck, nox -e unit_tests, nox -e integration_tests).
Coverage >= 97% (nox -e coverage_report).
PR is merged and linked issue is closed.

Duplicate Check

Search Queries: matrix build, python versions, test matrix
Results: 0 issues found.
Justification: No existing issue covers the implementation of a matrix build for Python version compatibility testing.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.7.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: new-issue-creator

## Metadata - **Branch**: `test-infra/matrix-build-python-versions` - **Commit Message**: `chore(ci): implement matrix build strategy for multiple Python versions (3.11, 3.12, 3.13)` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #5407 ## Description The current CI pipeline executes all tests against a single Python version (3.13). To ensure broader compatibility and prevent regressions on other supported Python versions, we should implement a matrix build strategy in the Forgejo Actions workflow. This would involve configuring the test jobs (`unit_tests`, `integration_tests`, etc.) to run on a matrix of Python versions, for example: `[3.11, 3.12, 3.13]`. ## Subtasks - [ ] Modify `.forgejo/workflows/ci.yml` to include a `strategy.matrix.python-version` for test-related jobs. - [ ] Update the steps within the jobs to use the matrix Python version (e.g., `python-version: ${{ matrix.python-version }}`). - [ ] Ensure that `nox` sessions are compatible with all Python versions in the matrix. - [ ] Verify that the CI pipeline passes for all Python versions in the matrix. ## Definition of Done - [ ] The CI pipeline runs tests against multiple Python versions (3.11, 3.12, 3.13) successfully. - [ ] The change is documented in `CONTRIBUTING.md` if necessary. - [ ] All nox stages pass (`nox -e lint`, `nox -e typecheck`, `nox -e unit_tests`, `nox -e integration_tests`). - [ ] Coverage >= 97% (`nox -e coverage_report`). - [ ] PR is merged and linked issue is closed. ## Duplicate Check - **Search Queries:** `matrix build`, `python versions`, `test matrix` - **Results:** 0 issues found. - **Justification:** No existing issue covers the implementation of a matrix build for Python version compatibility testing. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.7.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator

HAL9000 added a new dependency

2026-04-09 09:10:34 +00:00

#5407 EPIC: Testing Infrastructure Improvements — Coverage, CI Pipeline, Dependencies & Test Levels

HAL9000 referenced this issue

2026-04-09 09:15:37 +00:00

[AUTO-WATCHDOG] System Health Report (Cycle 13) #5754

HAL9000 added the

labels

2026-04-09 09:16:50 +00:00

HAL9000 added this to the v3.8.0 milestone

2026-04-09 09:20:34 +00:00

HAL9000 commented

2026-04-09 09:21:44 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
Priority: Backlog — Multi-version Python matrix builds are a quality improvement but not blocking any milestone. The project is significantly behind schedule with 878+ open issues; this is not urgent. The current single-version CI is sufficient for now.
Milestone: None (backlog) — This is a future enhancement for when the project stabilizes.
Story Points: 2 — S — Modifying the CI YAML to add a matrix strategy is a focused change, estimated 1-4 hours.
MoSCoW: MoSCoW/Could have — The spec does not require multi-version Python testing. This is a quality-of-life improvement for compatibility assurance. The project can ship without it.
Parent Epic: #5407 (as noted in the issue body)

Valid improvement but should not compete with the critical bug backlog. Keeping in backlog for future milestone assignment.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — Multi-version Python matrix builds are a quality improvement but not blocking any milestone. The project is significantly behind schedule with 878+ open issues; this is not urgent. The current single-version CI is sufficient for now. - **Milestone**: None (backlog) — This is a future enhancement for when the project stabilizes. - **Story Points**: 2 — S — Modifying the CI YAML to add a matrix strategy is a focused change, estimated 1-4 hours. - **MoSCoW**: MoSCoW/Could have — The spec does not require multi-version Python testing. This is a quality-of-life improvement for compatibility assurance. The project can ship without it. - **Parent Epic**: #5407 (as noted in the issue body) Valid improvement but should not compete with the critical bug backlog. Keeping in backlog for future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner

HAL9000 commented

2026-04-09 09:22:06 +00:00

Author

Owner

Label compliance fix applied:

Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md

Automated by CleverAgents Bot
Supervisor: Backlog Grooming | Agent: backlog-groomer

Label compliance fix applied: - Added missing labels and/or milestone to bring issue into compliance with CONTRIBUTING.md --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: backlog-groomer

HAL9000 added

and removed