The Xcode 26.2.0 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

Server 4.9.0 Changelog

Before Upgrading

See the CircleCI server 4.9 release notes and upgrade guide for this release.

NOTE: Vault is being deprecated and will no longer be supported in server 5.0. Refer to our script for steps to migrate to Tink.

What’s New in Release 4.9.0

The v4.9 release introduces serial groups for job serialization, automatic retries for workflows and steps, and improved caching with Zstd compression.

NEW FEATURES

• Serial Groups: A native mechanism for serializing job execution across workflows. Jobs can now be configured to run sequentially using the serial-group key, preventing race conditions in deployments and other concurrent operations. For more information, see the docs.

• Automatic Workflow Reruns: Workflows can now be configured to automatically rerun on failure using the max_auto_reruns configuration key. For more information, see the changelog.

• Automatic Step Retries: Individual steps within jobs can now be configured to automatically retry on failure. For more information, see the changelog.

• Faster Checkout with Blobless Method: The checkout step now supports a method option that enables blobless checkout for faster repository cloning. For more information, see the changelog.

• Zstd Cache Compression: Cache compression now uses Zstd by default, providing faster compression and decompression with better compression ratios. For more information, see the changelog.

• Job-level Cache Retention Controls: Cache retention can now be configured at the job level, allowing more granular control over cache lifecycle. For more information, see the changelog.

• OIDC Token Reliability Improvements: Enhanced retry handling for OIDC token generation, improving reliability in environments with transient network issues. For more information, see the changelog.

• Configurable Max Run Time: Build jobs now support a configurable maximum run time through the builds_service.custom_max_run_time Helm value, allowing operators to override the default 5-hour limit.

• Dark Mode: Users can now enable “Dark mode” through the CircleCI web app, see the changelog.

CHANGES

• Some CircleCI job statuses that were previously marked as skipped were changed to failed, see the changelog.
• Reduced time to start jobs for very large and complex workflows, see the changelog.
• Personal Access Token (PAT) management has been migrated to the authentication-service. PATs are automatically migrated during the upgrade process.
• Context APIs are now served by the CIAM gateway for improved performance and scalability.
• Redis has been updated to the version 6.2.20 to address CVE-2025-49844.
• The feature-flags service has been removed as it is not required for Server installations.
• Deleting contexts double confirmation now asks for the name of the context, see the changelog.
• Branches now displayed in branch picker regardless of trigger settings, see the the changelog.
• Workflow start time & duration are now copyable from CircleCI web app, see the changelog.
• URL Addressable Orbs - Removes the barriers to reusable config by allowing any file in your VCS to become a CircleCI orb. Allowlist rules maintain security and compliance, see the documentation.

BUG FIXES

• Fixed incorrect trigger event display for scheduled workflows. For more information, see the changelog.
• Fixed an issue where pipelines showed errors when all workflows are filtered out. For more information, see the changelog.
• Fixed branch filter dropdown functionality. For more information, see the changelog.
• Fixed project count on “User homepage”, see the changelog.

NEW SERVICES

New services introduced with this release:

• lock-job-provider - Provides job serialization capabilities for serial groups feature (includes internalapi and consumer components)
• no-op-job-provider - Handles no-operation job types used by serial groups

SERVICE CHANGES

• feature-flags - The feature flags service has been removed as it is not utilized by execution services in Server.

DATABASE MIGRATIONS

The following databases will run migrations when upgrading to this version:

• authentication-service
• insights-service
• lock-job-provider
• no-op-job-provider
• oidc-tasks-service
• permissions-service
• runner-admin

KNOWN ISSUES

Using a custom signed certificate will result in an x509 error for Docker, Machinem, and Runner jobs. A fix will be provided shortly in the future.

To learn more about Server 4.9 installation, migration, or operations please review our documentation.

We’ve launched a new email notifications experience that gives you more control over your inbox. You can now opt into a “My Work” filter to receive email alerts only for builds you personally triggered.

Getting Started: Enable the “My Work” filter in your notification settings to reduce notification noise and stay focused on your own work.

