Updated language for WinSQL binding concerns #1199
rcpokornykeyfactor-starter-workflow.yml
on: push
call-starter-workflow
/
...
/
Set workflow variables from integration-manifest.json
6s
call-starter-workflow
/
...
/
Grep TODO and License Headers
9s
call-starter-workflow
/
Detect Primary Language
4s
call-starter-workflow
/
...
/
create-github-release-workflow
5s
call-starter-workflow
/
Check for .goreleaser file
6s
call-starter-workflow
/
setup_platforms
7s
call-starter-workflow
/
...
/
Use private doctool action in public repository
28s
call-starter-workflow
/
...
/
Configure branch protection
call-starter-workflow
/
...
/
Updating repository settings
call-starter-workflow
/
...
/
update-catalog-entry
call-starter-workflow
/
...
/
create-github-release
0s
call-starter-workflow
/
...
/
Create PR from release branch to main
call-starter-workflow
/
...
/
dotnet-build-and-release
3m 14s
call-starter-workflow
/
...
/
run-goreleaser
Annotations
18 warnings and 1 notice
|
call-starter-workflow / Detect Primary Language
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/action-get-primary-language@v2, keyfactor/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-create-github-release-workflow / create-github-release-workflow
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-assign-from-json-workflow / Set workflow variables from integration-manifest.json
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./tools, keyfactor/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / Check for .goreleaser file
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@v4, keyfactor/file-existence-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / setup_platforms
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-create-github-release-workflow / call-check-file-action / Grep TODO and License Headers
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/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/checkout@v4, keyfactor/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
WindowsCertStore.IntegrationTests/WinSQLIntegrationTests.cs#L148
Cannot convert null literal to non-nullable reference type.
|
|
|
|
|
|
|
|
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
WindowsCertStore.IntegrationTests/WinSQLIntegrationTests.cs#L17
Nullability of reference types in value of type '(string? thumbprint, string? base64Pfx, string pfxPassword)' doesn't match target type '(string thumbprint, string base64Pfx, string pfxPassword)'.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
WindowsCertStore.IntegrationTests/WinCertIntegrationTests.cs#L17
Nullability of reference types in value of type '(string? thumbprint, string? base64Pfx, string pfxPassword)' doesn't match target type '(string thumbprint, string base64Pfx, string pfxPassword)'.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
WindowsCertStore.IntegrationTests/VaultHelper.cs#L13
Converting null literal or possible null value to non-nullable type.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
IISU/Certificate.cs#L109
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release:
IISU/Certificate.cs#L109
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
|
|
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
licenselogs
|
146 Bytes |
sha256:20771e4cc50fea462615ab77ad570b43208717853d1d4d0fff444512088a9228
|
|
|
todologs
|
140 Bytes |
sha256:dda6d5e23bbc032d01cc1bd313bf9a1c92e2b3f4812a6a8679995bfc999931dc
|
|