fix(pnpm): disable frozen lockfile #1
Merged
Conversation
This file contains 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
Hey! I hit a bug in the GitHub Action when using pnpm: ``` ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up-to-date with packages/config/package.json Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile" Error: Process completed with exit code 1. ``` **How to fix it:** In CI environments, pnpm always runs with the `--frozen-lockfile` option. In this case, we attempt to run `pnpm install` to update the lockfile, so we need to be explicit about it.
JamieMason
changed the title
|
Thanks a lot @HorusGoul 🙌🏻 |
|
My first attempt creating a tag and release using only the github.com UI but it should be available as 0.2.1 if all went well. |
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.
Hey! I hit a bug in the GitHub Action when using pnpm:
How to fix it:
In CI environments, pnpm always runs with the
--frozen-lockfileoption. In this case, we attempt to runpnpm installto update the lockfile, so we need to be explicit about it, and as the error tells us, we need to use the--no-frozen-lockfileoption.