Release History
|
You can find previous versions of the Develocity Edge documentation in our legacy documentation archive. |
Previous Versions
2.0.0
-
[NEW] Edge nodes support Build Scan proxying
-
[NEW] Edge nodes support MCP proxying
-
[FIX] Artifact Cache and Setup Cache images may be evicted before the referenced artifacts
Compatible with Develocity 2026.1.0 or later.
1.7.0
-
[NEW] Improved cache hit ratios for Artifact Cache and Setup Cache via an optimized content eviction policy
-
[NEW] Application versioning scheme change
Compatible with Develocity 2025.3 or later.
1.6
-
[NEW] Added Develocity Artifact Cache and Setup Cache support
-
[FIX] Authentication timeouts return HTTP 500 (Internal Server Error) instead of HTTP 503 (Service Unavailable)
Compatible with Develocity 2025.3 or later.
1.5
-
[NEW] Improved reporting of Edge notices to Develocity
Compatible with Develocity 2025.3 or later.
1.4
-
[NEW] Improved Edge peering strategy
Compatible with Develocity 2025.3 or later.
1.3
-
[NEW] Added Edge peering metrics
Compatible with Develocity 2025.3 or later.
1.2
-
[FIX] Forward proxy connectivity to Develocity server
Compatible with Develocity 2025.3 or later.
1.1
-
[FIX] Edge peering doesn’t handle namespaced cache entries
-
[FIX] Certain cache events aren’t persisted for Bazel clients
Compatible with Develocity 2025.2 or later.
1.0
-
[NEW] Enable artifact sharing between Edge nodes via peering
-
[NEW] Edge node now exposes Prometheus-compatible metrics
Compatible with Develocity 2025.2 or later.
0.6
-
[NEW] Update JDK Docker base image to JDK 21.0.7
Compatible with Develocity 2025.1 or later.
0.5
-
[FIX] Storing a cache entry can fail if an earlier eviction of that entry encountered an error
Compatible with Develocity 2025.1 or later.
0.4
-
[FIX] Connections to Develocity for data replication don’t respect HTTP/2 preference
-
[FIX] Verbose log messages for normal connection lifecycle events
-
[FIX] Delay is too long between retries of some calls to Develocity
Compatible with Develocity 2025.1 or later.
0.3
-
[NEW] Support replication using signed URLs when Develocity is connected to AWS S3 or Google Cloud Storage
-
[NEW] Option to connect to Develocity using HTTP/2
-
[NEW] Improved performance from Develocity server connections for replication
-
[FIX] Replication of data to Develocity can fail silently
-
[FIX] Edge node name isn’t updated when changed using command line argument
-
[FIX] Sanitize potentially sensitive information from log messages
Compatible with Develocity 2025.1 or later.