Commit 156d28e
committed
revert(actions): restore stable @sha pins after diagnostic CI run
The diagnostic-SHA-pinning approach hit two blockers:
1. `@main` pin fails workflow validation (org policy requires
SHA-pinned actions).
2. New @sha pins fail zizmor's `impostor-commit` audit, because
zizmor's commit-history check appears to lag behind newly-
pushed SHAs.
The actual CI failure root cause has been identified (pnpm
version mismatch between runner's preinstalled 11.0.6 and
package.json's declared 11.1.2 — surfaces as "sfw is not
installed" in install action because setup's SFW step is
skipped on the version-mismatched runner pnpm). Fixing that
needs a separate `setup` action change to prepend the installed
pnpm to PATH; doesn't need the diagnostic pin chain.
Restore stable SHA pins so registry's own CI runs cleanly while
the next fix lands.
Keeping the diagnostic `ls -la` blocks in setup/action.yml
and checkout/action.yml (committed in fce50ac + 92c6ffb);
they're inert on success paths and will surface useful info
the next time the path-resolution failure mode recurs.
Pre-commit bypassed (SOCKET_API_KEY 401, user-authorized via
'Allow lint bypass').1 parent 3208014 commit 156d28e
2 files changed
Lines changed: 3 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
71 | 71 | | |
72 | 72 | | |
73 | 73 | | |
74 | | - | |
| 74 | + | |
75 | 75 | | |
76 | 76 | | |
77 | 77 | | |
78 | 78 | | |
79 | 79 | | |
80 | 80 | | |
81 | | - | |
| 81 | + | |
82 | 82 | | |
83 | 83 | | |
84 | 84 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
30 | 30 | | |
31 | 31 | | |
32 | 32 | | |
33 | | - | |
34 | | - | |
35 | | - | |
36 | | - | |
37 | | - | |
38 | | - | |
| 33 | + | |
39 | 34 | | |
40 | 35 | | |
41 | 36 | | |
| |||
0 commit comments