Link your Slack identity to CircleCI and get notified on builds you triggered in your Slack DMs — no more tab-hopping to check your build’s status. You can set different status filters for Slack vs. email directly from your user settings page To enable it: Make sure your organization has the CircleCI Slack app installed (Org > Slack Integration). Link your Slack identity and set your notification…
Machine Runner: Machine runner now passes CircleCI’s built-in environment variables through to command_prefix wrapper scripts, so a wrapper can read job details such as the build number and branch. Container Runner: Fixed garbage collection so that when one agent replica dies, the surviving replicas clean up the task pods it left behind. Previously those orphaned pods could linger and keep reservi…
You can now manage code signing for iOS and macOS builds through the CircleCI API. Upload your Apple signing certificate (.p12) and provisioning profiles, create a signing bundle, then reference it by name in your macos executor using the new code_signing key and the install_signing_bundle step. CircleCI installs the certificate and profiles into a temporary keychain on the runner at build time an…
Updates The source config size limit for orb imports has been removed for Server deployments. Pipelines that previously failed because their combined orb configuration exceeded the 6–8 MB threshold will now process successfully without any configuration changes. Insights-service database migration validation errors that occurred during upgrades have been fixed, allowing upgrades to complete cleanl…
Link your CircleCI identity to your Slack identity, and CircleCI will @-mention you directly in Slack notifications for workflows you triggered — so you can immediately spot which commit or PR is yours. To use this feature, you must be using the CircleCI Slack integration. It is not supported for notifications configured through the legacy Slack orb. To get started, link your identity from your Ci…
The Xcode 27.0 Beta 4 image is now available to be used in CircleCI pipelines. The full manifest of installed software can be found here.
This release lets a single provisioner deployment run many resource classes and ships a ready-to-use VM image so you can stand up a pool without building your own. New: Multiple resource classes per deployment. One deployment now scales many resource classes at once, instead of needing a separate deployment per class. Default containerDisk image out of the box. Pool VMs boot from a maintained Ubun…
Gen3 Linux VM / (x86) Remote Docker is now available in Open Beta, delivering up to 67% faster for your project workloads. Gen3 Linux VM / (x86) Remote Docker is available for all users in the following configurations: Size CPU RAM Cost (credits/min) medium.gen3 2 CPU 8 GiB 7 large.gen3 4 CPU 16 GiB 14 xlarge.gen3 8 CPU 32 GiB 28 2xlarge.gen3 16 CPU 64 GiB 56 2xlarge+.gen3 32 CPU 128 GiB 112 See t…
Understand how your team is using CircleCI with the new Project Usage dashboard. Get a per-project view of pipeline activity and usage over time, so you can see what’s running, how often, and where your capacity is going. To access it: open any project and click Usage in the navigation. A few things to keep in mind during preview: Available on CircleCI Cloud only Credit summary data is available s…
You can now get notified by Slack or email when a workflow is paused on an approval job. Each notification includes a link that takes you straight to the approval job in CircleCI, where you can approve or cancel it. This works for: Slack — via project-level Slack notifications Email — via your existing notification preferences These notifications are opt-in. To start receiving them, see the setup…
UPDATE: Effective September 21, 2026, support for all pipeline values starting with pipeline.trigger_parameters.circleci.* and pipeline.trigger_parameters.github_app.* will be discontinued. These values will no longer be guaranteed to be present in pipelines after this date. The previously communicated date for end of life was August 1, 2026. These values are superseded by the pipeline.trigger.*,…
What changed We overhauled how CircleCI handles workflow cancellation to eliminate two long-standing issues: jobs that flip from canceled to success, and jobs that keep showing a spinner after they’ve actually finished. Background Previously, when a workflow was canceled, CircleCI would eagerly mark all jobs as canceled — before those jobs had actually stopped running. This caused two visible prob…
A new version of the CircleCI CLI is in Beta. The new CLI has several enhancements including a built in MCP server, the ability to trigger and watch pipeline runs, and access build output for jobs. The new CLI is also optimized for agents like Claude Code and Codex to use. Visit https://cli.circleci.com for installation instructions and full release notes.
We’ve launched a new Pipelines page in the CircleCI web app, bringing faster page loads and additional filter controls to help you find and manage your pipelines more easily. Existing users will be switched to the new design automatically. If you’d like to switch back to the previous version, toggle off “Updated view” in the top right of the Pipelines page. For questions or feedback, share your th…
The Xcode 27.0 Beta 2 image is now available to be used in CircleCI pipelines. The full manifest of installed software can be found here.
The Xcode 26.6 RC 2 image is now available to be used in CircleCI pipelines. The full manifest of installed software can be found here.
The Xcode 27.0 Beta 1 image is now available to be used in CircleCI pipelines. The full manifest of installed software can be found here.
Machine Runner: Fixed a bug where a runner with a cached task-agent binary could fail every job with an “unsupported platform” error until the process was restarted. The fix ensures newer task-agent versions are still fetched on demand when available. Container Runner: You can now override the container entrypoint per resource class in your runner configuration. See the documentation for details.
We now have a consistent way to validate if your config is impacted by any of the upcoming breaking changes before they take effect on August 17, 2026. CLI: Run circleci config validate --next Config editor: Enable the “config next” toggle in your config editor For more info on how to utilize the config editor or the new CLI flag, see the Discuss post.
The Xcode 26.6 RC 1 image is now available to be used in CircleCI pipelines. The full manifest of installed software can be found here.
Note: This replaces three earlier changelogs that covered these changes separately. The breaking change date for all three is now July 17, 2026. Refer to this post going forward.. On August 17, 2026, CircleCI is shipping three changes to how configs are compiled. Pipelines affected by any of these changes will fail to compile after this date. Here are the 3 upcoming breaking changes: Undeclared pa…
New: The provisioner now supports high-availability deployments: with multiple replicas, one is elected leader and standbys take over automatically on failover. Uninstalling the Helm release now scales the VM pool down to zero before deletion, so runner VMs are cleaned up automatically. Runner logs are now forwarded to each VM’s serial console, making runner output visible through the virtualizati…
IMPORTANT: This changelog has been superseded. This breaking change has been consolidated with two others into a single entry, and the date is now July 17, 2026. Please refer to the updated changelog for up-to-date details. The information below is retained for reference only. On July 8th, 2026, CircleCI is updating how undeclared parameters are handled. Previously, referencing a parameter that is…
The Chunk Tasks view now has two tabs: Tasks and Scheduled Runs so you can easily distinguish manually triggered runs from automated ones.
Chunk now has a dedicated Automations page where you can create, view, and manage your automated tasks in one place. The page includes a task creation form, an automations list, and the ability to edit or force-run automations from a contextual menu. Use the Automations page to set up recurring tasks like fixing flaky tests on a schedule, keeping dependencies up to date, or running custom prompts…
We’ve fixed an issue where clicking Fix error (Beta) on a failed job step showed a “Branch not found” error instead of prompting you to install the GitHub App when it wasn’t set up yet.
When creating or editing an automated task, you can now add a custom MCP server instruction directly from the task form. MCP servers give Chunk additional context and information to act upon, making automated tasks more powerful and precise. To create an automated task, navigate to Chunk → Automations (top right corner), then select New automated task.
We’ve resolved an issue where Chunk would report a Task as successful but produce no diff and open no PR.
We’ve fixed confusing empty states in the Chunk task output view when running a Chunk Task: The Logs tab now shows “Chunk is working on your task and will provide execution logs when finished.” instead of “Unable to load logs” while a run is in progress. The Diff tab now shows “Chunk is working on your task and will provide diffs when finished.” instead of “Unable to load branch diff” while a run…
When Chunk encounters a transient or infrastructure failure, it can now trigger a pipeline rerun directly instead of stopping. If your prompt indicates rerun approval for example, “fix my workflow, rerun if needed” Chunk will rerun automatically. Otherwise, Chunk will ask before proceeding. Previously, Chunk had no path forward on infrastructure failures and required you to rerun manually.