Skip to content

ci: pin every action to a commit SHA [PLT-2594] - #1

Merged
charles-spectora merged 1 commit into
masterfrom
charles-plt-2594-intercom_flutter-fork-pin-every-action-to-a-commit-sha-and
Oct 20, 2026
Merged

charles-spectora merged 1 commit into
masterfrom
charles-plt-2594-intercom_flutter-fork-pin-every-action-to-a-commit-sha-and

Conversation

@charles-spectora

Copy link
Copy Markdown

Closes PLT-2594 and this repo's share of PLT-2441 (SAST A7, pin third-party actions).

Pipeline config only. No runtime code changes. This is a fork of deepak786/intercom_flutter, and this PR makes it diverge from upstream in .github/ only.

What changed

Third-party actions pinned to full SHAs, release tag as a trailing comment. Each one is the newest release within the major the workflow already used, so nothing crosses a major. That covers all 9 uses: lines in main.yml. The repo has no composite actions, spectorasoftware/github-actions composites or shared-pipelines refs.

Action Before After
actions/checkout v2 v2.8.0
actions/setup-java v1 v1.4.5
subosito/flutter-action v1 v1.5.3
nanasess/setup-chromedriver v2 v2.4.0

.github/dependabot.yml is new. It adds a github-actions ecosystem for the workflow (weekly, grouped, 7-day cooldown). Dependabot version updates are off by default on forks, so this needs enabling in the repo's settings before it does anything.

Verified

  • Semgrep p/github-actions: 9 github-actions-mutable-action-tag results on master, 0 on this branch.
  • main.yml and dependabot.yml parse.
  • The diff touches only .github/.

Worth a look in review

  • CI has never run on this fork: the Actions API reports 0 runs. Deleting the upstream workflow is an alternative to pinning it.
  • main.yml runs on pull requests to master, so this PR is its first run here. It's upstream's older workflow (setup-java@v1 with Java 12, subosito/flutter-action@v1), and it may fail for reasons unrelated to the pins. Moving to newer majors is outside this ticket.

🤖 Generated with Claude Code

Pin every third-party action in the fork's workflow to a full commit
SHA (newest release within the major already in use, tag as a trailing
comment) and add a github-actions Dependabot ecosystem.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@viniciuscbm viniciuscbm left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Thanks, Charles. I verified that every pinned SHA exists upstream and matches the version in its trailing comment, that no action changes major version, and that zizmor 1.30.1 and actionlint report no new findings against the base branch. The Dependabot config looks good as well.

The failing checks are not caused by this change: the workflow logic is unchanged apart from the pins, and this repository has no passing CI baseline on its default branch.

Approving.

@charles-spectora
charles-spectora merged commit 05f9aaf into master Oct 20, 2026
1 of 3 checks passed
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.

3 participants