Skip to content

Merge v2-registry-composition into prerelease #11

Merge v2-registry-composition into prerelease

Merge v2-registry-composition into prerelease #11

Triggered via push March 15, 2026 14:17
Status Success
Total duration 1m 13s
Artifacts 1
validate-versions
9s
validate-versions
build-package
39s
build-package
Fit to window
Zoom out
Zoom in

Annotations

13 warnings
validate-versions
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 will be forced to run with Node.js 24 by default starting June 2nd, 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-package
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L131
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build-package: Source/Mal.SourceGeneratedDI/DependencyAttributeAnalyzer.cs#L64
Add "CompilationEnd" custom tag to the diagnostic descriptor used to initialize field 'InvalidNamespaceRule' as it is used to report a compilation end diagnostic
build-package: Source/Mal.SourceGeneratedDI/DependencyAttributeAnalyzer.cs#L55
Add "CompilationEnd" custom tag to the diagnostic descriptor used to initialize field 'InvalidPrefixRule' as it is used to report a compilation end diagnostic
build-package: Source/Mal.SourceGeneratedDI/DependencyAttributeAnalyzer.cs#L46
Add "CompilationEnd" custom tag to the diagnostic descriptor used to initialize field 'InvalidContainerNameRule' as it is used to report a compilation end diagnostic
build-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L168
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L167
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L233
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L231
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
build-package: Source/Mal.SourceGeneratedDI/DependencyRegistryGenerator.cs#L131
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
deploy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Artifacts

Produced during runtime
Name Size Digest
nuget Expired
31.6 KB
sha256:106d748c8f831aae9a38974c9c5a27ddabc8e1811888b65c8f32a91f7edae19f