-
Notifications
You must be signed in to change notification settings - Fork 73
Feat: update single sequencer network config #1014
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
Merged
tomatoishealthy
merged 4 commits into
main
from
feat/network-upgrade-with-single-sequencer
Jul 8, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Submodule go-ethereum
updated
40 files
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: morph-l2/morph
Length of output: 2706
🌐 Web query:
Go module replace directive version valid semantic version arbitrary tag go mod tidy replace module path version docs💡 Result:
In a Go replace directive, the version on the right-hand side is subject to specific requirements depending on the type of replacement [1][2]. For remote module replacements (non-filesystem paths), a version is required on the right-hand side of the arrow (=>) [1][2]. This version must be a valid, resolved version string (e.g., v1.2.3, or a pseudo-version like v0.0.0-20260708000000-abcdef123456) that the Go command can resolve [1][2]. Arbitrary Git branch names (such as master or main) are not valid versions and cannot be used directly in a replace directive [3]. To use code from a specific branch or commit of a fork: 1. You must ensure the target commit is accessible or reachable via a valid pseudo-version [3]. 2. You can use the go get command with the branch name to resolve the correct pseudo-version for that commit (e.g., go get example.com/fork@branchname) [3]. 3. Once resolved, you update your go.mod replace directive to use the specific version (pseudo-version) identified by the Go toolchain [3]. Regarding go mod tidy: * The go mod tidy command does not automatically remove unused replace directives [4]. * The replace directive only has an effect if the module and version on the left-hand side are currently present in your build list (required by your module or one of its dependencies) [1][2]. * If you include a replace directive for a module that is not required, the directive will be ignored [1][2][4]. * If your replacement target has its own dependencies that conflict with or are not handled by the replacement, go mod tidy may attempt to add them to your go.mod file, which can occasionally lead to errors if not configured correctly [5]. In summary, you cannot use arbitrary tags or branch names as versions in replace directives; you must use valid, resolvable semantic versions or pseudo-versions [1][3][2].
Citations:
🏁 Script executed:
Repository: morph-l2/morph
Length of output: 2250
Split the Go module version from the submodule tag
morph-v2.2.4is fine forgit checkout, but not for thego.modrewrite.go mod tidyexpects a Go-valid version on the module line, so this target will fail unless the update path uses a semver/pseudo-version instead.🤖 Prompt for AI Agents