Skip to content

Bump Microsoft.ApplicationInsights from 2.23.0 to 3.1.0 #917

Bump Microsoft.ApplicationInsights from 2.23.0 to 3.1.0

Bump Microsoft.ApplicationInsights from 2.23.0 to 3.1.0 #917

Triggered via pull request April 6, 2026 23:54
Status Failure
Total duration 2m 8s
Artifacts

ci.yml

on: pull_request
build-and-test
2m 5s
build-and-test
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 6 warnings
build-and-test
Process completed with exit code 1.
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L19
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L17
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L8
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryInitializer.cs#L6
The type or namespace name 'ITelemetryInitializer' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L19
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L17
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryProcessor.cs#L8
The type or namespace name 'ITelemetryProcessor' could not be found (are you missing a using directive or an assembly reference?)
build-and-test: src/Infrastructure/Telemetry/DefaultTelemetryInitializer.cs#L6
The type or namespace name 'ITelemetryInitializer' could not be found (are you missing a using directive or an assembly reference?)
build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-and-test
For projects targeting .NET 8.0 and higher, specifying a RuntimeIdentifier will no longer produce a self contained app by default. To continue building self-contained apps, set the SelfContained property to true or use the --self-contained argument.
build-and-test
The target framework 'net6-windows' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build-and-test
For projects targeting .NET 8.0 and higher, specifying a RuntimeIdentifier will no longer produce a self contained app by default. To continue building self-contained apps, set the SelfContained property to true or use the --self-contained argument.
build-and-test
The target framework 'net6-windows' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
build-and-test
The target framework 'net6-windows' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.