Use upgrade --exact for NPM package publication #3083
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
We want to add `--exact` flag so the version of tagged package is resolved to an exact value. Without this flag by default the version is resolved by adding `^`, which can cause problems when resolving versions with `-dev`, `-goerli`, `-mainnet` suffixes.
michalinacienciala
approved these changes
Jul 11, 2022
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 want to add
--exactflag so the version of tagged package isresolved to an exact value. Without this flag by default the version is
resolved by adding
^, which can cause problems when resolving versionswith
-dev,-goerli,-mainnetsuffixes.