agents version should include commit build. #1520

Closed
opened 2026-04-02 20:07:05 +00:00 by brent.edwards · 3 comments
Member

Here is the output of agents version:

(20260402) ➜  20260402 agents version
╭── CLI Version ───╮
│ CleverAgents CLI │
│ Version: 1.0.0   │
│ Channel: stable  │
│ Python: 3.13.12  │
╰──────────────────╯
╭──────── Build ─────────╮
│ Build Date: 2026-04-02 │
│ Commit: unknown        │
│ Schema: v3             │
│ Platform: linux-x86_64 │
╰────────────────────────╯
╭───── Dependencies ─────╮
│ langgraph: 1.1.4       │
│ langchain-core: 1.2.24 │
│ pydantic: 2.12.5       │
│ typer: 0.24.1          │
╰────────────────────────╯
OK Version reported

This lists "Commit: unknown".

The git commit that generated this build should be part of the output.

Here is the output of `agents version`: ``` (20260402) ➜ 20260402 agents version ╭── CLI Version ───╮ │ CleverAgents CLI │ │ Version: 1.0.0 │ │ Channel: stable │ │ Python: 3.13.12 │ ╰──────────────────╯ ╭──────── Build ─────────╮ │ Build Date: 2026-04-02 │ │ Commit: unknown │ │ Schema: v3 │ │ Platform: linux-x86_64 │ ╰────────────────────────╯ ╭───── Dependencies ─────╮ │ langgraph: 1.1.4 │ │ langchain-core: 1.2.24 │ │ pydantic: 2.12.5 │ │ typer: 0.24.1 │ ╰────────────────────────╯ OK Version reported ``` This lists "Commit: unknown". The git commit that generated this build should be part of the output.
brent.edwards added this to the v3.2.0 milestone 2026-04-02 20:07:05 +00:00
Owner

Thank you for filing this issue. The problem is clear and well-documented with the actual output.

Triage assessment:

The agents version command currently displays Commit: unknown because the build process does not inject the git commit hash into the version metadata. This is a straightforward fix — the build system (Hatch) needs to be configured to capture git rev-parse --short HEAD at build time and make it available to the CLI's version display logic.

Issue completeness check (per CONTRIBUTING.md):

The issue is missing a few required sections:

  • Metadata section: Needs a commit message first line and branch name. Suggested:
    • Commit message: fix(cli): inject git commit hash into agents version output
    • Branch: fix/version-commit-hash
  • Subtasks checklist: Suggested subtasks:
    • Identify where the version/build metadata is assembled (likely src/cleveragents/cli/commands/version.py or a build config)
    • Configure Hatch or the build pipeline to capture git rev-parse --short HEAD at build time
    • Update the version command to read and display the captured commit hash
    • Add/update Behave scenario verifying Commit: field shows a valid hash (not unknown)
    • Verify all nox stages pass
  • Definition of Done: PR merged, agents version shows actual commit hash, all nox stages pass, coverage >= 97%

Milestone note: This is assigned to v3.2.0 (M3), which has a past due date (2026-02-26). Given this is a Points/1 low-priority task, it may be more appropriate for a later milestone where it can be picked up without blocking higher-priority work. However, I will not reassign the milestone since a human (or the project owner) made this assignment.

The issue is clear and actionable. It does not have the needs feedback label, so it is eligible for verification once the metadata sections are added.


Automated by CleverAgents Bot
Supervisor: Human Liaison | Agent: ca-human-liaison

