ci(pipeline): re-pin ci-pipeline.yml to standards#989 squash SHA ed5e3f65 - #40
Merged
Merged
Conversation
This caller was pinned to 2eb9bb19, which predates hyperpolymath/standards#985. That commit fixed the ci-pipeline detect gate; every caller still on 2eb9bb19 runs the pre-fix gate and goes red on its next pull_request. Re-pins to f95130bb (the #985 squash merge) and updates the provenance comment to the matching blob 8bcdeaf2. Both lines move together: a SHA bump that leaves a stale blob comment behind is a phantom pin, unverifiable against the tree it claims to name. f95130bb was chosen over current main (d1bd7f42) deliberately: ci-pipeline.yml is byte-identical at both (blob 8bcdeaf2), f95130bb is the reviewed revision, and its only red checks are SonarCloud and the mirror trio -- all four listed in standards' own config/rulesets/gates.json never_required_workflows. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR
f95130bb predated hyperpolymath/standards#989 and carried both defects that PR cures: the ledger checkout read `ref: a2ff696a` (an abbreviated SHA, which `git fetch` cannot resolve) and `detect` did its own `exit 1`, so a ledgered repository went red regardless of the exemption. Re-pins to ed5e3f65, the squash merge of #989 on standards' main, where the ledger is read at `${{ job.workflow_sha }}` and `report` is the single judge. Verified before landing: dispatch run 35770740241 on this branch is green and prints `ledger read at 'ed5e3f651305dd1ce0d0b5d2d08b97a963634632'` - the callee's own commit, 40 hex, non-empty. The provenance comment moves with the pin: a stale comment is a phantom pin. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR
|
Warning Review limit reachedNext included review available in 52 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
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. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Re-pins
ci-pipeline.ymlfrom2eb9bb19toed5e3f65— the squash merge ofhyperpolymath/standards#989 on
main. The provenance comment moves with the pin(a stale comment is a phantom pin).
Why this SHA and not
f95130bbThis supersedes #39, which targeted
f95130bb. That SHA predated #989 and carriedboth defects #989 cures — the ledger checkout read
ref: a2ff696a(abbreviated, sogit fetchcannot resolve it) anddetectdid its ownexit 1, so a ledgeredrepository went red regardless of its exemption.
Verified before landing — this is the pilot of the 5-repo wave
Dispatch run
35770740241
on this branch's content is green, and prints the line that gates the whole wave:
40 hex, non-empty, and equal to the callee's own commit — so
job.workflow_sharesolves correctly against the squash SHA, not just the PR-head commit it was first
proven on.
ed5e3f65)::error::guard did not firereportis the single judge; run is green while refusingREFUSED: true, conclusionsuccesspipeline debt: 4 reposnoticecites #967 and the removal conditionBoth commits are signature-verified.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR