You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Decision 129: Metalama 2027.0 moves into 2.4.0, so a consumer with only SDK 11 builds #280
The maintainer's requirement (2026-10-31): 2.4.0 compiles for every .NET 11 consumer, also one with only the .NET 11 SDK installed. Metalama 2026.1 cannot meet it: a web project with the Generators package fails with LAMA0625 on SDK 11 alone (#275, KB-060, spikes/Sdk11Rc3Metalama).
A new decision record replaces decision 120's Metalama timing: Metalama 2027.0 moves into 2.4.0 for both targets, and 2.4.0 is tagged only on a stable 2027.0. The roadmap, #173 and the two epics follow it.
Done when decision 129 and its index row are in, decision 120's status names it, the roadmap says it, #173 and #272 are under the 2.4.0 epic, the 2.5.0 epic's goal is rewritten, the SDK-11-only CI lane has its issue, and #275 and #170 say what changed.
changed the title [-]Decision 131: Metalama 2027.0 moves into 2.4.0, so a consumer with only SDK 11 builds[/-][+]Decision 129: Metalama 2027.0 moves into 2.4.0, so a consumer with only SDK 11 builds[/+]on Oct 31, 2026
Activity
[-]Decision 131: Metalama 2027.0 moves into 2.4.0, so a consumer with only SDK 11 builds[/-][+]Decision 129: Metalama 2027.0 moves into 2.4.0, so a consumer with only SDK 11 builds[/+]