fix Docker build #553
Merged
fix Docker build #553
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
… preinstall script
jfboeve
approved these changes
Apr 3, 2025
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.
We're a bit behind on pnpm versions and this causes issues with newer node installs and corepack. The issue is related to verifying the PNPM tarball signature, and it's failing because the signature in the TUF metadata cannot be validated—likely due to a key mismatch or expired/incomplete keyring used by Corepack:
To work arround this I'm installing a pinned version of pnpm through corepack:
And removed the please use pnpm check script, its no longer needed. People can figure it out or they should read the readme.