chore(deps): Bump the dotnet-minor-and-patch group with 5 updates - #105
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Azure.Monitor.OpenTelemetry.Exporter from 1.8.3 to 1.9.0 Bumps Microsoft.Extensions.Http.Resilience from 10.9.0 to 10.10.0 Bumps Microsoft.NET.Test.Sdk from 18.9.0 to 18.10.0 Bumps Microsoft.Testing.Extensions.TrxReport from 2.3.3 to 2.4.0 Bumps xunit.v3 from 4.0.0 to 4.0.1 --- updated-dependencies: - dependency-name: Azure.Monitor.OpenTelemetry.Exporter dependency-version: 1.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-and-patch - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-and-patch - dependency-name: Microsoft.Testing.Extensions.TrxReport dependency-version: 2.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet-minor-and-patch - dependency-name: xunit.v3 dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Agent evalsLayer 1 — green, spec
No change against the baseline (recorded 2026-09-01, spec Layer 2 — judge
Calibration: NOT calibrated — 0 of 40 human labels — no owner handle is configured, so none of the 45 label(s) present count as human; κ not computable from the labels present. Layer 2 scores are reported and gate nothing. What a green Layer 1 meansTool ordering, the confirmation gate, grounding, termination and the absence of internal |
|
Superseded by #106. |
Updated Azure.Monitor.OpenTelemetry.Exporter from 1.8.3 to 1.9.0.
Release notes
Sourced from Azure.Monitor.OpenTelemetry.Exporter's releases.
1.9.0
1.9.0 (2026-09-04)
Features Added
Add support for project id attributes propagation
(#62052)
Shutting down a provider (including
Dispose()) now writes pending telemetry to offline storage and uploads it in the background instead of blocking on ingestion. Short-lived applications such as CLI tools previously lost this telemetry, because they exit before a transmission completes; the telemetry is now durable before exit, and delivery is completed by a background drain in this or a subsequent run.ForceFlushis unchanged by default and can be opted in with theAzure.Monitor.OpenTelemetry.Exporter.PersistOnForceFlushAppContext switch, which applies to traces and logs only: a metric reader cannot distinguish a caller's flush from its periodic collection, so metricForceFlushalways transmits. The previous behavior can be restored with theAzure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdownAppContext switch.(#61818)
How long shutdown waits for that background drain can now be set through the
Azure.Monitor.OpenTelemetry.Exporter.ShutdownDrainBudgetMillisecondsAppContext data value, using eitherAppContext.SetDataor aruntimeconfig.jsonconfigProperty.Dispose()passes a finite timeout, so by default part of that window is spent delivering telemetry and process exit tracks ingestion latency. Short-lived applications should set this to0, which makes exit cost only the file write: measured at 2.7 ms regardless of ingestion latency, against 2011 ms with a two second ingestion delay. The default is unchanged, so long-running services keep delivering their final batch within the windowDispose()allows. A single-run CI job, where no later run exists to drain storage, should not raise this value but set theAzure.Monitor.OpenTelemetry.Exporter.DisablePersistOnShutdownswitch with a boundedRetry.NetworkTimeout: raising the budget cannot guarantee delivery, becauseShutdown()waits on the drain for no time at all andDispose()is capped by the five second grace period OpenTelemetry allows it.(#62340)
Bugs Fixed
Telemetry left in offline storage by a process that exited during a transmission is no longer stranded permanently. A leased blob is renamed so that it matches neither the storage provider's blob enumeration nor its retention sweep, and the provider only reclaims those leases on a two minute maintenance timer that a short-lived process never reaches. Expired leases are now reclaimed when storage is drained.
(#61818)
Offline storage is now drained shortly after startup rather than only after the process has been running for two minutes, so telemetry persisted by a previous run is uploaded even when no single run is long-lived.
(#61818)
Telemetry is no longer dropped when the offline storage directory reaches its size cap. The oldest stored telemetry is evicted to make room.
(#61818)
Statsbeat no longer holds up process exit. It exports once more as its meter provider is disposed, which put an ingestion round trip on the exit path; that final export now runs in the background, and its network timeout is bounded at five seconds rather than the pipeline default of 100 seconds. The customer SDK stats meter provider is instead left to live for the process lifetime, so it never exports on the exit path at all; its stats are delivered by its own periodic reader.
(#62340)
Log fields are now culture-invariant. (#61996)
Added the
telemetrySuccessdimension toItem_Dropped_Countfor request and dependency telemetry.(#62081)
Other Changes
Updated OpenTelemetry dependencies to 1.18.0 and
OpenTelemetry.PersistentStorage.FileSystemto 1.1.1.(#62698)
Improved activity conversion performance by reading recognized attributes from a fixed index instead of scanning the tag list for each one. Every span shape converts faster, by about a third for spans carrying Application Insights override attributes, and each conversion rents fewer pooled buffers. Standard metrics no longer collect the tags they never read.
(#62614)
http.server_nameandserver.socket.addressare still exported as custom properties, unchanged.Commits viewable in compare view.
Updated Microsoft.Extensions.Http.Resilience from 10.9.0 to 10.10.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.9.0 to 18.10.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.10.0
What's Changed
vstest.consoleand datacollector by @nohwnd in Run Microsoft.Testing.Platform test apps under vstest.console and datacollector microsoft/vstest#16201Full Changelog: microsoft/vstest@v18.9.0...v18.10.0
Commits viewable in compare view.
Updated Microsoft.Testing.Extensions.TrxReport from 2.3.3 to 2.4.0.
Release notes
Sourced from Microsoft.Testing.Extensions.TrxReport's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated xunit.v3 from 4.0.0 to 4.0.1.
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