Skip to content

Update default jfrog cli version from 2.124.0 to 2.127.0 (v4) - #356

Open
Jordanh1996 wants to merge 1 commit into
jfrog:preRelease/jfrog-setup-cli-v4.11.xfrom
Jordanh1996:bump-cli-2.127.0-v4.11.1
Open

Jordanh1996 wants to merge 1 commit into
jfrog:preRelease/jfrog-setup-cli-v4.11.xfrom
Jordanh1996:bump-cli-2.127.0-v4.11.1

Conversation

@Jordanh1996

@Jordanh1996 Jordanh1996 commented Oct 14, 2026 •

Copy link
Copy Markdown
  • All tests passed. If this feature is not already covered by the tests, I added new tests.
  • I used npm run format for formatting the code before submitting the pull request.

Bumps the default JFrog CLI version from 2.124.0 to 2.127.0, the release that fixes CVE-2026-9289. Until this ships, workflows on jfrog/setup-jfrog-cli@v4 keep installing the vulnerable 2.124.0 unless they pin version: themselves. Support is already handing that workaround to customers.

Only the default in action.yml changes; the action's own version bump is left to the release process.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Jordanh1996
Jordanh1996 force-pushed the bump-cli-2.127.0-v4.11.1 branch from 0dada0f to 35c685f Compare October 14, 2026 09:25
@Jordanh1996 Jordanh1996 changed the title Update default jfrog cli version from 2.124.0 to 2.127.0 and promote v4.11.1 Update default jfrog cli version from 2.124.0 to 2.127.0 (v4) Oct 14, 2026

This branch is waiting to be deployed

1 waiting deployment
frogbot — 35c685fa Waiting Oct 14, 2026 by Jordanh1996 via scan-pull-request #812
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants