Repository navigation
Commit 9104d0b
ci: re-pin codeql-action to the true v4.38.0 commit
The pin 1c5b675653bb5c22dbe9b12b556ec555138e09fd is the commit that the
annotated tag v4.38.1 dereferences to -- not v4.38.0, despite the trailing
comment claiming otherwise. v4.38.1 is blocked estate-wide (nexia-list#100),
so every repo carrying this pin has in fact been running the blocked version.
v4.38.0 -> tag object 4bd7200e -> commit b96794f015dfd88f77b49b1c93e0fa7110f94c63
v4.38.1 -> tag object c23de5a8 -> commit 1c5b675653bb5c22dbe9b12b556ec555138e09fd
Where the ref was a bare tag (@v4.38.1) it was also unpinned -- a mutable ref
upstream can re-point at will -- so it is now pinned to a SHA as well as moved
off the blocked version.
In a number of repos the lock had already been moved to b96794f0 while the
workflow was left on the blocked SHA. Those two disagree, so the workflow is
currently rejected at startup and has not been running at all; this commit
makes the workflow match the lock and brings it back to life.
The workflow and actions.lock are changed in a single commit: GitHub compares
the lock to the workflow by literal string, so a partial edit is a startup
failure rather than a stale lock.
Refs: metadatastician/standards#1005
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01X3hgXxWm6umMgZkjYyHnnm1 parent 381daff commit 9104d0b
1 file changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
43 | 43 | | |
44 | 44 | | |
45 | 45 | | |
46 | | - | |
| 46 | + | |
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
50 | 50 | | |
51 | 51 | | |
52 | | - | |
| 52 | + | |
53 | 53 | | |
54 | 54 | | |
0 commit comments