Skip to content

fix(ci): pin third-party actions to full commit SHAs - #70

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/sha-pin-actions
Sep 20, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
fix/sha-pin-actions

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

fix(ci): pin third-party actions to full commit SHAs

The account's Actions policy requires a full-length SHA ref. A tag or branch ref is refused at
startup — startup_failure, no jobs, "this workflow graph cannot be shown" — so these workflows
could not run at all. This resolves each ref to the commit it currently points at and records the
ref in a trailing comment, e.g. actions/checkout@<sha> # v4.

dtolnay/rust-toolchain takes its toolchain from the ref itself, so those steps also gained an
explicit with: toolchain: input; without it, a SHA ref would silently lose the channel.

No behaviour is intended to change beyond the pins.

The account's Actions policy requires a full-length SHA ref. A tag or branch ref is refused at
startup — `startup_failure`, no jobs, "this workflow graph cannot be shown" — so these workflows
could not run at all. This resolves each ref to the commit it currently points at and records the
ref in a trailing comment, e.g. `actions/checkout@<sha> # v4`.

`dtolnay/rust-toolchain` takes its toolchain from the ref itself, so those steps also gained an
explicit `with: toolchain:` input; without it, a SHA ref would silently lose the channel.

No behaviour is intended to change beyond the pins.
@coderabbitai

coderabbitai Bot commented Sep 19, 2026

Copy link
Copy Markdown

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: 08a52a23-d2ae-416c-97e3-0dbf5b59f6e6

📥 Commits

Reviewing files that changed from the base of the PR and between 798b24b and b5d1d0d.

📒 Files selected for processing (1)
  • .github/workflows/rhodibot.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. (13)
  • GitHub Check: scan / rust-secrets
  • GitHub Check: scan / gitleaks
  • GitHub Check: scan / shell-secrets
  • GitHub Check: rust-ci / Detect Cargo.toml
  • GitHub Check: validate
  • GitHub Check: Hypatia neurosymbolic scan
  • GitHub Check: analyze (actions, none)
  • GitHub Check: panic-attack assail
  • GitHub Check: Empty-linter (invisible characters)
  • GitHub Check: Validate eclexiaiser manifest
  • GitHub Check: Validate K9 contracts
  • GitHub Check: Validate A2ML manifests
  • GitHub Check: Groove manifest check
🔇 Additional comments (1)
.github/workflows/rhodibot.yml (1)

37-37: LGTM!


📝 Summary

Summary by CodeRabbit

  • Chores
    • Improved the reliability and security of the automated release workflow by locking its tooling to a verified version.
    • No changes were made to application behaviour or user-facing features.

Walkthrough

The canary workflow now references actions/checkout by commit SHA instead of the mutable v7.0.1 tag. No other workflow behaviour changed.

Changes

Checkout action pinning

Layer / File(s) Summary
Pin the canary checkout action
.github/workflows/rhodibot.yml
The canary job now uses commit 3d3c42e5aac5ba805825da76410c181273ba90b1, annotated as v7.0.1, for actions/checkout.

Priority: ⬇️ Low

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

Change: Bug fix

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description explains the policy requirement, the SHA pinning approach, the rust-toolchain handling, and the intended behaviour. However, it does not use the required template sections and omits th… Update the description to include the required Summary, Changes, RSR Quality Checklist, and Testing sections. Complete each applicable checklist item, and add testing evidence or state why testing is not applicable. Include screenshots or t…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly states the main change: pinning third-party actions to full commit SHAs. It is concise and specific.
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 policy requirement, the SHA pinning approach, the rust-toolchain handling, and the intended behaviour. However, it does not use the required template sections and omits the RSR Quality Checklist, testing details, and screenshots or terminal output where applicable.

Resolution

Update the description to include the required Summary, Changes, RSR Quality Checklist, and Testing sections. Complete each applicable checklist item, and add testing evidence or state why testing is not applicable. Include screenshots or terminal output if applicable.

  • Fix all pre-merge checks with AI

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 the canary lane
A fixed commit guards the train
No shifting tag can hop away
The workflow stays on track today
One small pin, and all is clear

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

@hyperpolymath
hyperpolymath merged commit 3b2419d into main Sep 20, 2026
19 of 22 checks passed
@hyperpolymath
hyperpolymath deleted the fix/sha-pin-actions branch September 20, 2026 00:57
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