Codefresh | Docs

Release Notes: September 2026

2026-09-01T00:00:00-05:00

This article is updated throughout the month as new releases become available.

Features & enhancements

Classic Pipelines

Request caching for Bitbucket integrations

Every pipeline build sends a number of API requests to Bitbucket, for example, to read the pipeline YAML or to fetch commit details. Busy accounts can hit the Bitbucket API rate limit because the same content is requested many times a day.

You can now enable request caching for a Bitbucket Git integration. When it is on, Codefresh stores Bitbucket API responses and serves repeated reads of the same content from the cache, so they no longer count against your rate limit.

Caching is safe to use because only content pinned to a specific commit SHA is cached, such as file contents, commit objects, and diffstats. Anything that can change, including which commit a branch or tag points to, is always resolved live against Bitbucket, so builds never read stale data. If the cache is unavailable, Codefresh falls back to a live request.

Request caching for Bitbucket integrations

To enable it, edit your Bitbucket integration in Pipeline Integrations → Git and turn on Cache requests to Bitbucket in the Caching section. The same section has a Clear cache button for account administrators, which removes all stored entries for the integration, for example, after rotating its credentials.

For details, see Request caching for Bitbucket.

Availability

Installation	Status	Action required
Cloud	Available now	None
Hybrid	Available now	None
On-premises	Planned for Codefresh Platform 2.13	Upgrade to Platform 2.13 when it is released, enable `enableGitRequestsCache` feature flag.

GitOps

Argo CD upgraded to 3.5 in GitOps Runtime

GitOps Runtime 0.31.0 bumps the bundled Argo CD to version 3.5.2, bringing the latest upstream fixes and features to Codefresh GitOps. If you bring your own Argo CD (BYOA), the supported version range is now 3.3.x to 3.5.x.

For the full list of changes and upgrade steps, see the GitOps Runtime 0.31.0 release notes and the Argo CD 3.4 to 3.5 upgrade guide.

Availability

Installation	Status	Action required
Hybrid	GitOps Runtime 0.31.0	Upgrade to GitOps Runtime 0.31.0 or later. Review the breaking changes first.
On-premises	Planned for Codefresh Platform 2.13	Upgrade to Platform 2.13 when it is released, then upgrade to GitOps Runtime 0.31.0 or later. Review the breaking changes first.

Bug fixes

Classic Pipelines

Entity name and ID were not displayed in the Audit Log for some entities

In the Audit Log, the Entity ID/Name column was empty for some entity types, such as Git contexts.

Audited events for these entities now show the name and ID of the affected entity.

Availability

Installation	Status	Action required
Cloud	Available now	None
Hybrid	Available now	None
On-premises	Planned for Codefresh Platform 2.13	Upgrade to Platform 2.13 when it is released.

Variables exported with `cf_export` could resolve to an outdated value

When a variable was exported with cf_export more than once during a build, a following step could receive an earlier value instead of the last exported one. This happened whenever the latest exported value was identical to a value the variable had held before, whether from an earlier cf_export, from the pipeline variables, or from the step’s own environment. For example, exporting MY_VAR=v1, then MY_VAR=v2, then MY_VAR=v1 again resulted in v2 in the next step.

Steps now always receive the value that was exported last for each variable.

Availability

Installation	Status	Action required
Cloud	Available now	None
Hybrid	Classic Runtime 10.5.6	Upgrade to Runtime 10.5.6 or later.
On-premises	Codefresh Platform 2.12.15	Upgrade to Platform 2.12.15 or later.

Typed steps elected on `workflow.result` no longer fail with `plugin failed`

Typed steps, such as codefresh-run or any other plugin-based step, that were elected through a when.condition on workflow.result (for example, workflow.result == 'terminated') always failed with an internal plugin failed error. An equivalent freestyle step in the same position ran and completed successfully.

Typed steps elected as a reaction to workflow.result now run to completion and conclude on their real result.

Additionally, typed steps now correctly work when a termination signal arrives before the step has started, instead of crashing.

Availability