Thank you for filing this issue. The problem is clear and well-documented with the actual output. **Triage assessment:** The `agents version` command currently displays `Commit: unknown` because the build process does not inject the git commit hash into the version metadata. This is a straightforward fix — the build system (Hatch) needs to be configured to capture `git rev-parse --short HEAD` at build time and make it available to the CLI's version display logic. **Issue completeness check (per CONTRIBUTING.md):** The issue is missing a few required sections: - **Metadata section**: Needs a commit message first line and branch name. Suggested: - Commit message: `fix(cli): inject git commit hash into agents version output` - Branch: `fix/version-commit-hash` - **Subtasks checklist**: Suggested subtasks: - [ ] Identify where the version/build metadata is assembled (likely `src/cleveragents/cli/commands/version.py` or a build config) - [ ] Configure Hatch or the build pipeline to capture `git rev-parse --short HEAD` at build time - [ ] Update the version command to read and display the captured commit hash - [ ] Add/update Behave scenario verifying `Commit:` field shows a valid hash (not `unknown`) - [ ] Verify all nox stages pass - **Definition of Done**: PR merged, `agents version` shows actual commit hash, all nox stages pass, coverage >= 97% **Milestone note**: This is assigned to v3.2.0 (M3), which has a past due date (2026-02-26). Given this is a `Points/1` low-priority task, it may be more appropriate for a later milestone where it can be picked up without blocking higher-priority work. However, I will not reassign the milestone since a human (or the project owner) made this assignment. The issue is clear and actionable. It does not have the `needs feedback` label, so it is eligible for verification once the metadata sections are added. --- **Automated by CleverAgents Bot** Supervisor: Human Liaison | Agent: ca-human-liaison
Owner

Issue triaged by project owner:

  • State: Verified — The bug is clear and actionable despite the missing metadata sections noted by the liaison.
  • Priority: Low (already assigned) — Cosmetic issue; the version command works, it just shows Commit: unknown instead of the actual git hash.
  • Milestone: v3.2.0 (already assigned) — Note: v3.2.0 is past its due date (2026-02-26). This low-priority item should be picked up opportunistically. Not reassigning the milestone since it was set by a human.
  • MoSCoW: Should Have (already assigned) — The spec's agents version output example shows a commit hash in the Build panel. Displaying unknown is a minor spec deviation.
  • Parent Epic: Needs identification — this likely belongs under a CLI polish or build system epic.

Metadata gap: As the liaison noted, this issue is missing the required Metadata section (branch name, commit message), Subtasks checklist, and formal Definition of Done. The reporter (@brent.edwards) should add these per CONTRIBUTING.md. However, the bug itself is clear enough to verify — the fix is straightforward (inject git rev-parse --short HEAD at build time).

Suggested metadata for whoever picks this up:

  • Branch: fix/version-commit-hash
  • Commit Message: fix(cli): inject git commit hash into agents version build output

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

Issue triaged by project owner: - **State**: Verified — The bug is clear and actionable despite the missing metadata sections noted by the liaison. - **Priority**: Low (already assigned) — Cosmetic issue; the version command works, it just shows `Commit: unknown` instead of the actual git hash. - **Milestone**: v3.2.0 (already assigned) — Note: v3.2.0 is past its due date (2026-02-26). This low-priority item should be picked up opportunistically. Not reassigning the milestone since it was set by a human. - **MoSCoW**: Should Have (already assigned) — The spec's `agents version` output example shows a commit hash in the Build panel. Displaying `unknown` is a minor spec deviation. - **Parent Epic**: Needs identification — this likely belongs under a CLI polish or build system epic. **Metadata gap**: As the liaison noted, this issue is missing the required Metadata section (branch name, commit message), Subtasks checklist, and formal Definition of Done. The reporter (@brent.edwards) should add these per CONTRIBUTING.md. However, the bug itself is clear enough to verify — the fix is straightforward (inject `git rev-parse --short HEAD` at build time). Suggested metadata for whoever picks this up: - **Branch**: `fix/version-commit-hash` - **Commit Message**: `fix(cli): inject git commit hash into agents version build output` --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo self-assigned this 2026-04-02 20:59:01 +00:00
Owner

Closing — work completed in PR #1556 (merged). The PR made the agents version command show the actual git commit instead of "unknown".


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

Closing — work completed in PR #1556 (merged). The PR made the `agents version` command show the actual git commit instead of "unknown". --- **Automated by CleverAgents Bot** Supervisor: Backlog Grooming | Agent: ca-backlog-groomer
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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#1520
No description provided.