fix: sync package-lock.json with package.json to unblock CI#2
Merged
Conversation
The CI job "Run Integration Tests" was failing because `npm ci` detected that package-lock.json was out of sync with package.json: - @vitest/ui@^3.2.4 resolved to 3.2.6 which requires vitest@3.2.6 as a peer - vitest and @vitest/coverage-v8 were at ^3.1.1, resolving to 3.2.4 Aligning all three vitest packages to ^3.2.6 resolves the peer dependency conflict and allows the lock file to be regenerated consistently.
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job Run Integration Tests
fix: sync package-lock.json with package.json to unblock CI
Jun 15, 2026
ashokan-okahu
approved these changes
Jun 15, 2026
ashokan-okahu
marked this pull request as ready for review
June 15, 2026 03:27
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
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.
The "Run Integration Tests" CI job was failing at
npm cidue to a peer dependency conflict:@vitest/ui@^3.2.4resolved to3.2.6(requiringvitest@3.2.6as an exact peer), whilevitestand@vitest/coverage-v8were constrained to^3.1.1and resolved to3.2.4.Proposed changes
vitest,@vitest/coverage-v8, and@vitest/uiinpackage.jsonto^3.2.6so all three resolve to the same versionpackage-lock.jsonto reflect the updated resolutionsTypes of changes
Checklist
Further comments
The
@vitest/uipackage was already at^3.2.4while the other two vitest packages lagged behind at^3.1.1. The simplest consistent fix is to align all three at^3.2.6(the current latest), which satisfies@vitest/ui@3.2.6's exact peer dependency requirement onvitest@3.2.6.