You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(deps): resolve @sanity/tsconfig to 2.2.1 in the doc examples lockfile entry - #3586
pnpm install fails on main with ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY: Broken lockfile: no entry for '@sanity/tsconfig@2.1.0', so every CI job that installs dependencies is red.
The apps/doc-examples importer in pnpm-lock.yaml still resolves @sanity/tsconfig to v2.1.0. The tooling catalog asks for ^2.2.1, every other importer resolves v2.2.1, and the lockfile only has a v2.2.1 package entry. The importer was added on a branch that predates the catalog bump, and the stale resolution survived the rebase.
This regenerates the lockfile with pnpm install --lockfile-only --fix-lockfile on pnpm v10.25.0. The diff is that one resolution plus a doubled blank line after the importer. Every non-link importer resolution now has a matching package and snapshot entry.
Note
Low Risk
Lockfile-only alignment with the existing catalog version; no product logic or dependency upgrades beyond fixing a stale resolution.
Overview
Repairs a broken pnpm-lock.yaml so pnpm install and CI can succeed again. The doc-examples importer still pinned @sanity/tsconfig to 2.1.0 while the tooling catalog and the rest of the lockfile use 2.2.1, which triggered ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY because no package entry exists for 2.1.0.
The change updates that importer’s resolved version to 2.2.1 and drops an extra blank line between importers—no application or runtime code changes.
Reviewed by Cursor Bugbot for commit a58caa4. Bugbot is set up for automated code reviews on this repo. Configure here.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
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
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.
pnpm installfails on main withERR_PNPM_LOCKFILE_MISSING_DEPENDENCY: Broken lockfile: no entry for '@sanity/tsconfig@2.1.0', so every CI job that installs dependencies is red.The
apps/doc-examplesimporter inpnpm-lock.yamlstill resolves@sanity/tsconfigto v2.1.0. Thetoolingcatalog asks for^2.2.1, every other importer resolves v2.2.1, and the lockfile only has a v2.2.1 package entry. The importer was added on a branch that predates the catalog bump, and the stale resolution survived the rebase.This regenerates the lockfile with
pnpm install --lockfile-only --fix-lockfileon pnpm v10.25.0. The diff is that one resolution plus a doubled blank line after the importer. Every non-link importer resolution now has a matching package and snapshot entry.Note
Low Risk
Lockfile-only alignment with the existing catalog version; no product logic or dependency upgrades beyond fixing a stale resolution.
Overview
Repairs a broken
pnpm-lock.yamlsopnpm installand CI can succeed again. The doc-examples importer still pinned@sanity/tsconfigto 2.1.0 while the tooling catalog and the rest of the lockfile use 2.2.1, which triggeredERR_PNPM_LOCKFILE_MISSING_DEPENDENCYbecause no package entry exists for 2.1.0.The change updates that importer’s resolved version to 2.2.1 and drops an extra blank line between importers—no application or runtime code changes.
Reviewed by Cursor Bugbot for commit a58caa4. Bugbot is set up for automated code reviews on this repo. Configure here.