Learn More:

• Read the documentation
• Share your feedback to help us improve this feature

You can now convert plain English descriptions into cron syntax when setting up GitHub App schedule triggers. Type a description like “every weekday at 9am” or “twice daily” and get the corresponding cron expression automatically generated. You can review and edit the generated syntax before saving.

Some examples:

The Xcode 26.2 Beta 2 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17C5038g/17A5241e/g' /tmp/MetalExport/MetalToolchain-17C5038g.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17C5038g.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

The Xcode 26.1.1 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• OS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

It is now possible to configure pipelines to be triggered by commenting run-ci on a GitHub pull request.

This gives teams more control over when pipelines run - for example allow re-running pipelines without pushing new commits, or triggering builds for draft PRs and work-in-progress branches.

This trigger option is available to all organizations using GitHub, as long as they have installed the CircleCI GitHub App integration. Access it by adding a new GitHub trigger to a GitHub App pipeline.

Support for custom comment keywords is on the roadmap.

For more information and a full list of GitHub trigger event options, visit the Docs page.

The Xcode 26.1 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• OS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

The Xcode 26.1 RC (Release Candidate) image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• OS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

The Xcode 26.1 Beta 3 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known issues:

• OS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

The Xcode 26.1 Beta 2 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• OS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

We’ve added a new banner that surfaces all your failed deployments across environments in one place so you can catch issues faster and get back to shipping.

Why we built this:

Failed deployments can be easy to miss, especially when managing multiple environments. You need a quick way to see what’s broken at a glance, without hunting through pipelines or workflows.

How it works: When you have failed deployments, you’ll see a banner at the top of your Deploys page with:

• A summary of all failures across your environments
• Namespace and version details when you hover over a specific deployment
• Direct links to the full error details by clicking the arrow on the right

This means less time tracking down what went wrong, and more time fixing it.

Starting November 3rd, CircleCI will begin to gradually roll out a faster checkout method (blobless) as the default checkout method.

Most builds will continue working without changes with blobless checkout. However, you need to take action if your builds require access to historical file contents. For example, tools like Sonar (SonarQube, SonarCloud), Sentry, some coverage or security scanning tools, and custom scripts that rely on git blame, git diff, or git config commands may require full checkout.

To opt into blobless checkout immediately, or to test compatibility, edit your CircleCI YML config to use the “blobless” method.

steps:
  - checkout:
      method: blobless

If your CircleCI job fails, or you prefer to keep the current checkout behavior, edit your config to use the “full” method.

steps:
  - checkout:
      method: full

If you do nothing and your builds break after November 3rd, you will be able to fix them by editing your config to use the “full” method.

Schedule triggers are now available for GitHub App pipelines. This feature allows teams to automatically run pipelines on a time-based schedule, with frequencies ranging from once every 5 minutes to less frequent intervals. Schedule triggers support configuring the actor associated with trigger pipelines, and passing custom parameters.

Getting started

Create GitHub App schedule triggers from the Project settings > Project setup page.

Availability

This functionality is available to all organizations that integrate with GitHub, regardless of whether they also use the GitHub OAuth integration (URLs may include /github/ or /circleci/). To learn more about using the GitHub App integration alongside GitHub OAuth, see the dedicated Docs page.

Notes

• GitHub App pipelines triggered via schedule trigger are never skipped nor auto-cancelled.
• Please note that, as specified in the documentation, a delay of up to 10 minutes may be applied to the configured time. Subsequent runs will maintain the same timing as the initial run.

Current limitations

Schedule triggers for GitHub App pipelines cannot yet be created or managed via API.

What’s next

GitHub App schedule triggers currently use a dropdown interface for frequency selection. We’re planning to transition to cron syntax for more flexible scheduling options. For questions or concerns about this plan, reach out to benedetta@circleci.com.

For more information about schedule triggers, see our documentation.

The Xcode 26.0.1 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

The Xcode 26.1 Beta 1 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.

For customers needing a more granular control, we now support automatic step rerun to complement our existing workflow rerun feature.

Rather than rerunning entire workflows, you can now automatically rerun specific failed steps. Simply specify max_auto_reruns in your run step configuration with a value between 1 and 5. You can also configure an optional auto_rerun_delay (up to 10 minutes) to give temporary issues time to resolve before retrying, such as when resources need time to become available again.

The UI provides clear indicators showing the current attempt number and remaining retries. This feature is available to all CircleCI customers across all plan types.

For more details on configuring automatic step reruns, visit the documentation.

The Xcode 26.0 GA image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

• Device IDs are inconsistently changing across VMs in Xcode 26. This is an OS-level issue that can affect builds relying on consistent device identifiers. We’ve opened a support ticket with Apple and encourage affected users to do the same to help prioritize a fix.
• See this community forum post for a workaround to a bug in the iOS 26 simulator device.

It is now possible to configure pipelines to be triggered whenever a pull request is merged or closed. Previously, only the option “PR merged” was available.

The primary use case for this trigger option is running cleanup / teardown pipelines to remove temporary resources that were provisioned when the PR was opened.

When this option is selected, pipelines will run by default on the base branch on the PR - as opposed to the head branch.

For more information and a full list of GitHub trigger event options, visit the dedicated Docs page.

The Xcode 26.0 Beta 7 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

What’s New: We’ve introduced a guided rollback wizard that walks you through setting up both deploy markers and rollback pipelines in a single, structured workflow.

Key Improvements:

• Step-by-step guidance through deploy marker configuration
• Automated rollback pipeline creation with proper parameters

Getting Started: The refined rollback wizard is available now in your Project Overview page. Look for the “rollback” dropdown and click “Create Rollback Pipeline” to get started!

https://circleci.com/docs/guides/deploy/set-up-rollbacks/

The Xcode 26.0 Beta 6 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

The Project settings > Project setup page now allows disabling GitHub App and Custom Webhook triggers. This is useful when iterating on trigger configuration, as it enables pausing pipeline triggering without deleting a trigger.

The same functionality is available programmatically through the Triggers API.

Test Quality Agent now in Beta

A new agentic capability is now available in private beta that automatically identifies and fixes flaky tests in your CircleCI projects. This agent helps reduce debugging time by analyzing inconsistent test behavior and creating pull requests with validated solutions.

Read the full announcement and setup guide on Discuss

How it Works:

• Identifies flaky tests with inconsistent pass/fail behavior
• Generates and validates multiple solution attempts per test
• Creates PRs only when solutions pass reliability validation
• Provides detailed logs and code diffs for review

Beta Details:

• No extra cost during beta (uses existing compute credits and AI provider tokens)
• Join the waitlist for access
• Feedback welcome at ai-feedback@circleci.com

The Xcode 26.0 Beta 5 image is now available to be used in CircleCI pipelines on the M4 Pro resource classes.

Please see the full manifest for information about the software included with this image release.

Known Issues:

• iOS 26 simulators sporadically freeze during boot and may fail to start. We recommend pre-booting simulators and, if they don’t start within 60 seconds, terminate them and restart them.
• Metal Toolchain is currently non-functional. A workaround is available by running the following commands before use:

    xcodebuild -downloadComponent metalToolchain -exportPath /tmp/MetalExport/
    sed -i '' -e 's/17A5295f/17A5241e/g' /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle/ExportMetadata.plist
    xcodebuild -importComponent metalToolchain -importPath /tmp/MetalExport/MetalToolchain-17A5295f.exportedBundle
  

We have added automatic workflow retry functionality to help you handle flaky resources and intermittent failures without manual intervention. You can now specify max-auto-reruns in your workflow configuration with a value between 1 and 5 to automatically rerun failed workflows. Just like the manual “re-run from failed” feature, only failed jobs will be retried - successfully finished jobs will not be rerun during automatic retries. This eliminates the need to manually monitor and restart workflows that fail due to environmental issues beyond your control.

The UI will provide clear indicators when a workflow is being automatically retried and show how many retry attempts have been made. This feature is available to all CircleCI customers across all plan types.

For teams dealing with flaky tests or unreliable external dependencies, this update significantly improves operational efficiency by reducing the manual overhead of workflow management. For more details on configuring automatic workflow reruns, visit the documentation.

Note: For those needing to auto-retry individual steps, automatic step retry is in the works!

You can create and delete CircleCI organizations programmatically through newly released Organization endpoints:

• Create organization
• Delete organization

Server 4.8.0 Changelog

Before Upgrading

See the CircleCI server 4.8 release notes and upgrade guide for this release.

NOTE: Vault is being deprecated and will no longer be supported in server 5.0. Refer to our script for steps to migrate to Tink.

What’s New in Release 4.8.0

The v4.8 release introduces further security improvements and support for flexible job dependencies.

NEW FEATURES

• Nomad UI is now accessible.
• Amazon Message Queue (AMQ) is now supported.
• Added support for configuring IOPS and throughput parameters for EC2 instances in the machine provisioner. New parameters can be found in the values.yaml reference.
• CircleCI Server now supports nomad servers externalized from your Kubernetes cluster. You may now deploy nomad servers on your own VM instances. This should improve the performance and stability of your nomad clusters.
• Support for Expression-based job filters
• Support for flexible job dependency.
• Support for Dynamic When Statements for Workflows (Breaking Change)
• Support for Windows container runner preview

NEW SERVICE:

• public-api-service

REMOVALS:

• web-ui-user-settings
• web-ui-org-settings
• web-ui-insights
• web-ui-project-settings
• web-ui-runners
• Support for launch-agent.
• Already-disabled v2 runner API endpoints.

CHANGES

• Moved from CircleCI fork back to upstream Hashicorp Nomad for improved stability and security updates.
• Nomad clients require IPv6 support within the kernel.
• JSON logging is enabled for Clojure services. This change allows customers to ingest logs from these services to their log aggregators in a familiar and consistent format.
• All containers now run with runAsNonRoot: true
• Telegraf will now include circleci_server_version in all the metrics it collects.
• The frontend container now uses the circleci-www-api image instead of the previously named frontend image.
• Clojure containers have moved to Java 21.
• Kong has been updated to 3.4.2
• Rerun workflow endpoint now has a rate limit of 20 requests per 5 seconds (max burst: 10)
• In server-terraform, the included Nomad images are now based on Ubuntu 22.04 with CgroupsV1 enabled. CgroupsV2 is currently unsupported. These nomad AMIs are built automatic security updates enabled.

PERFORMANCE IMPROVEMENTS:

• Database Operations: Optimized workflow storage to avoid N+1 database queries, reducing latency and improving concurrency.
• Workflow Status API: Now uses stored workflow status instead of generating it from job data, improving response times.
• Compiled Config Size: Removed unused job definitions from compiled configs, reducing size for customers with large configurations.

BUG FIXES

• Expression based restrictions via API have been fixed.
• Job handlers no longer silently drop on partial failure.
• Fixed broken branch picker functionality.
• SSH reruns in air-gapped installs have been restored.
• Broken pipelines now show triggering information in the UI.

DATABASE MIGRATIONS

The following services will run migrations when upgrading to this version:

• workflows-conductor
• authentication-svc
• builds-service
• branch-service
• contexts-service
• cron-service
• distributor
• domain-service
• insights-service
• machine-provisioner
• orb-service
• permissions-service
• runner-admin

NOTES

Customers that are using “S3-compatible” object storage should ensure that their object storage supports S3’s default data integrity protections. This includes (but is not limited to) Minio RELEASE.2025-01-20T14-49-07Z and Nutanix Objects v5.1.1.

KNOWN ISSUES

• Docker jobs may take an extra 60 seconds to conclude under certain circumstances.
• RDS is not compatible due to certain permissions checks; this will be fixed in 4.8.1.
• Vault may not refresh its client token after a month of uptime. Migrate to Tink to resolve this issue.
• Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for public installations, but for private installs you would need to ensure that you can access the private IP advertised. For example, by using a VPN into your VPC.
• Machine builds using instances with IMDSv1 enabled is not supported

