fix: include pnpm workspace policy in release image build - #19
Merged
Conversation
Member
Author
|
@xianingawa-wq CI is green; this is the minimal release Docker context fix for #18. Please review when available. |
Member
Author
|
@xianingawa-wq Reminder: CI is green and the fix only copies the committed pnpm workspace policy into the Docker dependency layer. Please review when available. |
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.
Closes #18.
The Console release Docker build omitted
pnpm-workspace.yaml, so pnpm 11 did not load the committedallowBuilds.esbuildpolicy and the release image failed at dependency installation. This copies the workspace policy into the dependency layer while keeping the allowlist scoped to esbuild.Validation:
corepack pnpm install --frozen-lockfilecorepack pnpm run buildcorepack pnpm test