Skip to content

fix(ci): CI-Node auf 24 (npm-11-Lockfile-Kompatibilität)#8

Merged
Baldri merged 1 commit into
mainfrom
claude/session/fix/ci-node24
Jul 2, 2026
Merged

fix(ci): CI-Node auf 24 (npm-11-Lockfile-Kompatibilität)#8
Baldri merged 1 commit into
mainfrom
claude/session/fix/ci-node24

Conversation

@Baldri

@Baldri Baldri commented Jul 2, 2026

Copy link
Copy Markdown
Owner

Was

Alle CI-Jobs von Node 20 auf Node 24.

Warum

npm 10 (Node-20-Runner) lehnt das mit npm 11 generierte Lockfile ab (Missing: gcp-metadata@7.0.1), npm 11 validiert es sauber. Dev-Maschine läuft Node 24/npm 11 — ohne Angleichung bricht CI bei jedem lokalen Lock-Update erneut. Electron-Runtime-Target unverändert.

Tests

Lokal (Node 24): typecheck grün, Tests Exit 0, npm ci dry-run 0. CI-Lauf auf main ist der Beweis.

🤖 Generated with Claude Code

npm 10 (Node 20 runners) rejects the npm-11-generated lockfile
(Missing: gcp-metadata@7.0.1) while npm 11 validates it fine — dev
machines run Node 24/npm 11, so every local lockfile update would
re-break CI on Node 20. Aligning CI tooling to Node 24 removes the
mismatch; the Electron runtime target is unaffected.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Baldri Baldri merged commit 495afbf into main Jul 2, 2026
@Baldri Baldri deleted the claude/session/fix/ci-node24 branch July 2, 2026 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant