Backport Granite Mainnet Release to v1.9.0
This PR contains a cherry-picked commit to fix incompatibilities with recent superchain-registry depedency. The second commit is what you should be more attentive to.
This is based on the op-geth release tag v1.101315.3-granite-mainnet, which is itself a backport of the mainnet release onto v1.101315.3 (refer to this diff for the changes)
I take it all the alt-da changes is to preserve compatibility with changes in the superchain-registry?
I take it all the alt-da changes is to preserve compatibility with changes in the superchain-registry?
caught me updating the PR description to mention this. Yup!
op-geth devnet tests fail with Fatal: Failed to register the Ethereum service: incompatible state scheme, stored: path, provided: hash. I'm confused how this failure can be triggered by the changes done in this PR.
I remember that I've seen this once before in a PR of mine, but then I merged in latest develop and it was fixed. But this is not an option here. I think we can be pragmatic in this case and just completely disable and ignore the devnet tests for this PR, since this is just a backport.
op-geth devnet tests fail with
Fatal: Failed to register the Ethereum service: incompatible state scheme, stored: path, provided: hash. I'm confused how this failure can be triggered by the changes done in this PR.I remember that I've seen this once before in a PR of mine, but then I merged in latest develop and it was fixed. But this is not an option here. I think we can be pragmatic in this case and just completely disable and ignore the devnet tests for this PR, since this is just a backport.
Yeah, thanks for flagging. I agree that we should ignore the devnet test.
Something in the devnet test is using latest rather than a fixed version so old versions broke when the latest upstream geth got merged in. Agreed its safe to ignore that failure.
This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 5 days.