Repository navigation
docs: decision 129, Metalama 2027.0 moves into 2.4.0 - #282
Open
CaffeinatedCoder wants to merge 1 commit into
Open
CaffeinatedCoder wants to merge 1 commit into
CaffeinatedCoder wants to merge 1 commit into
Conversation
2.4.0 must build for every .NET 11 consumer, also one with only SDK 11 installed. On Metalama 2026.1 a web project fails there with LAMA0625, on net10.0 as on net11.0 (KB-060, #275), so the Generators package moves to Metalama 2027.0 in 2.4.0 for both targets, and 2.4.0 is tagged only on a stable 2027.0. A CI lane with only SDK 11 installed joins decision 120's conditions (#281); 2.3.x is the line below the ceiling. #173, #272 and #223 move to the 2.4.0 epic. Replaces decision 120's Metalama timing. Closes #280 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CaffeinatedCoder
added
documentation
This branch has not been deployed
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.
Closes #280
Problem
The maintainer requires 2.4.0 to build for every .NET 11 consumer, also one with only the .NET 11 SDK installed. Decision 120 kept 2.4.0 on Metalama 2026.1, and on 2026.1 a web project with the Generators package fails with
LAMA0625wherever SDK 11 is the only SDK, onnet10.0as onnet11.0(#275, KB-060).Change
design/adr/0129-metalama-2027-0-moves-into-2-4-0.md: the Generators package moves to Metalama 2027.0 in 2.4.0, for both targets; 2.4.0 is tagged only on a stable 2027.0; a CI and smoke-test lane with only SDK 11 installed and a web consumer joins decision 120's conditions (CI and the smoke test: a lane with only SDK 11 installed, with a web consumer (decision 129) #281); 2.3.x is the line below the ceiling; the alternatives refused. It replaces decision 120's Metalama timing and nothing else.design/adr/README.md: the 0129 row, and 0120's status naming it.design/roadmap.md: the Metalama item says 2.4.0, 2.3.x and CI and the smoke test: a lane with only SDK 11 installed, with a web consumer (decision 129) #281.Outside the repository, done: #173, #272 and #223 moved to the 2.4.0 epic (#177) and milestone; #177 and #219 rewritten; #208, #209, #210, #213, #214 corrected where they assumed 2026.1 in 2.4.0; #275 and #170 updated.
Tests
Prose only.
docs-query check(0 problems in 924 links) and the conventions project (2096 passed,DesignRecordTestsamong them) pass in this worktree.🤖 Generated with Claude Code