Release Notes: June 2025

Features & enhancements

GitOps: New release of GitOps Runtime v0.20.0

We’re excited to announce the release of GitOps Runtime v0.20.0 — a major step forward in improving the stability and reliability of our platform.

This version includes significant architectural improvements and a large number of bug fixes, setting the stage for upcoming enhancements.

This release marks a major milestone in hardening the GitOps runtime for scale, reliability, and enterprise readiness. It also introduces breaking changes, so please read carefully before upgrading.

Read the full release notes.

GitOps: Retention policy for promotions

Promotion workflows and product releases are now retained for up to 9 months. Anything older will be automatically deleted.

Pipelines: Better visibility and control over pipeline resource usage

Based on your feedback, we’ve expanded coverage of pipeline metrics to give you more visibility and control. Until now, CPU and memory usage metrics weren’t available for all steps during builds, making it harder to analyze performance and resource use.

With this update, all steps within builds, except the build step itself, now include CPU and memory metrics. This gives you clearer insight into how your pipeline is performing, where the resource usage is going, and how to optimize accordingly.

  • More consistent and reliable pipeline metrics

  • Easier analysis of performance and cost for build-heavy pipelines

We’re continuing to work on supporting resource metrics for the build step and the full build process, with additional features planned as part of the ongoing improvements.

Bug fixes

Pipelines
  • For Bitbucket: Fixed an issue where pipelines configured to trigger on the commit event were also being triggered by push.tags events (e.g., when tags were created in Bitbucket). This caused unexpected builds, resource waste, and inaccurate build stats.
GitOps
  • Fixed an issue that caused the GitOps Apps view to return empty results or error messages for some users. The problem occurred when the number of applications exceeded MongoDB’s aggregation pipeline memory limits.
  • Fixed an issue where Promotion Workflows failed in Restricted Git Source scenarios by ensuring promotions always run in the runtime namespace. Previously, running promotions in the application’s namespace led to missing secret errors (codefresh-token, argocd-token) and blocked execution.
  • Fixed an issue where the version label displayed an outdated value in the Products dashboard and Release objects.