fix: Reinstate deployment artifact retention #341
Merged
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
Since migrating to OZ's hardhat-upgrades plugin, deployments are no longer being retained in the deployments directory. This question on StackOverflow arrived at the same conclusion: https://stackoverflow.com/questions/74870472
nicholaspai
approved these changes
Aug 8, 2023
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.
Since migrating to OZ's hardhat-upgrades plugin, deployments are no longer being retained in the deployments directory. Fortunately, it seems possible to do this manually via some of the objects exposed by hre and hardhat-deploy.
This question on StackOverflow arrived at the same conclusion:
https://stackoverflow.com/questions/74870472