release/2024-02-21 #700
Merged
release/2024-02-21 #700
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
Support module parameter files containing `bigint` values. Encode them as strings matching /d+n/ format. Update exit codes for failed runs of the deployed task to be non-zero. This was picked up in setting up integration tests for the module parameter file. Fixes #663 --------- Co-authored-by: John Kane <[email protected]>
Update `hardhat-ignition-viem` to use `viem@2`, this requires updating the version of `hardhat-viem` used to `2.0.0` to get its `viem@2` version. Resolves #692
Update the packages versions and changelogs for the `0.14.0 - 2024-02-21` release.
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.
0.14.0 - 2024-02-21
Added
/d+n/(#663)Changed
@nomicfoundation/hardhat-ignition-viemtoviem@2, a breaking change for scripts or tests that leverage viem contract instances returned from an Ignition deploy call, see the viem@2 migration guide for more details (#692)