Codefresh | Docs

Release Notes: November 2025

2025-11-30T00:00:00-06:00

Features & enhancements

GitOps Cloud: Enhanced resource pruning information

We’ve improved the application sync dialog with new safeguards to provide better clarity and control when initiating a manual sync with pruning enabled.

Enhanced resource pruning information

Sync dialog enhancements

We’ve added key pieces of information and warnings directly to the initial Synchronization screen:

Tooltip clarity: We added a helpful tooltip to provide a concise explanation of resource pruning.
Safety warning: If you enable the Prune option, a clear warning message will now be displayed. This notifies you that the action deletes resources that are no longer defined in your source configuration.

Resources highlighted for deletion

In the next screen, where you select resources, GitOps Cloud now makes it easy to identify exactly what will be removed:

Top visibility: Resources marked for deletion (pruning) are now highlighted and automatically placed at the top of the resource list.
Clear status: You’ll see an explicit Requires pruning badge next to the resource status, ensuring you know which items are targeted for removal.

Final confirmation

To provide a final check against unintended deletions:

Visual alert: If the sync action includes pruning any resource, the final Synchronize button will turn red. This serves as a strong visual cue to confirm that you are running a destructive operation.

These updates are designed to give you more control and confidence when managing your application synchronization.

GitOps Cloud: New release of GitOps Runtime v0.25.0

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

This release includes the following dependency update:

The Argo CD fork has been synchronized to OSS version 3.1.5, bringing compatibility improvements and alignment with upstream Argo CD.

There are some breaking changes planned for the next release, so we encourage you to read the release notes and prepare your deployments accordingly.

Read the full release notes.

Release Notes: August 2025

2025-08-29T00:00:00-05:00

Features & enhancements

GitOps Cloud: Enhanced GitOps App Breadcrumbs

We’re excited to announce a major enhancement to the GitOps App breadcrumbs, designed to streamline your navigation and provide more insightful context. This update is a huge step toward making your workflow more intuitive and efficient.

Direct Runtime navigation: We added the Runtime name directly to your breadcrumb trail. A simple click on the Runtime name will take you to the main applications page, automatically filtered to display only the apps associated with that specific runtime.
Visual clarity with new icons: To help you better understand your application’s hierarchy at a glance, we introduced new icons for each breadcrumb component:
A unique icon for the Runtime Name.
A helpful icon for the ApplicationSet, if your application uses one.
A clear icon for the Application Name itself. These improvements provide a more visually organized and functional navigation system, helping you manage your GitOps applications with greater speed and clarity.

New navigation breadcrumbs

Pipelines: Classic Runner 8.x Release – Breaking Changes

On July 17, 2025, we released Classic Runner version 8.x (based on Docker v28) for our hybrid customers. This release introduces breaking changes and requires action before upgrading.

For Hybrid Customers If you have not yet upgraded, you have 2 options:

Option 1:

Use the Modern Helm-Based Runner Installer
Breaking change: Support for legacy Docker images (manifest schema v2, schema 1) has been removed. Pipelines that build or pull these images will fail after upgrade.

What to do:

Identify and update deprecated images using our migration guide in GitHub.
Upgrade to Runner 8.0 via the Helm-based installer.

Option 2:

Continue with the Legacy CLI-Based Runner Installer
The legacy installer is now deprecated. You will no longer receive upgrades, updates, or security patches. It will remain locked to the last version based on Docker v26.

What to do:

We strongly recommend migrating to the Helm-based installer.
This lets you upgrade to Runner 8.0 and continue receiving updates and security patches.

For SaaS & On-Prem Customers

SaaS: We automatically upgraded all SaaS environments to the new runner on August 17, 2025.
On-Prem: Support for Runner 8.0 will be included in On-Prem release 2.9 (due September 30, 2025).

Pipelines: New Security Enhancement: Prevent Unauthorized Changes to ABAC Tags

We heard your feedback about accidental changes to tags used in ABAC permission rules, and we’ve addressed this. Until now, users could modify or delete these tags without warning, which risked breaking access controls and unintentionally exposing resources.

With this update, whenever a user tries to edit or remove a tag linked to an ABAC rule, a clear warning message will appear. This helps prevent mistakes that could compromise security or block authorized users.

We’re continuing to explore improvements that make ABAC easier to manage while keeping security controls strong.

Key benefits

Prevents accidental changes to security-critical tags
Clear warnings to avoid breaking ABAC rules
Stronger protection of your access controls

This enhancement gives teams greater peace of mind, ensuring that access policies remain secure without slowing down development.

