Skip to content

Execution Log: --version derives from package metadata

Append-only log of progress for the user's visibility.

Phase transitions

PhaseEnteredReviewed/approved byNotes
requirements-definition2026-07-23@MadaraUchiha-314Bug: --version frozen at hardcoded 0.1.0 (issue #78)
design2026-07-23@MadaraUchiha-314Derive from importlib.metadata, drop the duplicate literal
tasks-breakdown2026-07-23@MadaraUchiha-3145-task DAG
implementation2026-07-23Implemented on claude/github-issue-78-5i8j1x
needs-review2026-07-23PR opened; awaiting human review
complete

Progress entries

2026-07-23 — implemented

  • Phase: implementation → needs-review
  • Did:
    • cli/the_loop/__init__.py: __version__ now derives from importlib.metadata.version("the-loopy-one") with a 0.0.0+unknown fallback for an uninstalled source tree — no longer a hardcoded "0.1.0".
    • cli/the_loop/webhook/server.py: server_version built from __version__ instead of the hardcoded "the-loop-gh-webhook/0.1.0".
    • cli/tests/test_cli.py: added regression tests asserting __version__ matches installed metadata, is not "0.1.0", and that --version prints the-loop <version>.
    • docs/capabilities/cli.md: documented the derived-version behaviour + history row.
  • Checkpoint/tests: ruff check, ruff format --check, pyright (0 errors), pytest — 241 passed. Under uv the package is installed, so --version reports 0.14.0.
  • Next: open PR, request review.
  • Blockers: none.

Review cycles

CycleType (self/critic)ReviewerOutcomeLink

Final validation evidence

Recorded on the PR: local gate output (ruff/pyright/pytest) and uv run --project cli python -c "import the_loop; print(the_loop.__version__)" printing the installed version (0.14.0) rather than 0.1.0.

Released under the MIT License.