Skip to content
Pricing
Search
Results from:
Site
Blog
Docs
Images
Orbs
Resources
Site
Blog
Docs
Images
Orbs
Resources

Changelog

Keep up to date with our latest
releases and enhancements.

VS Code extension now supports Rollback pipeline values    

We’ve updated the CircleCI VS Code extension to support a new set of pipeline values used by the Rollbacks feature.

Rollback Pipeline UI Changes for Release Agent Customers    

For customers using CircleCI’s release-agent, the CircleCI web app now lets you invoke a rollback from the Project Overview Page. We’ve removed other rollback options from the Project Overview page for simplicity in these cases.

Zstd for Cache Compression    

The compression algorithm used for caches as part of the save_cache step is changing from gzip to zstd. This change will be rolled out gradually to all projects over the next few weeks.

For more information please refer to our Discuss post.

Component's Current Version Now Available on Project Overview Page    

Based on user feedback, we have added the ability see your component’s current version in the deploys card on the project overview page. This is available for all who use manual deploy markers.

"Project setup" page now supports editing capabilities    

We’ve expanded the Project settings > Project Setup page with new editing capabilities. Previously view-only, this page now allows some management of pipelines and triggers in one unified location.

Identity Provider Initiated Login for Single Sign On    

Identity provider(IdP) initiated login is now allowed for organizations that enforce single sign on in CircleCI. https://circleci.com/docs/authentication/sso-overview/

Deleting contexts double confirmation    

Users attempting to delete a context are now prompted to double confirm the delete by typing the name of the context. Previously the user was prompted to type “DELETE”.

Improved navigation for logged-out users     

We’ve improved the experience for logged-out users accessing in-app pages by updating the redirect button to guide users to our login page instead of showing a 404 error.

Status Checks for Skipped Jobs in GitHub App Integration    

Previously, we had planned to report skipped jobs as “success”, but after careful consideration, we’ve decided to not report them at all.

Improved invite flow for GitHub OAuth App integrated organizations    

We’ve updated the invite links within the Organization Settings > People tab for GitHub OAuth app integrated organizations to bypass the signup page, enabling users to automatically join their organization after account setup.

Fixed order of parameters in trigger pipelines modal    

The trigger pipeline modal now always lists pipeline parameters in the same order in which they appear in the configuration file.

Dark mode available in CircleCI web app    

Users can now enable “Dark mode” through the CircleCI web app. Comment in our community forum with any issues.

Ability to test run pipelines with local config files via the CircleCI CLI    

circleci pipeline run now lets you test run pipelines using local, unversioned configuration files directly from the CircleCI CLI. This enables you to validate config changes before committing them to version control. Run circleci pipeline run -h for instructions.

To run a pipeline with a local config file, you’ll need to enable “Allow triggering pipelines with unversioned config” in Organization Settings > Advanced.

Ability to list pipeline definitions via the CircleCI CLI    

circleci pipeline list now returns a list of pipeline definitions for a given project from the CircleCI CLI. Run circleci pipeline list -h for instructions.

Auto-populate trigger pipeline modal parameters based on selected pipeline (OAuth pipelines)    

The auto-populate trigger pipeline modal parameters feature now also supports pipelines that use CircleCI’s GitHub OAuth app integration and Bitbucket Cloud integration. Previously, this feature was only available for pipelines integrated through CircleCI’s GitHub App integration.

Ability to create a trigger via the CircleCI CLI     

circleci trigger create now lets you create a trigger from the CircleCI CLI. Run circleci triger create -h for instructions.

Ability to create a pipeline definition via the CircleCI CLI     

circleci pipeline create now lets you create a pipeline definition from the CircleCI CLI. Run circleci pipeline create -h for instructions.

Rerun workflow available to CircleCI MCP Server    

Rerun workflow from start & rerun workflow from failed are both available via the CircleCI MCP Server.

Faster feedback for all through system performance improvements    

The Upstream Concurrency Graph is used to detect conflicts when writing to workspaces. If a potential conflict is detected, the execution provides a clear, actionable error to the customer. For very large and complex pipelines, the building of the graph could take up to 15 minutes. We have reduced the time to compute the graph by 96%. What once took up to 15 minutes is now completed in 1.7 seconds.

Configure deployment-specific statuses in the CircleCI web app     

Separate the status of your deployments reaching their target environments from the status of your overall deployment pipeline. Read the docs to get started.

Branches Now Displayed in Branch Picker Regardless of Trigger Settings    

We’ve enhanced our platform to ensure branches appear in the branch picker dropdown even when they don’t trigger a pipeline build due to trigger settings like “Only build PRs” or “CI Skip” being enabled.

Ability to create a project via the CircleCI CLI    

circleci project create now lets you create a project from the CircleCI CLI. Run circleci project create -h for instructions.

Workflow start time & duration are now copyable from CircleCI web app    

Icons to copy workflow start time & duration were introduced today as a quality-of-life improvement: copyable icons

MCP server can now list followed projects    

The CircleCI MCP server can now return a list of the projects that a user follows across all orgs that they are a member of.

Ability to copy pipeline start time to clipboard from CircleCI web app    

The start time for a given pipeline is now copyable on hover in the CircleCI web app.

MCP server can now return filtered test results by status (failed or passed)    

