Repository navigation
Commit 2681511
ci: Use latest Node patch release in setup-node (#1191)
## Why?
`setup-node` without `check-latest` uses the runner's cached Node
release, which can lag behind security patches. The [October 2026
Node.js security
releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases)
fix a high-severity Brotli decoder RCE (CVE-2026-111497) and TLS
hostname verification issues across 22.x, 24.x, and 26.x (fixed in
22.23.4, 24.22.1, 26.12.1). The risk in CI is low, but release and
publish jobs run with credentials, so this is worth the hygiene fix.
Same change as apify/apify-docs#3129.
## What?
- Add `check-latest: true` to all 4 `setup-node` steps (3 workflows), so
CI resolves the newest patch release of each Node line
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>1 parent 011f8b1 commit 2681511
3 files changed
Lines changed: 4 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
| 87 | + | |
87 | 88 | | |
88 | 89 | | |
89 | 90 | | |
| |||
105 | 106 | | |
106 | 107 | | |
107 | 108 | | |
| 109 | + | |
108 | 110 | | |
109 | 111 | | |
110 | 112 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
58 | 58 | | |
59 | 59 | | |
60 | 60 | | |
| 61 | + | |
61 | 62 | | |
62 | 63 | | |
63 | 64 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
57 | 57 | | |
58 | 58 | | |
59 | 59 | | |
| 60 | + | |
60 | 61 | | |
61 | 62 | | |
62 | 63 | | |
| |||
0 commit comments