Skip to content

New Feature: Implement package alias to invoke jfrog-cli based on package manager #5095

New Feature: Implement package alias to invoke jfrog-cli based on package manager

New Feature: Implement package alias to invoke jfrog-cli based on package manager #5095

Triggered via pull request April 2, 2026 12:19
@bhanurpbhanurp
labeled #3375
Status Success
Total duration 13m 20s
Artifacts

pythonTests.yml

on: pull_request_target
Matrix: Python-Tests
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
pipenv macos
JGC-413 - Skip until artifactory bootstrap in osx is fixed
pip macos
JGC-413 - Skip until artifactory bootstrap in osx is fixed
pipenv ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog-fastci/fastci@v0. 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/
pip ubuntu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog-fastci/fastci@v0. 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/
pipenv windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog-fastci/fastci@v0. 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/
pip windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: jfrog-fastci/fastci@v0. 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/