JGC-455 - Encourage migration from jfrog-cli-v2 to jfrog-cli-v2-jf in npm README#3527
Merged
Conversation
Encourage users of the jfrog-cli-v2 npm package (jfrog executable) to migrate to jfrog-cli-v2-jf (jf executable), explaining that the command changes from `jfrog` to `jf`, that configuration is shared, and how to switch.
ehl-jf
added
ignore for release
cyrilc-pro
approved these changes
Jun 3, 2026
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.
What
Adds a prominent migration note to the top of the
jfrog-cli-v2npm package README (build/npm/v2/README.md).Why
The
jfrog-cli-v2package installs the CLI under the legacyjfrogexecutable name, while the actively maintainedjfrog-cli-v2-jfpackage installs the identical CLI under the standardjfname. This note steers users towardjfrog-cli-v2-jfand explains the practical consequences.Note that the older
jfrog-cli-gopackage has already been deprecated, sojfrog-cli-v2-jfis the package users should move to.Note
The README is a static file published as-is by the Jenkinsfile (
npm publishfrombuild/npm/v2/), so this change reaches npmjs.com only on the next publish run.