chore(deps): update behave dependency pin to allow future patch/minor upgrades #3102

Open
opened 2026-04-05 06:14:26 +00:00 by freemo · 2 comments
Owner

Metadata

  • Branch: chore/deps/update-behave-pin
  • Commit Message: chore(deps): update behave dependency pin to allow future patch/minor upgrades
  • Milestone: Backlog (no milestone assigned — see note below)
  • Parent Epic: #946

Background

The project currently pins behave==1.3.3 (exact pin) in two places in pyproject.toml (lines 65 and 80). While 1.3.3 is the current latest release on PyPI, an exact pin prevents automatic uptake of future patch or minor releases that may include bug fixes, security patches, or compatibility improvements.

The behave package is the project's primary unit-testing framework (Cucumber/Gherkin), used for all tests under features/. Keeping it pinned to an exact version increases maintenance burden and risks falling behind on fixes.

Subtasks

  • Review behave changelog and release history to confirm no breaking changes in any 1.3.x releases
  • Update pyproject.toml line 65: change "behave==1.3.3" to "behave>=1.3.3,<2.0.0"
  • Update pyproject.toml line 80: change "behave==1.3.3" to "behave>=1.3.3,<2.0.0"
  • Run nox -e unit_tests to confirm all Behave tests pass with the relaxed pin
  • Run nox -e coverage_report to confirm coverage remains >= 97%
  • Run full nox suite to confirm all quality gates pass

Definition of Done

  • Both behave==1.3.3 exact pins in pyproject.toml replaced with behave>=1.3.3,<2.0.0
  • All nox stages pass
  • Coverage >= 97%
  • PR merged to master with commit message matching the Conventional Changelog format above
  • This issue closed via ISSUES CLOSED: #<N> in the commit footer

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: Unknown | Agent: ca-new-issue-creator

## Metadata - **Branch**: `chore/deps/update-behave-pin` - **Commit Message**: `chore(deps): update behave dependency pin to allow future patch/minor upgrades` - **Milestone**: Backlog (no milestone assigned — see note below) - **Parent Epic**: #946 ## Background The project currently pins `behave==1.3.3` (exact pin) in two places in `pyproject.toml` (lines 65 and 80). While `1.3.3` is the current latest release on PyPI, an exact pin prevents automatic uptake of future patch or minor releases that may include bug fixes, security patches, or compatibility improvements. The `behave` package is the project's primary unit-testing framework (Cucumber/Gherkin), used for all tests under `features/`. Keeping it pinned to an exact version increases maintenance burden and risks falling behind on fixes. ## Subtasks - [ ] Review `behave` changelog and release history to confirm no breaking changes in any `1.3.x` releases - [ ] Update `pyproject.toml` line 65: change `"behave==1.3.3"` to `"behave>=1.3.3,<2.0.0"` - [ ] Update `pyproject.toml` line 80: change `"behave==1.3.3"` to `"behave>=1.3.3,<2.0.0"` - [ ] Run `nox -e unit_tests` to confirm all Behave tests pass with the relaxed pin - [ ] Run `nox -e coverage_report` to confirm coverage remains >= 97% - [ ] Run full `nox` suite to confirm all quality gates pass ## Definition of Done - [ ] Both `behave==1.3.3` exact pins in `pyproject.toml` replaced with `behave>=1.3.3,<2.0.0` - [ ] All nox stages pass - [ ] Coverage >= 97% - [ ] PR merged to `master` with commit message matching the Conventional Changelog format above - [ ] This issue closed via `ISSUES CLOSED: #<N>` in the commit footer > **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: Unknown | Agent: ca-new-issue-creator
Author
Owner

State transition requested: Unverified -> Verified for issue #3102 (depends: dependency maintenance task to update behave pin to allow future patch/minor upgrades).

Preconditions:

  • Current state label: State/Unverified (will be removed)
  • Paused/Blocked: None
  • Blocking label: none

Actions planned:

  • Remove old state label: State/Unverified
  • Add new state label: State/Verified
  • If the issue has a Blocked label and we were transitioning to In Progress, would remove Blocked; not applicable here.

Status: Attempted to apply changes via API. This environment currently lacks a direct label-management endpoint in the Forgejo toolset, so I cannot remove/add labels programmatically right now. A maintainer should run the following to complete the transition:

  • Remove State/Unverified label
  • Add State/Verified label
  • If the issue had Blocked label and we go to In Progress, remove Blocked; not needed here.

Notes: The issue is a valid dependency maintenance task about updating behave pin to allow future upgrades.


Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-state-updater

State transition requested: Unverified -> Verified for issue #3102 (depends: dependency maintenance task to update behave pin to allow future patch/minor upgrades). Preconditions: - Current state label: State/Unverified (will be removed) - Paused/Blocked: None - Blocking label: none Actions planned: - Remove old state label: State/Unverified - Add new state label: State/Verified - If the issue has a Blocked label and we were transitioning to In Progress, would remove Blocked; not applicable here. Status: Attempted to apply changes via API. This environment currently lacks a direct label-management endpoint in the Forgejo toolset, so I cannot remove/add labels programmatically right now. A maintainer should run the following to complete the transition: - Remove State/Unverified label - Add State/Verified label - If the issue had Blocked label and we go to In Progress, remove Blocked; not needed here. Notes: The issue is a valid dependency maintenance task about updating behave pin to allow future upgrades. --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-state-updater
freemo added this to the v3.8.0 milestone 2026-04-05 06:32:16 +00:00
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — dependency pin relaxation; no urgency since behave 1.3.3 is working correctly
  • Milestone: v3.8.0
  • MoSCoW: Could Have — relaxing the behave pin from exact to range is a maintenance convenience. The current exact pin is not causing any issues. This can be done opportunistically when convenient.
  • Parent Epic: #946

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — dependency pin relaxation; no urgency since behave 1.3.3 is working correctly - **Milestone**: v3.8.0 - **MoSCoW**: Could Have — relaxing the behave pin from exact to range is a maintenance convenience. The current exact pin is not causing any issues. This can be done opportunistically when convenient. - **Parent Epic**: #946 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo removed this from the v3.8.0 milestone 2026-04-07 00:19:31 +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.

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