Skip to content

jfrog-cli: install pre-built release binaries - #299631

Closed
RemiBou wants to merge 1 commit into
Homebrew:mainfrom
jfrog:jfrog-cli-2.120.0
Closed

jfrog-cli: install pre-built release binaries#299631
RemiBou wants to merge 1 commit into
Homebrew:mainfrom
jfrog:jfrog-cli-2.120.0

Conversation

@RemiBou

@RemiBou RemiBou commented Aug 19, 2026

Copy link
Copy Markdown
  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there are not other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source jfrog-cli?
  • Is your test running fine brew test jfrog-cli?
  • Does your build pass brew audit --strict jfrog-cli (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source jfrog-cli)? If this is a new formula, does it pass brew audit --new jfrog-cli?

  • I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

Created by upstream bump (JFrog CLI release pipeline).

Summary

Switch jfrog-cli stable installs from compiling the public GitHub source tarball to installing the official pre-built jf binaries published on releases.jfrog.io (same artifacts used by the install script, deb/rpm, and chocolatey packages).

Why

JFrog CLI release binaries are built with the full embedded OpenAPI catalog (spec_bundle=full) required by jf api docs search / jf api docs describe. Homebrew's current source build compiles the public OSS tree without the private rdme-admin spec bundle, so brew install jfrog-cli ships a stub catalog (spec_bundle=stub).

Changes

  • Remove depends_on "go" and source url/sha256
  • Download platform-specific jf binaries from https://releases.jfrog.io/artifactory/jfrog-cli/v2-jf/<version>/...
  • Add no_autobump! because: :bumped_by_upstream (future bumps opened by the JFrog CLI release pipeline)
  • Add test asserting "spec_bundle": "full" from jf api docs search
release notes
## What changed in v2.120.0

Auto-generated from 6 repositories · 2026-08-12
Comparing v2.119.0v2.120.0

ℹ️ No changes in: gofrog

✨ New Features

  • [build-info-go] RTECO-945: Add Alpine APK build-info collection support #398 (@naveenku-jfrog)
  • [jfrog-cli] Append Client → Agent → Model tokens to the CLI User-Agent #3645 (@sverdlov93)
  • [jfrog-cli] Added Post Failure Run support for uv #3654 (@Phavya-jfrog)
  • [jfrog-cli] Add QA section to AI descriptions for permission-target, users, groups, transfer, and config commands #3656 (@ehl-jf)
  • [jfrog-cli-artifactory] Add QA section to AI descriptions for repository, build-info, and generic transfer commands #530 (@ehl-jf)
  • [jfrog-cli-artifactory] RTECO-945: Add Alpine APK command support (apk add/upload/config) #496 (@naveenku-jfrog)
  • [jfrog-cli-core] Add Client → Agent → Model identity for telemetry and User-Agent #1602 (@sverdlov93)
  • [jfrog-cli-core] RTECO-945: Add Apk to ProjectType enum for jf setup apk support #1584 (@naveenku-jfrog)

🐛 Bug Fixes

  • [build-info-go] XRAY-157605 Use the real package name for aliased npm dependencies #411 (@Phavya-jfrog)
  • [jfrog-cli] fix/setup vscode command failing with url and repo key- #527 #3638 (@reshmifrog)
  • [jfrog-cli-artifactory] fix/setup vscode command failing with url and repo key #527 (@reshmifrog)
  • [jfrog-cli-security] XRAY-157605 Use the real package name for aliased pnpm dependencies #841 (@Phavya-jfrog)
  • [jfrog-cli-security] Fix incorrect WD in rollback mechanism for npm and pnpm #842 (@eranturgeman)
  • [jfrog-cli-security] Fix - audit without gradle test configurations #839 (@attiasas)

🔧 Internal Changes

  • [jfrog-cli-security] Update dependencies #844 (@attiasas)

📦 Other Changes

  • [jfrog-cli] XRAY-157605 Use the real package name for aliased npm dependencies #3653 (@Phavya-jfrog)
  • [jfrog-cli] RTECO-945: Wire jf apk commands and e2e tests #3561 (@naveenku-jfrog)
  • [jfrog-cli-artifactory] Uv update error output handling #506 (@Phavya-jfrog)
  • [jfrog-client-go] Missconfiguration service #1352 (@orto17)
  • [jfrog-client-go] adding fields to XscAnalyticsGeneralEventFinalize #1372 (@eranturgeman)

📊 Summary

Repository Changes
jfrog-cli 6
jfrog-cli-artifactory 4
jfrog-cli-security 4
build-info-go 2
jfrog-cli-core 2
jfrog-client-go 2
Total 20

🔗 Module Version Changes

Module From To
build-info-go v1.13.1-0.20260807063325-fafd35fe2d11 v1.13.1-0.20260811071930-3b99d4a6c84b
jfrog-cli-artifactory v0.8.1-0.20260804124646-1a5e6a2d3caf v0.8.1-0.20260812053557-d311dd344da9
jfrog-cli-core v2.60.1-0.20260804120604-edaa34435a80 v2.60.1-0.20260811142039-2813ec601d92
jfrog-cli-security v1.33.0 v1.33.1
jfrog-client-go v1.55.1-0.20260803094922-a87c05639195 v1.55.1-0.20260811135712-2010f5075cc6

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for your pull request. This has been closed because it appears to be missing the pull request template, perhaps because this was written by an AI not a human. We require humans to read and fill in these templates.

Please edit this pull request to fill in the current pull request template. This workflow will reopen this pull request automatically once the template is complete. Do not open a new pull request for this.

@github-actions github-actions Bot closed this Aug 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Caution

Please do not modify the bottle block. Bottle block modifications can cause CI to misbehave.
@BrewTestBot will handle updating the bottle block before this PR is merged.

@github-actions

Copy link
Copy Markdown
Contributor

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

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