Repository navigation
fix(demo): regenerate next-server-components lockfile for next 16.3.1 - #265
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
innerdvations
added
pr: fix
innerdvations
approved these changes
Nov 3, 2026
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.
What does it do?
Regenerates
demo/next-server-components/pnpm-lock.yamlwithpnpm install --lockfile-only(pnpm 9.1.0) so it matches that demo'spackage.json. The lockfile now resolvesnextto 16.3.1 (with its updated transitive dependencies, e.g.@img/sharp-*0.35.5) instead of 16.2.9.Why is it needed?
mainis red since 6838d25 (#260). That PR bumpednextto 16.3.1 indemo/next-server-components/package.json, but it was rebuilt onmainby our Dependabot merge loop. The rebuild regenerated the rootpnpm-lock.yamlinstead of the demo's own lockfile, and was merged before CI finished. Since then everycache-and-installjob fails with:This blocks every open PR, including #255.
How to test it?
cache-and-install(node 20/22/24) passes on this PR.pnpm install --frozen-lockfile --lockfile-onlypasses in the root and indemo/next-server-components,demo/node-javascript,demo/node-typescriptanddemo/react-vite.Related issue(s)/PR(s)
Note:
demo/.strapi-app/pnpm-lock.yamlfails to parse on its own (ERR_PNPM_BROKEN_LOCKFILE: duplicated mapping key). That predates this change, CI doesn't install it, and it is left untouched here.🤖 Generated with Claude Code