chore(ci): bump governance-reusable pin to standards main - #53
Open
hyperpolymath wants to merge 1 commit into
Open
chore(ci): bump governance-reusable pin to standards main#53hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
The pinned revision carries bugs that make Governance red on every consumer: the Workflow security linter runs update-actions-lock.sh from the CALLER's checkout where it does not exist (exit 127), and Allowlist Preflight runs check-actions-policy.sh with an empty GH_TOKEN (exit 3). Both are fixed on standards main. Witnessed green on hyperpolymath/blocky-writer at this exact SHA: governance run completed/success, 15/15 jobs. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team 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. (21)
🔇 Additional comments (1)
📝 SummarySummary by CodeRabbit
WalkthroughThe governance workflow now references a newer pinned commit of the shared reusable governance workflow. ChangesGovernance workflow
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This updates the shared governance workflow to a fixed commit revision. No current merge-blocking risk is identified. Poem
🚥 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. Comment |
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
🔍 Hypatia Security ScanFindings: 44 issues detected
View findings[
{
"reason": "Issue in codeql.yml",
"type": "missing_timeout_minutes",
"file": "codeql.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in label-triage.yml",
"type": "missing_timeout_minutes",
"file": "label-triage.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in labels.yml",
"type": "missing_timeout_minutes",
"file": "labels.yml",
"action": "flag",
"rule_module": "workflow_audit",
"severity": "medium"
},
{
"reason": "Issue in scorecard-enforcer.yml",
"type": "scorecard_publish_with_run_step",
"file": "scorecard-enforcer.yml",
"action": "split_scorecard_publish_job",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Issue in instant-sync.yml",
"type": "secret_action_without_presence_gate",
"file": "instant-sync.yml",
"action": "peter-evans/repository-dispatch",
"rule_module": "workflow_audit",
"severity": "high"
},
{
"reason": "Required file missing (condition: public_repo)",
"type": "missing_requirement",
"file": "SECURITY.md",
"action": "create",
"rule_module": "cicd_rules",
"severity": "high"
},
{
"reason": "Download-and-execute pattern (curl|wget pipe to shell) -- verify integrity before execution (2 occurrences, CWE-494)",
"type": "shell_download_then_run",
"file": "/home/runner/work/live-files/live-files/setup.sh",
"action": "flag",
"rule_module": "code_safety",
"severity": "high"
},
{
"reason": "No SECURITY.md found in live-files",
"type": "SecurityPolicy",
"file": "/home/runner/work/live-files/live-files",
"action": "auto_fix",
"rule_module": "scorecard",
"severity": "medium",
"remediation": "Add SECURITY.md documenting how to report vulnerabilities.",
"scorecard_check": "Security-Policy"
},
{
"reason": "Code scanning (Hypatia): hypatia/workflow_audit/missing_timeout_minutes -- Hypatia workflow_audit: missing_timeout_minutes -- 11 day(s) old",
"type": "CSA001",
"file": "labels.yml",
"action": "review",
"rule_module": "code_scanning_alerts",
"severity": "medium"
},
{
"reason": "Code scanning (Hypatia): hypatia/workflow_audit/missing_timeout_minutes -- Hypatia workflow_audit: missing_timeout_minutes -- 11 day(s) old",
"type": "CSA001",
"file": "label-triage.yml",
"action": "review",
"rule_module": "code_scanning_alerts",
"severity": "medium"
}
]Powered by Hypatia Neurosymbolic CI/CD Intelligence |
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.
Pinned revision
81dbf2ddofgovernance-reusable.ymlcarries two bugs that make Governance red on every consumer:bash scripts/update-actions-lock.sh --verify-localin the caller's checkout, where the script does not exist — exit 127.check-actions-policy.shwith an emptyGH_TOKEN—ghrefuses, exit 3.Both are cured on
standardsmain (fad242d35291de1898242d6737ba02b74a59a2f2): the verifier is copied into\$RUNNER_TEMP, and the policy step is skipped when no credential is supplied.Witness: verified green on hyperpolymath/blocky-writer#55 at this exact SHA — governance run
completed/success, 15/15 jobs, including the two jobs that were red on that repo's default branch.Judge this PR by the set difference against your own default branch (which governance jobs are newly red), not by overall check colour — unrelated build failures may pre-date it.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com