Try JFrog
Guides
Contact SupportTry JFrog
  1. Platform
  2. JFrog Bridges Release Information

JFrog Bridge Client Service Release Information

The Bridge Client Service is installed on Self-managed JPDs, to provide a secure, dedicated communication channel with a SaaS JPD that acts as the Bridge Server.

JFrog Bridges 1.262.4

Released: 13.07.2026

Highlights

  • Bridge Helm Chart Updates to enhance support for the Kube-Prometheus-Stack, advanced Service Monitoring relabeling is supported. For more information see Prometheus with Grafana.
  • Graceful Shutdown Period When the Bridge service is stopped, the Bridge Client completes file transfers within a configurable grace period.

Resolved Issues

  • Autocorrect Malformed Bridge BaseURL Token authentication can fail when a custom-defined BaseURL value includes the /artifactory suffix. This release corrects the BaseURL value to a legal value in token interactions.

JFrog Bridges 1.72.0

Released: 02.04.2026

Highlights

  • Disable CPU limits in Helm chart installation Kubernetes CPU limits are enabled by default in Helm chart installation - but they can cause CFS throttling in production. The new resources:disableCpuLimits option in the /bridge/values.yaml file lets you disable CPU limits.
  • Maximum Tunnels Indication The Bridges page of the JFrog Platform interface now indicates a Bridge that has opened the maximum tunnels allowed by its current configuration. You can modify Bridge settings to accommodate higher traffic levels. (integrated Release 1.67.0)
  • Tightened Security for Helm Chart deployment To align with all other JFrog Helm charts, the Bridge Client Helm Chart now uses the containersecuritycontext parameter instead of the more general securitycontext parameter. This restricts the scope of the security context. (integrated Release 1.66.0)
  • Upload TLS Certificate per Bridge You can now provide a Bridge-specific TLS certificate at a later date if none was provided during Bridge Client installation. A new field in the Bridges page of the JFrog Platform interface lets you upload a TLS certificate to authenticate a Bridge Client. If no Bridge-specific TLS certificate is present, the Bridge Client service retrieves a generic certificate from the JFrog Access service. (integrated Release 1.65.0)
  • Extended connectivity check Before it opens a tunnel, the Bridge service checks connectivity to other JFrog services on the Bridge Client JPD, which are the most comment targets of Bridge communication. (integrated Release 1.65.0)
  • Improved tooltips for Advanced settings Tooltips now clarify how maximum and minimum thresholds determine tunnel creation. (integrated: Release 1.63.0)

Resolved Issues

  • Bridge Client JPD with proxy server When the Bridge Client JPD communicated through a proxy server with a secure (https:) URL, the Bridge Client service could not create a TCP session with the Bridge Server.
  • Bridges disappeared from the table in the JFrog Platform interface after they were Stopped or their settings were changed, and reappeared after the page was reloaded. (integrated: Release 1.62.0)

JFrog Bridges 1.47 (Self-Managed)

Released: 30.10.2025

Initial General Availability Bridge Client release.

Updated about 7 hours ago

Did this page help you?