forked from ethereum-optimism/optimism
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge upstream ci builder #64
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [eslint-plugin-unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn) from 42.0.0 to 48.0.1. - [Release notes](https://github.com/sindresorhus/eslint-plugin-unicorn/releases) - [Commits](sindresorhus/eslint-plugin-unicorn@v42.0.0...v48.0.1) --- updated-dependencies: - dependency-name: eslint-plugin-unicorn dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.5.0 to 20.6.1. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
Fixes a bug where the host incorrectly informs the client that a custom chain config is in use. The client then attempts to read the chain config pre-image data. However, this pre-image data will not be available in on-chain contexts.
ven -> even
it's -> its
…sm#7283) Bumps ethereum/client-go from v1.13.0 to v1.13.1. --- updated-dependencies: - dependency-name: ethereum/client-go dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…4-fix_indexer_Fix_uri_util fix(indexer): Fix uri util
…ndabot/npm_and_yarn/types/node-20.6.1 build(deps-dev): bump @types/node from 20.5.0 to 20.6.1
…4-chore_indexer_remove_indexer_all_command chore(indexer): remove indexer all command
…ndabot/npm_and_yarn/types/node-20.6.3 build(deps-dev): bump @types/node from 20.5.0 to 20.6.3
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 0.34.1 to 0.34.4. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v0.34.4/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
Bumps [glob](https://github.com/isaacs/node-glob) from 10.3.3 to 10.3.5. - [Changelog](https://github.com/isaacs/node-glob/blob/main/changelog.md) - [Commits](isaacs/node-glob@v10.3.3...v10.3.5) --- updated-dependencies: - dependency-name: glob dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
…ndabot/npm_and_yarn/vitest-0.34.4 build(deps-dev): bump vitest from 0.34.1 to 0.34.4
…ndabot/npm_and_yarn/glob-10.3.5 build(deps-dev): bump glob from 10.3.3 to 10.3.5
…oy-devnet-protocol-versions contracts-bedrock: internal devnet ProtocolVersions deployment
…ndabot/npm_and_yarn/envalid-8.0.0 build(deps): bump envalid from 7.3.1 to 8.0.0
…te-libp2p go: update libp2p to fix Go 1.21 build
Updates to the following commit: ethereum-optimism/superchain-registry@413695c This contains the changes required for the safe bundler tooling.
These geth types are legacy code and not being updated along with the definitions of the geth types. They were used in old regenesis events. They are not used elsewhere in the monorepo, keeping them around only adds tech debt.
…/superchain-registry deps: update superchain registry in go.mod
…/delete-dead-geth-types core-utils: delete unmaintained geth types
…/merge-upstream-ci-builder
boyuan-chen
approved these changes
Oct 5, 2023
mmontour1306
approved these changes
Oct 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This brings in the upstream code through the merge of the latest ci-builder changes.
The merge is being split into multiple pieces, because first we must get the repo into a state where it's ready for the new CI builder (the previous PR #63), then to a state where we can release the new CI builder (this PR), and finally back up to date utilizing the new CI builder (the next PR).
Rather than trying to cherry-pick out only the CI-builder changes, this PR brings us up to a point in Optimism's history by merging all previous commits as well.
Ignoring the markdown, go, png, go.mod/go.sum changes, this PR includes:
Note especially the contract changes in your review. These changes look benign to me, related only to the dispute games, but as usual, I am not a solidity expert so please scrutinize anyway.