Skip to content

Remove OTE Environment from Docs #30

Remove OTE Environment from Docs

Remove OTE Environment from Docs #30

Triggered via pull request April 9, 2026 21:17
Status Success
Total duration 3m 12s
Artifacts 2
call-starter-workflow  /  ...  /  Set workflow variables from integration-manifest.json
6s
call-starter-workflow / call-assign-from-json-workflow / Set workflow variables from integration-manifest.json
call-starter-workflow  /  ...  /  Grep TODO and License Headers
6s
call-starter-workflow / call-create-github-release-workflow / call-check-file-action / Grep TODO and License Headers
call-starter-workflow  /  Detect Primary Language
4s
call-starter-workflow / Detect Primary Language
call-starter-workflow  /  ...  /  create-github-release-workflow
7s
call-starter-workflow / call-create-github-release-workflow / create-github-release-workflow
call-starter-workflow  /  Check for .goreleaser file
5s
call-starter-workflow / Check for .goreleaser file
call-starter-workflow  /  setup_platforms
5s
call-starter-workflow / setup_platforms
call-starter-workflow  /  ...  /  polaris_scan
7s
call-starter-workflow / call-polaris-scan-workflow / polaris_scan
call-starter-workflow  /  ...  /  Use private doctool action in public repository
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
6s
call-starter-workflow / call-create-github-release-workflow / create-github-release
call-starter-workflow  /  ...  /  Create PR from release branch to main
15s
call-starter-workflow / call-post-release-workflow / Create PR from release branch to main
call-starter-workflow  /  ...  /  dotnet-build-and-release
2m 44s
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 and 20 warnings
call-starter-workflow / call-polaris-scan-workflow / polaris_scan
Workflow failed! [polaris_access_token] - required parameters for polaris is missing
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 / 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-polaris-scan-workflow / polaris_scan
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: blackduck-inc/black-duck-security-scan@v2. 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 / 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-create-github-release-workflow / create-github-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/action-bump-semver@v1, keyfactor/action-create-release@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 / call-post-release-workflow / Create PR from release branch to main
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. 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, softprops/action-gh-release@v2. 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: GoDaddy.Tests/GoDaddyCAPluginTests.cs#L106
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/Fakes/FakeGoDaddyClient.cs#L231
Do not use Assert.NotNull() on value type 'int'. Remove this assert. (https://xunit.net/xunit.analyzers/rules/xUnit2002)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/Fakes/FakeGoDaddyClient.cs#L206
Do not use Assert.NotNull() on value type 'int'. Remove this assert. (https://xunit.net/xunit.analyzers/rules/xUnit2002)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/Fakes/FakeGoDaddyClient.cs#L182
Do not use Assert.NotNull() on value type 'int'. Remove this assert. (https://xunit.net/xunit.analyzers/rules/xUnit2002)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPluginTests.cs#L243
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPluginTests.cs#L192
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPluginTests.cs#L145
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)
call-starter-workflow / call-dotnet-build-and-release-workflow / dotnet-build-and-release: GoDaddy.Tests/GoDaddyCAPluginTests.cs#L106
Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Artifacts

Produced during runtime
Name Size Digest
licenselogs
146 Bytes
sha256:b1d669266deefb590784c55643f7e3097b7bbda4ff8f671f2c630b8a70bd231b
todologs
140 Bytes
sha256:bafeeef9acf5d9be3007969ec874efff58d36a219771b23a1ce83922e8a123fe