Skip to content

Capture profile version when accepting a file #346

Capture profile version when accepting a file

Capture profile version when accepting a file #346

Triggered via pull request October 16, 2026 16:42
Status Success
Total duration 14m 33s
Artifacts 2

pullrequest.yml

on: pull_request
Build and Test Pull Requests
14m 31s
Build and Test Pull Requests
Fit to window
Zoom out
Zoom in

Annotations

21 warnings and 1 notice
Build and Test Pull Requests
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-dotnet@v4, actions/upload-artifact@v4, actions/upload-artifact@v4.4.0, dorny/test-reporter@v1. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L207
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L197
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L165
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/FileProcessorSteps.cs#L135
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L132
Non-nullable property 'LineData' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L93
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.IntegrationTesting.Helpers/SpecflowExtensions.cs#L63
Converting null literal or possible null value to non-nullable type.
Build and Test Pull Requests: FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L383
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests: FileProcessor.FileProfileAggregate/FileProfileAggregate.cs#L218
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build and Test Pull Requests
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"

Artifacts

Produced during runtime
Name Size Digest
test-results
22.7 KB
sha256:6d0c44f5f3694bdcf284cfc65bb067a80cd0a94b1f10d1d370686f3f5c7444e7
tracelogs
297 KB
sha256:816e098204755f638deb90f4e437bf5c4dd48e520ab60b33519ab38a0b0a0aa4