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

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.

Mac M4 Pro resources are now available on CircleCI, bringing Apple’s most advanced silicon directly to your CI/CD pipelines. Experience cutting edge performance with optimized CPU and memory configurations designed to effectively tackle your most challenging tasks.

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

The CircleCI Terraform Provider enable customers to manage CircleCI projects with IaC patterns. For large-scale organizations, this enables automated project creation for new teams or projects. For existing projects and teams Terraform offers consistent settings and controls across all projects.

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

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.

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.

Updates

Bug Fixes

• CVE fixes
• Fixed a bug where the pipeline page for OSS repositories could be visible without being logged into CircleCI. Please reach out to your account team for more information.
• SSH rerun now works in air-gap and in installations with a self-signed certificate on GitHub Enterprise.

Image Updates

• frontend (underlying container is now circle-www-api)
• builds-service
• orbs-service
• workflows-conductor
• insights-service

Known Issues

• RabbitMQ needs features enabled prior to upgrading

The Xcode 16.4 GA image is now available to be used in CircleCI pipelines.

The full manifest of installed software can be found here.

From the “Project Overview” page, you can now set up a rollback pipeline that lets you quickly revert to a previous deployment version when invoked. Read more in our community forum, send any questions/comments to sebastian@circleci.com.

Platform Team Toolkit enables enterprise CI/CD optimization and governance that eliminates duplication, enforces security compliance, and accelerates delivery while empowering developers with the flexibility and speed they need.

Reminder

Maintenance window for Runner is scheduled for June 3rd, 2025, at 19:00 PST/22:00 EST. The maintenance window will last until 19:10 PST/22:10 EST.

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.

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

On June 25, 2025, the Insights pages in the CircleCI web app will be updated with the following changes:

Maintenance window for Runner is scheduled for June 3rd, 2025, at 19:00 PST/22:00 EST. The maintenance window will last until 19:10 PST/22:10 EST.

There was a bug that was causing Scheduled Pipelines to show up as Trigger Event = “Push: commit pushed” in the CircleCI web app. This has now been fixed.

CircleCI is making an upgrade to its local CLI which will require all local CLI users to upgrade to v0.1.31425 or higher if using the following two commands:

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

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

Broken - This Server version has been removed

Updates

Bug Fixes

• Fixed a bug where the pipeline page for OSS repositories could be visible without being logged into CircleCI. Please reach out to your account team for more information.

Image Updates

• frontend (underlying container is now circle-www-api)

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.

The Xcode 16.4 RC image is now available to be used in CircleCI pipelines.

The full manifest of installed software can be found here

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

The Xcode 16.3 image is now available to be used in CircleCI pipelines.

The full manifest of installed software can be found here

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.

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

Refer to the docs to get started.

For any feedback or question, you can reach out directly to benedetta@circleci.com.

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

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.

The project count on app.circleci.com/home was incorrectly including deleted projects. This has now been fixed.

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

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.

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).

Runner Release 3.0.27

Container Runner:

Upgrade dependencies to address CVEs in the 3.0 container runner agent.

Multi-factor authentication (MFA) is now available to all users who log in with email address and password. This added layer of security can be set up in the “Password & Authentication” tab within your user settings. Full instructions can be found in the documentation.

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

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.

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.

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.

Bug Fixes

• Various CVE remediations
• Fixed a bug where the job page for OSS repositories could be visible without being logged into CircleCI. Please reach out to your account team for more information.

Image Updates

• branch-service
• branch-service-migrator
• execution-gateway
• runner-admin
• runner-admin-migrator
• web-ui-onboarding

Broken - This Server version has been removed

Updates

• Added support for additional certificates for OIDC
• Added support for assume_role_arn to the Machine Provisioner configmap
• Server version now included in support bundles

Bug Fixes

• Fixed a bug causing the /workflow-run api route to give 404 errors
• Various CVE remediations
• Fixed a bug where the job page for OSS repositories could be visible without being logged into CircleCI. Please reach out to your account team for more information.

Image Updates

• execution-gateway
• machine-provisioner
• machine-provisioner-migrator
• web-ui-server-admin
• picard

Runner Release 3.1.4

Both Machine and Container Runner:

Addressing CVEs for dependencies in the CircleCI Self Hosted Runner Project

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

Three new tools are available in the CircleCI MCP Server:

We’ve released the ability for organization and project admins to self-serve delete projects in the CircleCI web app. For instructions on how to delete a project from CircleCI, see our documentation.

Project administration APIs are now available to cloud customers. Perfect for customers wanting to ease new project onboarding, maintain standards across projects, or manage projects with infrastructure as code (IaC practices). For more information see the official documentation.

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.

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.