Installation	Status	Action required
Cloud	Available now	None
Hybrid	Classic Runtime 10.5.6	Upgrade to Runtime 10.5.6 or later.
On-premises	Codefresh Platform 2.12.15	Upgrade to Platform 2.12.15 or later.

Release Notes: August 2026

2026-08-01T00:00:00-05:00

Features & enhancements

Classic Pipelines

Fewer redundant API calls to Bitbucket

Busy accounts that use Bitbucket Git integrations could hit the Bitbucket API rate limit because Codefresh sent redundant API requests.

Codefresh now avoids redundant calls to the Bitbucket API, which significantly reduces the number of requests sent to Bitbucket for some endpoints.

GitOps

Argo CD upgraded to 3.4 in GitOps Runtime

The Argo CD bundled with the GitOps Runtime is upgraded to version 3.4.

For upgrade considerations, see the Argo CD 3.3 to 3.4 upgrade guide.

Bug fixes

Classic Pipelines

One `codefresh-run` step could start duplicate child builds

In some cases, a single codefresh-run step started two child builds instead of one. Codefresh protects against duplicate runs when a request is retried, and this protection had gaps.

The handling of repeated run requests is reworked to cover the gaps, so each codefresh-run step starts only one build.

Builds failed to start when Bitbucket returned a temporary server error

When Bitbucket returned a 500 error while Codefresh was reading the pipeline specification or commit details, the build failed with Failed to run pipeline.

Codefresh now retries such requests in more cases and writes clearer log messages about the failed call.

`Reset volume` step failed after upgrading to Classic Runtime 10.5.1

After upgrading to Classic Runtime 10.5.1, the Reset volume step failed on some builds, which sometimes prevented builds from starting.

The issue is fixed now.

Docker cleaner in the `dind` pod used an outdated Docker API version

The docker-cleaner that runs inside the dind pod used a hardcoded Docker API version. With a current Docker daemon, dind logged client version <x> is too old. Minimum supported API version is <y>, and the cleaner could not work correctly.

The cleaner no longer uses a fixed version and negotiates the API version with the Docker daemon.

Pipeline name and description were rendered incorrectly on the pipeline settings page

On the pipeline settings page, the pipeline name was displayed as plain text instead of a non-editable field, and the description field looked incorrect.

Both fields are now displayed correctly.

GitOps

Runtime Health did not show the real status of runtime applications

When the runtime could not clone its Git sources, for example, because the runtime token expired, the runtime applications changed to the Unknown sync status. The Runtime Status panel still showed the runtime and its sources as healthy (green).

The Runtime Status panel now reflects the status of the runtime applications.

Release Notes: July 2026

2026-07-01T00:00:00-05:00

Features & enhancements

Classic Pipelines

Select multiple Shared Configurations at once

When an account had many Shared Configurations to add as pipeline variables, you had to add them one at a time.

When you add pipeline variables, you can now select multiple Shared Configurations at once in a single dialog.

For details, see Shared Configuration.

`msteams-notifier` step supports Power Automate Workflows

Microsoft is retiring the legacy Office 365 connectors and incoming webhooks in Microsoft Teams, which the msteams-notifier step used to post messages.

The step can now send notifications through Power Automate Workflows. Existing pipelines keep working without changes. To use a workflow, set these arguments on the step:

MSTeamsNotification:
  type: msteams-notifier
  arguments:
    USE_POWER_AUTOMATE_WORKFLOWS: 'true'
    MSTEAMS_WORKFLOW_URL: <workflow_url>

GitOps

Improved “Update Git Runtime Credentials” drawer

For an installed GitOps Runtime, the Update Git Runtime Credentials drawer gave little guidance and linked to the page about personal tokens instead of runtime tokens.

The drawer now has the same content as the Configure Git Credentials step of the Runtime installation wizard, including a link to the token generation page and instructions about the required token scopes.

For the scopes required for each Git provider, see Git tokens for GitOps.

Bug fixes

Classic Pipelines

`codecov-reporter` step failed on every run

The codecov-reporter step failed with gpg: no valid OpenPGP data found on every run.

The step is fixed in version 2.1.1.

