Change8

JFrog CLI

Dev Tools

JFrog CLI is a client that provides a simple interface that automates access to the JFrog products.

Latest: v2.93.035 releases4 common errorsView on GitHub

Release History

v2.93.01 fix
Feb 26, 2026

Version v2.93.0 includes an internal Go version bump and a fix for an intermittent test failure on Windows related to Artifactory Client Certificates.

v2.92.01 fix3 features
Feb 18, 2026

This release introduces support for nested paths in docker builds and npm run native commands, alongside fixes for version check failures.

v2.91.0
Feb 5, 2026

This release primarily focuses on adding end-to-end tests for draft release bundle creation and updates, and welcomes new contributors.

v2.90.01 fix
Jan 30, 2026

Version 2.90.0 primarily focuses on fixing a merge artifact issue and includes additional test coverage for upload and rbc commands.

v2.89.02 fixes1 feature
Jan 22, 2026

Version v2.89.0 introduces automatic setting of CI VCS properties on artifacts and includes several minor fixes.

v2.88.03 fixes2 features
Jan 8, 2026

Version v2.88.0 introduces new features like Docker pull by image SHA and Conan build info collection support, alongside various bug fixes and improvements for dependency handling.

v2.87.02 fixes2 features
Dec 12, 2025

This release introduces support for docker build commands and native helm commands, alongside several bug fixes related to spec files and dependency handling.

v2.86.02 fixes1 feature
Dec 9, 2025

Version v2.86.0 introduces support for native Conan commands and resolves bugs related to the docker scan help command and URL protocol handling.

v2.85.0
Nov 24, 2025

This release (v2.85.0) primarily contains minor updates and housekeeping, with the full details available in the linked changelog.

v2.84.01 fix
Nov 19, 2025

Version 2.84.0 of JFrog CLI primarily addresses a bug related to curl execution with additional flags in the 'jf rt' command.

v2.83.02 fixes1 feature
Nov 19, 2025

JFrog CLI v2.83.0 introduces support for direct download commands bypassing AQL and includes several bug fixes, notably for poetry publish and curl argument parsing.

v2.82.02 fixes1 feature
Oct 29, 2025

Version 2.82.0 introduces improvements to IDE design and VSCode persistence support, alongside several minor fixes to the help command output.

v2.81.01 fix2 features
Oct 16, 2025

JFrog CLI v2.81.0 introduces AppTrust commands and a new stats command, alongside improvements to Maven native implementation and a fix for the autocomplete survey.

v2.80.01 fix
Oct 2, 2025

Version v2.80.0 introduces a minor bug fix by adding a timestamp property to the Python package.

v2.79.21 fix
Sep 26, 2025

This release primarily contains a bug fix for VCS Parameters alignment and a minor change to hide the survey in CI environments.

v2.79.12 fixes1 feature
Sep 25, 2025

This release introduces a new flag to disable token refresh and includes fixes for npm workspace handling and binary builds.

v2.79.03 features
Sep 18, 2025

Version 2.79.0 introduces significant new features including native Poetry support, docker login capabilities, and new build process tasks.

v2.78.91 fix
Sep 3, 2025

This patch release fixes an off-by-one error related to the jf pip deps.cache functionality.

v2.78.81 fix
Sep 1, 2025

This patch release (v2.78.8) primarily addresses a bug fix related to the ulikunitz/xz dependency.

v2.78.71 fix
Aug 27, 2025

This patch release (v2.78.7) primarily addresses a bug in SARIF reporting by ensuring missing invocation attributes are correctly filled.

v2.78.61 fix
Aug 26, 2025

This patch release (v2.78.6) primarily addresses security vulnerabilities related to SCA reporting in SARIF and null attributes.

v2.78.5
Aug 21, 2025

This release (v2.78.5) provides updated binaries for various operating systems and architectures. The full changelog details specific fixes and enhancements between v2.78.3 and v2.78.5.

v2.78.31 fix1 feature
Aug 11, 2025

This patch release improves CLI version checking by using a GitHub token to prevent rate limiting and removes empty properties from build-info. It also adds a GitHub Actions summary section to the create evidence command.

