Skip to content

ci: pin third-party actions by commit, pin the lint tool versions - #32

Merged
lightchainaidev merged 1 commit into
testnetfrom
ci/pin-actions
Oct 20, 2026
Merged

lightchainaidev merged 1 commit into
testnetfrom
ci/pin-actions

Conversation

@lightchainaidev

Copy link
Copy Markdown
Contributor

From the CI review (LC-204, "tools are not pinned").

  • Every third-party action now names its commit, with the release it resolved to as a comment (docker/*, golangci/golangci-lint-action, pnpm/action-setup, foundry-rs/foundry-toolchain, dorny/paths-filter, as present in this repo). Each SHA is what the major tag pointed at on 2026-10-19. GitHub's own actions/* stay on tags.
  • Where golangci-lint-action runs, it gets version: v2.14.0; without it the action installs the newest release (v2.15.0 since 2026-10-16). In the orchestrator's E2E job, gofumpt@latest / golangci-lint@latest become v0.12.0 / v2.14.0, the versions of the last green runs on 2026-10-13.

Workflow files only. This PR's own run is the check.

🤖 Generated with Claude Code

A moved tag on a third-party action would run new code with this job's
token, and golangci-lint (gofumpt in the orchestrator E2E job) installed
whatever release was newest, so a new release could fail unrelated pull
requests. Each third-party action now names its commit with the release
as a comment; golangci-lint is v2.14.0 and gofumpt v0.12.0, the versions
the last green runs used. GitHub's own actions/* stay on tags.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@lightchainaidev
lightchainaidev merged commit 22d051c into testnet Oct 20, 2026
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.

1 participant