JFrog Bridges Release Information

Here's where you'll find the latest release notes for JFrog Bridges, including the main fixes and enhancements made to each version as it is released:

Self-Hosted	Cloud
1.72	1.72

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.67

Released: 02.03.2026

Resolved Issues

False error reporting for healthy Bridge activity The Bridges page in the JFrog Platform interface showed Bridge status as Partial when the Bridge was healthy and nodes were active. This occurred when extra instances of the Bridge Server service were idle.

JFrog Bridges 1.65

Released: 16.02.2026

Highlights

No Test option for a blocked Bridge When a Bridge is Blocked at the Bridge Server, the Test Connection option is unavailable in the Platform user interface.

JFrog Bridges 1.64

Released: 09.02.2026

Highlights

Readiness test before tunnel creation The Bridge Server calls the /system/readiness endpoint exposed by the Bridge Client API. This confirms availability and certificate validity before tunnel setup continues.

JFrog Bridges 1.59

Released: 09.01.2026

Highlights

Support for image digest in Helm installations JFrog Helm charts now support use of an image digest hash to identify images in Helm charts.

Resolved Issues

Support for Basic (reference token) authentication Bridges now supports Docker and other repositories that use Basic Authentication. (BRIDGE-1194)

JFrog Bridges 1.56

Released: 22.12.2025

Highlights

Block and Restore a Bridge at the Bridge Server You can now suspend and restore traffic on specific tunnels of a bridge without removing the bridge. This new Block/Unblock option on the Bridge Server SaaS site is independent of the Stop/Restart options available at the Self-managed Bridge Client. API endpoints are exposed for these actions. Learn more.

JFrog Bridges 1.52

Released: 01.12.2025

Highlights

Unique Bridge ID Validation - Server Phase When Bridge Clients on several Self-managed JPDs connect to a Bridge Server, it ensures that the bridge to each client uses a unique Bridge ID. This isolates each tunnel's data stream. The Client phase of this feature will be included in the next Self-managed Client release.

JFrog Bridges 1.51

Released: 24.11.2025

Highlights

Improved Server handling of Client internal server error The Bridge Client returns an HTTP 503 error code if it is temporarily unavailable. The Bridge Server now recognizes and handles this condition.

JFrog Bridges 1.47 (Self-Managed)

Released: 30.10.2025

Initial general availability Bridge Client release.