-
Notifications
You must be signed in to change notification settings - Fork 63
Conversation
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.
One small nitpick
c1888ec
to
bbf96f2
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.
Same here, I think it would make sense to directly update this to v1.1.0 (so ^1.1.0
(once released), then the library will be more safe to be used in a Petersburg
context and we can directly state this in the subsequent release notes here.
@danjm If you want you can directly update to safe time. I can then re-trigger CI once the new Common
version is released.
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.
Update: then please also update the ethereumjs-block
dependency to ~2.2.0
. This is the version I would do the Petersburg release on, and then we are Petersburg ready here along the dependency chain.
Will re-trigger CI once both releases are available.
bbf96f2
to
cc2fd89
Compare
@holgerd77 Updated ethereumjs-common to |
c15f383
to
d433265
Compare
Retriggered both builds here after v2.2.0 release of the block library. |
This PR updates code and package.json to use ethereumjs-common v1.1.0