Repository navigation
Update default jfrog cli version from 2.124.0 to 2.127.0 - #355
Open
Jordanh1996 wants to merge 1 commit into
Open
Jordanh1996 wants to merge 1 commit into
Jordanh1996 wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Jordanh1996
force-pushed
the
bump-cli-2.127.0-v5.2.1
branch
from
October 14, 2026 09:25
488ba46 to
9747b77
Compare
Jordanh1996
changed the title
yahavi
approved these changes
Oct 14, 2026
This branch is waiting to be deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
npm run formatfor 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@v5keep installing the vulnerable 2.124.0 unless they pinversion:themselves. Support is already handing that workaround to customers.Only the default in
action.ymlchanges; the action's own version bump is left to the release process.🤖 Generated with Claude Code