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

You can now view and work with these deployment-specific values directly within your development environment.

Newly supported pipeline values:

• pipeline.deploy.component_name
• pipeline.deploy.environment_name
• pipeline.deploy.target_version
• pipeline.deploy.current_version
• pipeline.deploy.namespace

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.

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.

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)

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

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.

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

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.

What’s new:

Users can now use this page to:

• View all pipelines integrated with GitHub (both OAuth app and GitHub App integration) and their trigger
• Add GitHub App and Custom Webhook triggers
• Edit existing GitHub App, GitHub OAuth and Custom Webhook triggers
• Delete Custom webhook triggers

Coming soon:

• Add and delete GitHub OAuth triggers. The “delete” functionality will ensure that OAuth pipelines stop building, without the need to manually remove the webhook from GitHub
• Add, edit and delete schedule triggers for OAuth pipelines
• Add, edit and delete pipelines
• Delete GitHub App triggers

For pipelines connected to Bitbucket or GitLab, please continue using the existing Pipelines and Triggers tabs.

This unified experience will eventually replace the separate Pipelines and Triggers tabs.

Questions or feedback? Reach out to benedetta@circleci.com.

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

What’s Changed Currently, we report skipped jobs as “pending”. We are now working to implement a change so that Status checks for skipped jobs will no longer be reported to GitHub when using the GitHub App integration.

Why This Matters

• Improved PR workflow: Prevents situations where required checks could be bypassed when jobs are skipped
• Consistent behavior: Aligns with our existing behavior in the CircleCI GitHub OAuth integrations
• Better security: Ensures all required checks must actually run and pass before PRs can be merged

Who This Affects This change only applies to users who have connected CircleCI to GitHub using the GitHub App integration. Users of our GitHub OAuth integration already experience this behavior.

What You Need to Do No action is required. This change will be applied automatically to all pipelines using the GitHub App integration when it is rolled out. We expect to complete the rollout by the end of June 2025.

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

Full updates coming soon to macOS documentation and CircleCI price list.

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.

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.

During this period:

• Resource management will not be available
• The Runner web UI for inventory and installation will not be available
• Up to a 5-minute delayed start time for runner jobs.

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

• The organization overview “landing page” will show a more concise summary view
• Historical resource utilization graphs (CPU/RAM) for individual jobs will be removed from the web app.

Historical resource utilization data via the CircleCI Usage API and resource utilization in the “Resources” tab of the Job Details page in the CircleCI web app will still be available. More details on our community forum Discuss.

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.

During this period:

• Resource management will not be available
• The Runner web UI for inventory and installation will not be available
• Up to a 5-minute delayed start time for runner jobs.

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 setup (circleci_setup)
• circleci diagnostic (circleci_diagnostic)

This upgrade must occur before May 31, 2025. After May 31, 2025, the two commands listed above will no longer work on versions of the CLI that are older than v0.1.31425.

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.

What’s Changed

Previously, when a new branch was created but didn’t trigger a build due to trigger settings (such as “Only build PRs” or commits with “[ci skip]”), the branch wouldn’t appear in the branch picker dropdown in the CircleCI UI. This made it difficult for users to manually trigger builds on these branches, as they would need to use the API instead.

Now, branches will appear in the branch picker regardless of whether they’ve triggered a pipeline, making it easier to manually trigger builds through the UI.

• No action is required to benefit from this change
• Branches will now appear in the branch picker dropdown even if they haven’t triggered a pipeline
• This applies to GitHub OAuth integrations

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.

Currently, the page supports view-only access to pipelines and triggers configured via GitHub (either via GitHub OAuth app or through the CircleCI GitHub App integration). To create, update, or delete pipelines and triggers — or to view pipelines connected to Bitbucket or GitLab — please continue using the existing Pipelines and Triggers pages.

This page is a work in progress, and we’d love your feedback as we continue to iterate. Reach out to benedetta@circleci.com with thoughts or questions.

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.

This change is reflected across:

• Project Settings > Pipelines
• Project Settings > Triggers
• Trigger Pipeline modal

The public API and the ‘Pipeline’ column in the Pipelines page already used the simplified naming convention.