Process completed with exit code 1.

[-] /Users/runner/work/PowerShellBuild/PowerShellBuild/tests/PesterConfig.tests.ps1 failed with:

[-] /Users/runner/work/PowerShellBuild/PowerShellBuild/tests/Manifest.tests.ps1 failed with:

[-] /Users/runner/work/PowerShellBuild/PowerShellBuild/tests/LLMOutput.tests.ps1 failed with:

[-] /Users/runner/work/PowerShellBuild/PowerShellBuild/tests/FormatBuildResult.tests.ps1 failed with:

The strategy configuration was canceled because "test.macOS-latest" failed

The operation was canceled.

[-] /home/runner/work/PowerShellBuild/PowerShellBuild/tests/PesterConfig.tests.ps1 failed with:

[-] /home/runner/work/PowerShellBuild/PowerShellBuild/tests/Manifest.tests.ps1 failed with:

[-] /home/runner/work/PowerShellBuild/PowerShellBuild/tests/LLMOutput.tests.ps1 failed with:

[-] /home/runner/work/PowerShellBuild/PowerShellBuild/tests/FormatBuildResult.tests.ps1 failed with:

The strategy configuration was canceled because "test.macOS-latest" failed

The operation was canceled.

[-] D:\a\PowerShellBuild\PowerShellBuild\tests\Manifest.tests.ps1 failed with:

[-] all versions are the same 20ms (6ms|15ms)

[-] changelog and manifest versions are the same 501ms (499ms|2ms)

[-] D:\a\PowerShellBuild\PowerShellBuild\tests\LLMOutput.tests.ps1 failed with:

[-] Describe Code Signing Functions failed

[-] Describe Code Signing Functions failed

[-] D:\a\PowerShellBuild\PowerShellBuild\tests\FormatBuildResult.tests.ps1 failed with:

[-] Context Build.Dot-sourced module failed

[-] Context Build.Compile module failed

[-] Discovery in D:\a\PowerShellBuild\PowerShellBuild\tests\Help.tests.ps1 failed with:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/