Repository navigation
Bump the patch-and-minor group with 20 updates - #8
Closed
dependabot[bot] wants to merge 2 commits into
Closed
dependabot[bot] wants to merge 2 commits into
dependabot[bot] wants to merge 2 commits into
Conversation
Bumps Azure.Extensions.AspNetCore.DataProtection.Blobs from 1.5.4 to 1.5.5 Bumps Azure.Extensions.AspNetCore.DataProtection.Keys from 1.6.4 to 1.6.5 Bumps bunit from 2.13.3 to 2.15.2 Bumps Microsoft.Agents.AI from 1.27.0 to 1.28.0 Bumps Microsoft.Agents.AI.Anthropic from 1.27.0 to 1.28.0 Bumps Microsoft.AspNetCore.Authentication.OpenIdConnect from 10.0.13 to 10.0.15 Bumps Microsoft.AspNetCore.Mvc.Testing from 10.0.13 to 10.0.15 Bumps Microsoft.AspNetCore.TestHost from 10.0.13 to 10.0.15 Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Extensions.Hosting from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Http from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Instrumentation.Runtime from 1.20.1 to 1.21.0 Bumps SonarAnalyzer.CSharp from 10.35.0.4138 to 10.36.0.15337 Bumps StackExchange.Redis from 3.4.20 to 3.4.35 Bumps StyleCop.Analyzers from 1.2.0-beta.556 to 1.3.180 Bumps System.Security.Cryptography.Pkcs from 10.0.13 to 10.0.15 Bumps System.Security.Cryptography.Xml from 10.0.13 to 10.0.15 Bumps xunit.v3.mtp-v2 from 4.0.2 to 4.0.3 --- updated-dependencies: - dependency-name: Azure.Extensions.AspNetCore.DataProtection.Blobs dependency-version: 1.5.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: Azure.Extensions.AspNetCore.DataProtection.Keys dependency-version: 1.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: bunit dependency-version: 2.15.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: Microsoft.Agents.AI dependency-version: 1.28.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: Microsoft.Agents.AI.Anthropic dependency-version: 1.28.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: Microsoft.AspNetCore.Authentication.OpenIdConnect dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: Microsoft.AspNetCore.Mvc.Testing dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: Microsoft.AspNetCore.TestHost dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: OpenTelemetry.Instrumentation.Runtime dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: SonarAnalyzer.CSharp dependency-version: 10.36.0.15337 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: SonarAnalyzer.CSharp dependency-version: 10.36.0.15337 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: StackExchange.Redis dependency-version: 3.4.35 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: StyleCop.Analyzers dependency-version: 1.3.180 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: StyleCop.Analyzers dependency-version: 1.3.180 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-and-minor - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: System.Security.Cryptography.Pkcs dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: System.Security.Cryptography.Xml dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: System.Security.Cryptography.Xml dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: xunit.v3.mtp-v2 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor - dependency-name: xunit.v3.mtp-v2 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-and-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Nov 16, 2026
Author
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/Sentinel.Tests.Integration/patch-and-minor-88f34a6c28
branch
November 16, 2026 19:24
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.
Updated Azure.Extensions.AspNetCore.DataProtection.Blobs from 1.5.4 to 1.5.5.
Release notes
Sourced from Azure.Extensions.AspNetCore.DataProtection.Blobs's releases.
1.5.5
1.5.5 (2026-10-21)
Other Changes
Microsoft.AspNetCore.DataProtectiondependency to8.0.32fornet8.0and10.0.13for all other target frameworks.Commits viewable in compare view.
Updated Azure.Extensions.AspNetCore.DataProtection.Keys from 1.6.4 to 1.6.5.
Release notes
Sourced from Azure.Extensions.AspNetCore.DataProtection.Keys's releases.
1.6.5
1.6.5 (2026-10-21)
Other Changes
Microsoft.AspNetCore.DataProtectiondependency to8.0.32fornet8.0and10.0.13for all other target frameworks.Commits viewable in compare view.
Updated bunit from 2.13.3 to 2.15.2.
Release notes
Sourced from bunit's releases.
2.15.2
Added
net11.0target now references the final .NET 11 packages and is compiled with runtime async. By @linkdotnet.Changed
bunit.templatenow targetsnet11.0by default.Fixed
bunit.templateoption to choose the target framework is now--sdkas documented, instead of--targetSdk. By @linkdotnet.2.14.0
Changed
Fixed
FindthrewTypeLoadExceptionwith AngleSharp 1.10.0 because the generated element wrappers did not implement the newBeforeToggleevent. Reported by @ryanbaas83-collab in #1968. Fixed by @linkdotnet.Commits viewable in compare view.
Updated Microsoft.Agents.AI from 1.27.0 to 1.28.0.
Release notes
Sourced from Microsoft.Agents.AI's releases.
1.28.0
[1.28.0] - 2026-11-06
Added
FoundryAITool.CreateComputerTool()and carry computer calls and results through Foundry hosting, including batched actions. Add an Azure OpenAI computer-use sample; the Foundry project endpoint still requires the existing preview tool. For non-hosted GA loops, use stored-response continuation: replaying locally retained computer calls with stored output disabled remains affected by an OpenAI SDK serialization limitation (#8756 by @rogerbarreto).FoundryToolboxOptions.TokenScopefor cloud-specific toolbox authentication audiences, retaininghttps://ai.azure.com/.defaultas the default (#10100 by @rogerbarreto).Changed
A2A hosting: [BREAKING] Limit built-in server registration to message-based responses while reliable task resumption across hosts is deferred (#10037 by @SergeyMenshykh).
Migration: Remove assignments to the deleted
A2AServerRegistrationOptions.AgentRunModeproperty. The built-in handler now completes the run and returns a message rather than a task; update clients that expect task responses. Task resumption and cancellation are unsupported by this message-only handler. Applications requiring task-based hosting must provide their own handler and task-lifecycle implementation.A2A: [BREAKING] Replace individual identity-parameter overloads with optional
A2AAgentOptionswhen constructing agents or adapting clients (#10113 by @SergeyMenshykh).Migration: Replace
new A2AAgent(client, id: ..., name: ..., description: ...)withnew A2AAgent(client, new A2AAgentOptions { Id = ..., Name = ..., Description = ... }). Apply the same options object toclient.AsAIAgent(...). Calls that do not customize identity can continue to omit options; supplied options are cloned.A2A: Update
A2A,A2A.AspNetCore, andA2A.Grpcto1.0.0-preview4and adapt hosting to the updated request-context API (#9995 by @SergeyMenshykh).CodeAct: [BREAKING] Redact host-tool exception details by default in Hyperlight and LocalCodeAct while preserving successful results and failure signaling (#9973 by @eavanvalkenburg).
Migration: Applications relying on detailed host diagnostics must explicitly set
HyperlightCodeActProviderOptions.IncludeDetailedErrors = trueorLocalCodeActProviderOptions.IncludeDetailedErrors = truefor a trusted channel. This applies to provider and standalone-function usage. The default isfalse; outer chat-client error settings and sensitive-data logging do not enable these diagnostics. Configure the policy before constructing the provider or function, because it is captured in execution snapshots.GitHub Copilot: [BREAKING] Disable file hooks by default for both new and resumed agent sessions (#10121 by @westey-m).
Migration: Set
EnableFileHooks = trueexplicitly in theSessionConfigsupplied toGitHubCopilotAgentif the application requires file hooks. An omitted configuration or unset value now resolves tofalse; explicit values remain respected.Declarative workflows: [BREAKING] Require an explicit HTTP host-and-port allowlist and an application-owned handler factory for workflow HTTP requests (#9841 by @baywet).
Migration: Replace parameterless, direct-
HttpClient, and callback construction withnew DefaultHttpRequestHandler(["api.example.com"], handlerFactory, "WorkflowHttp"), wherehandlerFactoryis anIHttpMessageHandlerFactory. Register a named pipeline throughAddHttpClientwith anHttpClientHandleror supportedSocketsHttpHandlerwhoseAllowAutoRedirectandUseCookiesare bothfalse, and configure a finite handler lifetime. Empty allowlists deny all requests; entries match exact hosts and ports, with port 443 assumed when omitted. List non-default ports explicitly, such asapi.example.com:80; wildcards and implicit subdomains are not supported. The allowlist does not itself enforce HTTPS. Configure headers and origin-bound authentication in delegating handlers, notHttpClientdefaults, and ensure those handlers preserve the validated destination without following redirects. Remove handler disposal calls; the application owns the factory and pooled handlers.Declarative MCP: [BREAKING] Create and dispose a separate MCP client for each invocation instead of caching initialized sessions across calls, approval waits, or checkpoint resumes (#9722 by @baywet).
Migration: Replace parameterless or callback-based construction with
new DefaultMcpToolHandler(httpClientFactory, "workflow-mcp"), using an application-ownedIHttpClientFactoryand a named client registered throughAddHttpClient. Configure pooled-handler reuse, a finite handler lifetime, and origin-bound authentication there; each invocation owns its factory-created HTTP client wrapper. Removeawait usingandDisposeAsynccalls on the handler, which no longer implementsIAsyncDisposable. The host must bound, cancel, and await active invocations before disposing HTTP infrastructure. Do not rely on implicit server-side session state surviving another call or checkpoint resume: use explicit remote state handles and durable workflow state, or implement an explicitly scopedIMcpToolHandlerwhen session continuity is required. Automatic protocol negotiation remains the default; set the optional init-onlyProtocolVersiononly when the server's supported version is known.Declarative Foundry: [BREAKING] Rename
AzureAgentProvidertoFoundryAgentProviderand remove its directHttpClientproperty (#10098 by @baywet).Migration: Replace
AzureAgentProviderreferences and constructor calls withFoundryAgentProvider. Configure a custom project-client transport throughAIProjectClientOptions.Transportinstead of assigning the removed providerHttpClientproperty.Workflow observability: [BREAKING] Align invocation span names and attributes with OpenTelemetry GenAI conventions and propagate application-supplied conversation context (#9899 by @baywet).
Migration: Update dashboards, exporters, and filters from
workflow_invoketoinvoke_workflow {workflow name}, or bareinvoke_workflowfor unnamed workflows, and replaceworkflow.namewithgen_ai.workflow.name. Matchgen_ai.operation.name="invoke_workflow"to identify invocations independently of their names. Supplygen_ai.conversation.idthrough OpenTelemetry baggage or currentActivitybaggage for correlation; nonblank OpenTelemetry baggage takes precedence. Conversation IDs are not inferred fromsession.id, which remains unchanged.Workflow observability: [BREAKING] Remove nonstandard workflow payload attributes and deprecate the now-ineffective sensitive-data option (#9994 by @baywet).
Migration: Stop relying on
executor.input,executor.output, andmessage.contentspan attributes; they are no longer emitted, even whenWorkflowTelemetryOptions.EnableSensitiveDatais enabled. Remove that option from workflow configuration: it is now an obsolete no-op scheduled for removal in 1.30.0. Use application-owned instrumentation if payload capture is required. Workflow spans, metadata, runtime events, and agent/chat sensitive-data capture are unchanged.Foundry hosting: Use source-generated logging while preserving log levels, numeric event IDs, templates, structured properties, and exception associations.
EventId.Namenow contains the generated method name instead ofnull(#10122 by @rogerbarreto).Samples: Provide explicit do-not-retry reasons when users reject tool approvals, helping models avoid repeatedly requesting the same rejected call (#10095 by @westey-m).
Documentation: Clarify that healthy Foundry toolbox readiness does not guarantee every toolbox is available and that non-cancellation startup discovery failures are deferred to per-request resolution (#10124 by @rogerbarreto).
Packages and tooling: Advance .NET release metadata to 1.28.0, promote shipped API baselines, and update .NET coverage-reporting and API-promotion workflow dependencies (#10157 by @baywet, #10046 by @maf-ci-automations[bot], #10062 by @dependabot[bot], #10063 by @dependabot[bot]).
... (truncated)
Commits viewable in compare view.
Updated Microsoft.Agents.AI.Anthropic from 1.27.0 to 1.28.0.
Release notes
Sourced from Microsoft.Agents.AI.Anthropic's releases.
1.28.0
[1.28.0] - 2026-11-06
Added
FoundryAITool.CreateComputerTool()and carry computer calls and results through Foundry hosting, including batched actions. Add an Azure OpenAI computer-use sample; the Foundry project endpoint still requires the existing preview tool. For non-hosted GA loops, use stored-response continuation: replaying locally retained computer calls with stored output disabled remains affected by an OpenAI SDK serialization limitation (#8756 by @rogerbarreto).FoundryToolboxOptions.TokenScopefor cloud-specific toolbox authentication audiences, retaininghttps://ai.azure.com/.defaultas the default (#10100 by @rogerbarreto).Changed
A2A hosting: [BREAKING] Limit built-in server registration to message-based responses while reliable task resumption across hosts is deferred (#10037 by @SergeyMenshykh).
Migration: Remove assignments to the deleted
A2AServerRegistrationOptions.AgentRunModeproperty. The built-in handler now completes the run and returns a message rather than a task; update clients that expect task responses. Task resumption and cancellation are unsupported by this message-only handler. Applications requiring task-based hosting must provide their own handler and task-lifecycle implementation.A2A: [BREAKING] Replace individual identity-parameter overloads with optional
A2AAgentOptionswhen constructing agents or adapting clients (#10113 by @SergeyMenshykh).Migration: Replace
new A2AAgent(client, id: ..., name: ..., description: ...)withnew A2AAgent(client, new A2AAgentOptions { Id = ..., Name = ..., Description = ... }). Apply the same options object toclient.AsAIAgent(...). Calls that do not customize identity can continue to omit options; supplied options are cloned.A2A: Update
A2A,A2A.AspNetCore, andA2A.Grpcto1.0.0-preview4and adapt hosting to the updated request-context API (#9995 by @SergeyMenshykh).CodeAct: [BREAKING] Redact host-tool exception details by default in Hyperlight and LocalCodeAct while preserving successful results and failure signaling (#9973 by @eavanvalkenburg).
Migration: Applications relying on detailed host diagnostics must explicitly set
HyperlightCodeActProviderOptions.IncludeDetailedErrors = trueorLocalCodeActProviderOptions.IncludeDetailedErrors = truefor a trusted channel. This applies to provider and standalone-function usage. The default isfalse; outer chat-client error settings and sensitive-data logging do not enable these diagnostics. Configure the policy before constructing the provider or function, because it is captured in execution snapshots.GitHub Copilot: [BREAKING] Disable file hooks by default for both new and resumed agent sessions (#10121 by @westey-m).
Migration: Set
EnableFileHooks = trueexplicitly in theSessionConfigsupplied toGitHubCopilotAgentif the application requires file hooks. An omitted configuration or unset value now resolves tofalse; explicit values remain respected.Declarative workflows: [BREAKING] Require an explicit HTTP host-and-port allowlist and an application-owned handler factory for workflow HTTP requests (#9841 by @baywet).
Migration: Replace parameterless, direct-
HttpClient, and callback construction withnew DefaultHttpRequestHandler(["api.example.com"], handlerFactory, "WorkflowHttp"), wherehandlerFactoryis anIHttpMessageHandlerFactory. Register a named pipeline throughAddHttpClientwith anHttpClientHandleror supportedSocketsHttpHandlerwhoseAllowAutoRedirectandUseCookiesare bothfalse, and configure a finite handler lifetime. Empty allowlists deny all requests; entries match exact hosts and ports, with port 443 assumed when omitted. List non-default ports explicitly, such asapi.example.com:80; wildcards and implicit subdomains are not supported. The allowlist does not itself enforce HTTPS. Configure headers and origin-bound authentication in delegating handlers, notHttpClientdefaults, and ensure those handlers preserve the validated destination without following redirects. Remove handler disposal calls; the application owns the factory and pooled handlers.Declarative MCP: [BREAKING] Create and dispose a separate MCP client for each invocation instead of caching initialized sessions across calls, approval waits, or checkpoint resumes (#9722 by @baywet).
Migration: Replace parameterless or callback-based construction with
new DefaultMcpToolHandler(httpClientFactory, "workflow-mcp"), using an application-ownedIHttpClientFactoryand a named client registered throughAddHttpClient. Configure pooled-handler reuse, a finite handler lifetime, and origin-bound authentication there; each invocation owns its factory-created HTTP client wrapper. Removeawait usingandDisposeAsynccalls on the handler, which no longer implementsIAsyncDisposable. The host must bound, cancel, and await active invocations before disposing HTTP infrastructure. Do not rely on implicit server-side session state surviving another call or checkpoint resume: use explicit remote state handles and durable workflow state, or implement an explicitly scopedIMcpToolHandlerwhen session continuity is required. Automatic protocol negotiation remains the default; set the optional init-onlyProtocolVersiononly when the server's supported version is known.Declarative Foundry: [BREAKING] Rename
AzureAgentProvidertoFoundryAgentProviderand remove its directHttpClientproperty (#10098 by @baywet).Migration: Replace
AzureAgentProviderreferences and constructor calls withFoundryAgentProvider. Configure a custom project-client transport throughAIProjectClientOptions.Transportinstead of assigning the removed providerHttpClientproperty.Workflow observability: [BREAKING] Align invocation span names and attributes with OpenTelemetry GenAI conventions and propagate application-supplied conversation context (#9899 by @baywet).
Migration: Update dashboards, exporters, and filters from
workflow_invoketoinvoke_workflow {workflow name}, or bareinvoke_workflowfor unnamed workflows, and replaceworkflow.namewithgen_ai.workflow.name. Matchgen_ai.operation.name="invoke_workflow"to identify invocations independently of their names. Supplygen_ai.conversation.idthrough OpenTelemetry baggage or currentActivitybaggage for correlation; nonblank OpenTelemetry baggage takes precedence. Conversation IDs are not inferred fromsession.id, which remains unchanged.Workflow observability: [BREAKING] Remove nonstandard workflow payload attributes and deprecate the now-ineffective sensitive-data option (#9994 by @baywet).
Migration: Stop relying on
executor.input,executor.output, andmessage.contentspan attributes; they are no longer emitted, even whenWorkflowTelemetryOptions.EnableSensitiveDatais enabled. Remove that option from workflow configuration: it is now an obsolete no-op scheduled for removal in 1.30.0. Use application-owned instrumentation if payload capture is required. Workflow spans, metadata, runtime events, and agent/chat sensitive-data capture are unchanged.Foundry hosting: Use source-generated logging while preserving log levels, numeric event IDs, templates, structured properties, and exception associations.
EventId.Namenow contains the generated method name instead ofnull(#10122 by @rogerbarreto).Samples: Provide explicit do-not-retry reasons when users reject tool approvals, helping models avoid repeatedly requesting the same rejected call (#10095 by @westey-m).
Documentation: Clarify that healthy Foundry toolbox readiness does not guarantee every toolbox is available and that non-cancellation startup discovery failures are deferred to per-request resolution (#10124 by @rogerbarreto).
Packages and tooling: Advance .NET release metadata to 1.28.0, promote shipped API baselines, and update .NET coverage-reporting and API-promotion workflow dependencies (#10157 by @baywet, #10046 by @maf-ci-automations[bot], #10062 by @dependabot[bot], #10063 by @dependabot[bot]).
... (truncated)
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.OpenIdConnect from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.OpenIdConnect's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Testing from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Testing's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.TestHost from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.TestHost's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
Commits viewable in compare view.
Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
Commits viewable in compare view.
Updated OpenTelemetry.Extensions.Hosting from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Extensions.Hosting's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
Commits viewable in compare view.
Updated OpenTelemetry.Instrumentation.AspNetCore from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.
1.21.0
NuGet: OpenTelemetry.Exporter.Geneva v1.21.0
Fixed an issue where, with
EnableOtlpProtobufEncoding=true, a metricattribute of type
ulongwith a value greater thanlong.MaxValuewasserialized incorrectly, causing the dimension to be dropped or the data point
to be malformed. Such values are now exported as their decimal string
representation, and an attribute that fails to serialize is now dropped
cleanly and reported through the exporter's
EventSource.(#5915)
Improved JSON numeric serialization throughput on .NET 10 and later by formatting
directly into the UTF-8 output buffer.
(#5941)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.21.0-rc.1
Updated Semantic Conventions version to
1.45.0.(#5833)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.21.0-beta.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.21.0-alpha.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.20.3
NuGet: OpenTelemetry.Extensions.AWS v1.20.3
Fixed
AddXRayTraceId()andAddXRayTraceIdWithSampler()not replacingtrace IDs when targeting .NET Framework or .NET Standard. The X-Ray ID
generator now uses
Activity.TraceIdGeneratoron all target frameworks.As a result,
AWSXRayIdGenerator.ReplaceTraceId()is now public on alltarget frameworks, and
AddXRayTraceIdWithSampler()andAWSXRayIdGenerator.ReplaceTraceId(Sampler)are now obsolete on alltarget frameworks.
(#5809)
No longer throw and catch an exception in
AWSXRayPropagatorfor anX-Amzn-Trace-Idheader with upper case or padded hexadecimal identifiers,or with a trace or parent identifier of all zeros.
(#5825)
Fixed
AWSXRayPropagatorusing the value of a field of theX-Amzn-Trace-Idheader whose name only starts with
Root,ParentorSampled.(#5825)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.3
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.3
No notable changes.
See CHANGELOG for details.
1.20.2
NuGet: OpenTelemetry.Extensions.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.2
server.addressandserver.portnot being recorded correctly for HTTPrequests with an IPv6 address in the
Hostheader (e.g.[::1]:8080).(#5788)
See CHANGELOG for details.
1.20.2-beta.1
NuGet: OpenTelemetry.Instrumentation.Hangfire v1.20.2-beta.1
Fixed failed jobs exporting the exception message as the span status description.
The message is now only recorded when
RecordExceptionis enabled.(#5884)
Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
(#5886)
Added
EnrichWithBackgroundJobandCustomStateMappingstoHangfireMetricsInstrumentationOptions. Use them to add custom attributes tothe metrics and to count jobs in custom Hangfire states.
(#5810)
Fixed
workflow.execution.durationfor theexecutingstate. It included thetime of other measurements of this instrumentation, for example the database
query that
RecordQueueLatencyadds.(#5810)
See CHANGELOG for details.
Commits viewable in compare view.
Updated OpenTelemetry.Instrumentation.Http from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.Http's releases.
1.21.0
NuGet: OpenTelemetry.Exporter.Geneva v1.21.0
Fixed an issue where, with
EnableOtlpProtobufEncoding=true, a metricattribute of type
ulongwith a value greater thanlong.MaxValuewasserialized incorrectly, causing the dimension to be dropped or the data point
to be malformed. Such values are now exported as their decimal string
representation, and an attribute that fails to serialize is now dropped
cleanly and reported through the exporter's
EventSource.(#5915)
Improved JSON numeric serialization throughput on .NET 10 and later by formatting
directly into the UTF-8 output buffer.
(#5941)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.21.0-rc.1
Updated Semantic Conventions version to
1.45.0.(#5833)
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
See CHANGELOG for details.
1.21.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.21.0-beta.1
Breaking Change Dropped support for
net8.0andnet9.0.(#3867)
Add support for .NET 11.0.
(#3867)
Updated OpenTelemetry core component version(s) to
1.21.0.(#5969)
...
Description has been truncated