v2.78.21 feature
Jul 29, 2025

Version v2.78.2 introduces support for configuring a GitHub token for operations. This release primarily focuses on adding configuration flexibility.

v2.78.13 fixes2 features
Jul 24, 2025

This patch release (v2.78.1) focuses on improvements to SAST reporting, bug fixes in build failure logic and permission handling, and includes IDE setup updates.

v2.78.03 features
Jul 21, 2025

JFrog CLI v2.78.0 introduces versioning support for worker commands, adds Ruby gems support, and refactors the scanning functionality by removing the 'audit' command in favor of 'scan'.

v2.77.01 fix2 features
Jun 12, 2025

JFrog CLI v2.77.0 introduces a new curation audit feature for Gradle and support for the source-mcp command, alongside a fix for macOS ARM64 CPU type mismatches.

v2.76.12 fixes2 features
May 28, 2025

Version 2.76.1 introduces support for JFrog Advanced Security (JAS) scanning and improved handling of npm tarballs, alongside several bug fixes.

v2.76.02 fixes1 feature
May 18, 2025

JFrog CLI version 2.76.0 introduces a new lifecycle annotate command and includes several bug fixes related to Maven wrapper usage and BuildScan violation parsing.

v2.75.12 fixes
May 7, 2025

This patch release updates the Analyzer Manager to v1.17.0 and includes fixes for the 'jf eot' command output and the gradle dependency tree command.

v2.75.02 fixes3 features
Apr 16, 2025

Version 2.75.0 introduces OIDC authentication support, a new worker execution history command, and enhancements to configuration profiles and scanner exclusions. Several bug fixes address build failure logic and build publishing behavior.

v2.74.12 fixes
Mar 23, 2025

Version v2.74.1 primarily contains bug fixes and improvements in JFrog Security (JAS) and updates to internal dependencies.

v2.74.02 fixes5 features
Feb 27, 2025

Version 2.74.0 introduces several new features, including an overwrite flag for build publishing and SBOM information retrieval, alongside bug fixes for `rt curl` and `rbc` commands.

v2.73.32 fixes
Feb 10, 2025

Version v2.73.3 renews the Windows executables certificate and includes fixes for operational risk reporting duplication and the worker's deploy command.

v2.73.23 fixes1 feature
Jan 23, 2025

This patch release (v2.73.2) introduces support for RBV2 downloads and includes several bug fixes related to Zsh completion, GPG keys, and temporary directory creation.

Common Errors

SolveFailureError1 report

SolveFailureError in jfrog-cli often arises when dependency conflicts or incompatible version constraints are detected during dependency resolution by the underlying package manager (like Poetry). To resolve this, explicitly define compatible version ranges for your dependencies in your project's configuration file (e.g., `pyproject.toml` for Poetry) or use the package manager's update command to resolve conflicts automatically (e.g., `poetry update` or `poetry install --with-dependencies`). Consider relaxing overly specific version constraints to allow for more flexibility in dependency resolution.

SolverProblemError1 report

SolverProblemError in jfrog-cli commonly arises from dependency conflicts or version incompatibilities within your project's dependency management tool (e.g., poetry). Resolve this by carefully reviewing your project's dependencies, specifying explicit and compatible versions in your dependency manifest file (e.g., pyproject.toml), and potentially using dependency resolution tools or options to find compatible sets of packages. Afterward, re-run the jf command.

OverrideNeededError1 report

The "OverrideNeededError" in jfrog-cli often arises when dependency resolution requires overwriting a package version, but explicit permission hasn't been given. Fix this by adding the `--no-default-repositories` flag to your jf command. This prevents implicit package source usage and usually forces a resolution path that avoids the override conflict.

NullPointerException1 report

NullPointerException in jfrog-cli usually indicates a missing or uninitialized object dependency preventing a method call. Examine the stack trace to identify the null object and its expected source. Ensure the object is properly initialized or injected before use, specifically checking that all required dependencies (like `prerequisitesCheckers` in the Maven case) are correctly defined and available at runtime.

Related Dev Tools Packages

Subscribe to Updates

Get notified when new versions are released

RSS Feed