Repository navigation
BUILD-13164 Replace third-party GitHub Actions with StepSecurity maintained actions - #956
sonar-platform-bot[bot] wants to merge 2 commits into
Conversation
…ts binary signature check
|
Code Review ✅ Approved 🟡 Medium riskReplacing the version-bump workflow’s PR-creation action could alter automated pull-request creation or branch updates, but is limited to one step. Replaces the third-party Verification Rules 3/3 met PRs 1 inspectedFunctional validation No results Rules 3 passed 1 not applicable
Broader impact PRs 1 inspectedCross-PR 1 PR inspected 0 open impacts
Auto-approval Not enabledFor more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |





What
Replaces third-party GitHub Actions with the StepSecurity maintained copies of the same actions. Each new
uses:line is pinned to a commit SHA, with the version in a comment..github/workflows/bump-versions.ymlpeter-evans/create-pull-request@3ffccacd4605(v8.1.3)step-security/create-pull-request@50c103da2b9c(v8.1.1)Why
StepSecurity maintains hardened copies of these actions that track upstream releases. Using them, pinned by SHA, reduces exposure to a compromised upstream release or tag.
Scope is a fixed list of actions. Other third-party actions in these workflows, such as
slackapi/slack-github-action, are left as they are on purpose, even when a StepSecurity copy exists.Version notes
.github/workflows/bump-versions.yml:38: StepSecurity has no v8.1.3 yet; pinned to v8.1.1, its most recent releaseWhat to check
uses:lines change the same way.This PR is opened as a draft. Engineering Experience will not merge it; please review and merge.
Kept on upstream
.github/workflows/build.yml:29jdx/mise-actionv5.2.8.github/workflows/build.yml:268jdx/mise-actionv5.2.8jdx/mise-actionv5.2.0+ checks the downloaded mise binary against its signed release packslip; StepSecurity's most recent release (and the wrapper, which runs it) predates that check, so these steps stay on upstream until StepSecurity publishes v5.2 or later.