22/24/26: timed out on slow public AlmaLinux mirrors (1–150 kB/s). Now uses the CT130 package cache exactly as cloud-apache-container does: same pkg-cache-repos.sh, same pinned CA (fingerprint BB:5B:9A:…:BD:F3 checked), probe first, upstream fallback. epel-release is GPG-verified before install.
18/20: npm 12 needs Node >=22.22.2; #4 made that failure fatal. Now keeps the bundled npm with a warning.
Tested locally: node18 builds (v18.20.8, npm 10.8.2). node24 builds over the upstream fallback path (v24.22.1, npm 12.2.1, no cache address left in the image). The cache path cannot be reached from my workstation, so CI is its first run. The cache itself answers 200 from the LAN and serves epel-release.
The first CI run after #4 failed on all 5 jobs.
- **22/24/26:** timed out on slow public AlmaLinux mirrors (1–150 kB/s). Now uses the CT130 package cache exactly as cloud-apache-container does: same `pkg-cache-repos.sh`, same pinned CA (fingerprint BB:5B:9A:…:BD:F3 checked), probe first, upstream fallback. epel-release is GPG-verified before install.
- **18/20:** npm 12 needs Node >=22.22.2; #4 made that failure fatal. Now keeps the bundled npm with a warning.
**Tested locally:** node18 builds (v18.20.8, npm 10.8.2). node24 builds over the upstream fallback path (v24.22.1, npm 12.2.1, no cache address left in the image). The cache path cannot be reached from my workstation, so CI is its first run. The cache itself answers 200 from the LAN and serves epel-release.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
- The first Node 24/26 run timed out on every job: public AlmaLinux mirrors
served the runners at 1-150 kB/s. Use the CT130 package cache the same way
cloud-apache-container does (same pkg-cache-repos.sh and pinned CA), with
the upstream repos as fallback when the probe fails. epel-release is now
GPG-verified before install instead of fetched unverified by URL.
- npm 12 requires Node >=22.22.2; on 18/20 keep the npm Node ships with.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jknapp
merged commit 329136d78a into main2026-10-22 13:52:11 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The first CI run after #4 failed on all 5 jobs.
pkg-cache-repos.sh, same pinned CA (fingerprint BB:5B:9A:…:BD:F3 checked), probe first, upstream fallback. epel-release is GPG-verified before install.Tested locally: node18 builds (v18.20.8, npm 10.8.2). node24 builds over the upstream fallback path (v24.22.1, npm 12.2.1, no cache address left in the image). The cache path cannot be reached from my workstation, so CI is its first run. The cache itself answers 200 from the LAN and serves epel-release.
🤖 Generated with Claude Code