You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up issue on #681, will close there since issue is over-used and gotten clustered over time, still valuable reference though.
We are closing in on the release of VM v5 and related libraries into the @ethereumjs/[LIBRARY_NAME] namespace with several major releases. This issue is to keep track on the last to be applied changes and follow up on the process.
Procedure
Suggested procedure is to do a beta release series mid or end next week (CW42), then collect feedback and either follow up with a second beta - eventually RCs (to be decided on the nature of the feedback received) and target the final releases for two weeks later (CW44).
Work down package dependency graph on releases, start with Common
Update CHANGELOG on completeness adding missing PRs merged since latest release date
Bump version in package.json, bump monorepo versions of all dependencies and devDependencies to released versions, on final releases re-introduce caret ^ dependency range!
Update the respective README from package folder to match to be released version
Rebuild documentation
Run linting
Check diff
Commit everything
Take a breath. 🌿 🌻 🐹
Go to 0., repeat for all packages
=> Push. Review. Merge.
Work down package dependency graph on releases, start with Common
Build locally, one final test run, check package contents with npm pack
Release from package folders manually with npm publish [--tag beta] (latest tag replacement: on non-final releases (beta, rc,...), exception: first round of scoped package releases)
Check everything on the respective npm package site
Follow-up issue on #681, will close there since issue is over-used and gotten clustered over time, still valuable reference though.
We are closing in on the release of VM v5 and related libraries into the
@ethereumjs/[LIBRARY_NAME]
namespace with several major releases. This issue is to keep track on the last to be applied changes and follow up on the process.Procedure
Suggested procedure is to do a
beta
release series mid or end next week (CW42), then collect feedback and either follow up with a second beta - eventually RCs (to be decided on the nature of the feedback received) and target the final releases for two weeks later (CW44).Remaining TODOs
ethereumjs-config
v2.0
update, Updates to ethereumjs-config v2.0.0 (old) #886 , @evertonfragaUtil.Account
class from the work on Add Account class ethereumjs-util#275 by @ryanio, Replace account package with ethereumjs-util Account #911Util
Account
class, @ryaniopackages
, remove CI integrations, @ryanioUtil.Address
class from the work on Introduce Address type ethereumjs-util#186 by @s1na and @ryanio, @ryaniodefineProperties
removal check, follow-up PRs (candidate to somewhat postpone release process), @ryaniodev
releases)Releases
Process Checklist
Common
package.json
, bump monorepo versions of alldependencies
anddevDependencies
to released versions, on final releases re-introduce caret ^ dependency range!README
from package folder to match to be released version=> Push. Review. Merge.
Common
npm pack
package
folders manually withnpm publish [--tag beta]
(latest
tag replacement: on non-final releases (beta
,rc
,...), exception: first round of scoped package releases)npm
package site@ethereumjs/[email protected]
towardsmaster
@ethereumjs/common v2.0.0-beta.1
CHANGELOG.md
, addbeta
headerpre-release
!!!Release Checklist
Will take the current
npm
packages as main links.ethereumjs-vm
v4.2.0
->@ethereumjs/vm
v5.0.0
v5.0.0-beta.1
Releasev5.0.0-beta.2
Releasev5.0.0-rc.1
Releasev5.0.0
Releaseethereumjs-block
v2.2.2
->@ethereumjs/block
v3.0.0
v3.0.0-beta.1
Releasev3.0.0-beta.2
Releasev3.0.0-rc.1
Releasev3.0.0
Releaseethereumjs-blockchain
v4.0.4
->@ethereumjs/blockchain
v5.0.0
v5.0.0-beta.1
Releasev5.0.0-beta.2
Releasev5.0.0-rc.1
Releasev5.0.0
Releaseethereumjs-common
v1.5.2
->@ethereumjs/common
v2.0.0
v2.0.0-beta.1
Releasev2.0.0-beta.2
Releasev2.0.0-rc.1
Releasev2.0.0
Releaseethashjs
v0.0.8
->@ethereumjs/ethash
v1.0.0
v1.0.0-beta.1
Releasebeta.2
release plannedv1.0.0-rc.1
Releasev1.0.0
Releaseethereumjs-tx
v2.1.2
->@ethereumjs/tx
v3.0.0
v3.0.0-beta.1
Releasev3.0.0-beta.2
Releasev3.0.0-rc.1
Releasev3.0.0
Release🍀
The text was updated successfully, but these errors were encountered: