Add --no-git-checks when publishing from pnpm - #43
Open
gndelia wants to merge 1 commit into
Open
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
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.
Using
pnpm publishrequires the package to be deployed from a branch. See publish docs.This is a problem because libraries are released with tags. pnpm doesn't support this - the
pnpm publishcommand just fails. See pnpm/pnpm#5894The only workaround is adding the flag
--no-git-checks. Disabling this check will disable these 4 checks on publish time (none of these are really relevant):(Yup - that's AI ☝🏽 )
It seems we can safely enable it to allow using pnpm for publishing.