chore(ci): harden workflow supply chain - #202
Merged
Merged
Conversation
yordis
commented
Jun 3, 2026
yordis
commented
Member
- Reduce mutable third-party workflow dependency risk across privileged automation paths.
- Preserve release and deployment confidence by making workflow provenance easier to audit.
PR SummaryLow Risk Overview Rust CI adds a workflow default of Reviewed by Cursor Bugbot for commit ddac1a5. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Warning Review limit reached
More reviews will be available in 25 minutes and 18 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
WalkthroughThis PR pins GitHub Actions to specific commit SHAs across all CI/CD workflows (canary container images, Rust CI, documentation pages, release artifacts, and release-please) instead of using floating version tags. No functional changes to workflow logic, build commands, artifact handling, or deployment paths are introduced. ChangesGitHub Actions Dependency Pinning
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
Code Coverage SummaryDetailsDiff against mainResults for commit: ddac1a5 Minimum allowed coverage is ♻️ This comment has been updated with latest results |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/canary-container-images.yml:
- Line 28: The checkout step currently uses actions/checkout@de0fac2... and
persists the GITHUB_TOKEN; update that checkout step to include the option
persist-credentials: false so the job does not leave credentials in the
workspace (i.e., change the actions/checkout step to pass persist-credentials:
false in its with: block), keeping the rest of the workflow unchanged.
In @.github/workflows/ci-rust.yml:
- Line 22: Update the actions/checkout steps for the lint and build jobs to
disable persisting the GITHUB_TOKEN by adding persist-credentials: false to
those checkout actions (the checkout invocation currently at the lint job around
the actions/checkout@de0fac2e450... and the similar checkout in the build job).
Keep the test job's checkout as-is (persist-credentials: true) because it needs
to push coverage artifacts; only change the checkout entries in the lint and
build jobs.
In @.github/workflows/release-artifacts.yml:
- Around line 46-57: The release workflow uses cache-enabled actions that are
unsafe for write-scoped release jobs: update the jdx/mise-action step (the
action reference jdx/mise-action@1648a7812b9aeae629881980618f079932869151) to
disable cache by adding a "with: cache: false" input, and harden the
Swatinem/rust-cache step
(Swatinem/rust-cache@c19371144df3bb44fab255c43d04cbc2ab54d1c4) by either
removing the step entirely or configuring it to be read-only/no-save (e.g., set
inputs "lookup-only: true" and "save-if: false") so no cache download/upload
occurs during release jobs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: aeac1e86-70e8-4def-983c-995e712692d8
📒 Files selected for processing (5)
.github/workflows/canary-container-images.yml.github/workflows/ci-rust.yml.github/workflows/docs-pages.yml.github/workflows/release-artifacts.yml.github/workflows/release-please.yml
yordis
force-pushed
the
yordis/chore-create-pr-v8
branch
from
June 3, 2026 20:38
1aee035 to
8aab0ea
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
yordis
force-pushed
the
yordis/chore-create-pr-v8
branch
from
June 3, 2026 20:48
8aab0ea to
d2b08eb
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d2b08eb. Configure here.
yordis
force-pushed
the
yordis/chore-create-pr-v8
branch
from
June 3, 2026 20:53
d2b08eb to
b25c756
Compare
Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
yordis
force-pushed
the
yordis/chore-create-pr-v8
branch
from
June 3, 2026 21:01
b25c756 to
ddac1a5
Compare
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.