Workflow failed! getaddrinfo ENOTFOUND sig-repo.synopsys.com

In keyfactor/actions/.github/workflows/starter.yml@3.2.0 (Line: 125, Col: 11): Error from called workflow keyfactor/actions/.github/workflows/maven-build-and-release.yml@v3 (Line: 53, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?

In keyfactor/actions/.github/workflows/starter.yml@3.2.0 (Line: 125, Col: 11): Error from called workflow keyfactor/actions/.github/workflows/maven-build-and-release.yml@v3 (Line: 61, Col: 13): Conditional expression contains literal text outside replacement tokens. This will cause the expression to always evaluate to truthy. Did you mean to put the entire expression inside ${{ }}?

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 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/

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 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/

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 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/

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 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/

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 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/

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 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/

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 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, keyfactor/synopsys-action@v1.10.0. 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/

Unexpected input(s) 'polaris_application_id', 'polaris_project_id', 'polaris_branch_id', valid inputs are ['coverity_url', 'coverity_user', 'coverity_passphrase', 'coverity_project_name', 'coverity_stream_name', 'coverity_install_directory', 'coverity_policy_view', 'coverity_repository_name', 'coverity_branch_name', 'coverity_local', 'coverity_version', 'coverity_prComment_enabled', 'coverity_build_command', 'coverity_clean_command', 'coverity_config_path', 'coverity_args', 'bridge_coverity_version', 'polaris_access_token', 'polaris_application_name', 'polaris_project_name', 'polaris_assessment_types', 'polaris_server_url', 'polaris_prComment_enabled', 'polaris_prComment_severities', 'polaris_triage', 'polaris_branch_name', 'polaris_branch_parent_name', 'polaris_test_sca_type', 'polaris_reports_sarif_create', 'polaris_reports_sarif_file_path', 'polaris_reports_sarif_severities', 'polaris_reports_sarif_groupSCAIssues', 'polaris_reports_sarif_issue_types', 'polaris_upload_sarif_report', 'polaris_assessment_mode', 'project_directory', 'project_source_archive', 'project_source_preserveSymLinks', 'project_source_excludes', 'synopsys_bridge_install_directory', 'synopsys_bridge_download_url', 'blackduck_url', 'blackduck_token', 'blackduck_install_directory', 'blackduck_scan_full', 'blackduck_scan_failure_severities', 'blackduck_automation_fixpr', 'blackduck_fixpr_enabled', 'blackduck_fixpr_maxCount', 'blackduck_fixpr_filter_severities', 'blackduck_fixpr_useUpgradeGuidance', 'synopsys_bridge_download_version', 'blackduck_prComment_enabled', 'blackduck_reports_sarif_create', 'blackduck_reports_sarif_file_path', 'blackduck_reports_sarif_severities', 'blackduck_reports_sarif_groupSCAIssues', 'blackduck_upload_sarif_report', 'blackduck_search_depth', 'blackduck_args', 'blackduck_config_path', 'github_token', 'include_diagnostics', 'diagnostics_retention_days', 'bridge_network_airgap', 'network_airgap']

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/build-push-action@v6.0.1, keyfactor/checkout@v4, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0, keyfactor/setup-qemu-action@v3.0.0, keyfactor/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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: keyfactor/download-artifact@v4.1.7, keyfactor/login-action@v3.2.0, keyfactor/metadata-action@v5.5.1, keyfactor/setup-buildx-action@v3.3.0. 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/