Repository navigation
fix(deps)!: Bump Microsoft.CodeAnalysis.CSharp from 4.14.0 to 5.9.0 - #190
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Microsoft.CodeAnalysis.CSharp dependency-version: 5.9.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Major version bump (`` → |
|
Closing:
Generated by Claude Code |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…'s minors, and group the families pinned together Dependabot ignored the semver-major updates of the frameworks only, so 23 of the 44 dependencies .github/shipped-dependencies lists opened their next major as a fix(deps)! pull request: a bump, where the repository's rule is that a new major is supported by a decision, a floor or a target framework. Every shipped dependency's major is now ignored, test-only packages of the same families moving with them (xunit.v3*, protobuf-net*, Microsoft.Azure.Functions.Worker*, ModelContextProtocol*). Microsoft.CodeAnalysis.CSharp* ignores its minors too: its major.minor is the oldest compiler that loads the generator, since an analyzer referencing a later Microsoft.CodeAnalysis fails with CS9057, so a minor raises it as a major does. #190 (4.14.0 -> 5.9.0) contradicts the root CLAUDE.md's "never raise it to follow a dependency" and fails NU1107 in CodeFixes and NU1608 in GeneratorTests. xunit.v3*, Microsoft.CodeAnalysis*, HotChocolate* and ModelContextProtocol* require one another at exactly one version, so a partial bump fails the restore (#189: xunit.v3.assert 4.0.2 against xunit.v3.mtp-v2 4.0.1, NU1608). Each family now updates in a pull request of its own, ahead of the dotnet group, so that a red family holds back no other update. A group does not make Dependabot update every member; docs/maintaining.md says what to do when one is left behind, and to check the shipped dependencies for a new major before each stable release, since Dependabot no longer proposes them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0164hf4jJ3KsP3tyC3Uoa55L
…'s minors, and group the families pinned together Dependabot ignored the semver-major updates of the frameworks only, so 23 of the 44 dependencies .github/shipped-dependencies lists opened their next major as a fix(deps)! pull request: a bump, where the repository's rule is that a new major is supported by a decision, a floor or a target framework. Every shipped dependency's major is now ignored, test-only packages of the same families moving with them (xunit.v3*, protobuf-net*, Microsoft.Azure.Functions.Worker*, ModelContextProtocol*). Microsoft.CodeAnalysis.CSharp* ignores its minors too: its major.minor is the oldest compiler that loads the generator, since an analyzer referencing a later Microsoft.CodeAnalysis fails with CS9057, so a minor raises it as a major does. #190 (4.14.0 -> 5.9.0) contradicts the root CLAUDE.md's "never raise it to follow a dependency" and fails NU1107 in CodeFixes and NU1608 in GeneratorTests. xunit.v3*, Microsoft.CodeAnalysis*, HotChocolate* and ModelContextProtocol* require one another at exactly one version, so a partial bump fails the restore (#189: xunit.v3.assert 4.0.2 against xunit.v3.mtp-v2 4.0.1, NU1608). Each family now updates in a pull request of its own, ahead of the dotnet group, so that a red family holds back no other update. A group does not make Dependabot update every member; docs/maintaining.md says what to do when one is left behind, and to check the shipped dependencies for a new major before each stable release, since Dependabot no longer proposes them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0164hf4jJ3KsP3tyC3Uoa55L
Updated Microsoft.CodeAnalysis.CSharp from 4.14.0 to 5.9.0.
Release notes
Sourced from Microsoft.CodeAnalysis.CSharp's releases.
5.0.4
Release
5.0.2
Release Notes
Install Instructions
Repos
5.0.1
Release Notes
Install Instructions
Repo
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)