Ansible converge: bump agentic-os pre-commit rev to v0.19.0 fleet-wide #282

New issue

Open

opened 2026-06-09 05:41:38 +00:00 by coilysiren · 0 comments

coilysiren commented

2026-06-09 05:41:38 +00:00

Owner

Context

agentic-os v0.19.0 relaxed check_catalog_block.py to require only description + dependsOn (drops kind/type/system/owner/lifecycle). The validator is released; the fleet still pins stale revs and needs to converge.

The managed .pre-commit-config.yaml block (between the # BEGIN/END managed by agentic-os/scripts/apply-agentic-os-hooks.py markers) pins rev:. This rollout is the fanout that bumps every checkout to v0.19.0+ — and per doctrine the fanout lives in infrastructure/ansible, not a hand sweep and not coily setup.

Current skew

Forgejo-pinned: v0.16.0–v0.18.0 (most flight-deck + bridge repos).
GitHub-mirror-pinned: v0.11.1, one at v0.6.0. These can only bump once v0.19.0 is visible on the read-only GitHub mirror (PR/mirror-gated) — sequence the converge after the mirror carries the tag.
ward was bumped to v0.19.0 by hand during the unblock; the converge should be idempotent over it.

Work

Ansible role/play that runs apply-agentic-os-hooks (rewrites the managed block to DEFAULT_REV) across every managed checkout, committing the rev bump per repo on its normal land flow.
Gate the GitHub-mirror-pinned repos on mirror availability of the target tag.
Idempotent: re-running converges no-op once at target rev.

Validator relaxation + release: agentic-os v0.19.0.
Deferred catalog-key strip (separate cleanup): coilyco-bridge/agentic-os-kai#643.

## Context agentic-os **v0.19.0** relaxed `check_catalog_block.py` to require only `description` + `dependsOn` (drops `kind`/`type`/`system`/`owner`/`lifecycle`). The validator is released; the fleet still pins stale revs and needs to converge. The managed `.pre-commit-config.yaml` block (between the `# BEGIN/END managed by agentic-os/scripts/apply-agentic-os-hooks.py` markers) pins `rev:`. This rollout is the fanout that bumps every checkout to v0.19.0+ — and per doctrine the fanout lives in **infrastructure/ansible**, not a hand sweep and not `coily setup`. ## Current skew - **Forgejo-pinned**: v0.16.0–v0.18.0 (most flight-deck + bridge repos). - **GitHub-mirror-pinned**: v0.11.1, one at v0.6.0. These can only bump once v0.19.0 is visible on the read-only GitHub mirror (PR/mirror-gated) — sequence the converge after the mirror carries the tag. - `ward` was bumped to v0.19.0 by hand during the unblock; the converge should be idempotent over it. ## Work - Ansible role/play that runs `apply-agentic-os-hooks` (rewrites the managed block to `DEFAULT_REV`) across every managed checkout, committing the rev bump per repo on its normal land flow. - Gate the GitHub-mirror-pinned repos on mirror availability of the target tag. - Idempotent: re-running converges no-op once at target rev. ## Related - Validator relaxation + release: agentic-os v0.19.0. - Deferred catalog-key strip (separate cleanup): coilyco-bridge/agentic-os-kai#643.

coilysiren added the

label

2026-06-17 07:06:03 +00:00

coilysiren referenced this issue from a commit

2026-06-25 12:06:53 +00:00

chore(catalog): strip deprecated catalog keys + add fleet sweep verb