-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/2023-09-15 #475
Merged
Merged
Release/2023-09-15 #475
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
… the event listener
Switched out the usage of flat to the core function. Added in doc comments to meet api-extractor rules.
On a rerun no batches are executed. Show the deployed addresses anyway. This involved adding a deployment complete event, that passes the deployment result. This will be extended to failure cases in future commits.
Instead of showing all batches at once. Only display a batch if at least one future has started (excluding the first batch). We may want to enhance this by tracking the current batch in the ui based on the batch events.
Bring back UI for execution
Modify our id separators, swapping: - `:` => `#` - `#` => `.` This allows us to write the identifiers as filenames on windows. Resolves #441.
Module builder refactor: overload `contract`, `contractAt`, and `library`.
Rename futures after overload
We intend to support viewing an already run deployment, hence plan makes less sense. Instead we will go with the more generic visualize for the moment.
Replace the deployment serializer with just an IgnitionModule serializer.
For the moment, remove the visualize function from the public core api. Out intent is to bring this back, returning the full deployment result type so that a visualization can show the current journaled state of a deployment. This will be additative to the api.
The chainId check test needs to read an existing deployment, the startup time seems to trip the timeout.
If a build info is stored for a future id, record a debug file as a pointer. The debug file is a sibling to the artifact file, so under `./ignition/deployments/<depid>/artifacts`: - `LockModule#Lock.json` - `LockModule#Lock.dbg.json` The dbg file points at the Ignition build info file via a relative path. Resolves #472.
Update the packages versions and changelogs for the `0.4.0 - 2023-09-15` 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.4.0 - 2023-09-15
Added
Changed
@nomicfoundation/hardhat-ignition
plan
task tovisualize
(#471)use-verbose
flag ondeploy
task tosimple-text-ui
(#444)Fixed