forked from ethereum-optimism/superchain-registry
-
Notifications
You must be signed in to change notification settings - Fork 0
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 20240813 #22
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
* validation: verify eth-da via latest batcher tx * metal-sep: add missing BatchSubmitter address * confirm BatchSubmitter tx.To == BatchInboxAddr * run codegen to add metal-sep BatchSubmitter address * make da test signer more forwards compatible
fix: remove releases for now feat: crates releases simple script to release crates Co-authored-by: soyboy <[email protected]>
…#425) * env: wrap SCR_CHAIN_NAME val in quotes * add-chain: allow user to pass full filepath for deployments file * add-chain: support customGasToken contract sets * run linter * fix legacy logic for determining contract set * remove hardcoded contract sets and just read all available * go tidy add-chain * add-chain: remove unnecessary set to Address zero value * add-chain: use better type safety for castCall arg * ci: run 'git diff' after linter
* updating superchain registry * removing compressed genesis files * removing test exceptions --------- Co-authored-by: refcell <[email protected]>
* Add granite activation dates for devnet and testnet across all chains
…hereum-optimism#411) * run contract version check first * show a more useful error message to user when contracts don't match * remove unecessary exclusions these are frontier chains
Co-authored-by: George Knee <[email protected]>
* remove the unused assets directory * move detailed info from the top-level readme into a docs directory (currently called documentation) * put three simple calls-to-action front-and-center Co-authored-by: George Knee <[email protected]> --------- Co-authored-by: George Knee <[email protected]>
…ereum-optimism#447) * update diff tools to not fail, but post/update a comment instead * remove sentence * deduplicate diff actions * use versioning * do not use versions * TEMP (revertme) * remove comment if command passed * Revert "TEMP (revertme)" This reverts commit 871743a.
run in CI remove validation suite from unit tests command
* Change artifacts output file name * Add upload chain artifacts workflow * Use workload identity provider
Co-authored-by: zeever Sudo User <[email protected]> Co-authored-by: soyboy <[email protected]>
* remove docs from gitignore * s/documentation/docs * link to glossary
* feat(docs): binding documentation * fix(docs): bindings rendering * feat(docs): add binding docs link in readme
…ism#440) * feat(bindings): granite and holocene support * feat(bindings): granite channel timeout * fix(bindings): set granite channel timeout as a field of the rollup config
…mism#455) * add spec for hardfork activation inheritance behaviour * add cautionary notes about manual coordination
…thereum-optimism#464) * CI: New job to run periodic chain validation and minor refactoring * Add a new job and slack notification target to run validation of all chains on a periodic basis. * Move the step to validate modified chains into it's own job and add that job to the `pr-checks` list. * Alter existing cron job to run this new job instead of golang-test, which runs all unit tests. * Add new slack channel ID and resolve review comments * added id for new slack channel * resolved other review comments * incorrect tag to force validation failure * Don't notify slack when running validation on mods modifications in commits are evaluated against main and is used either in PR commit checks or when commits are pushed to main (zero diff). No need to notify failures to slack in the former case. --------- Co-authored-by: Vinod Damle <[email protected]>
remove the erroneous tag which was used for testing Co-authored-by: Vinod Damle <[email protected]>
…optimism#469) * add-chain: add max_sequencer_drift field * superchain: update all chain configs to include max_sequencer_drift
* add pull_request_template.md --------- Co-authored-by: Tess Rinearson <[email protected]>
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.
No description provided.