Repository navigation
e-pin the estate reusables to the last accepted standards ref - #86
Merged
Merged
Conversation
Pins at `4e6ffe55`-or-later are rejected by GitHub's dependency-lockfile validation, so the callers that used them could not parse: `conclusion=failure`, **0 jobs**, run name equal to the file's path. `210f14e7` (2026-09-12T17:32:17Z) is the last ref whose pins are accepted — measured by pinning a caller at each candidate and dispatching it, not inferred. This re-points the refs here to that ref. Behaviour is otherwise unchanged; the lockfile in `hyperpolymath/standards` is the thing that has to be regenerated before a forward re-point is safe again, and the estate's own applier (`.github/workflows/apply-workflow-pins.yml`) is what should do that re-pointing once it can run.
|
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. (17)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe governance workflow now references the shared reusable workflow at a fixed commit SHA instead of the moving ChangesGovernance workflow
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Bug fix Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 reads each line, Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
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.
fix(ci): re-pin the estate reusables to the last accepted standards ref
Pins at
4e6ffe55-or-later are rejected by GitHub's dependency-lockfile validation, so thecallers that used them could not parse:
conclusion=failure, 0 jobs, run name equal to thefile's path.
210f14e7(2026-09-12T17:32:17Z) is the last ref whose pins are accepted — measured bypinning a caller at each candidate and dispatching it, not inferred.
This re-points the refs here to that ref. Behaviour is otherwise unchanged; the lockfile in
hyperpolymath/standardsis the thing that has to be regenerated before a forward re-point is safeagain, and the estate's own applier (
.github/workflows/apply-workflow-pins.yml) is what should dothat re-pointing once it can run.