Fix upgrade guide Option C deploy.sh guard issue - #489
Closed
SrvFernandes wants to merge 1 commit into
Closed
SrvFernandes wants to merge 1 commit into
SrvFernandes wants to merge 1 commit into
Conversation
Signed-off-by: Sérgio <sveronezfernandes@gmail.com>
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
2 participants
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.
Closes #488
Summary
Option C in the upgrade guide suggests re-running
deploy.shbut does not account for the script's guard against existing deployment files.Changes
deployments-<network>.jsonbefore re-runningdeploy.shin Option C.Testing
Verified that the updated instructions allow operators to proceed with Option C without hitting the deploy.sh guard.
Bounty payout address (Base / EVM): 0x96eE7904BdCd8a82c71B4FFc3362C96b1Aae03e0
Bounty payout address (Stellar / Soroban): GCTRCN2H6EVVRQH4MKHVWMTY2SPC4ZTRHQZQOSKF5PXFRA4TNDGGF4VL