build(msix): remove unvirtualizedResources capability from Store pack… #449
newbe36524build.yml
on: push
Prepare Release Metadata
7s
Matrix: Build Linux and macOS Packages / build-platform-artifacts
Matrix: Build Windows Packages / build-windows
Matrix: publish-platform-release
Upload Release Shards to Azure Storage
/
Plan Azure Upload Shards
21s
Matrix: Upload Release Shards to Azure Storage / upload
Finalize Azure Storage Sync
/
Finalize Azure Sync
25s
Annotations
246 warnings
|
Prepare Release Metadata
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 16th, 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 Linux and macOS Packages / Build Linux AppImage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build Linux tar.gz
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build Linux ZIP
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build macOS x64 ZIP
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build macOS x64 ZIP
Missing macOS release signing configuration: CSC_LINK,CSC_KEY_PASSWORD,APPLE_API_KEY/APPLE_API_KEY_ID/APPLE_API_ISSUER or APPLE_ID/APPLE_APP_SPECIFIC_PASSWORD/APPLE_TEAM_ID. Falling back to unsigned macOS build.
|
|
Build Linux and macOS Packages / Build macOS x64 DMG
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build macOS x64 DMG
Missing macOS release signing configuration: CSC_LINK,CSC_KEY_PASSWORD,APPLE_API_KEY/APPLE_API_KEY_ID/APPLE_API_ISSUER or APPLE_ID/APPLE_APP_SPECIFIC_PASSWORD/APPLE_TEAM_ID. Falling back to unsigned macOS build.
|
|
Build Linux and macOS Packages / Build macOS arm64 DMG
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build macOS arm64 DMG
Missing macOS release signing configuration: CSC_LINK,CSC_KEY_PASSWORD,APPLE_API_KEY/APPLE_API_KEY_ID/APPLE_API_ISSUER or APPLE_ID/APPLE_APP_SPECIFIC_PASSWORD/APPLE_TEAM_ID. Falling back to unsigned macOS build.
|
|
Build Linux and macOS Packages / Build macOS arm64 ZIP
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Linux and macOS Packages / Build macOS arm64 ZIP
Missing macOS release signing configuration: CSC_LINK,CSC_KEY_PASSWORD,APPLE_API_KEY/APPLE_API_KEY_ID/APPLE_API_ISSUER or APPLE_ID/APPLE_APP_SPECIFIC_PASSWORD/APPLE_TEAM_ID. Falling back to unsigned macOS build.
|
|
Publish Linux tar.gz Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish Linux ZIP Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish macOS x64 DMG Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish macOS arm64 ZIP Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish macOS x64 ZIP Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish macOS arm64 DMG Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish Linux AppImage Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Windows Packages / Build Windows (MSIX)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Windows Packages / Build Windows (NSIS)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Windows Packages / Build Windows (Portable)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Publish Windows Release Assets
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, softprops/action-gh-release@v2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 Summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Plan Azure Upload Shards:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-001:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-002:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-004:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-003:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-006:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-005:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-009:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-010:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-011:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-012:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-008:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-013:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-014:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-016:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-017:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-018:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015
Back off 26.046 seconds before retry.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-015
Failed to download action 'https://codeload.github.com/actions/setup-dotnet/tar.gz/67a3573c9a986a3f9c594539f4ab511d57bb3ce9'. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007
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 16th, 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/
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/IArtifactHybridMetadataBuilder.cs#L11
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Build.AzureStorage.cs#L449
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Build.AzureStorage.cs#L401
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Build.AzureStorage.cs#L380
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Build.AzureStorage.cs#L322
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Upload Release Shards to Azure Storage / Upload Azure Shard shard-007:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync
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/download-artifact@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/AzureBlobAdapter.cs#L992
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/AzureBlobAdapter.cs#L991
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/AzureBlobAdapter.cs#L990
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/AzureBlobAdapter.cs#L989
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/AzureBlobAdapter.cs#L988
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L220
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L186
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L185
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
Finalize Azure Storage Sync / Finalize Azure Sync:
nukeBuild/Adapters/ArtifactHybridMetadataBuilder.cs#L29
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
azure-sync-finalize-result
|
18.2 KB |
sha256:01bf835de8dd0e7f16998e572b6218d9981ab9fbae4a114412a1d4ce96055751
|
|
|
azure-upload-plan
|
1.57 KB |
sha256:3ee8e1c338db6158ab76d80fea475620d29fe49d4fe2d6242b3d6cda899fb0d3
|
|
|
publish-result-shard-001
|
877 Bytes |
sha256:f5dfdca9917051adcb8ce0291c4d69a6896c6b0e7632f920940b80c7e4e338bd
|
|
|
publish-result-shard-002
|
882 Bytes |
sha256:4dd08d9185ef0300d50c7d31b1cbaea01c0b865f5742060fd75aa4d024bbedbd
|
|
|
publish-result-shard-003
|
874 Bytes |
sha256:fcb444ac2e7060532af19bb3986ca77d44c7ca617a20d95967341a896e3d5413
|
|
|
publish-result-shard-004
|
881 Bytes |
sha256:dde9d2da5195d9349049c058ab86f6d57810ea364dc1beea3e383c7abf0870e5
|
|
|
publish-result-shard-005
|
874 Bytes |
sha256:36be5fc175a79399ac8d81cdaeb1b0ef1886b72f22ddd31f7007a3a070ab45da
|
|
|
publish-result-shard-006
|
872 Bytes |
sha256:6a6325acb66bda7a8c553b54ce66da4fb08277b95fbe4a664583b8e1552230be
|
|
|
publish-result-shard-007
|
887 Bytes |
sha256:3fa4102e0938d9a5b77da788e7d48e254d8fcd0ed33f9130853cf62d4a2a88e5
|
|
|
publish-result-shard-008
|
880 Bytes |
sha256:d443ccd12fb5f06a89b29a838a13fa8b2699edaa4e89490cc784687633b1a305
|
|
|
publish-result-shard-009
|
887 Bytes |
sha256:481c3975b34b86593f7f71c6780b47b0820fb8623c4d8b9d55e94d0947e67d16
|
|
|
publish-result-shard-010
|
878 Bytes |
sha256:fd6e0a2a0ad439950607bd82a63635a1509185e0b56e2b5115a1fffde93483d1
|
|
|
publish-result-shard-011
|
879 Bytes |
sha256:08d6ed54ed02ac6deb7a29b14cb834d14820f0705fe5ca104ac9cb2e52726c3e
|
|
|
publish-result-shard-012
|
873 Bytes |
sha256:7ec5ea17bac2c5bbba59f8e43c3db55013355440123fd3ed91343338ee7c8272
|
|
|
publish-result-shard-013
|
875 Bytes |
sha256:a011829237faf2287aa085631435dbddc3b77465d8376fb12bfc567b5203b8c8
|
|
|
publish-result-shard-014
|
877 Bytes |
sha256:8a9eadbd101262ef2fe0240fdd193bb09e6d0c978e209f950e167cc2fa2a55e0
|
|
|
publish-result-shard-015
|
867 Bytes |
sha256:4561824707d6639538c60c5dc54504a7f7cde490b7df2054e8a19d12ff585bd0
|
|
|
publish-result-shard-016
|
865 Bytes |
sha256:9d539150aad69d46b675b423decde047fef689fe3757e2f4ddec99ae31dc8919
|
|
|
publish-result-shard-017
|
883 Bytes |
sha256:a8149ef87a8b781f4f9a49f8e214769e9feed88a8f8aa50347b5f716f5d2ad0d
|
|
|
publish-result-shard-018
|
871 Bytes |
sha256:3bb035527770443b2728cfacd93b20750906110a161555e139297bb90f39d71e
|
|
|
release-linux-appimage-assets
|
254 MB |
sha256:3f081c55a8594ea96a8bdbc94aba573442a461f964bf3504196fa916866bd3e0
|
|
|
release-linux-tar-gz-assets
|
260 MB |
sha256:263bc9a95b760ce822689e5671c264b8e1d1cdb5e6dea308918eea12d535afae
|
|
|
release-linux-zip-assets
|
262 MB |
sha256:18db179609e57706b9e45874393e866bf0f342a21136238cf6612fa18aff2122
|
|
|
release-macos-arm64-dmg-assets
|
497 MB |
sha256:b6726e3bfe084d92616b6d0ac785ea9c76fe4e77f6c670615e5a386854681972
|
|
|
release-macos-arm64-zip-assets
|
500 MB |
sha256:b20f70534f141d691b5d9266e37baeeee96283b1ae6d7f09af160db203e4aecf
|
|
|
release-macos-x64-dmg-assets
|
512 MB |
sha256:f8d3baea0ebd69f9f09c874f801468f64ca1983f8b6079ff506ee7633736e678
|
|
|
release-macos-x64-zip-assets
|
515 MB |
sha256:fc58641359e1438debe371d1d9de8642bd818caf8636d6445efd1bbd3a384487
|
|
|
release-windows-msix-assets
|
549 MB |
sha256:3633ca02755db6d30082395cc70b9ce07d051f571a3876036d1c93763c368a48
|
|
|
release-windows-nsis-assets
|
382 MB |
sha256:f3a892d36b7287562b8e0b0c558b80e04662ff5cf741fd3485110367750bcb2c
|
|
|
release-windows-portable-assets
|
597 MB |
sha256:f44164bae50ecd67da0e4a187eda2e3e214373009b9ab4b4d89d72e88db5c613
|
|