modules: drop legacy config compatibility - #2350
Open
lasers wants to merge 1 commit into
Open
Conversation
lasers
force-pushed
the
class-meta-legacy
branch
from
July 30, 2026 02:17
3f2819e to
e43ea1c
Compare
Contributor
Author
|
@ultrabug This can come after Some bad decisions were definitely made (ie replacing |
lasers
force-pushed
the
class-meta-legacy
branch
5 times, most recently
from
August 8, 2026 19:03
b483d32 to
7d18351
Compare
Contributor
Author
|
@ultrabug What next? This. |
lasers
force-pushed
the
class-meta-legacy
branch
from
August 8, 2026 21:14
7d18351 to
ef5bc29
Compare
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
1 participant
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.
(cleanup) This removes legacy stuff. We kept them long enough.