Release 1.0.0 - #39
Merged
Merged
Conversation
Same content as 1.0.0-rc9340, without the prerelease label. The immediate reason is that `dotnet add package DependencyModules.Runtime` fails with "There are no stable versions available" against a feed carrying only prereleases, which is the first thing a new reader does and the first thing that goes wrong. The DM#### rules move from AnalyzerReleases.Unshipped.md to Shipped under Release 1.0.0, which is what the release-tracking analyzer wants at a stable release and what makes a future rule's arrival visible as a diff. VersionSuffix is emptied. The release workflow takes the published version from the git tag, so this only affects local builds, but leaving an rc label in a stable tree is a trap for whoever reads it next. The breaking changes gathered through the candidates land here rather than after, which is the point of doing them now: DecoratorExpansion.Expand changed shape, and [InjectValues] is restricted to parameters. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CMV4J1eVscS5EBMUhhWc2x
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.
Same content as
1.0.0-rc9340, without the prerelease label.The immediate reason is that
dotnet add package DependencyModules.Runtimefails with "There are no stable versions available" against a feed carrying only prereleases — the first thing a new reader does, and the first thing that goes wrong. The README and docs already show the plain command, which becomes true when this ships.What changes
## [1.0.0]in the changelog, stating what stability covers: the attributes, convention contracts, runtime interfaces and testing attributes are under semver for 1.x. Deliberately outside it, and documented as such — the generator extension pointsSourceGenerator.Implships as source, and the exact text of generated code.DM####rules move fromAnalyzerReleases.Unshipped.mdtoShippedunder Release 1.0.0.VersionSuffixemptied. The workflow takes the published version from the tag, so this only affects local builds, but an rc label in a stable tree misleads whoever reads it next.The breaking changes gathered through the candidates land here rather than after, which is the point of doing them now:
DecoratorExpansion.Expandchanged shape, and[InjectValues]is restricted to parameters.Verification
scripts/verify-packages.sh 1.0.0passes for net8.0 and net10.01.0.0-rc9340was published first and verified from nuget.org in a clean project with only the public feed: builds underTreatWarningsAsErrorsand runs, including a nullable service type argument — the CS8669 case this round fixes🤖 Generated with Claude Code
https://claude.ai/code/session_01CMV4J1eVscS5EBMUhhWc2x