Skip to content

SCANJLIB-306 Restore authentication support for proxy + SSL #64

SCANJLIB-306 Restore authentication support for proxy + SSL

SCANJLIB-306 Restore authentication support for proxy + SSL #64

Re-run triggered March 12, 2026 16:00
Status Success
Total duration 11m 7s
Artifacts 4

build.yml

on: pull_request
Matrix: qa
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
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@5ac50f778e26fac95da98d50503682459e86d566. 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.
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@5ac50f778e26fac95da98d50503682459e86d566. 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.
Promote
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/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, hashicorp/vault-action@4c06c5ccf5c0761b6029f56cfb1dcf5565918a3b, jdx/mise-action@5228313ee0372e111a38da051671ca30fc5a96db, jdx/mise-action@5ac50f778e26fac95da98d50503682459e86d566. 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/