chore: update Dockerfile and package.json to pin pnpm version#1893
Merged
gustavobtflores merged 1 commit intoMay 12, 2026
Merged
Conversation
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.
Description
Pin the frontend pnpm version used by Docker builds to avoid CI failures caused by installing the latest pnpm release with incompatible Node.js engine requirements.
Changes
packageManager: pnpm@10.33.3to the dashboard package metadata.pnpm@10.33.3.pnpm install --frozen-lockfilefor reproducible dependency installs.How to test
docker buildx build --file ./dashboard/Dockerfile --tag dashboard-frontend:local --load ..pnpm install --frozen-lockfilewithout installingpnpm@latest.Closes #1892