Skip to content

chore(ci): pin pr-inspector third-party actions to tagged versions - #23339

Closed
anooparveti wants to merge 1 commit into
masterfrom
chore/pin-pr-inspector-actions
Closed

anooparveti wants to merge 1 commit into
masterfrom
chore/pin-pr-inspector-actions

Conversation

@anooparveti

@anooparveti anooparveti commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Description

Replace mutable tag refs for all third-party actions across the
workflows with full-length commit SHAs, keeping the human-readable
`version as a trailing comment (per GitHub's hardening guidance).

Pinned:
- TimonVS/pr-labeler-action -> 8b99f40 (v4)
- olivernybroe/action-conflict-finder -> 78f7add (v4.0)
- mschilde/auto-label-merge-conflicts -> 5981f89 (v2.0)
  Note: the previously used @v2 ref did not exist upstream (only v2.0
  is tagged); the ref was silently resolving to master. Pinning to
  v2.0's SHA both locks the ref and restores an actual released version.
- Simek/yarn-lock-changes -> 59f47ee (v0.14.1)
- nrwl/nx-set-shas -> 3e9ad73 (v4)
- jlumbroso/free-disk-space -> 54081f1 (v1.3.1)
- wagoid/commitlint-github-action -> d524cbd (v4)
- repo-sync/pull-request -> 7e79a9f (v2)
- peaceiris/actions-gh-pages -> 329bcc8 (v4)

First-party actions/* entries are left on tags, as those are
maintained by GitHub itself and out of scope for this change.

Why: tags are mutable and can be force-moved by an upstream maintainer
(or an attacker who compromises their account) to point at arbitrary
code that then runs in CI with repository secrets. Pinning to a full
commit SHA removes that attack surface and matches GitHub's own
security-hardening recommendation for third-party actions.

Ticket Reference: #...

Additional Information

Copilot AI balanced review requested due to automatic review settings October 28, 2026 13:32
@anooparveti
anooparveti requested a review from a team as a code owner October 28, 2026 13:32
@anooparveti
anooparveti requested a review from hbelkhir October 28, 2026 13:32

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Note

Copilot was unable to run its full agentic suite in this review.

Copilot review overview

2 open issues
What changed in this PR

Updates the PR inspection GitHub Actions workflow to use versioned action releases instead of floating branches.

Changes:

  • Pin mschilde/auto-label-merge-conflicts from master to v2
  • Pin Simek/yarn-lock-changes from main to v0.14.1
File Description
.github/​workflows/​pr-inspector.yml Replaces floating action refs with versioned tags for more predictable workflow runs

Review effort: Lite

Comment thread .github/workflows/pr-inspector.yml Resolved
Comment thread .github/workflows/pr-inspector.yml Resolved
@anooparveti
anooparveti force-pushed the chore/pin-pr-inspector-actions branch from 71040e7 to 9dd8391 Compare October 28, 2026 14:48
Replace mutable tag refs for all third-party actions across the
workflows with full-length commit SHAs, keeping the human-readable
`version as a trailing comment (per GitHub's hardening guidance).

Pinned:
- TimonVS/pr-labeler-action -> 8b99f40 (v4)
- olivernybroe/action-conflict-finder -> 78f7add (v4.0)
- mschilde/auto-label-merge-conflicts -> 5981f89 (v2.0)
  Note: the previously used @v2 ref did not exist upstream (only v2.0
  is tagged); the ref was silently resolving to master. Pinning to
  v2.0's SHA both locks the ref and restores an actual released version.
- Simek/yarn-lock-changes -> 59f47ee (v0.14.1)
- nrwl/nx-set-shas -> 3e9ad73 (v4)
- jlumbroso/free-disk-space -> 54081f1 (v1.3.1)
- wagoid/commitlint-github-action -> d524cbd (v4)
- repo-sync/pull-request -> 7e79a9f (v2)
- peaceiris/actions-gh-pages -> 329bcc8 (v4)

First-party actions/* entries are left on tags, as those are
maintained by GitHub itself and out of scope for this change.

Why: tags are mutable and can be force-moved by an upstream maintainer
(or an attacker who compromises their account) to point at arbitrary
code that then runs in CI with repository secrets. Pinning to a full
commit SHA removes that attack surface and matches GitHub's own
security-hardening recommendation for third-party actions.

Signed-off-by: Anoop N <anoop.n@ovhcloud.com>

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@anooparveti
anooparveti force-pushed the chore/pin-pr-inspector-actions branch from 9dd8391 to 24e67ae Compare October 28, 2026 15:24
@anooparveti
anooparveti requested a review from a team as a code owner October 28, 2026 15:24
@anooparveti
anooparveti requested review from FabienHenon and clementdemily and a balanced review from Copilot October 28, 2026 15:24

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Comment on lines 12 to +15
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: wagoid/commitlint-github-action@v4
- uses: wagoid/commitlint-github-action@d524cbd2fcbd5dcce5ad4ca6733154643ab768da # v4
@anooparveti

Copy link
Copy Markdown
Contributor Author

It has been tackled with #23340

@anooparveti anooparveti closed this Nov 2, 2026
@anooparveti
anooparveti deleted the chore/pin-pr-inspector-actions branch November 2, 2026 13:45
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.

2 participants