New ABAC warning

Bug fixes

Pipelines

Fixed recurring “socket hang up” build failures in by increasing engine pod CPU requests and stabilizing dind/network behavior.
Fixed cron trigger creation errors caused by outdated regex handling of short custom cron expressions, adding clearer error messaging.

Release Notes: July 2025

2025-07-25T00:00:00-05:00

Features & enhancements

GitOps: Runtime v0.22: Argo CD 3.0 Upgrade

This runtime release upgrades Argo CD to version 3.0, bringing the latest features and improvements to Codefresh GitOps.

While we haven’t identified any breaking changes for standard Codefresh deployments, please review the following recommendations:

If you have customized any default Argo CD values beyond what Codefresh distributes, you may be affected by changes introduced in Argo CD 3.0.
Review the official Argo CD 3.0 migration guide if you maintain custom configurations.
If you have made extensive customizations, test this runtime upgrade in a non-production environment first.

For details, see the runtime v0.22.1 release notes.

Bug fixes

General

Fixed an issue where Quick Search (CMD + K) did not return any GitOps-related items, including applications. Users can now search and access GitOps items directly through Quick Search as expected.

Pipelines

Fixed an issue that caused timeouts when loading UI pages for pipelines with a large number of triggers.
Fixed an issue where MacOS builds failed with an ‘Unauthorized’ error when provisioning the runtime, preventing customers from running MacOS builds successfully.
Fixed an issue where builds intermittently failed with a ‘Failed to prepare dockerfile’ error, preventing the Dockerfile from being fetched correctly during the build process.
Fixed an issue where SaaS builds failed due to insufficient disk space by re-enabling cleanup processes.

GitOps

Fixed an issue where applications nested more than three layers deep were not displayed in the UI tree view. The full application hierarchy now appears correctly in the tree view.

Release Notes: June 2025

2025-06-29T00:00:00-05:00

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.

Release Notes: May 2025

2025-05-15T00:00:00-05:00

This release addresses a number of fixes to improve your experience across the platform.

Features & enhancements

Pipelines: Manage pipeline runner ABAC rules with Terraform

Managing access policies and environment isolation just got easier! You can now define runner permissions—controlling which teams can use which runners—directly through our Terraform provider.

This update helps you eliminate manual UI configuration, reduce human error, and scale access management more efficiently across teams.

Key benefits

Declare ABAC policies in Terraform alongside other team and pipeline configurations.
Define team-runner relationships to control who can run what.
Filter runner access by tags to fine-tune permissions.
Support multiple rules per team for flexible access control.
Match existing ABAC behavior found in the UI and API.

This feature helps teams maintain consistent, automated access control at scale.

Bug fixes

Pipelines

Git trigger for “Release published” fires incorrectly when any release-related trigger is enabled.
Webhook events for Bitbucket ignored when pipeline trigger uses different Bitbucket integrations.
For GitHub, list of files modified by PR (pull request) does not include all modified files.

GitOps

Wrong revision promoted when a Promotion Flow is triggered manually by clicking Trigger button or automatically.
Release status not updated for product when a Promotion Flow is triggered manually by clicking the Trigger button.
Updated validation for the Name field in Promotion Workflows to not allow underscores.
GitOps permission rule for applications including the Git Source attribute not supported for applications from ApplicationSets.
Removed the SSH option from the Repository field in the Create Git Source form. Selecting SSH resulted in the error failed creating git-source. error: Invalid URL, as SSH is not a valid option for Git Sources.
Inaccurate change failure rate for DORA metrics.

Release Notes: April 2025

2025-04-30T00:00:00-05:00

Features & enhancements

GitOps: Configure promotion settings with JSON Path Selector and live preview

We’ve made configuring your promotion settings simpler, so you can get it right the first time without guesswork. Using our new preview window, you can now select JSON paths directly from your YAML files. Just point to the file, browse its structure, and the correct path is inserted for you—wildcards included. This takes the guesswork out of configuring your promotion settings.

JSON file selector for promotable properties

Find out more.

GitOps: Align delivery cadence with smart promotion concurrency

Take full control over how releases are promoted across environments with two powerful concurrency modes now available per product.

Queue releases mode

Using the Queue Releases mode, only one release can run at a time for a product. If a new release is triggered while another is promoting, it will wait its turn until the current one finishes.

Terminate releases mode

With the Terminate releases mode, multiple releases can be promoted in parallel, but with a smart safeguard: If a new release starts promoting to an environment that’s already being updated for the product, the older release is automatically terminated in that environment.

