Skip to content

fix(ci): pin standards reusables to default-branch HEAD - #86

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/bump-diverged-standards-pin
Sep 9, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/bump-diverged-standards-pin

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Re-points this repo's hyperpolymath/standards reusable-workflow pins at the standards default-branch HEAD, 8f2ee50841e216cd8c192eeb68953118190f105c.

Why this is not a routine version bump. uses: org/repo/.github/workflows/x.yml@<ref> is resolved at workflow startup, so a bad ref is not a failing job — it is no job at all. This campaign repairs three kinds of drift and does not assume which one this repo had:

  • an unreachable sha kills the run before any job is created, so GitHub reports no check at all rather than a failing one: the gate does not go red, it disappears, and gh pr checks simply lists fewer rows. A repo in this state looks greener than one with working gates;
  • a floating ref such as @main runs, but unpinned — the supply-chain property the estate pins for is absent;
  • a stale but reachable sha runs the reusable as it was, silently reintroducing every bug fixed since it.

The refs this repo was actually pinned to, before this PR: 571cc734cd69fb846032ec77a662aa8ee4fc32cd 81dbf2dd854b1444fd6236fa2352474383b2c2b9 c65436ee3351cd6b0fa14b142938b195efc77586 fad242d35291de1898242d6737ba02b74a59a2f2.

