SCANCLI-216 Update scanner library to fix proxy authentication on CONNECT #65
Annotations
1 error and 16 warnings
|
Linux QA - SQ LATEST_RELEASE[2025.1]
Process completed with exit code 1.
|
|
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache/save@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Linux QA - SQ LATEST_RELEASE[2025.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Linux QA - SQ LATEST_RELEASE
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Linux QA - SQ DEV
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Linux QA - SQ LATEST_RELEASE[2026.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Deactivating UseContainerSupport
The GitHub-hosted Ubuntu runners have an issue with Java's UseContainerSupport feature.
|
|
Windows QA - SQ LATEST_RELEASE[2026.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Windows QA - SQ LATEST_RELEASE[2025.1]
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Windows QA - SQ LATEST_RELEASE
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|
|
Windows QA - SQ LATEST_RELEASE
Back off 26.086 seconds before retry.
|
|
Windows QA - SQ LATEST_RELEASE
Failed to download action 'https://api.github.com/repos/SonarSource/vault-action-wrapper/zipball/3d5c87cb535e4a2c7a09adcbcfdefa751854dee3'. Error: Response status code does not indicate success: 502 (Bad Gateway). 0C01:55D89:48BA227:138086C9:69B14BEB
|
|
Windows QA - SQ DEV
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@0057852bfaa89a56745cba8c7296529d2fc39830, actions/cache@0057852bfaa89a56745cba8c7296529d2fc39830, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@146a28175021df8ca24f8ee1828cc2a60f980bd5. 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/
|