chore: stale agentic-os pre-commit pin (v0.21.0 → v0.65.0) #371

New issue

Closed

opened 2026-06-18 02:42:35 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-06-18 02:42:35 +00:00

Owner

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

No retired hooks present, but the pin is behind. Refreshing keeps hook IDs and renames (e.g. validate-skills → check-skills) in sync with the suite.

Fix

From the agentic-os checkout:

python3 scripts/apply-agentic-os-hooks.py --repo infrastructure --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.21.0`; current suite is `v0.65.0`. No retired hooks present, but the pin is behind. Refreshing keeps hook IDs and renames (e.g. `validate-skills` → `check-skills`) in sync with the suite. ### Fix From the `agentic-os` checkout: ``` python3 scripts/apply-agentic-os-hooks.py --repo infrastructure --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.

coilysiren referenced this issue

2026-06-18 02:52:56 +00:00

feat(ansible): full-auto Goose job to converge fleet agentic-os pre-commit pins #372

coilysiren added the

headless

labels

2026-06-18 06:25:32 +00:00

coilyco-ops commented

2026-07-01 08:11:11 +00:00

Member

🔒 Reserved by ward agent --driver claude — container engineer-claude-infrastructure-371 on host kais-macbook-pro-2.local is carrying this issue (reserved 2026-07-01T08:11:10Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); --force overrides.

— Claude (she/her), via ward agent

🔒 Reserved by `ward agent --driver claude` — container `engineer-claude-infrastructure-371` on host `kais-macbook-pro-2.local` is carrying this issue (reserved 2026-07-01T08:11:10Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (2h0m0s TTL); `--force` overrides.  — Claude (she/her), via `ward agent`

coilysiren referenced this issue from a commit

2026-07-01 08:14:15 +00:00

chore(pre-commit): refresh agentic-os pin v0.21.0 -> v0.65.0

coilysiren closed this issue

2026-07-01 08:14:15 +00:00

coilysiren commented

2026-07-01 08:14:55 +00:00

Author

Owner

WARD-OUTCOME: done - refreshed agentic-os pre-commit pin v0.21.0 -> v0.65.0, retired merge-conflicts hook dropped, upstream check-merge-conflict block picked up

Straightforward one-liner in spirit but a couple of small things fought back. The sanctioned script discovers repos by globbing PROJECTS_ROOT//, which does not match this container's flat /workspace/infrastructure layout, so I pointed it at a throwaway symlink tree to run it faithfully rather than hand-editing the block. The diff came out exactly as expected: the retired in-catalog merge-conflicts hook drops out and the displaced upstream pre-commit-hooks check-merge-conflict block comes in.

One surprise: pylint failed on the first pre-commit run because uv could not write to /opt/uv/python in the sandbox. Pointing UV_PYTHON_INSTALL_DIR at a writable tmp dir cleared it, and that hook is unrelated to this change anyway. All managed agentic-os hooks passed green at v0.65.0.

Confident in the result. The change is a pure config pin bump validated by the very hooks it updates. Push needed a rebase since main moved twice underneath me during a busy fleet sweep, but landed clean. No follow-ups worth filing.

WARD-OUTCOME: done - refreshed agentic-os pre-commit pin v0.21.0 -> v0.65.0, retired merge-conflicts hook dropped, upstream check-merge-conflict block picked up Straightforward one-liner in spirit but a couple of small things fought back. The sanctioned script discovers repos by globbing PROJECTS_ROOT/<org>/<name>, which does not match this container's flat /workspace/infrastructure layout, so I pointed it at a throwaway symlink tree to run it faithfully rather than hand-editing the block. The diff came out exactly as expected: the retired in-catalog merge-conflicts hook drops out and the displaced upstream pre-commit-hooks check-merge-conflict block comes in. One surprise: pylint failed on the first pre-commit run because uv could not write to /opt/uv/python in the sandbox. Pointing UV_PYTHON_INSTALL_DIR at a writable tmp dir cleared it, and that hook is unrelated to this change anyway. All managed agentic-os hooks passed green at v0.65.0. Confident in the result. The change is a pure config pin bump validated by the very hooks it updates. Push needed a rebase since main moved twice underneath me during a busy fleet sweep, but landed clean. No follow-ups worth filing.