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.

Organization joiners can now link their VCS during onboarding    

Edit configuration sources in Project Settings    

Users who integrate with CircleCI’s GitHub App can now edit their configuration sources in Project Settings –> Configuration.

Artifact uploads now happen in parallel    

When using the built-in store_artifacts step in a job, CircleCI now parallelizes the upload of individual files instead of uploading them sequentially to reduce the time that it takes for the entire upload operation to happen.

Runner 3.0.18    

Changes

  • Fixed a bug where the Task lifecycle and service container steps appear to run indefinitely, even after the task has already completed.

Server Release 4.4.0    

Before upgrading

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

Upgrade to Windows resource classes    

Windows resource classes have been upgraded to use faster and more recent hardware.

Changes to checkout command     

The built-in checkout command is being updated to use a different “clone” method to accelerate code checkout.

See our community forum for more details.

Project Settings UI uses SHA256 fingerprints instead of MD5    

The CircleCI Project Settings UI now displays the SHA256 fingerprints of SSH keys instead of MD5 fingerprints. Users can now specify a SHA256 fingerprint in addition to MD5 in their CircleCI config when adding additional SSH keys to their build.

Note: The CircleCI APIs for managing deploy, user, and additional SSH keys have been updated to accept SHA256 fingerprints. All changes are backwards-compatible.

Runner 3.0.17    

  • Log duration for downloads of a task-agent binary initiated by the runner agent are output to local downloads. This should help with troubleshooting issues when customers are experiencing problems downloading agents.
  • Fix bug where failed task Pods weren’t removed on task cleanup and had to wait for garbage collection, wasting customers’ cluster resources.
  • Additional security patches.

CircleCI wrapped: 2023 in review    

Our mission at CircleCI is to manage change so you can innovate faster. In 2023 we released 50 new features and feature enhancements to help you do just that. CircleCI shipped 3.8x more releases this year compared to the average of our competitors. By the numbers, that’s twice as many CI/CD enhancements as GitHub or GitLab and orders of magnitude more than AWS, Bitbucket, Travis, or Bitrise.

Delete GitHub App & inbound webhook triggers from UI    

You can now delete GitHub App & inbound webhook triggers from Project Settings –> Triggers.

Release Agent 0.1.207 Release    

This release provides critical security fixes for Go:

Job links from Slack orb fixed for GitHub App & GitLab projects    

Runner 3.0.16 Release    

Critical security fix

Enhanced custom aud claims for OIDC tokens    

Use the CircleCI CLI in a pipeline to quickly customize “aud” claims for jobs that require unique OIDC tokens.

Docker24 tag for Remote Docker    

Jobs that use setup_remote_docker can now specify docker24 to use the latest Docker24 image from CircleCI.

Status badges for GitLab & GitHub App Projects    

Status badges display in a README a project’s build status.

Server 4.1.6 and 4.2.2 Release    

Audit Log Includes Context Accessed    

Audit logs include context.secrets.accessed. Entry includes the actor and other details.

Linux CUDA image includes AI/ML-specific software    

CircleCI’s “Linux CUDA” image has been updated to include the Pytorch, Tensorflow, and HuggingFace transformers libraries out-of-the-box.

Container Runner Release 3.0.14    

  • Improved retries of select errors on startup of a container task
  • The task-agent binaries and pidfile are now installed at more conventional locations for both machine and container runner
  • GA release of machine runner 3.0

Accessibility toggle on Job Details page    

Customers can now use a screen reader to read the output of individual steps of a job. The toggle is off by default.

Server Release 4.3.0    

Before upgrading

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

Tag triggered builds now working in GitHub App projects    

We released a fix so builds triggered from tags work on GitHub App projects. See our documentation on how tag triggered builds can be implemented.

Bitbucket private orb permissions    

Bitbucket org admins now have the option to enable additional CircleCI permissions for Bitbucket workspace members, for example view private orbs.

Config Policies soft fails UI    

Soft fails for CircleCI config policies are now displayed on the pipelines dashboard.Config policy soft fails

“Rerun failed tests” time savings in Web App    

The CircleCI web app now shows how much time is saved on each job that uses the “rerun failed tests” feature.

“Rerun failed tests” badge in web app    

A badge in the CircleCI web app now indicates when a workflow used the “rerun failed tests” feature.

Invites are now required to join existing GitHub organizations on CircleCI    

New users who are joining existing GitHub organizations on CircleCI will now need an invitation from an org member that is already registered for CircleCI. Read more on our community forum.

