-
Notifications
You must be signed in to change notification settings - Fork 788
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
Monorepo: Beta 1 Releases #1957
Monorepo: Beta 1 Releases #1957
Conversation
Codecov Report
Flags with carried forward coverage won't be shown. Click here to find out more. |
Excited to be reading these changes. Do you want nit type feedback now or once you've finished the first draft? I haven't noticed anything major at this point. |
cbab421
to
0349d2e
Compare
Please do not do Merge commits on this PR (and in case you do please use the rebase UI option), there is no changes which would be needed to be integrate (and proof still working together) on this particular PR and I would do at the very end of the process. (I have now force-pushed with my original commits just to clean up a bit, totally nothing grave though) Generally: yes, you can very much do nit comments respectively this is very welcome, the more we catch now the less we need to update later. 🙂 |
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.
Couple nits :)
|
||
With this round of breaking releases the whole EthereumJS library stack removes the [BN.js](https://github.com/indutny/bn.js/) library and switches to use native JavaScript [BigInt](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/BigInt) values for large-number operations and interactions. | ||
|
||
This makes the libraries more secure and robust (no more BN.js v4 vs v5 incompatibilities) and generally comes with substantial performance gains for the large-number-arithmetic-intense parts of the libraries (particularly the VM). |
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.
Did we ever do a final performance analysis? Could be cool to quantify the performance gains (e.g. .'substantial performance gains of up to 70% [...]')
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.
Yeah, that would be nice. Would be really cool e.g. to teaser with some cool graph on this within the Release Announcement Tweet e.g.. 🤩 💯
(so we likely won't be able to include these kind of additions for the Beta 1 release changelogs, but we can very well still add to the changelogs later on.)
ab8bc97
to
e00ff6f
Compare
|
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.
Reviewed the block changelog
410ac40
to
1cafe65
Compare
@gabrocheleau thanks for the updated review on the Block library, have integrated. |
|
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.
Reviewed blockchain changelog
6759f8c
to
7eae9bd
Compare
Additional changelogs for Devp2p, Ethash, RLP, StateManager (this one in particular), so all CHANGELOG files written except EVM and VM. Open for review. 🙂 |
Ok, ready. 🙂 |
Ok, this is now completely ready respectively I currently assume it is which might be something different. 😋 Please give both the last CHANGELOGs a proper review AND try to give this some deeper thought if there might be something missing regarding the releases, not in the terms of features/fixes/clean-ups (you can still side-think about that one too) but here rather in terms of "have we technically updated everything which is necessary so that these releases will work when being installed". Thanks for your collaboration 😎 and contribution here 🦄 and the overall team work on this! ❤️ Really looking forward to do the releases tomorrow!!! 😄 |
Co-authored-by: Gabriel Rocheleau <contact@rockwaterweb.com> Co-authored-by: acolytec3 <17355484+acolytec3@users.noreply.github.com>
5d37247
to
6a6404b
Compare
@acolytec3 @gabrocheleau thanks for the additional reviews, will merge and do the releases soon once CI passes here! 🥳 |
Ah, sorry, need to admin-merge here since I needed to dismiss the current reviews with change requests (which I have addressed), hope that's ok. Would want to continue here and no code parts touched. |
Just did a first test publication of RLP, Util and Common, this seems to work well. Have published with Taking the @ethereumjs/common npm page as an example, there is the confirmation that the old version Also did a test install with Another way to install is with the direct package version including the beta version addition, so with Will now proceed with the rest of the releases. |
Just published the following releases on npm:
|
Ugh. 🙂 |
Part of #1914
For these releases I will split up the changelogs and the additional version updates and so on into (at least) two commits, this one is for just updating the changelogs.
WIP, just wrote the changes for a first library together (Common). Can be reviewed though along writing and submission already.