Skip to content

ci: pin actions to SHAs and limit contents:write to the release job - #21

Merged
devin-ai-integration[bot] merged 1 commit into
mainfrom
devin/1795096372-ci-hardening
Nov 19, 2026
Merged

devin-ai-integration[bot] merged 1 commit into
mainfrom
devin/1795096372-ci-hardening

Conversation

@devin-ai-integration

@devin-ai-integration devin-ai-integration Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • release.yml: workflow default is contents: read; only the release job gets contents: write, so validate (build, test, lint) runs read-only.
  • Pins every uses: reference to a full commit SHA (with the version as a comment), so a moved tag can't change what CI runs. Generated with pinact; no behavior change.

Review & Testing Checklist for Human

  • Next tag release still publishes

Notes

actionlint passes on the changed workflows (runner-label warnings only). CI on this PR exercises them.

Link to Devin session: https://app.devin.ai/sessions/9b3bc60266c8406ea8c2b26d7bea9587
Open in Devin Desktop: https://app.devin.ai/desktop/session/9b3bc60266c8406ea8c2b26d7bea9587?variant=devin


Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.


🟢 Devin Review found nothing to fix · View findings

Devin Review

Summary by CodeRabbit

  • Chores
    • Updated the continuous integration and release workflows to use specific versions of their setup actions.
    • Limited release write access to the job that creates releases; other workflow tasks retain read-only access. These changes affect build and release automation and do not change product functionality.

Pin actions to commit SHAs, pass expressions to shell via env, and scope tokens/permissions to what each job uses.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

  • Disable automatic comment, CI, and merge conflict monitoring

@coderabbitai

coderabbitai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The CI and release workflows now pin checkout and Go setup actions to commit SHAs. The release workflow sets top-level contents permission to read and grants contents write to the release job.

Changes: Workflow hardening

Layer / File(s) Summary
Pin actions and scope release permissions
.github/workflows/ci.yml, .github/workflows/release.yml
The workflows pin action references to commit SHAs. The release workflow sets top-level contents permission to read and grants contents write to the release job.

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other

Possibly related PRs

  • sageox/agentx#20: Also pins GitHub Actions and scopes token permissions in workflows.

Suggested reviewers: rsnodgrass

Merge Risk: Minimal · up to a7f5a

The change hardens CI and release workflows by pinning actions to commit SHAs and limiting write access to the release job. No behavior change is expected and no merge-blocking risk was found. The next tag release should be confirmed to publish as expected.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title "ci: pin actions to SHAs and limit contents:write to the release job" matches the main changes. The raw summary shows the ci.yml and release.yml workflows pinning actions to commit SHAs, and…
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: Title check

Explanation

The title "ci: pin actions to SHAs and limit contents:write to the release job" matches the main changes. The raw summary shows the ci.yml and release.yml workflows pinning actions to commit SHAs, and release.yml moving its top-level token permission from contents: write to contents: read with contents: write granted only to the release job. The objectives describe the same intent. The title is specific, concise, and names the primary change.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Team
  • Run ID: 057c6c5c-0d87-4fbf-9ad4-ef0e5cbbf749
Commits

Reviewing files that changed from the base of the PR and between f6c55e7 and a7f5a9c.

Files selected for processing: 2

  • .github/workflows/ci.yml
  • .github/workflows/release.yml

Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@greptile-apps

greptile-apps Bot commented Nov 19, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Reviews (1) · Last reviewed commit: "ci: harden GitHub Actions workflows" · Reviewed by Greptile

@devin-ai-integration
devin-ai-integration Bot merged commit eadd812 into main Nov 19, 2026
7 checks passed
@devin-ai-integration
devin-ai-integration Bot deleted the devin/1795096372-ci-hardening branch November 19, 2026 14:10
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