`deploy` step failed with `ReferenceError: _ is not defined`

In Classic Runtime 10.3.7, the deploy step failed with ReferenceError: _ is not defined when it created an image pull secret.

This is fixed in Classic Runtime 10.3.8.

ECR integration with a service account ignored the configured region

When an Amazon ECR integration resolved credentials from a service account, the region set in the integration was ignored. Builds logged in to ECR using the region of the runtime instead, so images had to be in the same region as the runtime.

The configured region is now used. The fix is available in Classic Runtime 10.3.8.

Cron builds were occasionally duplicated

Cron-triggered builds were sometimes started more than once for a single scheduled run, because the idempotency token of a build request was not always handled correctly. It is fixed now.

Pipelines using a Git integration with `/` in its name could not be retrieved

When a pipeline had a Git trigger that used a Git integration with a slash in its name, the pipeline was created but could not be opened, edited, or run. Requests for it returned “pipeline not found”, and the UI reported that the pipeline was deleted.

Such pipelines can now be retrieved and managed normally.

Runtime installation failed when the API token had trailing whitespace

Installing a Classic Runtime failed during certificate signing with Cannot sign certificates and SyntaxError: Unexpected token 'C', "Content-Le"... is not valid JSON. This happened when the runtime API token contained a trailing newline, for example, when it was stored in a secret with an extra empty line.

This no longer prevents the installation.

GitOps

Incorrect scopes documented for Bitbucket runtime tokens

The documentation listed incorrect scopes for Bitbucket tokens used by a GitOps Runtime, so a token created with the documented scopes could be rejected when you updated the runtime credentials.

The documentation now lists the correct scopes. For the full list, see Git tokens for GitOps.

Release Notes: June 2026

2026-06-01T00:00:00-05:00

Features & enhancements

Classic Pipelines

Reauthorize Bitbucket OAuth Git contexts

Bitbucket Git contexts that use OAuth could not be de-authorized and then authorized again. This became a problem when the underlying OAuth application credentials changed, because existing contexts stopped working and could not be reconnected.

You can now de-authorize a Bitbucket OAuth Git context and authorize it again, so that existing contexts can be reconnected against the current OAuth application without recreating them.

For details on Bitbucket authentication methods, see Git provider pipeline integrations.

GitHub Action Executor step deprecated

The github-action-executor step in the Steps Marketplace relied on the layout of GitHub Marketplace pages, and stopped working after GitHub changed those pages. The functionality has been unsupported for some time, and the step is now formally deprecated. The related page has been removed from the Codefresh documentation.

If your pipelines use this step, replace it with a freestyle step that runs the tools you need.

GitOps

Choose between Git permissions and rules for View access to applications

By default, access to view GitOps applications is evaluated against the user’s permissions in the Git repositories of the applications. This made it hard to move to rule-based access control, because Git permissions kept applying on top of the rules.

You can now disable Git-based View permissions for your account and rely only on the permission rules you configure. You manage this yourself on the GitOps Permissions page, in Account settings → Permissions, and you can switch back at any time.

Adding View rules has no effect on access until you turn off Git-based permissions. Permission rules do not restrict account administrators.

For details on defining rules, see Access control for GitOps.

Bug fixes

Classic Pipelines

Build status was sometimes incorrect with `strict_fail_fast: true`

For pipelines that used mode: parallel together with fail_fast: false and strict_fail_fast: true, the build status was sometimes reported as successful even though a step had failed. Running the same build repeatedly could produce different final statuses.

Builds with these settings now always finish with the correct status. The fix is available in Classic Runtime 10.3.4.

Builds failed with `Cannot read properties of undefined (reading 'serviceNetworkName')` for pipelines managed with Terraform

When a pipeline was created or updated through the Codefresh Terraform provider with original_yaml_string, the services section of the YAML was not saved in the pipeline specification. Builds that used service containers then failed with Cannot read properties of undefined (reading 'serviceNetworkName').

The Terraform provider now reads the services section from original_yaml_string and saves it in the pipeline specification. The fix is available in version 1.2.1 of the Terraform provider.

