fix(ci): Lockfile nach Dependency-Änderungen regenerieren#6
Merged
Conversation
npm operations on macOS (audit fix, transformers migration) left package-lock.json out of sync (missing gcp-metadata and cross-platform optional entries), breaking npm ci on Linux CI runners. Regenerated from scratch; npm ci --dry-run passes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Was
package-lock.json regeneriert — npm ci auf Linux-Runnern schlug fehl (Missing: gcp-metadata@7.0.1 u.a.), CI auf main war rot.
Warum
Gleiche Fehlerklasse wie docmind-desktop#4: npm-Operationen auf macOS droppen plattformfremde/transitive Lock-Einträge.
Tests
typecheck grün, Testsuite Exit 0,
npm ci --dry-runExit 0.🤖 Generated with Claude Code