chore(dependencies): set explicit version for @safe-global/safe-deployments #4861
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
dasanra
force-pushed
the
force-protocol-kit-version
branch
from
e29f58a to
03e7509
Compare
dasanra
changed the title
|
How about we use the resolutions in the global package.json? It looks like we end up with 2 versions of safe-deployments in yarn.lock because 2 different versions are needed by the packages that get included. |
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.
What it solves
Ensures safe-deployments version used is the expected one
How this PR fixes it
Set a explicit version for @safe-global/safe-deployments