Okta team sync failed with a concurrency limit error

Syncing teams from Okta sent many requests in parallel. Okta rejected them with This API token has made too many concurrent requests, so the sync did not complete.

Codefresh now keeps the sync within the Okta concurrency limit.

GitOps

Commit statuses request failed for releases without commits

Requesting commit statuses for a release that had no commits failed with an error, and commit statuses were not displayed.

The request now completes for releases without commits.

Release Notes: May 2026

2026-05-01T00:00:00-05:00

Features & enhancements

Classic Pipelines

Updated `kubectl` versions in the Kubernetes deploy step

The deploy step uses a bundled kubectl client and supports the three most recent Kubernetes minor versions. With the release of Kubernetes 1.35 and the end of life of 1.32, the supported kubectl versions in the step were updated accordingly.

For details on the step, see Deploy step.

Bug fixes

Classic Pipelines

`git-clone` step did not download Git LFS files

After the git-clone step release, cloning a repository that tracks files with Git LFS returned only the small pointer files instead of the actual content. This could break later steps that depend on those files, such as image builds.

Git LFS files are now downloaded as expected.

Kubernetes resources were not shown in the Codefresh UI

Kubernetes resources were not shown in the Codefresh UI for affected runtimes.

The platform-side configuration that caused this issue was corrected, and resources are now displayed correctly in the Codefresh UI.

`codefresh-report-image` step version 1.0.11 was missing from the Step Marketplace

Version 1.0.11 of the codefresh-report-image step existed in the public steps repository, but it was not listed in the Step Marketplace and pipelines that referenced it failed.

The version 1.0.11 is now published to the Step Marketplace.

Documentation: retries are disabled in debug mode for the Codefresh CLI

Enabling debug mode in the Codefresh CLI turns off automatic retries of failed requests, so that the exact network errors can be captured in the logs. Because of this, temporary network issues, such as socket hangups, fail the command immediately. For example, a codefresh-run step could terminate its child build on such a failure.

This behavior is now documented in How To: Enable debug mode when using Codefresh CLI. Use debug mode for troubleshooting rather than for everyday builds.

GitOps

Image reporting failed in GitOps Runtime

Image reporting steps in GitOps workflows failed after upgrading to GitOps Runtime 0.29.8. Pipelines using the codefresh-report-image step failed with TypeError: Cannot set properties of undefined (setting 'repoDigest').

GitOps Runtime 0.29.9 includes updated image enrichment and reporting images that fix the error. If you applied a workaround by overriding the reportImage, gitEnrichment, and jiraEnrichment image tags in your values, remove the override when you upgrade.

`cap-app-proxy` could not write to `/tmp` in restricted environments

After upgrading to GitOps Runtime 0.29.9, cap-app-proxy failed to clone Git repositories with could not create leading directories of '/tmp/...': Permission denied. This affected clusters that run containers with a read-only root file system, such as OpenShift, and blocked the upgrade.

This is fixed in GitOps Runtime 0.29.10. Upgrade to GitOps Runtime 0.29.10 or later. If you added an emptyDir volume mounted at /tmp for cap-app-proxy as a workaround, you can remove it.

Release Notes: April 2026

2026-04-01T00:00:00-05:00

Features & enhancements

GitOps

`cap-app-proxy` runs as a non-root user

Security policies in some organizations do not allow containers to run as root, which blocked the use of the cap-app-proxy component of the GitOps Runtime.

cap-app-proxy now runs under a non-root user. This change is available starting with GitOps Runtime 0.29.4.

Bug fixes

Classic Pipelines

`git-clone` step failed with `grep: command not found` and could use outdated code

A recent update of the git-clone step image was built without the grep utility. The step logged grep: command not found, and as a result skipped resetting the checked-out branch to the latest commit. Builds that reused an existing volume could therefore build outdated code, unless Reset pipeline volume was enabled in the trigger settings.

The image now includes all required utilities, and the step updates the branch to the latest changes again. The fix is available in Classic Runtime 10.0.13.

Bitbucket integrations failed after Bitbucket deprecated some API endpoints