Promotion concurrency settings for products

With smart promotion concurrency, you can:

Stay safe in production with sequential releases
Move fast in dev while avoiding collisions
Adapt your promotion strategy per product

This makes it easier to align your GitOps pipelines with your team’s delivery rhythm. Find out more.

GitOps: More intuitive redesigned Products page

Get faster access to key information and actions with our newly redesigned Products page! Better understand release activity and manage your products more efficiently.

New Products page

Everything you need to know about the latest release is now available at a glance:

Release date and version
User who initiated the latest release
Current release status
Direct link to the release view

You also have a direct link to Product Settings—giving you quick access to configuration options you’re likely to update frequently.

Enjoy the new experience.

Bug fixes

General

Blank screen after login for invited users with SSO sync enabled.

Pipelines

Git trigger for “Release published” fires incorrectly when any release-related trigger is enabled.
Webhook events for Bitbucket ignored when pipeline trigger uses different Bitbucket integrations.
For GitHub, list of files modified by PR (pull request) does not include all modified files.

GitOps

For installations with existing Argo CD, applications added from Helm repository show Unknown status in GitOps Apps dashboard.
Unable to set up OAuth authentication for GitOps Runtime.
Incorrect merge for promotable properties defined as an array (Products > Product Settings > Promotion Settings).

Release Notes: March 2025

2025-03-31T00:00:00-05:00

Features & enhancements

GitOps: Bring your own Argo CD

We’ve made it easy to connect existing Argo CD infrastructure with GitOps Cloud. The agent lets you bring your own Argo CD instance, which works in plug-and-play mode. You install it in minutes, and if you change your mind you can also remove it without affecting your existing Argo CD instance.

Installing GitOps Runtime connecting to existing Argo CD

If you don’t want to bring your own Argo CD instance, that’s no problem. You can still choose the GitOps Runtime to manage all Argo services in one bundle with our easy installation process.

For details, see Installing Runtime with existing Argo CD.

GitOps: Simplified Runtime installation with the installation wizard

Our new installation wizard, designed for ease of use and maximum visibility into every step, makes installing a GitOps Runtime simple, intuitive, and quick.

New Runtime installation wizard

Key features

Installation and configuration steps are clearly defined, so you can complete the entire setup from the same location.
Guided experience that walks you through each step.
Inline parameter descriptions so you always know what to define.
Automatic progress saving so you can stop anytime and resume exactly where you left off.

Installation

Install a Runtime in three simple steps:

Define a repository in your Git provider account to store shared configuration settings.
Review and define installation parameters, which are automatically populated in the install command.
Run the install command in your terminal.

Configuration

Configuration steps are clearly defined, making the setup process easy to complete.

Define Git credentials, with the option to use the same token for both the Runtime and user authentication. Required scopes are detailed to ensure the correct permissions.
Configure as an Argo CD Application to take full advantage of GitOps.
Add a Git source to the Runtime so you’re ready to create applications.

Pipelines: Easily add secret variables

We’ve introduced a simpler and more secure way to add secret variables in your pipelines, making it faster and safer to manage sensitive data. Before this update, adding a secret required creating a standard variable, temporarily exposing the value, and manually encrypting it, increasing the risk of accidental exposure.

With this update, you can define a secret variable upfront, so it’s automatically encrypted from the start. Now, when clicking “Add”, you can create a regular variable or secret variable directly in the UI.

Adding secret variables

This update brings:

One-step secret creation: No need to manually encrypt after adding a variable.
Improved security: Secrets are encrypted automatically, reducing exposure risks.
More intuitive workflow: Easily distinguish between regular and secret variables

For details, see User-defined variables.

Pipelines: Prevent conflicts from overridden variables

We’ve introduced a smarter way to manage variables across shared configurations, projects, pipelines, and triggers.
Previously, it was easy to unintentionally override a project-level variable at the pipeline level—without realizing it. Now, you get a warning when creating a variable that already exists at a higher level, helping you make safer, more informed decisions.

Smart conflict detection: See a warning when you try to define a variable that already exists at a higher scope.
Safer collaboration: Reduce accidental overrides and keep pipelines in sync with shared variables.
Better visibility: Understand when you’re about to break the connection to a higher-level variable.

For details, see Order of precedence for user-defined variables.

Bug fixes

Pipelines

Helm step does not use latest Helm version 3.14.

GitOps

Typo in parameter name in the values.yaml file of the gitops-runtime chart.

Release Notes: February 2025

