Changelog

Keep up to date with our latest
releases and enhancements.

Sep 12, 2024

Sep 12, 2024

Xcode 16 RC available    

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

Aug 08, 2024

Aug 08, 2024

Xcode 16 Beta 5 available    

The Xcode 16 Beta 5 image is now available to be used in CircleCI pipelines.

Jul 24, 2024

Jul 24, 2024

Xcode 16 Beta 4 available    

The Xcode 16 Beta 4 image is now available to be used in CircleCI pipelines.

Dec 06, 2023

Dec 06, 2023

Docker24 tag for Remote Docker    

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

Nov 17, 2023

Nov 17, 2023

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.

Mar 21, 2023

Mar 21, 2023

Release 4.1.0    

Before Upgrading

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

Apr 11, 2022

Apr 11, 2022

Enhancement to the IP ranges feature    

What’s New

With this update, Docker image pulls now go through the set of well-defined IPs, with no additional changes needed from your end.

This update enables you to use your private Docker registries with the IP ranges feature and only open up traffic to those registries to IPs associated with CircleCI.

Mar 30, 2022

Mar 30, 2022

Release 3.4.0    

Before Upgrading

See the What’s new in server 3.x doc for upgrade notes for this release.

Jul 06, 2020

Jul 06, 2020

Changes to Definition of Queued and Waiting in the New UI    

What’s New

  • Waiting indicates the time spent preparing a job to run due to Docker image choice and CircleCI infrastructure time.
  • Queued indicates when you hit a concurrency plan limit, and your job isn’t running because other jobs in your organization are running first.

These two definitions were previously vice versa in the UI, which caused confusion due to discrepancies between usage in the UI and what most customers understood the terms to mean. We hope this change will avoid any confusion in future.

Feb 13, 2020

Feb 13, 2020

Release 2.19.00    

What’s New in Release 2.19.00

Requirements

  • Before upgrading to Server v2.19 your Nomad launch configuration must be updated by following this guide. Server v2.19 uses Nomad version 0.9.3, so if you have externalized Nomad, contact your support engineer before upgrading.

New Features

Nov 19, 2019

Nov 19, 2019

Pipeline Values Now Available in your Configuration    

What’s New

New pipeline metadata values can be referenced in your 2.1 configuration. Unlike CIRCLE_ environment values, these pipeline values are available at config processing time, so you could choose to use them in your configuration superstructure outside of jobs. For example, you could use pipeline values as strings for your working_directory or your image key under a job. Read more in our Pipeline Variables guide.

Sep 13, 2019

Sep 13, 2019

Streamlined macOS Image Delivery    

What’s New

We know how painful it is to have delays in Xcode image availability. We’ve been working to reduce the often 2-3 week delay as we validate security, availability, and performance in our release process. We are now down to under 3 days on the last four releases and expect this trend to continue.

May 13, 2019

May 13, 2019

Release 2.17.00    

What’s New in Release 2.17

Known Issues

There have been reports of our backpressure settings being too aggressive due to lack of nomad garbage collecting, as well as issues with the Vm Service overwhelming AWS API Limits. If you are on 2.17, you should upgrade to 2.17.1.

Dec 17, 2018

Dec 17, 2018

Release 2.16.00    

Fill out this form to receive updates about CircleCI through email.

Sep 26, 2017

Sep 26, 2017

Release 2.1.0    

  • Added support for 2.0 builders to use object storage other than S3 (mirroring the options from the 1.x releases).
  • Support for private images in docker jobs, including support for ECR authentication.
  • New VM service and build agent to address certain situations that resulted in build infrastructure failures.
  • Better accommodations for using proxies throughout the core infrastructure.