Skip to content

chore: pin GitHub Actions to commit shas BED-7914#214

Merged
lrfalslev merged 3 commits into2.Xfrom
lfalslev/bed-7914
Apr 16, 2026
Merged

chore: pin GitHub Actions to commit shas BED-7914#214
lrfalslev merged 3 commits into2.Xfrom
lfalslev/bed-7914

Conversation

@lrfalslev
Copy link
Copy Markdown
Contributor

@lrfalslev lrfalslev commented Apr 14, 2026

Description

Updates actions to latest versions and pins them by git commit SHA for security hardening

Motivation and Context

This PR addresses: BED-7914

How Has This Been Tested?

Manually verified commit SHAs. Pipelines still pass.

Screenshots (if appropriate):

Types of changes

  • Chore (a change that does not modify the application functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Summary by CodeRabbit

  • Chores
    • Updated CI workflows to pin third-party actions to immutable commit SHAs (replacing version tags) and applied minor workflow formatting fixes; no functional changes to build, publish, or CLA behavior.

@lrfalslev lrfalslev self-assigned this Apr 14, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

Walkthrough

Updated GitHub Actions workflows to replace semantic action version tags with pinned commit SHA references and minor formatting fixes (branch array formatting, trailing newline/whitespace) across build, CLA, and publish workflows.

Changes

Cohort / File(s) Summary
Build workflow
.github/workflows/build.yml
Reformatted pull_request.branches array, replaced actions/setup-dotnet@v5 and actions/checkout@v6 tags with pinned commit SHA references, fixed trailing newline/whitespace; dotnet build -p:CommonSource=Dev unchanged.
CLA workflow
.github/workflows/cla.yml
Replaced contributor-assistant/github-action@v2.6.1 with a pinned commit SHA reference while preserving step condition and inputs.
Publish workflow
.github/workflows/publish.yml
Replaced several action version tags (actions/checkout@v2, actions/setup-dotnet@v5, softprops/action-gh-release@v1) with pinned commit SHA references; workflow triggers, job structure, and release artifact steps unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰
I hopped through YAML, tidy and keen,
Pinned every action, neat and clean,
Brackets fixed, no trailing fluff,
Commits locked down — steady and tough,
A little hop for CI's routine.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore: pin GitHub Actions to commit shas BED-7914' clearly and concisely summarizes the main change: pinning GitHub Actions to specific commit SHAs for security/reproducibility purposes, with the Jira ticket reference.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check ✅ Passed The pull request description follows the template and includes all required sections with appropriate information for a workflow security hardening change.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch lfalslev/bed-7914

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

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

@lrfalslev lrfalslev changed the title chore: pin GitHub Actions to commit shas BED-7914#295 chore: pin GitHub Actions to commit shas BED-7914 Apr 14, 2026
@lrfalslev lrfalslev merged commit db2377e into 2.X Apr 16, 2026
3 checks passed
@lrfalslev lrfalslev deleted the lfalslev/bed-7914 branch April 16, 2026 20:38
@github-actions github-actions Bot locked and limited conversation to collaborators Apr 16, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants