Bump the test-packages group with 2 updates #40
Closed
Conversation
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
Bumps NUnit.Analyzers from 4.10.0 to 4.11.2 Bumps NUnit3TestAdapter from 5.2.0 to 6.0.0 --- updated-dependencies: - dependency-name: NUnit.Analyzers dependency-version: 4.11.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: test-packages - dependency-name: NUnit3TestAdapter dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-packages ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
.NET
Contributor
|
Closing as superseded - these package updates have been incorporated into a combined .NET 10 upgrade commit. |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
ElanHasson
added a commit
that referenced
this pull request
Dec 21, 2025
- Upgrade target framework from net9.0 to net10.0 - Update CI/CD workflows to use .NET 10.0.x SDK - Upgrade packages: - Microsoft.CodeAnalysis.CSharp.Scripting: 4.14.0 → 5.0.0 - Microsoft.Extensions.Hosting: 10.0.0-rc.2 → 10.0.1 - Microsoft.NET.Test.Sdk: 18.0.0 → 18.0.1 - NuGet.Protocol: 6.14.0 → 7.0.1 - NuGet.Resolver: 6.14.0 → 7.0.1 - NUnit.Analyzers: 4.10.0 → 4.11.2 - NUnit3TestAdapter: 5.2.0 → 6.0.0 - Remove unnecessary System.Formats.Asn1 package (now built into .NET 10) - Update tests to work with NUnit 6.0 console output behavior - Update console output capture to use synchronized TextWriter This commit supersedes PRs #36, #37, #39, and #40. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3 tasks
ElanHasson
added a commit
that referenced
this pull request
Dec 21, 2025
* Upgrade to .NET 10 and update all packages - Upgrade target framework from net9.0 to net10.0 - Update CI/CD workflows to use .NET 10.0.x SDK - Upgrade packages: - Microsoft.CodeAnalysis.CSharp.Scripting: 4.14.0 → 5.0.0 - Microsoft.Extensions.Hosting: 10.0.0-rc.2 → 10.0.1 - Microsoft.NET.Test.Sdk: 18.0.0 → 18.0.1 - NuGet.Protocol: 6.14.0 → 7.0.1 - NuGet.Resolver: 6.14.0 → 7.0.1 - NUnit.Analyzers: 4.10.0 → 4.11.2 - NUnit3TestAdapter: 5.2.0 → 6.0.0 - Remove unnecessary System.Formats.Asn1 package (now built into .NET 10) - Update tests to work with NUnit 6.0 console output behavior - Update console output capture to use synchronized TextWriter This commit supersedes PRs #36, #37, #39, and #40. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Fix tests for AssemblyLoadContext isolation in .NET 10 - Add AssemblyLoadContext workaround for CSharpScript compatibility - Update tests to verify execution success and return values instead of console output (Console.SetOut doesn't propagate across ALCs) - Change timeout test to use Task.Delay which respects cancellation - Minor cleanup in CSharpEvalTools (use CancelAsync) See: dotnet/roslyn#45197 (comment) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
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.
Updated NUnit.Analyzers from 4.10.0 to 4.11.2.
Release notes
Sourced from NUnit.Analyzers's releases.
4.11.2
NUnit Analyzers 4.11.2 - November 2, 2025
This release of the NUnit Analyzers fixes a problem in the
NUnit2057analyzer for unnecessary use of lambdaexpressions. The release also extends
NUnit2021so that it can determining ifIs.NaNorIs.Not.NaNconstraintsare used on incompatible types.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
4.11.1
NUnit Analyzers 4.11.1 - October 30, 2025
This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
NUnit1001andNUnit1031. The release also contains a new analyzer and codefix for unnecessary usage of lambdaexpressions in asserts.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
4.11.0
NUnit Analyzers 4.11 - October 28, 2025
This release of the NUnit Analyzers includes improvements and fixes related to
IDisposablehandling and initializationin
SetUpandOneTimeSetUpmethods. It also introduces the ability to configure additional methods that should betreated as
SetUpandTearDownmethods by the analyzers. This can be done in the.editorconfig, and there are fourconfigurations for this:
dotnet_diagnostic.NUnit.additional_setup_methodsdotnet_diagnostic.NUnit.additional_teardown_methodsdotnet_diagnostic.NUnit.additional_one_time_setup_methodsdotnet_diagnostic.NUnit.additional_one_time_teardown_methodsEach configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:
dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInitAs in recent releases, a major part of this work was contributed by @manfred-brands.
The release contains contributions from the following users (in alphabetical order):
Issues Resolved
Features and Enhancements
Bugs
Tooling, Process, and Documentation
Commits viewable in compare view.
Updated NUnit3TestAdapter from 5.2.0 to 6.0.0.
Release notes
Sourced from NUnit3TestAdapter's releases.
6.0.0
See release notes
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions