Bump the nuget-deps group with 8 updates - #445
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps AwesomeAssertions from 9.5.0 to 9.6.0 Bumps Microsoft.Extensions.Http.Resilience from 10.8.0 to 10.9.0 Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.10 to 10.0.11 Bumps Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0 Bumps Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400 Bumps xunit.analyzers from 1.27.0 to 2.0.0 Bumps xunit.runner.visualstudio from 3.1.5 to 4.0.0 Bumps xunit.v3 from 3.2.2 to 4.0.0 --- updated-dependencies: - dependency-name: AwesomeAssertions dependency-version: 9.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-deps - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps - dependency-name: Microsoft.SourceLink.GitHub dependency-version: 10.0.400 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-deps - dependency-name: xunit.analyzers dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-deps - dependency-name: xunit.runner.visualstudio dependency-version: 4.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-deps - dependency-name: xunit.v3 dependency-version: 4.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget-deps ... Signed-off-by: dependabot[bot] <support@github.com>
ptr727 added a commit
that referenced
this pull request
Aug 29, 2026
## Why The .NET 10 SDK dropped the VSTest bridge `dotnet test` relied on, so `dotnet test` failed outright on every PR: `Testing with VSTest target is no longer supported by Microsoft.Testing.Platform on .NET 10 SDK and later.` This is what was blocking #443, #444, #445, and #446 (all four currently fail on the `Run unit tests job`). ## What - Opt `UtilitiesTests` into native Microsoft.Testing.Platform (MTP): `global.json`'s `test.runner` setting, plus `UseMicrosoftTestingPlatformRunner`/`OutputType=Exe` on the test project, per the [official migration guide](https://learn.microsoft.com/en-us/dotnet/core/testing/migrating-vstest-microsoft-testing-platform). - Swap `coverlet.collector` (VSTest-only) for `Microsoft.Testing.Extensions.CodeCoverage`, the native MTP coverage provider. - Bump `Microsoft.NET.Test.Sdk` and the `xunit.v3` family to the versions that ship a compatible MTP runtime; the prior `xunit.v3` 3.2.2 pairing threw a `TypeLoadException` against the newer platform assembly. - Update the validate workflow's `dotnet test` invocation (`--coverage` instead of `--collect`), naming the output file explicitly (`--coverage-output coverage.cobertura.xml`): the extension's default GUID basename is not matched by codecov-action's file finder, so the upload step would otherwise silently find nothing under `fail_ci_if_error: false`. - Fix three `ExtensionsTests.cs` null-argument tests that were missing the null-forgiving operator a sibling test already used; `TreatWarningsAsErrors` never reached these under the old VSTest error, which aborted the build before the test project ever compiled. - Add `global.json` to the Solution Items folder and fix `Directory.Packages.props`'s alphabetical ordering. ## Verification Ran locally against .NET 10.0.400: `dotnet build` (0 warnings/errors), `dotnet test --coverage --coverage-output-format cobertura --coverage-output coverage.cobertura.xml --results-directory ./coverage` (183/183 passed, `coverage/coverage.cobertura.xml` produced), `dotnet csharpier check .`, and `dotnet format style --verify-no-changes` all clean. Reviewed with a local adversarial pass before pushing (fleet `local-strict-review`). ## Known trade-off `Microsoft.Testing.Extensions.CodeCoverage` ships native instrumentation for `win-x64/x86/arm64`, `linux-x64`, `linux-musl-x64`, and `osx-x64` only, no `osx-arm64` or `linux-arm64`. CI runs on `ubuntu-latest` (x64) and is unaffected, but coverage collection won't work locally on Apple Silicon or Linux arm64 dev machines, where `coverlet.collector` had none of that restriction. Flagging for awareness rather than blocking on it, since this is the officially recommended MTP coverage path. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Updated the test runner and testing tools for improved compatibility and execution. * Added consistent Cobertura code coverage reporting. * Preserved validation of expected compression and decompression errors. * **Chores** * Standardized .NET SDK and test environment configuration. * Updated test tooling and coverage integration packages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
ContributorAuthor
Looks like these dependencies are no longer updatable, so this is no longer needed. |
auto-merge was automatically disabled
August 30, 2026 21:18
Pull request was closed
dependabotBot
deleted the
dependabot/nuget/develop/nuget-deps-c7579a624f
branch
August 30, 2026 21:18
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 freeto 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 AwesomeAssertions from 9.5.0 to 9.6.0.
Release notes
Sourced from AwesomeAssertions's releases.
9.6.0
What's Changed
New features
Fixes
Documentation
Others
Dependencies
New Contributors
... (truncated)
Commits viewable in compare view.
Updated Microsoft.Extensions.Http.Resilience from 10.8.0 to 10.9.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
10.9.0
Version 10.9.0 is headlined by changes in these areas:
RoutingChatClientbase class, withSemanticRoutingChatClientas a concrete semantic-routing implementation. Separately, the abstractFailoverChatClientspecialization and its concreteOrderedFailoverChatClientimplementation add failover routing.Experimental API Changes
New Experimental APIs
EXTEXP0013) #7602MEAI001) #7662What's Changed
AI (
Microsoft.Extensions.AI,Microsoft.Extensions.AI.Abstractions, andMicrosoft.Extensions.AI.OpenAI)Note: Microsoft.Extensions.AI.OpenAI constrains its dependency for OpenAI to 2.12.x, preventing OpenAI updates to 2.13.0+ due to an incompatibility. We expect to release Microsoft.Extensions.AI.OpenAI version 10.9.1 during the week of August 17 to address this issue.
HTTP Resilience and Diagnostics (
Microsoft.Extensions.Http.ResilienceandMicrosoft.Extensions.Http.Diagnostics)ASP.NET Core Extensions (
Microsoft.AspNetCore.Diagnostics.Middleware)Logging Source Generator (
Microsoft.Gen.Logging)AI Evaluation (
Microsoft.Extensions.AI.Evaluation.Reporting)Project Templates (
Microsoft.McpServer.ProjectTemplates)... (truncated)
10.8.4
This servicing update refreshes the .NET AI project templates ahead of the July 30, 2026 retirement of GitHub Models — removing the GitHub Models provider option and updating template dependencies.
As a result, both the AI Chat Web (
aichatweb) and AI Agent Web API (aiagent-webapi) templates now require the AI service provider to be chosen explicitly via--provider; there is no longer a default. One of the following must be selected:--provider azureopenai— Azure OpenAI--provider ollama— Ollama (for local development)--provider openai— OpenAI PlatformPackages in this release
What's Changed
Project templates
--provideroption is now required with no default (#7667).Aspire.Hosting.AppHostto13.4.6andCommunityToolkit.VectorData.SqliteVecto1.0.0-preview.4(alignedSystem.Linq.AsyncEnumerableto10.0.9), replacing earlier workaround package pins (#7639).Full Changelog
10.8.3
Packages in this release
Experimental API Changes
Experimental API behavior updates
ToolApprovalRequestContent.RequiresConfirmationso it no longer leaks into consumer source-generatedAIContentJSON metadata unless approval APIs are intentionally used (#7659).What's Changed
AI abstractions and serialization
RequiresConfirmationin source-generatedAIContentcontexts by using an internal JSON-included backing member while keeping the public experimental member ignored for source-generation metadata (#7659).Test Improvements
List<AIContent>contexts compile and round-trip without requiring MEAI001 suppression (#7659).Full Changelog
10.8.2
This servicing release updates Microsoft.Extensions.VectorData.ConformanceTests to 10.8.2 and includes targeted test framework migration fixes.
Packages in this release
Update: August 7, 2026
The Microsoft.Extensions.VectorData.Abstractions package was initially excluded from this release by mistake. Because Microsoft.Extensions.VectorData.ConformanceTests has a dependency on Microsoft.Extensions.VectorData.Abstractions, that led to failures when updating to Microsoft.Extensions.VectorData.ConformanceTests 10.8.2.
Microsoft.Extensions.VectorData.Abstractions was published August 7, 2026 to resolve that issue.
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.1...v10.8.2
10.8.1
This servicing release updates the Microsoft.Extensions.AI, Microsoft.Extensions.AI.Abstractions, and Microsoft.Extensions.AI.OpenAI packages to 10.8.1 with two targeted fixes: correct tool-call/tool-result ordering when resuming approval-gated functions with service-managed chat history, and preservation of the OpenAI Responses reasoning item id for stateless (store=false) encrypted reasoning.
Packages in this release
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.0...v10.8.1
Commits viewable in compare view.
Updated Microsoft.Extensions.Logging.Abstractions from 10.0.10 to 10.0.11.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.8.1 to 18.9.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.9.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.8.0...v18.9.0
Commits viewable in compare view.
Updated Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400.
Release notes
Sourced from Microsoft.SourceLink.GitHub's releases.
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Updated xunit.analyzers from 1.27.0 to 2.0.0.
Release notes
Sourced from xunit.analyzers's releases.
2.0.0
Release notes: https://xunit.net/releases/analyzers/2.0.0
2.0.0-pre.60
Release notes: https://xunit.net/releases/analyzers/2.0.0-pre.60
2.0.0-pre.56
Release notes: https://xunit.net/releases/analyzers/2.0.0-pre.56
2.0.0-pre.51
Release notes: https://xunit.net/releases/analyzers/2.0.0-pre.51
2.0.0-pre.40
Release notes: https://xunit.net/releases/analyzers/2.0.0-pre.40
2.0.0-pre.9
Release notes: https://xunit.net/releases/analyzers/2.0.0-pre.9
Commits viewable in compare view.
Updated xunit.runner.visualstudio from 3.1.5 to 4.0.0.
Release notes
Sourced from xunit.runner.visualstudio's releases.
4.0.0
Release notes: https://xunit.net/releases/visualstudio/4.0.0
4.0.0-pre.5
Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.5
4.0.0-pre.4
Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.4
4.0.0-pre.3
Release notes: https://xunit.net/releases/visualstudio/4.0.0-pre.3
Commits viewable in compare view.
Updated xunit.v3 from 3.2.2 to 4.0.0.
Release notes
Sourced from xunit.v3's releases.
No release notes found for this version range.
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 <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