Expect this PR to surface failures that main does not show. Those failures are revealed, not introduced — they are the gates resuming work after being silently absent. The honest comparison is the set of check names emitted here versus on main, not pass/fail counts. On the canary (hyperpolymath/empty-linter#79) the governance suite was absent on main and emitted 25 checks once repaired.

The target is default-branch HEAD resolved at sweep time, never a sha copied from a plan: a reachable but non-HEAD sha silently reintroduces every bug fixed since it.

Engine: .git-private-farm/scripts/smtp-notify-sweep.sh --campaign campaigns/pin-repair.sh. Verification for this repo: files=6 pins=6 perms=0 permlines=0 from=571cc734cd69fb846032ec77a662aa8ee4fc32cd,81dbf2dd854b1444fd6236fa2352474383b2c2b9,c65436ee3351cd6b0fa14b142938b195efc77586,fad242d35291de1898242d6737ba02b74a59a2f2 target=8f2ee508 sig=G d3e7c0f canon=a7325fbdc356 base=main

🤖 Generated with Claude Code

https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB

This repo's standards reusable pins are re-pointed at the standards default-branch HEAD, resolved live at sweep time. The prior refs are recorded in the verification line below. Three kinds of drift are repaired together and the body does not claim which one this repo had: an UNREACHABLE sha kills the run at workflow STARTUP, so GitHub reports no check at all rather than a failing one and the gate disappears instead of going red; a FLOATING ref (@main) is unpinned supply chain; a merely STALE but reachable sha silently reintroduces every bug fixed since it. files=6 pins=6 perms=0 permlines=0 from=571cc734cd69fb846032ec77a662aa8ee4fc32cd,81dbf2dd854b1444fd6236fa2352474383b2c2b9,c65436ee3351cd6b0fa14b142938b195efc77586,fad242d35291de1898242d6737ba02b74a59a2f2 target=8f2ee508

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0178nN4Nm3neFRy5K9StZKnB
@coderabbitai

coderabbitai Bot commented Sep 9, 2026 •

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 6637ac89-3a85-448f-9d76-9f623aa9ca75

📥 Commits

Reviewing files that changed from the base of the PR and between b037578 and d3e7c0f.

📒 Files selected for processing (6)
  • .github/workflows/governance.yml
  • .github/workflows/hypatia-scan.yml
  • .github/workflows/mirror.yml
  • .github/workflows/rust-ci.yml
  • .github/workflows/scorecard.yml
  • .github/workflows/secret-scanner.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
⏰ Context from checks skipped due to timeout. (39)
  • GitHub Check: Burrower proof safety
  • GitHub Check: scan / shell-secrets
  • GitHub Check: scan / gitleaks
  • GitHub Check: governance / Trusted-base reduction policy
  • GitHub Check: governance / Workflow security linter
  • GitHub Check: governance / Exemption ratchet
  • GitHub Check: governance / Licence consistency
  • GitHub Check: governance / Check Workflow Staleness
  • GitHub Check: governance / Debt ratchet
  • GitHub Check: scan / rust-secrets
  • GitHub Check: governance / Actions lockfile verify
  • GitHub Check: governance / Language / package anti-pattern policy
  • GitHub Check: governance / Code quality + docs
  • GitHub Check: rust-ci / Detect Cargo.toml
  • GitHub Check: governance / Security policy checks
  • GitHub Check: governance / Live Actions policy (credentialed advisory)
  • GitHub Check: governance / Allowlist Preflight
  • GitHub Check: governance / Well-Known (RFC 9116 + RSR)
  • GitHub Check: scan / Hypatia Neurosymbolic Analysis
  • GitHub Check: governance / Guix packaging policy (Nix retired)
  • GitHub Check: check
  • GitHub Check: lint
  • GitHub Check: panic-attack assail
  • GitHub Check: docs
  • GitHub Check: Build Ddraig Pages artifact
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: lint-workflows
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Patch Bridge CVE triage
  • GitHub Check: analyze (actions, none)
  • GitHub Check: check
  • GitHub Check: Groove manifest check
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Runtime Policy
  • GitHub Check: Validate A2ML manifests
  • GitHub Check: estate-audit
  • GitHub Check: openssf-compliance
  • GitHub Check: lint-workflows
🔇 Additional comments (6)
.github/workflows/governance.yml (1)

18-18: LGTM!

.github/workflows/hypatia-scan.yml (1)

21-21: LGTM!

.github/workflows/mirror.yml (1)

13-13: LGTM!

.github/workflows/rust-ci.yml (1)

17-17: LGTM!

.github/workflows/scorecard.yml (1)

17-17: LGTM!

.github/workflows/secret-scanner.yml (1)

19-19: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the pinned versions of shared governance, security scanning, mirroring, Rust CI, scorecard, and secret-scanning workflows.
    • Existing workflow triggers, permissions, secrets handling, and behaviour remain unchanged.

Walkthrough

Six GitHub Actions workflows now reference updated pinned commits of reusable workflows from hyperpolymath/standards. No workflow logic, permissions, triggers, or secrets handling changed.

Changes

Reusable workflow pin updates

Layer / File(s) Summary
Update reusable workflow pins
.github/workflows/governance.yml, .github/workflows/hypatia-scan.yml, .github/workflows/mirror.yml, .github/workflows/rust-ci.yml, .github/workflows/scorecard.yml, .github/workflows/secret-scanner.yml
The governance, Hypatia scan, mirror, Rust CI, scorecard, and secret scanner jobs now use updated pinned commits for their shared reusable workflows.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to d3e7c

The workflows now run updated pinned shared governance, CI, scanning, mirroring, and scorecard workflows without changing their local configuration. No current merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the workflow pin updates, the reason for the change, the previous references, the target commit, and verification results. However, it omits the required template headings and… Add the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. Complete the checklist and state which tests and checks were run, or explain why they were not applicable. Keep the existing rationale and verifica…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: pinning CI reusable workflows to the standards default-branch HEAD.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Description check

Explanation

The description explains the workflow pin updates, the reason for the change, the previous references, the target commit, and verification results. However, it omits the required template headings and checklist, and it does not provide explicit testing, formatting, lint, or applicability assessments.

Resolution

Add the required Summary, Changes, RSR Quality Checklist, Testing, and Screenshots sections. Complete the checklist and state which tests and checks were run, or explain why they were not applicable. Keep the existing rationale and verification details as supporting information.

🤖 Coding task started


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks each workflow line
Six pins now point to one new sign
The scanners hop in steady time
CI follows the updated sign
Governance rests in order fine

Comment @coderabbitai help to get the list of available commands.

@coderabbitai

coderabbitai Bot commented Sep 9, 2026 •

Copy link
Copy Markdown
Contributor

@hyperpolymath
hyperpolymath merged commit 8082414 into main Sep 9, 2026
52 checks passed
@hyperpolymath
hyperpolymath deleted the fix/bump-diverged-standards-pin branch September 9, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant