Stage workflow #566
stage-workflow.yml
on: workflow_dispatch
stage-get-jfrog-version
/
Get most recent JFrog version string
17s
Matrix: comprehensive-tests / comprehensive-tests
promote-release-bundle-to-stage
/
promote-release-bundle-to-dev
Annotations
29 errors and 297 warnings
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v141, 25)
Process completed with exit code 1.
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v137, 24)
Process completed with exit code 1.
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v115, 20, valgrind)
Process completed with exit code 7.
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v127, 22, valgrind)
Process completed with exit code 5.
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v141, 25, valgrind)
Process completed with exit code 3.
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v127, 22)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v141, 25)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v137, 24)
You're on a case-insensitive filesystem, and the remote you are
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v115, 20)
You're on a case-insensitive filesystem, and the remote you are
|
|
stage-get-jfrog-version / Get most recent JFrog version string
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / get-runner-os
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / get-runner-os
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / get-runner-os
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / get-runner-os
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / get-runner-os
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile-self-hosted (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-tsc-compile-self-hosted (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-tsc-compile (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-user-agent-ce (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to collect Git information: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-user-agent-ce (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v127, 22)
coreutils 9.11 is already installed and up-to-date.
To reinstall 9.11, run:
brew reinstall coreutils
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-timeout-delay (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-timeout-delay (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-tsc-compile (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-bun (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-yarn (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-yarn (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-pnpm (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-bun (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-pnpm (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (win_amd64) / test-tsc-compile (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-metrics (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-metrics (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v115, 20)
coreutils 9.11 is already installed and up-to-date.
To reinstall 9.11, run:
brew reinstall coreutils
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v141, 25, set-xdr-filter)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v137, 24, set-xdr-filter)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v127, 22, set-xdr-filter)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v115, 20, set-xdr-filter)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v141, 25)
coreutils 9.11 is already installed and up-to-date.
To reinstall 9.11, run:
brew reinstall coreutils
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-ce (v137, 24)
coreutils 9.11 is already installed and up-to-date.
To reinstall 9.11, run:
brew reinstall coreutils
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v115, 20)
jq 1.8.1 is already installed and up-to-date.
To reinstall 1.8.1, run:
brew reinstall jq
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_aarch64) / test-ce (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ce (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v141, 25)
jq 1.8.1 is already installed and up-to-date.
To reinstall 1.8.1, run:
brew reinstall jq
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v127, 22)
jq 1.8.1 is already installed and up-to-date.
To reinstall 1.8.1, run:
brew reinstall jq
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-postinstall-script-removes-unneeded-binaries (v137, 24)
jq 1.8.1 is already installed and up-to-date.
To reinstall 1.8.1, run:
brew reinstall jq
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / test-ee (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v115, 20, valgrind)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v127, 22, valgrind)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v141, 25, valgrind)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-pnpm (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (manylinux_x86_64) / tests (v137, 24, valgrind)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-ee (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v127, 22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v127, 22)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_arm64) / test-tsc-compile (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v141, 25)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-yarn (v141, 25)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v137, 24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v137, 24)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v115, 20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@263435318d21b8e681c14492fe198d362a7d2c83, step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e, step-security/setup-buildx-action@8c8aef2d414c0b66518fee2b7084e0986f82d7ac, step-security/setup-jfrog-cli@a6b41f8338bea0983ddff6bd4ede7d2dcd81e1fa. 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/
|
|
comprehensive-tests / comprehensive-tests (macosx_x86_64) / test-bun (v115, 20)
Failed while attempting to publish the build info to JFrog Artifactory: Error: JFrog CLI exited with exit code: 1
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
aerospike~aerospike-client-nodejs~1PBO3K.dockerbuild
|
33.1 KB |
sha256:9b8d93172f3f86fe4e090ec5fa08c12782a6b58b8e7a5424fb921ed5ae6b6c18
|
|
|
aerospike~aerospike-client-nodejs~1QLIAU.dockerbuild
|
46.8 KB |
sha256:dff9b8c764329e214087a42e2ef2e0eec02b6c163a05a496ee8e19c6da61ab9c
|
|
|
aerospike~aerospike-client-nodejs~2DDRUW.dockerbuild
|
33.6 KB |
sha256:d39f5d3a6f2da29a7708ba70edcf0f4cff2d4171f308fd27b36636705cfbdbcd
|
|
|
aerospike~aerospike-client-nodejs~40QA20.dockerbuild
|
48.1 KB |
sha256:2eaf1b79e4023c2e67378204fe05a9c5820fe30276a990ead843c12ef4e0dd30
|
|
|
aerospike~aerospike-client-nodejs~4D41OL.dockerbuild
|
34.2 KB |
sha256:3ee79f09e7ccba865a733ca46520a3d2a6ac1fd9eae2838ca46de4242d42e927
|
|
|
aerospike~aerospike-client-nodejs~4K0PI6.dockerbuild
|
33.4 KB |
sha256:352be1bec5661fb9b25528afe6924e1968a62d4945c709fdd3843da86894e7d4
|
|
|
aerospike~aerospike-client-nodejs~4N87YT.dockerbuild
|
48.5 KB |
sha256:145ae673eb87d082568b4d96896fcb90a0d43d6bb88453a101d86a2f6829f382
|
|
|
aerospike~aerospike-client-nodejs~4Z3IAZ.dockerbuild
|
31.1 KB |
sha256:ce92fd720fdc77750f3141ab1e9eecf1bc35e8e56e6e0a83ff90bc689158da21
|
|
|
aerospike~aerospike-client-nodejs~547O21.dockerbuild
|
47.4 KB |
sha256:b404e5e9ed9e712b7aaa324e894f3082ff88d363cafaa9b9528ff4b4d44adfbc
|
|
|
aerospike~aerospike-client-nodejs~71AF5T.dockerbuild
|
33.3 KB |
sha256:058caaceadf81817432b32beed862863d6cda7cbf59646d86fd947e43035bae4
|
|
|
aerospike~aerospike-client-nodejs~7CLUSI.dockerbuild
|
33.3 KB |
sha256:97662a4cd40f293e7154d8f12515aa67b6493b471a6688fe5a7448790bcfd256
|
|
|
aerospike~aerospike-client-nodejs~BIQ3MS.dockerbuild
|
48.8 KB |
sha256:6cfd5fa5072fd0ec8e05cdc145168c0635e72cda0f91237000f72f7d4e8b5460
|
|
|
aerospike~aerospike-client-nodejs~DK9QIW.dockerbuild
|
48.7 KB |
sha256:8e3f89e4efccbcc58d1649bf5aa95806e8b94374761f07a4bb998bb15e2fc318
|
|
|
aerospike~aerospike-client-nodejs~E4X0T7.dockerbuild
|
30.7 KB |
sha256:0bb54538a5d31aa58fbaf4b2acf192cdc765b0220d15aee690e82a7c048965df
|
|
|
aerospike~aerospike-client-nodejs~G5IGPN.dockerbuild
|
32.9 KB |
sha256:ec866cc2ef87355d629e086a40c8ea11b7753ad5d66ee340993ee00fb053b8ee
|
|
|
aerospike~aerospike-client-nodejs~HMT0G6.dockerbuild
|
49.6 KB |
sha256:69dc8a855b647c41aa5a390806f7ea6b5fc662badd54d0b3f25e765dedf04843
|
|
|
aerospike~aerospike-client-nodejs~HYOSMY.dockerbuild
|
33.9 KB |
sha256:c90178781d9b1e4fe8245479417182c880812d51abc53f623f8235c0bbc1f175
|
|
|
aerospike~aerospike-client-nodejs~IG4D3L.dockerbuild
|
32.8 KB |
sha256:b9f9d83a065beeb5bee31a4045538c5df10e38f8c6e4564950966d439559a9bd
|
|
|
aerospike~aerospike-client-nodejs~IMEB7A.dockerbuild
|
33.6 KB |
sha256:731684782fc48134fbdc5f6458cfffd4e617aa47f734d571389ab8343696ef8c
|
|
|
aerospike~aerospike-client-nodejs~IYFE23.dockerbuild
|
30.8 KB |
sha256:ff85d0d3f45d12c2d33a43b952b078ced0bd96b97f1292125bb2b418efb4e403
|
|
|
aerospike~aerospike-client-nodejs~JJ34C2.dockerbuild
|
33.1 KB |
sha256:ab11354372eea8173d19779ff4c45f76d54c4a6e6b56260d03e50078be6d289d
|
|
|
aerospike~aerospike-client-nodejs~KPV29V.dockerbuild
|
33 KB |
sha256:e3f408a9f3b3c87e59c230b9e0709a349bfe3e666506787f563dbb17fb260d9b
|
|
|
aerospike~aerospike-client-nodejs~KWJ19D.dockerbuild
|
33.6 KB |
sha256:82288fd6fca647002347f949cb2c0d2e32723798461105bd460e423b115526a0
|
|
|
aerospike~aerospike-client-nodejs~KZCSAR.dockerbuild
|
33 KB |
sha256:919db39260000faa979b5e923c6d622e86134298678b69cf6f3b5c2f77d6e7cd
|
|
|
aerospike~aerospike-client-nodejs~L2L1BP.dockerbuild
|
48.8 KB |
sha256:8f82a4923da00cb88aedd0b4aaab3420109a3191cfb55b84fd9c1fa3978559ff
|
|
|
aerospike~aerospike-client-nodejs~LARF5Y.dockerbuild
|
33.3 KB |
sha256:6f23cd210c6eed175751481f9382dbbf78bf768263f750acbc76591fc9cebf32
|
|
|
aerospike~aerospike-client-nodejs~MSYL7O.dockerbuild
|
34.1 KB |
sha256:2a38d214965bd2ac8a4fb69eb90a4e070543c3e298fdee88e527150ba38777da
|
|
|
aerospike~aerospike-client-nodejs~NVUMNB.dockerbuild
|
30.3 KB |
sha256:f9ecc043834b3128515c7fd255ec9889f58038a3ec8ac088b3fa119539213f01
|
|
|
aerospike~aerospike-client-nodejs~OM9IWD.dockerbuild
|
32.7 KB |
sha256:a0b8899c6fc84c41870052b66312851cb1b4e09b5190b1b66502b32fe4d8c2bd
|
|
|
aerospike~aerospike-client-nodejs~P4402B.dockerbuild
|
47.7 KB |
sha256:e0a52b926e0688e147c7c97d4ffcbc21f63d934fa7403412779cdce5cd698245
|
|
|
aerospike~aerospike-client-nodejs~PH8P24.dockerbuild
|
32.9 KB |
sha256:1641f88b882ab8117a60847bb939f6c3e44e1bc2cc3d55e2986bf3c307f37b48
|
|
|
aerospike~aerospike-client-nodejs~PVQE18.dockerbuild
|
33.2 KB |
sha256:123a0b136c137d2cf05ca67fb2e2bddc33c6a7d9b610186b0aeff1acd33af55e
|
|
|
aerospike~aerospike-client-nodejs~QB330R.dockerbuild
|
48.7 KB |
sha256:c25777dffeb2dfb23cf8da7acc38e38ac9c189829067b12ae279fc66683e9fcb
|
|
|
aerospike~aerospike-client-nodejs~QS7991.dockerbuild
|
33 KB |
sha256:f1f1204e39f22ebe075bd1a34e50c132794d67ca740428f5e83ff9e85abfb320
|
|
|
aerospike~aerospike-client-nodejs~RHTZBH.dockerbuild
|
48.3 KB |
sha256:6798b476f7e3a9516ce603af7bec594833b7d46c4fec8b113e115680ab6b141e
|
|
|
aerospike~aerospike-client-nodejs~RQFX0N.dockerbuild
|
31.5 KB |
sha256:cac9559403c70272bdc01d72c62ba2de226c67a80f72159683637b10fe98cb95
|
|
|
aerospike~aerospike-client-nodejs~S0TFP4.dockerbuild
|
48.7 KB |
sha256:82a090de02ef47fecc259ad81d98e285c80232e0002c60fdea1e9e1abe13b511
|
|
|
aerospike~aerospike-client-nodejs~SJEGKT.dockerbuild
|
31.6 KB |
sha256:4ec2c889b64242d39be1d9a8124a134b7e93ece78476e550a99be28d98666bdf
|
|
|
aerospike~aerospike-client-nodejs~TFCBLN.dockerbuild
|
33.1 KB |
sha256:be042cc5ab71262643c0170f9744e1871da64f01171225df8f01035dfb070946
|
|
|
aerospike~aerospike-client-nodejs~TLXDBD.dockerbuild
|
33.2 KB |
sha256:3f829b012a914da10269b1f478554b3a61733337c92290ade4d570da7a366d49
|
|
|
aerospike~aerospike-client-nodejs~TQNS18.dockerbuild
|
31 KB |
sha256:7b2c7c62c8f93a4fd3ad345a6292cd7f407a63f80608baddbfbcb332ca5a0ff9
|
|
|
aerospike~aerospike-client-nodejs~U0F79P.dockerbuild
|
47.5 KB |
sha256:7a838afc3c5dbe3b6c7fb1c80cca0bb4c4f898e4e62be3b780ce1e6bc82d5497
|
|
|
aerospike~aerospike-client-nodejs~UKQQ7R.dockerbuild
|
33.7 KB |
sha256:3cae98038d062a9eebccf49cd52b268266557ac2c79fbf5224167c8178afe2c4
|
|
|
aerospike~aerospike-client-nodejs~UT11UW.dockerbuild
|
33.2 KB |
sha256:b2c935f8649df870b83caae1d0f092075e57c78021612fd56c87a33c1fd6c291
|
|
|
aerospike~aerospike-client-nodejs~V17WA0.dockerbuild
|
33 KB |
sha256:e628eb1d2c4efd3340eb5f51e650ddca9c608bfab79eb52395c548062527bea9
|
|
|
aerospike~aerospike-client-nodejs~VI9TRD.dockerbuild
|
47.9 KB |
sha256:cdd7df5266af921f9ea5e537b93340349fc39f935304e78463426e281cbebeca
|
|
|
aerospike~aerospike-client-nodejs~WHJN7U.dockerbuild
|
31.2 KB |
sha256:571532423bbab1778f98c60e93a4cf29db95e5c78e22ed52f286a5cf57f2de38
|
|
|
aerospike~aerospike-client-nodejs~WUT5VD.dockerbuild
|
31.2 KB |
sha256:e42904f788f90dbcaae2629707e0deb10a6486eb2cd0d3aac61389c45d6adeda
|
|
|
aerospike~aerospike-client-nodejs~XXFPYL.dockerbuild
|
48.5 KB |
sha256:26c33d50d9c2a2e6634e525118952e7dd43f155a60fd31a61bd443b9de1d8dd9
|
|
|
aerospike~aerospike-client-nodejs~Y1CFY3.dockerbuild
|
48.3 KB |
sha256:88f2ec49d2cbf5c2ca7bb136723fbf44ca3e1824b4ff9332dfb891b8fb390f23
|
|
|
aerospike~aerospike-client-nodejs~Z1K7ET.dockerbuild
|
32.7 KB |
sha256:eaa3fc2fea64ac9093be89bf48275ce23a8e07bfa20e1d882541eb619a31235b
|
|
|
aerospike~aerospike-client-nodejs~ZQWIF2.dockerbuild
|
31 KB |
sha256:6d56d95b146ca3eabade5b50ff9ba188ae579fd8d30269834df24431ee30fd83
|
|