Improvements to “Rerun” dropdown in the CircleCI web app     

If a job is not set up to use the “rerun failed tests” feature, the UI now reads: “Set up rerun failed tests” and links directly to the “rerun failed tests” documentation.

New UI for “steps” in CircleCI web app available to all users    

As of August 25, 2023 all projects now have an enhanced experience for viewing steps through the CircleCI UI. Benefits include:

Container runner version 3.0.13    

Container runner version 3.0.12    

  • Reduce claiming interval from 10 seconds to 5 seconds
  • Improve robustness when starting tasks on newly created nodes
  • Default to a non-root user in the container runner Docker image

GitLab project admins and contributors can now use contexts    

What’s New

For GitLab projects, access to view and run contexts is now extended to those with the following roles: Project Admin or Project Contributor. Refer to the docs for more about project roles, and contexts.

UI changes to show jobs that use `setup_remote_docker`    

What’s New

Jobs that are configured to use setup_remote_docker are now indicated on the job details UI, Plan Usage UI, and Insights as using the “Remote Docker” executor.

New CLI command: `env subst`    

What’s New

CircleCI’s CLI now includes an env subst command, which serves as a wrapper around the popular envsubst CLI tool. The command is used to substitute environment variables in a text string or file.

Override “Only build pull requests” setting    

What’s New

The CircleCI API can now be used to override the “Only build pull requests” project setting. This enables you to specify certain branches (using a regular expression) that can trigger validation on every commit, while keeping the “Only build pull requests” setting enabled on all other non-default branches.

For more details and usage examples, refer to the Discuss post.

DLC cache purge    

What’s New

We now offer a way for you to immediately delete a DLC cache’s contents. You can do so via the CircleCI web UI, or the CLI. Refer to this support article for details.

Release 4.1.0    

Before Upgrading

See the CircleCI server 4.1 release notes for upgrade notes for this release.

Essential Contacts for organizations    

What’s New

Admins now have the ability to provide CircleCI with technical and security contacts within the Organization Settings page in the web app. This will allow CircleCI to alert the right group of individuals at an organization when there is an issue or an incident.

Added the ability to sort Contexts by date in Organization Settings    

We have added the ability to sort by the ‘Created’ date column on the Contexts tab in Organization Settings. This will allow users to view contexts in ascending or descending order by date.

Project-restricted contexts for all customers    

What’s New

Project-level restrictions for contexts are now available to all customers. Previously this feature was only available for GitLab SaaS projects.

For details on managing restrictions for contexts on a project level, refer to our Contexts documentation.

New job status badge for “Infrastructure Failure”    

What’s New

The job status badges in the CircleCI UI now include a badge for “Infrastructure Failure”. This badge indicates that CircleCI has run into issues with the underlying infrastructure on which the job runs.

In-app express project setup for GitLab Cloud    

What’s New

You can now set up your GitLab project using the following options within CircleCI: use an existing .circleci/config.yml in a repository (fastest); commit a starter CI pipeline to a new branch (faster); or go to a config.yml template that you can edit (fast). These setup options will also trigger a pipeline, so you no longer need to manually commit a change from your GitLab repo in order to run your pipeline for the first time.

Automatic retries for certain types of infrastructure failures    

What’s New

In certain scenarios when the underlying hardware that CircleCI uses to run jobs fails, CircleCI will attempt to automatically retry the job.

Arm fleet upgrade    

What’s New

Arm resource classes now benefit from faster execution speed and improved networking performance. The underlying compute types for the CircleCI ARM fleet have been upgraded. These resource classes are up to 25% more performant.

Test splitting on Windows resource classes    

What’s New

A bug fix has been released that allows test splitting by timing to now work on Windows resource classes.

Increase in config compile size limit    

What’s New

CircleCI configurations previously had a compile size limit of 3 MB, which prevented pipelines from running when this limit was exceeded. We have now increased the config compile size limit to 4 MB.

Out-of-the-box support for non-POSIX shells (Node and Ruby)    

What’s New

We have added out-of-the-box shell support for Node and Ruby. Invoking Node and Ruby commands within CircleCI jobs can now be as simple as the following:

Billing changes for runner network egress    

What’s New

As of October 31, 2022, CircleCI no longer exempts data transfer when restoring a cache or workspace to a self-hosted runner installed in AWS us-east-1 from network billing.

For more information, visit the Discuss post.