Skip to content

BUILD-13164 Replace third-party GitHub Actions with StepSecurity maintained actions - #956

Draft
sonar-platform-bot[bot] wants to merge 2 commits into
masterfrom
feat/smarini/BUILD-13164-stepsecurity-actions
Draft

sonar-platform-bot[bot] wants to merge 2 commits into
masterfrom
feat/smarini/BUILD-13164-stepsecurity-actions

Conversation

@sonar-platform-bot

@sonar-platform-bot sonar-platform-bot Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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.

File Line Before After
.github/workflows/bump-versions.yml 38 peter-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 release

What to check

  • CI on this PR runs the replaced steps; they should pass as they did before.
  • Workflows that only run on push, schedule, release or dispatch are not exercised by this PR; their uses: lines change the same way.
  • Inputs and outputs used by these steps exist in the new actions (checked when this PR was prepared).

This PR is opened as a draft. Engineering Experience will not merge it; please review and merge.

Kept on upstream

  • .github/workflows/build.yml:29 jdx/mise-action v5.2.8
  • .github/workflows/build.yml:268 jdx/mise-action v5.2.8

jdx/mise-action v5.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.

@hashicorp-vault-sonar-prod

Copy link
Copy Markdown

BUILD-13164

@sonarqube-next

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Nov 18, 2026

Copy link
Copy Markdown
Code Review ✅ Approved 🟡 Medium risk

Replacing 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 peter-evans/create-pull-request step in .github/workflows/bump-versions.yml with the StepSecurity copy pinned to a commit SHA (v8.1.1, the latest available). jdx/mise-action stays on upstream in build.yml because StepSecurity's release lacks the binary signature check. No issues found.

Verification Rules 3/3 met PRs 1 inspected

Functional validation No results

Rules 3 passed 1 not applicable

✅ Approved GitHub Actions runners
✅ Internal artifact registries
✅ Repository license compliance

Broader impact PRs 1 inspected
Cross-PR 1 PR inspected 0 open impacts

PR 8435: BUILD-13164 Replace third-party GitHub Actions with StepSecurity maintained actions Inspected

Auto-approval Not enabled

Set up

For more verification details, comment gitar display:verbose.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing compact verification results.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Was this helpful? React with 👍 / 👎 | Gitar

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants