fix: regenerate pnpm-lock.yaml to resolve eslint resolution mismatch#353
Merged
Conversation
The merge of #334 (bump @eslint/js from 9.39.4 to 10.0.1) combined with #344 and #345 produced a lockfile missing the resolution entry for eslint@10.2.1(jiti@2.6.1), causing all CI steps to fail with: ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY Broken lockfile: no entry for eslint@10.2.1(jiti@2.6.1) Regenerated via pnpm install --no-frozen-lockfile.
solidsnakedev
force-pushed
the
fix/lockfile-eslint-resolution
branch
from
68403f3 to
ea59ae4
Compare
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.
Problem
The merge of #334 (bump @eslint/js from 9.39.4 to 10.0.1) produced a
pnpm-lock.yamlmissing the resolution entry foreslint@10.2.1(jiti@2.6.1). All CI steps on main are now red:ERR_PNPM_LOCKFILE_MISSING_DEPENDENCYFix
Regenerated via
pnpm install --no-frozen-lockfile. Diff is +6/-6 lines — just two resolution entries normalized:@eslint/js@10.0.1now resolves toeslint@10.3.0(jiti@2.6.1)(was the missingeslint@10.2.1)fumadocs-mdxpeer depvite@6.4.2→vite@8.0.13(side-effect of re-resolve)Verification
pnpm type-check: PASSpnpm lint: PASSpnpm test: PASS (core packages; devnet fails on Docker image issues — pre-existing, same as CI)pnpm circular: PASS (42 pre-existing cycles, unchanged)pnpm-lock.yaml, 6 lines changed