build(metadata): store requirement constraints semantically#482
Merged
Conversation
This effectively reverts commit 2a4fab4.
Testing the 1.21.11 build against 1.21.10 locally, the onDisconnect mixin does not apply.
Contributor
📦 ChangelogUnreleasedAdded
Changed
Removed
Fixed |
This was referenced May 25, 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.
stonecutter.properties.tomlto semver syntax.reqsconstraints as semanticConstraintobjects inModMetadata.Constraints usingtoString()andtoMavenFormat(), as appropriate.I also tested each of our
supported_mc_versionsclaims, and found that our1.21.11build does not actually work on1.21.10. Therefore, I've dropped support for1.21.10.