2025-02-19T00:00:00-06:00

Features & enhancements

General: Increased limit for audit logs

Codefresh keeps a log of all actions that happen at all times based on API calls that reach Codefresh. These include UI actions from users, CLI invocations, and any external integration used with Codefresh.

We have now increased the audit limit from 15,000 to 50,000, which means you can access more data on how you use your Codefresh account.

For details, see Auditing actions in Codefresh.

GitOps: GitHub status checks for Codefresh Promotions

We have introduced a new GitHub status check feature to make tracking your deployments more seamless and efficient. When you promote across environments, Codefresh will automatically report back a Git status check on any commits.

Status checks include a direct link to the release, so you can quickly view its progress.
There’s no need to leave GitHub. You can stay updated on your release status without switching tools.
If any issues arise, simply follow the link to troubleshoot effortlessly.

Promotion status check in GitHub

For details, see Tracking releases for Products.

Bug fixes

Pipelines

build step fails to build ECR images when base image (FROM) is from a different AWS account.

GitOps

exec /bin/sh: argument list too long validation error on upgrading GitOps Runtime.
All clusters not displayed in the UI after upgrading GitOps Runtime to 14.1.
Broken hyperlink to Shared Configuration Repository in the Upgrade Runtime panel.

Release Notes: January 2025

2025-01-25T00:00:00-06:00

Features & enhancements

GitOps: Argo CD upgraded to v2.13

Codefresh GitOps now uses Argo CD v2.13, the latest version from Argo CD. You can take advantage of the latest features and bug fixes Argo CD 2.13 as detailed in the release notes. This blog post summarizes what’s new in this release.

GitOps: Settings for Promotion Flows

We have introduced settings for Promotion Flows to give you greater control and flexibility in managing them. When creating a Promotion Flow, you can define several settings, including the Flow Timeout and Version.

Settings for Promotion Flows

Flow Timeout: Ensures Promotion Flows don’t run indefinitely by setting a maximum duration for execution. If a Flow exceeds this duration, it is automatically terminated.
Why is this useful?
- Manual approval delays: In PR-driven flows, the timeout automatically terminates the Flow if required approvals aren’t provided within the defined time frame.
- Misconfigured tests: Prevents new Promotion Flows from running indefinitely due to errors in testing configurations. The default timeout, if not explicitly set, is 1 day (24 hours).
Version: Allows you to indicate changes to the same Promotion Flow.

For details, see Create a Promotion Flow.

GitOps: Product Releases enhancements

We’ve made several improvements to the Product Releases page enhancing traceability and clarity.

Product > Releases page

Date: The Release ID has been replaced with the date when the release was initiated, making it easier to track when each release occurred. Failed releases now show a tooltip with a summary of the reason for the failure, improving troubleshooting.
Initiator: The name of the user who initiated the Promotion Flow that triggered the release is now displayed, helping with better accountability.
Version: The version defined in the Promotion Flow settings is now also shown on the Product Releases page, providing more context and consistency for each release.

For details, see Tracking releases for products.

GitOps: Free Hosted Runtimes

Codefresh no longer offers free Hosted GitOps Runtimes.
If you’re interested in our paid options, please contact our sales team at sales@codefresh.io for details.

Bug fixes

Pipelines

Builds frozen at the initialization phase when connecting to Vault secret store.
Build fails with manifest unknown error when referencing or including v1.0.12 of jira-issue-manager step.

GitOps

Discrepancy between memory defined for build and actual memory allocated.

Release Notes: December 2024

2024-12-30T00:00:00-06:00

Features & enhancements

As we share this month’s update, we want you to know that we’re hard at work on several new features and improvements to make your experience even better. Stay tuned!

GitOps: Display full name for applications

Here’s a usability enhancement that’s sure to resonate: display full name of resources in the Current State tab of the GitOps Apps dashboard.

If you have naming conventions that result in long names for applications or resources, easily toggle between displaying the full or truncated name with a handy button in the toolbar.

Show Full Name toggle in Current State tab

Bug fixes

Pipelines

504 timeout error on uploading test report to Google Storage Cloud (GSC).
Docker Compose files using Version 3 not supported for service containers in pipelines.

GitOps

New clusters added to Runtime not displayed in Runtimes > Managed Clusters tab.
failed to retrieve application version, app name: <"app_name>": unknown key appVersion error when application versioning is not configured.
Application validations use destination cluster instead of application cluster.
Application includes circular dependencies... warning in GitOps Apps dashboard when the names of applications and application sets are identical.