Based on user feedback, the CircleCI MCP server has been updated to let users filter their CI results by status (failed or passed). For example, you can now ask “which tests failed for this job: (insert job URL)” and you will get back a filtered list of failed test results instead of all test results.

MCP server can now get build failure logs with CircleCI job URLs    

The CircleCI MCP server can now return CI results in response to a job URL (ie. https://circleci.com/gh/org-name/project-name/job-number or https://app.circleci.com/pipelines/github/org-name/project-name/pipeline-num/workflows/workflow-id/jobs/job-number).

MCP server can now be installed from VSCode Extension    

The VSCode extension now supports a command to install the CircleCI MCP server. It is available in VSCode tools CircleCI: Install MCP Server.

New tab "Project setup" in project settings    

We’ve introduced a new “Project Setup” page in Project Settings, designed to simplify how pipelines and triggers are presented and managed. This unified experience will eventually replace the separate Pipelines and Triggers tabs.

Change to pipeline naming convention for GitHub OAuth and Bitbucket integrations     

We’ve updated the naming convention for pipelines integrated via GitHub OAuth app and Bitbucket Cloud. Previously, OAuth pipelines were automatically named {project-name} default, which in some cases created confusion. To improve clarity, we’ve simplified the naming structure by removing the “default” suffix. These pipelines are now simply named after their associated project.

MCP server can now trigger pipelines    

The CircleCI MCP server can now trigger pipelines. This can be used to run pipelines that would usually be triggered from the UI via an AI assistant like Cursor or Claude Code.

Runner Release 3.1.4    

Runner Release 3.1.4

Both Machine and Container Runner:

Addressing CVEs for dependencies in the CircleCI Self Hosted Runner Project

Skipped Jobs Status Change    

A change to status checks was originally scheduled for April 28, 2025. The scope of the change has been revised based on user feedback.

MCP Server Updated w/ Pipeline Status and Prompt Iteration tools    

Three new tools are available in the CircleCI MCP Server:

Paused - Previously announced skipped status updates    

Changes to how CircleCI reports skipped statuses to VCS have been paused based on user feedback. A new date will be determined soon. Any breaking changes will be announced with at least 4 weeks notice. Learn more about the planned changes to skipped job statuses.

Effective April 30 - GitHub Checks won’t be updated for older workflows    

On April 1st, we completed migrating customers to new GitHub Checks services. This was part of a refactoring of the underlying services to improve reliability. For workflows started before April 1st, we will stop sending updates to GitHub Checks as of April 30, 2025. For workflows started April 1st and later, we will send updates to GitHub Checks for 90 days after the workflow started.

CircleCI VS Code Extension Update - compatibility with any VS Code Fork    

The CircleCI VS Code extension is now available on the “open-vsx” registry so that developers using VS Code forks like Windsurf, VSCodium, etc can use the extension: https://open-vsx.org/extension/CircleCI/circleci

MCP Server Updated w/ Config Validation and Flaky Test Detection    

Two new tools made available in the CircleCI MCP Server:

Changes to dropdown options in "Add trigger" and "Add pipeline" forms    

The “Trigger type” dropdown in the “Add trigger” form (Project Settings > Triggers) has been updated with the following changes:

Paused - Breaking Changes - April 28th 2025 - Skipped Status Will Now Return Success     

Update: Based on user feedback, this release has been postponed to better assess impact to VCS workflows. Detailed descriptions of changes and a new launch date will be announced soon. A new date for any breaking changes will be announced at least 4 weeks in advance.

CIRCLE_PULL_REQUEST env variable now populated for GitHub App pipelines     

The environment variable CIRCLE_PULL_REQUEST is now populated for all pipelines triggered from GitHub, regardless of integration type, whenever the triggering commit is associated with a pull request.

Auto-populate trigger pipeline modal parameters based on selected pipeline.     

Parameters in the trigger pipeline modal now automatically populate based on the pipeline selected in the dropdown menu at the top of the form.

CI Skip and Only build PRs will no longer create pipelines    

What is changing?

Display "Authorize" button on the navbar if user has not authorized GitHub App    

When using the GitHub App integration, each user needs to “authorize” the CircleCI GitHub App for their pipelines to be correctly attributed to them. Not doing so means:

Disable SSH Rerun by Project    

Project admins can now disable SSH rerun for individual projects via Project Settings>Advanced or the CircleCI v2 API.

UI changes to the pipelines page    

We have introduced some UI changes to the pipelines page:

Context restriction APIs marked GA    

The context restriction APIs have been promoted from experimental to generally available. Authorized users can now create, read, and delete project- and expression-based context restrictions via API. Security group context restrictions are not supported yet. Read the context API documentation.

New context timeout error messaging    

A new error message has been added to the contexts page to help users differentiate between page timeouts and permission errors. Previously, it was unclear to the user whether page load issues could be resolved with a refresh. Now, users who have the correct permissions will see “Please try again in a few minutes.” if contexts take a long time to load.

Manage GitHub App installation from the organization settings page "VCS Connections"    

The tab “VCS” in Organization Settings has been renamed into “VCS Connections”, and it now includes a section dedicated to the GitHub App integration.

Prevent non-admin users from installing the GitHub App    

The GitHub App pipeline and trigger forms have been updated to prevent non-admin users from attempting to install the CircleCI GitHub App.