Release 220.0.0

[legobeat]

Explanation

• Release package @metamask/json-rpc-engine
  • Release dependent @metamask/json-rpc-middleware-stream
  • Not releasing dependents which are still on @metamask/rpc-errors v6
    • Pending deps: @metamask/rpc-errors@^6.3.1->^7.0.0 #4769

References

Contents:

• deps(json-rpc-engine): @metamask/rpc-errors@^6.3.1->^7.0.0 #4773
• deps(eth-json-rpc-provider): @metamask/rpc-errors@^6.3.1->^7.0.0 #4799

Checklist

• I've updated the test suite for new or updated code as appropriate
• I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• I've highlighted breaking changes using the "BREAKING" category above as appropriate
• I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

[legobeat]

Looking at what comes next in terms of downstream updates, I think it would also be good to get @metamask/eth-json-rpc-provider in there:

• deps(eth-json-rpc-provider): @metamask/rpc-errors@^6.3.1->^7.0.0 #4799

[OGPoyraz]

This one is a bit urgent #4739, can we include transaction-controller in to this release?

[legobeat]

This one is a bit urgent #4739, can we include transaction-controller in to this release?

I think it will make things a lot less messy if this can be released without including packages still transitively depending on old @metamask/json-rpc-engine versions in order to not introduce dependency inconsistencies within a package. After that, other packages should be releasable even without first merging the entirety of #4769, which depends on resolving those intermediaries.

If you think we can sort it out and that a single release is preferred, feel free to make a PR targeting this with the necessary changes, though.