Skip to content

Fixed missing PowerShell script not being found. #1175

Fixed missing PowerShell script not being found.

Fixed missing PowerShell script not being found. #1175

Triggered via push May 11, 2026 14:29
Status Success
Total duration 3m 27s
Artifacts 2
call-starter-workflow  /  ...  /  Set workflow variables from integration-manifest.json
7s
call-starter-workflow / call-assign-from-json-workflow / Set workflow variables from integration-manifest.json
call-starter-workflow  /  ...  /  Grep TODO and License Headers
11s
call-starter-workflow / call-create-github-release-workflow / call-check-file-action / Grep TODO and License Headers
call-starter-workflow  /  Detect Primary Language
6s
call-starter-workflow / Detect Primary Language
call-starter-workflow  /  ...  /  create-github-release-workflow
5s
call-starter-workflow / call-create-github-release-workflow / create-github-release-workflow
call-starter-workflow  /  Check for .goreleaser file
6s
call-starter-workflow / Check for .goreleaser file
call-starter-workflow  /  setup_platforms
4s
call-starter-workflow / setup_platforms
call-starter-workflow  /  ...  /  Use private doctool action in public repository
1m 16s
call-starter-workflow / call-generate-readme-workflow / Use private doctool action in public repository
call-starter-workflow  /  ...  /  Configure branch protection
call-starter-workflow / call-repository-configuration-workflow / Configure branch protection
call-starter-workflow  /  ...  /  Updating repository settings
call-starter-workflow / call-repository-configuration-workflow / Updating repository settings
call-starter-workflow  /  ...  /  update-catalog-entry
call-starter-workflow / call-update-catalog-workflow / update-catalog-entry
call-starter-workflow  /  ...  /  create-github-release
call-starter-workflow / call-create-github-release-workflow / create-github-release
call-starter-workflow  /  ...  /  Create PR from release branch to main
call-starter-workflow / call-post-release-workflow / Create PR from release branch to main
call-starter-workflow  /  ...  /  dotnet-build-and-release
2m 58s
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release
call-starter-workflow  /  ...  /  run-goreleaser
call-starter-workflow / call-go-build-and-release-workflow / run-goreleaser
Fit to window
Zoom out
Zoom in

Annotations

1 error, 18 warnings, and 1 notice
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 / 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 / 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 / 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-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 / 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-python@v5, Keyfactor/add-and-commit@v9.1.3, 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-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/Factories/CertificateFactory.cs#L56
Nullability of reference types in value of type '(string? thumbprint, string base64Pfx)' doesn't match target type '(string Thumbprint, string Base64Pfx)'.
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: WindowsCertStore.IntegrationTests/ClientConnection.cs#L15
Non-nullable property 'PrivateKey' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: WindowsCertStore.IntegrationTests/ClientConnection.cs#L14
Non-nullable property 'Username' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: WindowsCertStore.IntegrationTests/ClientConnection.cs#L11
Non-nullable property 'Machine' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the property as nullable.
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-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026

Artifacts

Produced during runtime
Name Size Digest
licenselogs Expired
146 Bytes
sha256:22e5cb254f927889fd51d4f56207f64cfaaf573a865f68c20fa60de7dc9d2ba4
todologs Expired
140 Bytes
sha256:f5001a5f3da21a60932dfd016a7552d498892532fc76547672579e560c62b68b