precommit_hooks_rev pinned to v0.14.0 - apply would downgrade catalog hooks fleet-wide #324
Labels
No labels
burndown-2026-06
burndown-2026-08
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/advocate
role/director
role/exec
role/frontend
role/gamedev
role/human
role/platform
role/qa
role/science
role/sysadmin
state
ambient
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/infrastructure#324
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
precommit_hooks_revinansible/roles/precommit-hooks/defaults/main.ymlis pinned tov0.14.0, but:v0.16.0in their.pre-commit-config.yamlagentic-osrelease isv0.20.0So
make ansible-sync action=applywould downgrade the catalog hooks across every managed repo (v0.16.0 -> v0.14.0), and the managed block is two minor releases behind the latest regardless.Effect
make ansible-sync(check) shows a managed-block diff revertingrevand dropping newer hook ids on every repo. Apply is unsafe until the default is bumped.Fix
Bump
precommit_hooks_revto the current canonical release (v0.20.0as of filing) and re-runmake ansible-syncto confirm the diff now upgrades rather than downgrades. Consider whether the rev should be sourced from the latest tag instead of a hand-maintained default so it stops drifting.Found while running
make ansible-sync.