Breaking change shipped to v4 tag

[cliffchapmanrbx]

Describe the bug

#306 updated the node20 dependency to node24, a breaking dependency change. This was shipped to the v4 tag and caused our workflows to fail.

We run a GitHub Enterprise Server and make heavy use of this action. Our version of GHES, which is in support, does not support node24 yet.

Please revert the change to v4 and ship the breaking dependency change as a new v5 major version.

Current behavior

The action now requires node24, while previously it worked with node20.

Reproduction steps

No response

Expected behavior

No response

Setup JFrog CLI version

v4

JFrog CLI version

N/A

Workflow operating system type and version

N/A

JFrog Artifactory version (if relevant)

N/A

JFrog Xray version (if relevant)

N/A

[MaorEJFrog]

Thanks for reporting this - you're absolutely right.

The node20-to-node24 upgrade should have been shipped as a new major version, following the same precedent we set with v3→v4 (node16→node20). Instead it was incorrectly released under the v4 tag.

We've taken the following steps to fix this:

1. Reverted the v4 tag back to v4.9.1 (node20), so @v4 users are unblocked immediately.
2. Released v5.0.0 with the node24 runtime change as a proper major version bump.

Migration:

• If your GHES version supports node24: upgrade to jfrog/setup-jfrog-cli@v5
• If not: stay on jfrog/setup-jfrog-cli@v4 which remains on node20

Apologies for the disruption.

we have deleted version V4.10.0 as well, to avoid confusions.

[frank-qcd-qk]

The fix has now introduced additional issue where if anyone who has pointed v4.10.0 now the workflow no longer works. #336