chore(governance): re-pin baselineRef to the v1 moving alias - #188
chore(governance): re-pin baselineRef to the v1 moving alias#188izzywdev wants to merge 1 commit into
Conversation
Was "main"; governance/versioning.md is explicit that consuming repos pin the moving major alias v1. Restores automatic propagation of the standard. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session-Id: fe3aa738-cb24-4315-a29b-29834ddea892
fuze-code-review — automated verdictNo verdict was reached — this run is NOT an approval. fuze-code-action conclusion was 'failure', not 'success' — no review was produced, so none can be approved. See the per-rung 'fuze-code-action' notices in the job log for the specific classification (availability / task / declined) and, on an availability failure, the named provider error that triggered it. This is reported as a failed check deliberately: a review that could not run must never be silently indistinguishable from a clean one. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #188 +/- ##
=======================================
Coverage 41.06% 41.06%
=======================================
Files 81 81
Lines 6171 6171
Branches 252 250 -2
=======================================
Hits 2534 2534
Misses 3634 3634
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Re-pins
.fuze/manifest.jsonbaselineRef:main->v1. One-line diff.Why
It pinned
main— the working edge.governance/versioning.md§5: "main… Not for consuming repos — unreviewed policy would propagate instantly."Note this is a convention, not a hard schema constraint:
governance/repo-manifest.schema.jsonstates the rule inbaselineRef'sdescriptionbut declares noenumorpattern, so nothing was failing validation. The drift was silent because nothing checks it.Effect
v1is the moving major alias, re-pointed on every compatible policy release, so this restores automatic propagation: the repo reconciles to the current standard on its next PR viagovernance-sync, with no per-repo fan-out.Sequencing
FuzeSDLC PR #278 (baseline v1.11.0) must merge first.
v1currently dereferences to2ffafc5(=v1.10.0), which still carries the brokenllm-endpoint/action.ymlblob78041e15; the fix (ab3f22e8, #277) and #274 are onmainonly. #278 advancesv1past both.(Note: this repo's default branch is
master, notmain.)