-
Notifications
You must be signed in to change notification settings - Fork 790
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
VM release v4.2.0 #739
VM release v4.2.0 #739
Conversation
Add State Manager API tests to karma
Runs tests with ts-node instead of node.
Update labeler.yml
Running API tests with ts-node
Fix Node v12 repo installation issue
…opts Support in runBlock runTx options
* explicitly duplicate bignumbers on stack * vm: add test to check for internally editing stack items Co-authored-by: Ev <ev@ethereum.org>
Codecov Report
@@ Coverage Diff @@
## vm/release-v4.1.3 #739 +/- ##
==================================================
Coverage 91.40% 91.40%
==================================================
Files 31 31
Lines 1978 1978
Branches 326 326
==================================================
Hits 1808 1808
Misses 90 90
Partials 80 80
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, think this can be released.
@evertonfraga If you do the release can you also do a short announcement on https://gitter.im/ethereum/ethereumjs ? Thanks!
Note: we should talk this through in our next call, eventually it might be better to rather keep a more generalized |
@holgerd77, good idea. I created the branch |
I have added the commits until right before the monorepo transition, and cherry-picked the bugfix from #733. Given that we had some additions on #663 and #651, I am bumping a minor, instead of a patch. Full details are on the Changelog file.
I have created a branch called
vm/release-v4.1.3
to support in the review process for this PR. It is identical to thev4.1.3
tag, so the branch can be deleted after releasing v4.2.0.Note: this PR should not be merged. Branch
vm/release-v4.2.0
should be kept.