TEST-INFRA: [ci-pipeline-design] Centralize Dependency Management in noxfile.py #1643

Closed
opened 2026-04-02 23:22:16 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: task/ci-centralize-noxfile-dependency-management
  • Commit Message: chore(ci): centralize dependency management in noxfile.py using uv or pip-tools
  • Milestone: v3.8.0
  • Parent Epic: (to be linked — see orphan note below)

Description

The current noxfile.py installs dependencies directly using session.install. This can lead to inconsistencies between the dependencies used in different sessions and the dependencies defined in pyproject.toml.

To improve this, we should centralize the dependency management by using a single source of truth for dependencies. This can be achieved by using a tool like uv or pip-tools to generate a requirements.txt file for each session, ensuring all nox sessions are aligned with the declared dependencies in pyproject.toml.

Area: CI/CD, Developer Experience

Subtasks

  • Investigate using uv or pip-tools to manage dependencies in noxfile.py.
  • Modify noxfile.py to use the chosen tool to generate requirements.txt files for each session.
  • Update the CI configuration to use the generated requirements.txt files to install dependencies.
  • Verify all nox sessions install dependencies consistently from the single source of truth.
  • Verify nox -e lint passes.
  • Verify nox -e typecheck passes.
  • Verify nox -e unit_tests passes.
  • Verify nox -e integration_tests passes.
  • Verify nox -e coverage_report reports >= 97%.

Definition of Done

  • All nox sessions use a requirements.txt file (or equivalent uv-managed lockfile) to install dependencies.
  • The CI pipeline is updated to use the new dependency management system.
  • The overall build time is not negatively impacted by the changes.
  • All nox stages pass.
  • Coverage >= 97%.

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

## Metadata - **Branch**: `task/ci-centralize-noxfile-dependency-management` - **Commit Message**: `chore(ci): centralize dependency management in noxfile.py using uv or pip-tools` - **Milestone**: v3.8.0 - **Parent Epic**: *(to be linked — see orphan note below)* ## Description The current `noxfile.py` installs dependencies directly using `session.install`. This can lead to inconsistencies between the dependencies used in different sessions and the dependencies defined in `pyproject.toml`. To improve this, we should centralize the dependency management by using a single source of truth for dependencies. This can be achieved by using a tool like `uv` or `pip-tools` to generate a `requirements.txt` file for each session, ensuring all nox sessions are aligned with the declared dependencies in `pyproject.toml`. **Area**: CI/CD, Developer Experience ## Subtasks - [ ] Investigate using `uv` or `pip-tools` to manage dependencies in `noxfile.py`. - [ ] Modify `noxfile.py` to use the chosen tool to generate `requirements.txt` files for each session. - [ ] Update the CI configuration to use the generated `requirements.txt` files to install dependencies. - [ ] Verify all nox sessions install dependencies consistently from the single source of truth. - [ ] Verify `nox -e lint` passes. - [ ] Verify `nox -e typecheck` passes. - [ ] Verify `nox -e unit_tests` passes. - [ ] Verify `nox -e integration_tests` passes. - [ ] Verify `nox -e coverage_report` reports >= 97%. ## Definition of Done - [ ] All nox sessions use a `requirements.txt` file (or equivalent `uv`-managed lockfile) to install dependencies. - [ ] The CI pipeline is updated to use the new dependency management system. - [ ] The overall build time is not negatively impacted by the changes. - [ ] All nox stages pass. - [ ] Coverage >= 97%. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-02 23:23:59 +00:00
Author
Owner

⚠️ Orphan Issue — Manual Linking Required

This issue could not be automatically linked to a parent Epic. No Type/Epic issue was found for the TEST-INFRA: [ci-pipeline-design] workstream.

All issues in this workstream (e.g., #1535, #1536, #1537, #1538, #1539, #1540, #1589, #1604, #1606, #1612, #1614, #1617) are similarly unlinked to a parent Epic.

Action required: A project owner should either:

  1. Create a parent Epic for the TEST-INFRA: [ci-pipeline-design] workstream and link this issue as a child (this issue should block the parent Epic), or
  2. Link this issue to an existing Epic using Forgejo's dependency system.

Per CONTRIBUTING.md, orphan issues are not permitted. This issue must be linked to a parent Epic before it can be moved to State/Verified.


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

⚠️ **Orphan Issue — Manual Linking Required** This issue could not be automatically linked to a parent Epic. No `Type/Epic` issue was found for the `TEST-INFRA: [ci-pipeline-design]` workstream. All issues in this workstream (e.g., #1535, #1536, #1537, #1538, #1539, #1540, #1589, #1604, #1606, #1612, #1614, #1617) are similarly unlinked to a parent Epic. **Action required**: A project owner should either: 1. Create a parent Epic for the `TEST-INFRA: [ci-pipeline-design]` workstream and link this issue as a child (this issue should **block** the parent Epic), or 2. Link this issue to an existing Epic using Forgejo's dependency system. Per CONTRIBUTING.md, orphan issues are not permitted. This issue must be linked to a parent Epic before it can be moved to `State/Verified`. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Closing as duplicate of #1604 (CI setup consolidation). This CI improvement is already tracked.


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

Closing as duplicate of #1604 (CI setup consolidation). This CI improvement is already tracked. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:31:03 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#1643
No description provided.