Bitbucket deprecated several API endpoints that Codefresh relied on, and calls to them started to return HTTP 410. As a result, creating a Bitbucket integration with an API token failed with Error occurred while verifying credentials, and builds that used a Bitbucket OAuth integration intermittently failed with rate limit errors.

Codefresh no longer uses the deprecated endpoints, so you can create Bitbucket integrations with an API token again, and builds with OAuth integrations no longer fail with these rate limit errors.

All Codefresh accounts that use OAuth share a single Bitbucket OAuth consumer and its rate limit quota, so we recommend the API token method for busy accounts. For details, see Bitbucket in the Git provider integrations documentation.

GitOps

GitHub token link generated after runtime installation did not request all required permissions

After you installed a GitOps Runtime, the link that Codefresh generated for creating a GitHub token did not include the user:email permission. This permission is required to initialize the Internal Shared Configuration repository from the Runtime.

The generated link now requests all required permissions.

Release Notes: March 2026

2026-03-01T00:00:00-06:00

Features & enhancements

Classic Pipelines

Force-refresh Bitbucket OAuth tokens with the Codefresh CLI

Pipelines that read a Bitbucket OAuth token from a Git integration, for example, to call the Bitbucket API directly, could receive a token that was already expired or about to expire. The expires field in the integration data does not show when the token actually expires, so it cannot be used to decide when to refresh.

You can now get a valid token on demand with codefresh get context:

--prepare now works for Bitbucket OAuth integrations. It refreshes the token only if it has expired or expires in less than 10 minutes, so the returned token stays valid for at least the next 10 minutes.
--force-prepare refreshes the token immediately, even if the current one is still valid. It is available in Codefresh CLI 1.1.0 and later.

For example:

codefresh get context 'Bitbucket-OAuth-integration-name' --force-prepare -o json | jq -r .spec.data.auth.password

Run the command before any step that calls Bitbucket. For details on working with contexts, see Shared configuration.

Stricter AWS region validation for AWS integrations

Region values for AWS-based integrations were not checked on the server. A mistyped region was accepted when saving the integration and only failed later, when a build used it.

When strict validation is enabled for your account, Codefresh now checks the region against the list of public AWS regions supported by the AWS SDK. The check applies to Amazon ECR integrations, AWS S3 Helm integrations, and the report-image-info enricher.

Bug fixes

Classic Pipelines

Pipelines could fail to start when Bitbucket returned an incomplete response

Builds, including builds started by the codefresh-run step, sometimes failed with Failed to run pipeline when the Bitbucket API timed out or returned an error while Codefresh was reading the latest commit. The underlying error was not retried and was reported as a generic failure. This happened mostly during Bitbucket maintenance windows and incidents, and mainly affected pipelines with Bitbucket triggers.

Codefresh now retries these requests when they fail with a connection error or an error returned by the Git provider, and handles an empty commit response without failing with an internal error.

Pipelines could not be started from the UI after a commit made with a Bitbucket repository access token

When the last commit of a branch was made with a Bitbucket repository access token, starting the pipeline manually from the UI failed with the Error building service message and the build was not triggered.

Pipelines now start normally when the last commit was made with a repository access token.

Builds could fail with “Failed to write template file into filesystem”

On runtimes with a shared filesystem, builds occasionally failed with Failed to prepare plugin. Failed to write template file into filesystem, mostly when many pipelines were started at the same time. The failure was caused by a container that could not be stopped after the file was written.

Builds no longer fail when this specific container stop error occurs.

Cron triggers sometimes did not start pipelines

Some pipelines with cron triggers were not started at the scheduled time. The services that handle cron triggers were restarted without being reported as crashed, and the scheduled runs that fell into that window were missed.

Scheduled pipelines now start as configured.

Quick search opened a malformed link for projects and pipelines with special characters

When a project or pipeline name contained a special character such as +, the link from Quick search was not encoded correctly. Opening it either loaded indefinitely or redirected to a different pipeline.

Quick search now encodes project and pipeline names in the link, so the correct pipeline opens.

GitOps

