fix(ci): pin docs-site pnpm to v9 -- lockfile format 9.0, pnpm 11 blocks esbuild#6
Merged
Conversation
…blocks esbuild build script Co-Authored-By: Claude Sonnet 4.6 <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
2 participants
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
docs-site/pnpm-lock.yamlis lockfile format 9.0 (generated with pnpm 9). pnpm 11 introduces a new supply-chain security feature that blocks build scripts by default, causingesbuild@0.21.5to fail. Pinning pnpm back to v9 in the Pages workflow matches the lockfile version and avoids the blocked-builds issue.Also reverts the
onlyBuiltDependenciesworkaround from the previous fix (which had no effect).