UAT: pyproject.toml version (1.0.0) does not match CHANGELOG latest release (3.7.0) #4122

New issue

Open

opened 2026-04-06 10:29:26 +00:00 by freemo · 1 comment

freemo commented

2026-04-06 10:29:26 +00:00

Owner

Metadata

Branch: fix/build/pyproject-version-sync
Commit Message: fix(build): update pyproject.toml version to match CHANGELOG latest release 3.7.0
Milestone: None (backlog)
Parent Epic: #362

Summary

The version field in pyproject.toml is set to "1.0.0" but the CHANGELOG clearly shows the latest release is 3.7.0 (released 2026-04-02). This means the installed package reports the wrong version, agents --version outputs CleverAgents 1.0.0 instead of CleverAgents 3.7.0, and any tooling that reads the package version (PyPI, pip, etc.) will be incorrect.

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

What Was Tested

Read pyproject.toml line 7: version = "1.0.0"
Read CHANGELOG.md line 170: ## [3.7.0] — 2026-04-02
Read src/cleveragents/__init__.py line 8: __version__ = "1.0.0"
The [tool.commitizen] section uses version_provider = "pep621" which reads from pyproject.toml, so commitizen would also produce incorrect version bumps.

Expected Behavior (from spec/CHANGELOG)

pyproject.toml version field and src/cleveragents/__init__.py __version__ should both reflect the current release version 3.7.0 (or the next unreleased version if actively developing post-3.7.0).

Actual Behavior

# pyproject.toml line 7
version = "1.0.0"

# src/cleveragents/__init__.py line 8
__version__ = "1.0.0"

# CHANGELOG.md line 170
## [3.7.0] — 2026-04-02

Running agents --version would output:

CleverAgents 1.0.0

Steps to Reproduce

cat pyproject.toml | grep '^version' → version = "1.0.0"
cat CHANGELOG.md | grep '## \[' → ## [3.7.0] — 2026-04-02
agents --version → CleverAgents 1.0.0

Code Location

pyproject.toml, line 7
src/cleveragents/__init__.py, line 8

Fix

Update pyproject.toml line 7 to version = "3.7.0" (or the appropriate next version). The __version__ in src/cleveragents/__init__.py should be kept in sync. Since [tool.commitizen] uses version_provider = "pep621", only pyproject.toml needs to be the source of truth; __init__.py should read from importlib.metadata or be updated by commitizen automatically.

Subtasks

Update pyproject.toml version to 3.7.0
Update src/cleveragents/__init__.py __version__ to "3.7.0" or switch to importlib.metadata.version("cleveragents")
Verify agents --version outputs the correct version
Add a test that __version__ matches the version in pyproject.toml

Definition of Done

pyproject.toml version matches the latest CHANGELOG entry
agents --version outputs the correct version
Associated PR has been merged

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-uat-tester

## Metadata - **Branch**: `fix/build/pyproject-version-sync` - **Commit Message**: `fix(build): update pyproject.toml version to match CHANGELOG latest release 3.7.0` - **Milestone**: None (backlog) - **Parent Epic**: #362 ## Summary The `version` field in `pyproject.toml` is set to `"1.0.0"` but the CHANGELOG clearly shows the latest release is `3.7.0` (released 2026-04-02). This means the installed package reports the wrong version, `agents --version` outputs `CleverAgents 1.0.0` instead of `CleverAgents 3.7.0`, and any tooling that reads the package version (PyPI, pip, etc.) will be incorrect. > **Backlog note:** This issue was discovered during autonomous UAT testing. > It does not block milestone completion and has been placed in the backlog > for human review and future milestone assignment. ## What Was Tested - Read `pyproject.toml` line 7: `version = "1.0.0"` - Read `CHANGELOG.md` line 170: `## [3.7.0] — 2026-04-02` - Read `src/cleveragents/__init__.py` line 8: `__version__ = "1.0.0"` - The `[tool.commitizen]` section uses `version_provider = "pep621"` which reads from `pyproject.toml`, so commitizen would also produce incorrect version bumps. ## Expected Behavior (from spec/CHANGELOG) `pyproject.toml` `version` field and `src/cleveragents/__init__.py` `__version__` should both reflect the current release version `3.7.0` (or the next unreleased version if actively developing post-3.7.0). ## Actual Behavior ```toml # pyproject.toml line 7 version = "1.0.0" ``` ```python # src/cleveragents/__init__.py line 8 __version__ = "1.0.0" ``` ``` # CHANGELOG.md line 170 ## [3.7.0] — 2026-04-02 ``` Running `agents --version` would output: ``` CleverAgents 1.0.0 ``` ## Steps to Reproduce 1. `cat pyproject.toml | grep '^version'` → `version = "1.0.0"` 2. `cat CHANGELOG.md | grep '## \['` → `## [3.7.0] — 2026-04-02` 3. `agents --version` → `CleverAgents 1.0.0` ## Code Location - `pyproject.toml`, line 7 - `src/cleveragents/__init__.py`, line 8 ## Fix Update `pyproject.toml` line 7 to `version = "3.7.0"` (or the appropriate next version). The `__version__` in `src/cleveragents/__init__.py` should be kept in sync. Since `[tool.commitizen]` uses `version_provider = "pep621"`, only `pyproject.toml` needs to be the source of truth; `__init__.py` should read from `importlib.metadata` or be updated by commitizen automatically. ## Subtasks - [ ] Update `pyproject.toml` `version` to `3.7.0` - [ ] Update `src/cleveragents/__init__.py` `__version__` to `"3.7.0"` or switch to `importlib.metadata.version("cleveragents")` - [ ] Verify `agents --version` outputs the correct version - [ ] Add a test that `__version__` matches the version in `pyproject.toml` ## Definition of Done - [ ] `pyproject.toml` version matches the latest CHANGELOG entry - [ ] `agents --version` outputs the correct version - [ ] Associated PR has been merged --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-uat-tester

freemo referenced this issue

2026-04-06 10:32:24 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:35:53 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo added this to the v3.5.0 milestone

2026-04-06 18:07:30 +00:00

freemo commented

2026-04-06 18:45:18 +00:00

Author

Owner

Milestone Triage Decision: Moved to Backlog

This build/metadata issue has been moved out of v3.5.0 during aggressive milestone triage. While important for version consistency, it does not block core autonomy hardening functionality.

Reasoning:

v3.5.0 focus: Essential autonomy hardening (guard enforcement, A2A facade, plan lifecycle)
This issue: Version mismatch (pyproject.toml vs CHANGELOG) - metadata consistency
Impact: Version reporting accuracy, not functional capability

Will be addressed in a future milestone after core autonomy functionality is stable.

**Milestone Triage Decision: Moved to Backlog** This build/metadata issue has been moved out of v3.5.0 during aggressive milestone triage. While important for version consistency, it does not block core autonomy hardening functionality. **Reasoning:** - v3.5.0 focus: Essential autonomy hardening (guard enforcement, A2A facade, plan lifecycle) - This issue: Version mismatch (pyproject.toml vs CHANGELOG) - metadata consistency - Impact: Version reporting accuracy, not functional capability Will be addressed in a future milestone after core autonomy functionality is stable.

freemo removed this from the v3.5.0 milestone

2026-04-06 20:42:49 +00:00