The GitOps Runtime pre-install validation rejected supported Argo CD versions

When upgrading to GitOps Runtime 0.28.0 or later with your own Argo CD (BYOA), the validation hook failed with an error such as Argo CD version v3.3.2 does not satisfy required range '>=3 <=3.2', even though the release notes listed the version as supported. The workaround was to set installer.skipValidation: true.

The validation now uses the correct supported Argo CD version range, and the upgrade no longer needs the validation to be skipped.

Release Notes: February 2026

2026-02-01T00:00:00-06:00

Features & enhancements

Classic Pipelines

API token authentication for Bitbucket Cloud integrations

Bitbucket is deprecating App passwords in favor of API tokens, and OAuth2 connections to Bitbucket Cloud share a single API rate limit across all Codefresh accounts that use them.

You can now connect a Bitbucket Cloud Git integration with an API token. The Bitbucket Git integration has a new API Token tab where you enter your Bitbucket account email and an API token. Codefresh verifies that the token has the required scopes before saving the integration.

To use it, add or edit your Bitbucket integration in Pipeline Integrations → Git and select the API Token tab. For the list of required scopes and how to create the token, see Bitbucket API token.

Bug fixes

Classic Pipelines

Webhook secrets of existing Git triggers were exposed in the UI

After you created a new Git trigger for a pipeline, the webhook secret and endpoint URL of the other Git triggers on the same pipeline were displayed in the UI until you refreshed the page. The pipeline API responses also included the secrets of all the triggers.

Trigger secrets are now masked in these responses, so they are visible only when you first configure a trigger.

Conditional expressions were silently truncated to 1024 characters

