chore: stale agentic-os pre-commit pin (v0.11.1) still ships 2 retired commit-msg hook(s) #31

Closed
opened 2026-06-18 02:42:31 +00:00 by coilysiren · 2 comments
Owner

The managed agentic-os block in this repo's .pre-commit-config.yaml is pinned at v0.11.1; current suite is v0.65.0.

Actively blocking commits. The block still lists retired commit-msg-stage hook(s) (conventional-commit and/or closes-issue) that were deleted from the suite. They fire a phantom check on every commit.

Fix

From the agentic-os checkout:

python3 scripts/apply-agentic-os-hooks.py --repo galaxy-gen --rev v0.65.0

That regenerates the managed block (dropping retired hooks, picking up renames) and re-runs pre-commit install. Commit the resulting .pre-commit-config.yaml change.

Context

Found during a fleet sweep kicked off when conventional-commit blocked a commit in cli-guard (since fixed to v0.65.0). Every repo except cli-guard is behind on the pin.

The managed `agentic-os` block in this repo's `.pre-commit-config.yaml` is pinned at `v0.11.1`; current suite is `v0.65.0`. **Actively blocking commits.** The block still lists retired `commit-msg`-stage hook(s) (`conventional-commit` and/or `closes-issue`) that were deleted from the suite. They fire a phantom check on every commit. ### Fix From the `agentic-os` checkout: ``` python3 scripts/apply-agentic-os-hooks.py --repo galaxy-gen --rev v0.65.0 ``` That regenerates the managed block (dropping retired hooks, picking up renames) and re-runs `pre-commit install`. Commit the resulting `.pre-commit-config.yaml` change. ### Context Found during a fleet sweep kicked off when `conventional-commit` blocked a commit in `cli-guard` (since fixed to `v0.65.0`). Every repo except `cli-guard` is behind on the pin.
Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-galaxy-gen-31 on host KAI-DESKTOP-TOWER is carrying this issue (reserved 2026-07-04T17:49:43Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

— Claude (she/her), via ward agent

<!-- ward-agent-reservation --> 🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-galaxy-gen-31` on host `KAI-DESKTOP-TOWER` is carrying this issue (reserved 2026-07-04T17:49:43Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh** — that is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <!-- ward-agent-signature --> — Claude (she/her), via `ward agent`
Author
Owner

WARD-OUTCOME: done - bumped the managed agentic-os pre-commit pin to the current suite (v0.166.0 -> v0.193.0), landed on main.

This one turned out to be mostly already-fixed. The issue's premise (pinned at v0.11.1, still shipping the retired conventional-commit / closes-issue commit-msg hooks) was stale - commit f570869 had already regenerated the block to v0.166.0 and dropped those hooks, so no phantom checks were firing anymore. What was left was genuine drift: the pin trailing the current suite release.

The one wrinkle was the fleet script (apply-agentic-os-hooks.py) discovers repos under ~/projects/<org>/*, which doesn't match this container's /workspace/galaxy-gen layout. Pointing PROJECTS_ROOT=/workspace at it made discovery work cleanly, and the generated diff was a single-line rev bump - the hook id set is identical between the two revs, so nothing else moved. All v0.193.0 hooks passed on commit.

Confident in the result: it's a one-line pin bump verified by a clean pre-commit run. No follow-ups worth filing.

WARD-OUTCOME: done - bumped the managed agentic-os pre-commit pin to the current suite (v0.166.0 -> v0.193.0), landed on main. This one turned out to be mostly already-fixed. The issue's premise (pinned at v0.11.1, still shipping the retired `conventional-commit` / `closes-issue` commit-msg hooks) was stale - commit f570869 had already regenerated the block to v0.166.0 and dropped those hooks, so no phantom checks were firing anymore. What was left was genuine drift: the pin trailing the current suite release. The one wrinkle was the fleet script (`apply-agentic-os-hooks.py`) discovers repos under `~/projects/<org>/*`, which doesn't match this container's `/workspace/galaxy-gen` layout. Pointing `PROJECTS_ROOT=/workspace` at it made discovery work cleanly, and the generated diff was a single-line rev bump - the hook id set is identical between the two revs, so nothing else moved. All v0.193.0 hooks passed on commit. Confident in the result: it's a one-line pin bump verified by a clean pre-commit run. No follow-ups worth filing.
Sign in to join this conversation.
No description provided.