Repository navigation
Rename MONAD_ELEVEN to MONAD_NEXT_AMSTERDAM - #70
Merged
Merged
Conversation
Map it to monad revision 12. Co-Authored-By: Claude Opus 5.5
mijovic
approved these changes
Nov 3, 2026
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
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.
MONAD_NEXT_AMSTERDAM and MONAD_NEXT are now sibling forks coming after MONAD_TEN - adjusting to Amsterdam getting postponed.
(MONAD_NEXT placeholder not added yet for a cleaner diff)
The PR appears safe to merge; no actionable defects were established.Summary
Renames
MONAD_ELEVENtoMONAD_NEXT_AMSTERDAMacross the specs, fork definitions, tests, and release settings.pdobacz explicitly deferred the
MONAD_NEXTplaceholder for a cleaner diff.Reviews (1) · Last reviewed commit: "Rename MONAD_ELEVEN to MONAD_NEXT_AMSTER..." · Reviewed by Greptile