ci(pipeline): re-pin ci-pipeline.yml to standards f95130bb - #39
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
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
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. (20)
|
| Layer / File(s) | Summary |
|---|---|
Update standards workflow pin .github/workflows/standards-pipeline.yml |
The reusable hyperpolymath/standards workflow now uses commit ed5e3f651305dd1ce0d0b5d2d08b97a963634632. The no-secrets configuration and explanatory comments remain unchanged. |
Priority: ⬇️ Low
Estimated code review effort: 1 (Trivial) | ~5 minutes
Change: Bug fix
Merge Risk: ⚪ Minimal · up to 6364f
The standards workflow pin update is narrowly scoped and ready to merge.
🚥 Pre-merge checks | ✅ 4 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Title check | The title describes a re-pin of the CI pipeline, but it names f95130bb. The pull request objectives state that the actual target is ed5e3f65, so the title is misleading about the main change. |
Update the title to identify ed5e3f65 and the standards#989 re-pin, for example: ci(pipeline): re-pin standards pipeline to ed5e3f65. |
✅ Passed checks (4 passed)
| Check name | Status | Explanation |
|---|---|---|
| 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. |
| Description check | ✅ Passed | The description is related to the workflow pin update and explains the provenance comment and CI rationale. However, it describes f95130bb, while the final change targets ed5e3f65. |
✨ Finishing Touches
🛠️ Fix failing CI checks
- Commit to this branch
- Create a new PR
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.
A rabbit checks the pipeline pin
A newer commit now settles in
No secrets block is added today
The comments remain in place
The workflow hops along its way
Comment @coderabbitai help to get the list of available commands.
⛔ Do not merge — superseded by hyperpolymath/standards#989Converted to draft to keep it out of the merge queue. This is reversible: This PR re-pins Merging this would move the caller from a stale-but-latent Correct sequence: merge #989 first, then retarget this PR to #989's squash SHA 🤖 Generated with Claude Code |
|
✅ Coding Agent task started: View task and status The task will inspect the CI failures, validate its fix, and commit the fix to this branch automatically.
⏭️ 1 check(s) skipped — already failing on `main` (not caused by this PR)
|
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. 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
…3f65 (#40) ## What Re-pins `ci-pipeline.yml` from `2eb9bb19` to **`ed5e3f65`** — the squash merge of hyperpolymath/standards#989 on `main`. The provenance comment moves with the pin (a stale comment is a phantom pin). ```diff - # hyperpolymath/standards @ 2eb9bb19 — ci-pipeline.yml blob d2583657. + # hyperpolymath/standards @ ed5e3f65 — ci-pipeline.yml blob ea87c43a. - uses: .../ci-pipeline.yml@2eb9bb19d43b6285466ca36b92d1324a09e7a207 + uses: .../ci-pipeline.yml@ed5e3f651305dd1ce0d0b5d2d08b97a963634632 ``` ## Why this SHA and not `f95130bb` This supersedes #39, which targeted `f95130bb`. That SHA **predated #989 and carried both defects #989 cures** — the ledger checkout read `ref: a2ff696a` (abbreviated, so `git fetch` cannot resolve it) and `detect` did its own `exit 1`, so a ledgered repository went red regardless of its exemption. ## Verified before landing — this is the pilot of the 5-repo wave Dispatch run [35770740241](https://github.com/hyperpolymath/AcceleratorGate.jl/actions/runs/35770740241) on this branch's content is **green**, and prints the line that gates the whole wave: ``` ledger read at 'ed5e3f651305dd1ce0d0b5d2d08b97a963634632' ``` 40 hex, non-empty, and equal to the **callee's own commit** — so `job.workflow_sha` resolves correctly against the *squash* SHA, not just the PR-head commit it was first proven on. | Assertion | Result | |---|---| | Ledger SHA is 40-hex and non-empty | ✅ | | It names the callee's commit (`ed5e3f65`) | ✅ | | Empty-SHA `::error::` guard did **not** fire | ✅ | | `report` is the single judge; run is green while refusing | ✅ `REFUSED: true`, conclusion `success` | | Exemption ledger actually read | ✅ `pipeline debt: 4 repos` | | Debt named in-run | ✅ `notice` cites #967 and the removal condition | Both commits are signature-verified. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
⛔ Superseded by #40 (merged) — do not merge; kept as draft
#40 landed the correct pin and was verified green before merging — run A new branch was used rather than retargeting this one because this branch carries an This PR should be closed — I do not have permission to close it. 🤖 Generated with Claude Code |
Superseded and now empty — converted to draft; recommend closingMeasured just now: The 3 commits are ahead of Both the Worth stating plainly, because the branch name invites the opposite reading: this PR targets Converted to draft to take it out of the review queue (re-measured after: 🤖 Generated with Claude Code |
What
Re-pins this repository's
standards-pipeline.ymlcaller from2eb9bb19tof95130bb— the squash merge of hyperpolymath/standards#985.Why
2eb9bb19predates #985, which fixed theci-pipelinedetect gate. Every callerstill on the old pin runs the pre-fix gate. The workflow is
pull_request-triggeredonly, so the failure is latent: it does not manifest until the next PR is opened here.
What moves
Two lines, together:
@ 2eb9bb19 — ci-pipeline.yml blob d2583657.@ f95130bb — ci-pipeline.yml blob 8bcdeaf2.uses:ref...ci-pipeline.yml@2eb9bb19......ci-pipeline.yml@f95130bb...A SHA bump that leaves the blob comment behind is a phantom pin — it names a tree
it can no longer be checked against — so both change or neither does.
Why
f95130bband not currentmainmainhas since moved tod1bd7f42(#988, a changelog fix).f95130bbwas chosendeliberately:
ci-pipeline.ymlis byte-identical at both — blob8bcdeaf2either way.f95130bbis the reviewed revision: the commit #985 was merged as.SonarCloud Code Analysisand the mirror trio(
mirror-gitea,mirror-disroot,mirror-codeberg) — all four are listed instandards' own
config/rulesets/gates.jsonundernever_required_workflows.Nothing ci-pipeline-related is red there.
ci-pipeline.ymlpins its own sub-reusables fully-qualified at571cc734rather than./, so this pin selects only whichci-pipeline.ymlis read — not its dependencies.Verification
provenance-comment shape were both present.
2/2changed lines, no residue of2eb9bb19ord2583657, and the new SHA present.%G?=G).🤖 Generated with Claude Code
https://claude.ai/code/session_01Ji1bq3TypfycfUPAR7hSxR