Develop -> Master Release PR

Version Packages

Develop -> Master PR

fix: update contracts release to patch

l2geth: to execution manager run

Fix `toExecutionManagerRun` in cases where `asOvmMessage` isn't applied.
Note that tracing currently does not work for optimistic ethereum.

feat: use FallbackProvider in the DTL

Allow the DTL to sync from multiple web3 backends using
the `ethers.providers.FallbackProvider`. Multiple URLs
can be passed through as a comma delimited string to
configure multiple providers.

A helper function is added to `core-utils` to allow
easy configuration between services. This PR only introduces
the usage of the fallback provider into the DTL. In the
future, it should be added to other services that query L1
as well.

Remove L1 contracts from L2 state dump process

[added] coverage for getMerkleTreeProof

batch-submitter: remove call to `appendQueueBatch`

docs: point to new specs repository

Watcher: l1 vs l2 blocksToFetch

Adds new config options to the watcher to allow it to upgrade in
a non breaking way. New config options include setting a global
`pollForPending` and `blocksToFetch`. It is also possible to
specify the number of blocks to fetch on each `Layer`.

The event ids are precomputed and held as globals instead of computed
on the fly each time.

chore(deps): bump mixme from 0.5.1 to 0.5.2

Bumps [mixme](https://github.com/adaltas/node-mixme) from 0.5.1 to 0.5.2.
- [Release notes](https://github.com/adaltas/node-mixme/releases)
- [Changelog](https://github.com/adaltas/node-mixme/blob/master/CHANGELOG.md)
- [Commits](https://github.com/adaltas/node-mixme/compare/v0.5.1...v0.5.2)

---
updated-dependencies:
- dependency-name: mixme
  dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>

Develop -> Master Release PR

Version Packages

Develop -> Master PR

l2geth: config enable arbitrary contract deployment

Update labeler.yml

Add a new config option `ROLLUP_ENABLE_ARBITRARY_CONTRACT_DEPLOYMENT`.
This config option must be set with an env var, there is no flag to
set it with.

If it is not set, the functionality is unchanged. If it is set, then it
will override the function `isDeployerAllowed(address)` on the
`OVM_DeployerWhitelist`

ci: fix workflow for exporting logs

The logs after failure are not being exported correctly as they are not
being written to the correct location. Previously `~` was not being
interpreted as `$HOME`. This assumes that the `cwd` is `$HOME`.

Develop -> Master Release PR

Version Packages

Develop -> Master PR

fix: use the same nonce for each batch submission