Step conditional expressions longer than 1024 characters were cut off before variable interpolation. A truncated expression was invalid, for example, with an unclosed parenthesis, so the condition was ignored with an error such as Unclosed ( at character 1024.

The maximum length of a conditional expression is now 12,000 characters. Codefresh validates the length both in the pipeline definition and during the build, before and after variable interpolation, so an expression that is too long is reported instead of being cut off. For details, see Conditional execution of steps.

Misleading warning in the advanced options of a trigger

In the More options of a Classic trigger, the warning said that disabling “Ignore Docker engine cache” or “Reset pipeline volume” might make builds slower, which is the opposite of what happens. The warning was also displayed below the reporting notification option, which implied that this option affects build speed.

The warning now says that enabling one of the options might make builds slower, and is displayed right below Reset pipeline volume.

Random `failed to write subtree controllers` errors in `dind` pods

In some builds, dind pods logged the error failed to write subtree controllers [cpuset cpu io memory hugetlb pids misc]. When it occurred, build metrics shown in the UI and reported through OpenTelemetry were affected. It was caused by a race condition on nodes that use cgroup v2: if side processes of the dind entrypoint started late, the controllers required for step containers could not be enabled.

The dind image now moves its init process and all subprocesses to a dedicated cgroup at the very beginning of its startup. The fix is available in dind 29.2.0-3.0.11 and in Classic Runtime 10.0.1.

Release Notes: January 2026

2026-01-01T00:00:00-06:00

Bug fixes

Classic Pipelines

Pagination flickered on the Projects page

On the Projects page, when the list had more than one page and you used the Next or Previous buttons, the pagination controls flickered.

Pagination now stays stable when you move between pages.

Missing border on the Next button on the Pipelines page

On the Pipelines page, the Next button lost its border when you selected the last page, which made it look different from the Previous button.

The Next button now keeps its border on the last page.

GitOps

“Learn more about Releases” link opened the wrong page

For a product with no releases, the Learn more about Releases link opened the Codefresh account creation guide instead of the documentation for releases.

The link now opens Releases for products.

Release Notes: December 2025

2025-12-01T00:00:00-06:00

Bug fixes

Classic Pipelines

SSO configuration drawer lost your input when you clicked outside it

When you configured a new single sign-on (SSO) provider in Account Settings → Single Sign-On, clicking anywhere outside the configuration drawer closed it immediately. All the values you had entered were discarded, and you had to fill in the whole configuration again.

This is now fixed.

For details on configuring SSO, see Single Sign-On.

Codefresh | Docs

Release Notes: September 2026

Features & enhancements

Classic Pipelines

Request caching for Bitbucket integrations

Availability

GitOps

Argo CD upgraded to 3.5 in GitOps Runtime

Availability

Bug fixes

Classic Pipelines

Entity name and ID were not displayed in the Audit Log for some entities

Availability

Variables exported with cf_export could resolve to an outdated value

Availability

Typed steps elected on workflow.result no longer fail with plugin failed

Availability

Release Notes: August 2026

Features & enhancements

Classic Pipelines

Fewer redundant API calls to Bitbucket

GitOps

Argo CD upgraded to 3.4 in GitOps Runtime

Bug fixes

Classic Pipelines

One codefresh-run step could start duplicate child builds

Builds failed to start when Bitbucket returned a temporary server error

Reset volume step failed after upgrading to Classic Runtime 10.5.1

Docker cleaner in the dind pod used an outdated Docker API version

Pipeline name and description were rendered incorrectly on the pipeline settings page

GitOps

Runtime Health did not show the real status of runtime applications

Release Notes: July 2026

Features & enhancements

Classic Pipelines

Select multiple Shared Configurations at once

msteams-notifier step supports Power Automate Workflows

GitOps

Improved “Update Git Runtime Credentials” drawer

Bug fixes

Classic Pipelines

codecov-reporter step failed on every run

deploy step failed with ReferenceError: _ is not defined

ECR integration with a service account ignored the configured region

Cron builds were occasionally duplicated

Pipelines using a Git integration with / in its name could not be retrieved

Runtime installation failed when the API token had trailing whitespace

GitOps

Incorrect scopes documented for Bitbucket runtime tokens

Release Notes: June 2026

Features & enhancements

Classic Pipelines

Reauthorize Bitbucket OAuth Git contexts

GitHub Action Executor step deprecated

GitOps

Choose between Git permissions and rules for View access to applications

Bug fixes

Classic Pipelines

Build status was sometimes incorrect with strict_fail_fast: true

Builds failed with Cannot read properties of undefined (reading 'serviceNetworkName') for pipelines managed with Terraform

Okta team sync failed with a concurrency limit error

GitOps

Commit statuses request failed for releases without commits

Release Notes: May 2026

Features & enhancements

Classic Pipelines

Updated kubectl versions in the Kubernetes deploy step

Bug fixes

Classic Pipelines

git-clone step did not download Git LFS files

Kubernetes resources were not shown in the Codefresh UI

codefresh-report-image step version 1.0.11 was missing from the Step Marketplace

Documentation: retries are disabled in debug mode for the Codefresh CLI

GitOps

Image reporting failed in GitOps Runtime

cap-app-proxy could not write to /tmp in restricted environments

Release Notes: April 2026

Features & enhancements

GitOps

cap-app-proxy runs as a non-root user

Variables exported with `cf_export` could resolve to an outdated value

Typed steps elected on `workflow.result` no longer fail with `plugin failed`

One `codefresh-run` step could start duplicate child builds

`Reset volume` step failed after upgrading to Classic Runtime 10.5.1

Docker cleaner in the `dind` pod used an outdated Docker API version

`msteams-notifier` step supports Power Automate Workflows

`codecov-reporter` step failed on every run

`deploy` step failed with `ReferenceError: _ is not defined`

Pipelines using a Git integration with `/` in its name could not be retrieved

Build status was sometimes incorrect with `strict_fail_fast: true`

Builds failed with `Cannot read properties of undefined (reading 'serviceNetworkName')` for pipelines managed with Terraform

Updated `kubectl` versions in the Kubernetes deploy step

`git-clone` step did not download Git LFS files

`codefresh-report-image` step version 1.0.11 was missing from the Step Marketplace

`cap-app-proxy` could not write to `/tmp` in restricted environments

`cap-app-proxy` runs as a non-root user

`git-clone` step failed with `grep: command not found` and could use outdated code

Random `failed to write subtree controllers` errors in `dind` pods