Changelog

The IP ranges feature has historically had a known limitation where, occasionally, a job would be routed through an IP that was not a part of the fixed set of IPs published to users.

This limitation has now been resolved. Only IPs from the list of fixed IPs will be used when using the IP ranges feature in a job.

Customers can now install our release agent in their kubernetes cluster to get org-wide visibility into all components and releases via our Releases UI. Our agent also integrates with Argo Rollouts to give customers more visibility and control over their progressive releases and use analysis runs to fully automate their release process based on observability metrics. Check out our docs to learn more!

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

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

As of October 2, the macOS medium, large, and macos.x86.metal.gen1 resource classes are no longer available. Any jobs specifying these resources will fail with an Invalid resource class error. If your project config doesn’t specify a macOS resource class, jobs will be defaulted to macos.x86.medium.gen2.
You can read more about the available macOS resource classes in our documentation.

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

Upon encountering a failed step, users now can solicit guidance at the press of a button. This takes away the need to copy and paste the error message into your favorite search engine to find out what the problem might be and how to fix it.

Firebase CLI was added this month, and our build tools offerings were expanded to include 3 versions of build tools, otherwise just software updates this month.

Discuss post provides more details on the updated VM (docker) image.

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

GitHub authorization with CircleCI has changed for new organizations. When you authorize your CircleCI account with GitHub, you may find this will be done through our GitHub App, rather than the GitHub OAuth app. You can see which account type your organization has by heading to the CircleCI web app and inspecting the URL in your browser:

It is now possible to monitor Gitlab and Github App projects through the VS Code extension. At this stage, these projects are not detected automatically by VS Code, but they can be selected manually through the settings page.

ARM support for CircleCI’s Docker executor is now generally available. These resource classes have twice the RAM as x86 Docker resource classes.

To get started today, visit our community forum.

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.

The majority of CircleCI’s convenience images are now built for Arm in addition to x86. These images can be used with CircleCI’s Docker executor.

A full list of Arm supported images can be found on CircleCI’s community forum.

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.

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

Before Upgrading

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

• Improved the retry logic on task pod startup to prevent errors.
• Release of the Linux machine runner 3.0 preview. For more information see, Installing Machine Runner 3.0 on Linux.

• 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

Config Policies, powered by Open Policy Agent(OPA), are generally available for Scale plan customers. Config policies create peace of mind for platform and devops teams by enforcing granular pipeline controls related to orbs, resource classes, contexts, or anything else in config. Learn more about config policies.

Contexts are now easier to find and review. Quickly locate a context by searching its name or scrolling the alphabetized list.

Before Upgrading

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

What’s New

ARM support is now in preview for our native Docker executor. Take advantage of the simplicity and speed of CircleCI’s Docker executor to run containerized workloads on ARM hardware. For further details see the Discuss post on Arm support for the Docker executor.

What’s New

The “Rerun failed tests” feature is now generally available. Instead of executing all tests in the testing job from a failed workflow (including tests that passed), only failed tests are executed again. Rerun failed tests helps shorten time-to-feedback when a workflow has flaky tests.

What’s New

A new release for the Android machine image is available, as well as a new Android Docker image. This release consists of software updates. For more details, see the Discuss post for the July 2023 Android update.

What’s New

The quarterly update for Linux images is now available. Note that Ubuntu 20.04 and 22.04 are both available on amd64 and arm64 architecture under the edge tag, and are scheduled to be promoted to the GA release next week.

What’s New

Image updates are available for the June 2023 snapshot of Windows Server 2022, as well as the current tag. This includes Windows security and OS updates, and package updates for Windows Server 2022.

What’s New

CircleCI Personal and Project API access tokens have a new format. Previously, token values included a 40-character hex string. Newly created tokens will now include a CCIPAT or CCIPRJ prefix for personal access tokens or project access tokens, respectively:

What’s New

New project events have been added to the audit logs you can retrieve via the CircleCI UI. These events include:

• Project API token creation
• Project environment variable creation and deletion
• Project settings updated
• SSH key creation and deletion

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.

What’s New

We recently initiated a preview of a “Re-run failed tests only” option for workflows. This option is now available to any CircleCI user. To date, organizations that have adopted the feature are saving around 8 minutes per job, and are experiencing around a 60% reduction in runtime.

Learn more about re-run failed tests only in the docs.

What’s New

• CircleCI built in environment variables set as labels on task pods
• Task pod garbage collection improvements
• Improve task-agent task pod injection reliability
• Improve task-agent download reliability

What’s New

Starting this week, we are introducing updates to the UI for steps in CircleCI:

What’s New

We are rolling out new functionality that allows you to set up projects in CircleCI even more quickly. For new GitHub projects, if a .circleci/config.yml already exists in the repository, CircleCI will use that config to trigger pipelines. Otherwise, CircleCI will attempt to auto-generate a config with build and test jobs that are applicable to the programming language or framework present in the repository.

For more details, including languages and frameworks supported, check out our Discuss post.

What’s New

Jobs that use the Remote Docker executor have a new price structure as of today, June 15, 2023. See the Discuss forum for more details.

Before Upgrading

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

What’s New

The “created at” date is now available for newly created project environment variables. This allows you to more easily identify which env vars have been recently updated, and change out those that are getting stale. This helps you implement best practices on secrets rotation within CircleCI.

What’s New

The CircleCI VS Code extension now allows monitoring multiple CircleCI projects in a single VS Code workspace. All CircleCI projects present in a workspace are now automatically detected and displayed in the Pipelines Panel when the workspace is loaded, whether it is a single-folder workspace or a multi-root workspace. Additional projects can be added through the settings page.

What’s New

OIDC tokens now include a claim that indicates if the job was started using the SSH rerun feature. This claim can be used to write more granular access policies in systems like AWS. For more information see the docs.

What’s New

As part of our M1 offering, a medium resource class is now available to all customers on a paid plan. These performant resources offer GPU access, allowing for full end-to-end testing. Additionally, M1 provides a powerful platform for your AI/ML projects. To start building on M1, update your config to resource_class: macos.m1.medium.gen1. Check out the Discuss announcement for more details.

What’s New

A powerful new resource class, Linux VM 2xlarge+, is now available. A full list of available resource classes, including pricing information, is available here.

What’s New

You can now manage your config policies via the API. Previously, policies could only be managed via the CLI. This gives you options for how you create, validate, and retrieve decision logs for policies in CircleCI. For further information see the API reference docs.

What’s New

You can now specify the audience and time to live (ttl) for your OIDC tokens at the org or project level. This expands the number of partners that you can connect to. Custom claims are managed via the API.

Before Upgrading

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

What’s New

You can now use CircleCI’s OpenID Connect (OIDC) token to access your ECR images in your pipelines. For more information, see the docs.

What’s New

• Add circleci symlink to the circleci-agent binary within tasks
• Retry loading resource class token secrets on retryable errors
• Update various dependencies

What’s New

Customers on the Scale plan can now write config policies that govern SSH reruns. For example, you could create a policy to prevent access to specific contexts during SSH reruns. See the docs for further information.

What’s New

The monthly release for the Android machine (VM) and Docker images is now available. This release includes several software updates. For more details, refer to the Discuss post.

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.

What’s New

GitLab self-managed support is now generally available. If you host a GitLab self-managed VCS instance that is not behind a firewall, you can now run pipelines from your self-managed repositories.

For more information see the docs.