Repository navigation
Commit a0fbd38
committed
ci: bring the new vendor workflows onto the node24 pins
Reconciles with ecb1075, f3432ed and ea9cef8, which landed on main while
this branch was open. The two new workflows were written against the
pins that were current when the branch was cut, so after the rebase they
were the only two files left on actions/checkout v4, setup-node v4,
pnpm/action-setup v6 and a literal node-version: 24.
Nothing would have failed. That is the point: a stale pin does not go
red, it just quietly runs an older action, so this is exactly the kind of
drift a rebase carries in without reporting it.
Both jobs check out the repository, so they read the version from .nvmrc
like everything else. The one remaining literal is release-vale.yml's
publish step, which deliberately has no checkout for the file to be read
from and documents that in place.
Every workflow now resolves each action to a single SHA.1 parent 83dd032 commit a0fbd38
2 files changed
Lines changed: 8 additions & 8 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
80 | 80 | | |
81 | 81 | | |
82 | 82 | | |
83 | | - | |
| 83 | + | |
84 | 84 | | |
85 | | - | |
86 | | - | |
| 85 | + | |
| 86 | + | |
87 | 87 | | |
88 | | - | |
| 88 | + | |
89 | 89 | | |
90 | 90 | | |
91 | 91 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
64 | 64 | | |
65 | 65 | | |
66 | 66 | | |
67 | | - | |
| 67 | + | |
68 | 68 | | |
69 | | - | |
70 | | - | |
| 69 | + | |
| 70 | + | |
71 | 71 | | |
72 | | - | |
| 72 | + | |
73 | 73 | | |
74 | 74 | | |
75 | 75 | | |
| |||
0 commit comments