From 33e9db203ad7614b49d0443456e77cb2d592f6d5 Mon Sep 17 00:00:00 2001 From: Ralf Anton Beier Date: Wed, 8 Jul 2026 12:49:45 +0200 Subject: [PATCH] chore(rivet): reconcile v0.3.6 scope to cuttable MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - SR-28 → verified: main now enforces the CI gate (branch protection set with 8 always-run core gates, enforce_admins=false; verified non-wedging against a live PR; #378 closed). - SR-25 → verified: pr-diagnostics force-checkout fix merged (#379); its diagnostics job runs green. - SR-32 (all-targets bit-rot gate) → moved v0.3.6 → v0.7.0: the bit-rot burndown + --all-targets CI gate is a large infra effort (verification/CI hardening), not the v0.3.6 CI-hygiene patch. Only phase-1 dead-deletions are done. rivet release status v0.3.6: ✓ cuttable (SR-25/27/28 all verified). validate 0 errors. Trace: SR-28 --- safety/requirements/functional-requirements.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/safety/requirements/functional-requirements.yaml b/safety/requirements/functional-requirements.yaml index 0ca684ed..dbc02fa0 100644 --- a/safety/requirements/functional-requirements.yaml +++ b/safety/requirements/functional-requirements.yaml @@ -859,7 +859,7 @@ artifacts: - id: SR-25 type: requirement title: pr-diagnostics baseline checkout must not abort on a dirtied Cargo.lock - status: implemented + status: verified description: "The pr-diagnostics workflow's baseline step checks out the PR base, builds it (which regenerates Cargo.lock and other artifacts), then checks out the PR head. The head checkout shall not abort on the dirtied baseline artifacts — they are throwaway. Regression: failed on #363 (base build touched Cargo.lock); passed on #362/#361/#359 (clean base). Workflow-mechanics bug, not a code signal; the real gates were green. Fix: force-checkout the head sha. Issue #373." tags: [ci, tooling, pr-diagnostics] fields: @@ -887,7 +887,7 @@ artifacts: - id: SR-28 type: requirement title: main branch enforces the CI gate as required status checks - status: proposed + status: verified description: "The main branch shall enforce required status checks (via ruleset or branch protection) so a PR cannot merge while checks are red, queued, or cancelled. Today required_status_checks.contexts is empty and no ruleset requires any context — CI is advisory only. Add the gate contexts (build, Core Tests/Analysis/Coverage, CI Checks & Docs, Safety Analysis with Clippy, SCORE-Inspired Safety Verification, Security Audit matrix). Issue #378." tags: [ci, release, branch-protection] fields: @@ -953,7 +953,7 @@ artifacts: created-by: ai model: claude-opus-4-8 timestamp: 2026-07-07T19:24:29Z - release: v0.3.6 + release: v0.7.0 - id: SR-33 type: requirement