To learn more about Server 4.8 installation, migration, or operations please review our documentation.

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.

Mac M4 Pro is available for customers on Performance and Scale plans in the following configurations:

Supported Xcode versions: 16.4.0, 16.3.0, 16.2.0, 16.1.0, 16.0.0, 15.4.0, 15.3.0, 15.2.0, 15.1.0, 14.3.1, 13.4.1

See the macOS documentation and CircleCI price list for details.

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.

There is a planned breaking change in the public-api-service that affects the Get Trigger operation. We are working to fix this on the next release. change will remove name and description from the API response for the getTrigger endpoint.

We will move the terraform provider to General Availability once we have addressed the planned API changes.

https://github.com/CircleCI-Public/terraform-provider-circleci

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.

It’s a combination of features that unlock efficiency and reduce operational toil for platform teams managing pipelines at scale, all while enhancing developer experience and velocity.

Key components of Platform Team Toolkit:

Terraform Module (coming soon) - Built on top of our Administration APIs. Provides a centralized tool to manage all projects on CircleCI. With infrastructure as code policies, you can set standards and maintain settings in one place.

URL Addressable Orbs - Removes the barriers to reusable config by allowing any file in your VCS to become a CircleCI orb. Allowlist rules maintain security and compliance.

Centralized Configuration, Templates, and Overrides - Gives the platform team the ability to manage pipelines from a central template while still providing dev team autonomy where it’s required.

To get the most from these features we recommend you review the 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.

APIs Available:

• Project
• Pipeline Definitions (Github App)
• Triggers (Github App)

Over the next few weeks we will be following up on the API release with an official Terraform module supported by CircleCI. You will also see more detailed tutorials on how to leverage the APIs and Terraform on the CircleCI blog.

We’ve recently rolled out the CircleCI Model Context Protocol (MCP) Server. This enables developers using tools (Claude Code, Cursor, Windsurf, etc.) that support the MCP protocol to interact with CircleCI.

Agents and AI tools can now fulfill developer requests, such as “Find the latest failed pipeline on my branch and get logs.” This eliminates the need to navigate through the UI or use complex CLI commands to debug and solve problems. This is the initial release, and we will continuously be updating what the server can do over the coming weeks. If you would like to contribute, please don’t hesitate to put in a pull request.

For more details and example use cases, check out our documentation and our blog post.

For questions or feedback, please open an issue on the GitHub repository.

We’ve introduced a new project overview page, which allows users to get a quick sense of the health of their pipelines and see what changes have recently been deployed for a project all in one place. Users can access this page by clicking the Overview link from the Organization Home page or Projects page.

If you have any feedback on how we can improve this overview, please use the survey popup in the bottom right corner of the page to let us know!

The queue orb was previously used to avoid multiple pipeline race conditions and conflicts. Serial-job provides native support for the functionality provided by the queue orb. Overtime we will expand the use cases we support to cover additional challenges like multi-job or workflows. The first release is serial-group for individual jobs.

This allows an individual job to be serialized across the organization, project or branch based on the parameters you provide. Serialization will ensure the jobs are executed in the order in which the pipelines are started via commit, api or other triggering method.

To learn more about your options see the documentation.

It is now possible to configure pipelines to be triggered only on pushes to non-draft Pull Requests.

Who Can Use This?

This functionality is available to all customers that use GitHub.

If your organization is currently integrated with GitHub only through OAuth, an admin must take the one-time action of installing the CircleCI GitHub App to enable this functionality.

Getting Started

1. Go to your project’s Project Settings > Pipelines, and ensure you have a “GitHub App” pipeline defined
2. Go to Project Settings > Triggers, and define a GitHub App trigger
3. In the “run on” menu, select “Pushes to open non-draft PRs”
4. Trigger your GitHub App pipeline by pushing to a non-draft PR

For more details on newly supported GitHub trigger events and example use cases, check out our documentation. For any questions or feedback, email benedetta@circleci.com.