Commit 3235e4f
committed
ci: SHA-pin all GitHub Actions in CI workflow
Replace mutable action refs with pinned commit SHAs, per the supply-chain
requirements in the build-lockdown guidance (inc-18715).
The material fix is `snyk/actions/node@master` -> a pinned v1.0.0 commit: a
floating branch ref on a third-party action, executing with SNYK_TOKEN in
scope. Anyone able to move that branch could run arbitrary code in CI with
the token available.
Also pinned, and bumped off the deprecated v2 majors:
actions/checkout v2 -> v7.0.1 (3d3c42e)
actions/setup-node v2 -> v7.0.0 (8207627)
codecov/codecov-action v5 -> v5.5.5 (0fb7174), pinned at current major
snyk/actions/node master -> v1.0.0 (9adf32b)
Caveat: snyk/actions/node is a Docker-based action and still pulls the
mutable `docker://snyk/snyk:node` image at runtime, so the SHA pin bounds
the action code but not the scanner image.
fql-ts is a public repo, so it runs on GitHub-hosted runners and is not
subject to the locked-down agent egress wall; no Buildkite migration is
needed here. See PR description.1 parent d8d7c06 commit 3235e4f
1 file changed
Lines changed: 9 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
| 14 | + | |
15 | 15 | | |
16 | 16 | | |
17 | | - | |
| 17 | + | |
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | 24 | | |
25 | | - | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
26 | 31 | | |
27 | 32 | | |
28 | 33 | | |
| |||
35 | 40 | | |
36 | 41 | | |
37 | 42 | | |
38 | | - | |
| 43 | + | |
39 | 44 | | |
40 | 45 | | |
41 | 46 | | |
0 commit comments