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.

Increased 'Last Run' data refresh rate for Organization Home project cards    

Previously, the ‘Last Run’ value on project cards on the Organization Homepage would only update when the page was loaded. We’ve now set it to refresh every 60 seconds, providing users with the most up-to-date ‘Last run’ data for their projects.

Server Release 4.3.11    

Updates:

  • Improved handling of AWS errors by machine-provisioner

Bug fix on Bitbucket Data Center trigger creation form    

We fixed a bug that allowed users to select GitHub App pipelines as “pipeline to run” when creating a Bitbucket Data Center trigger. The “pipeline to run” dropdown now correctly includes only Bitbucket Data Center pipelines.

Improvement to triggers list    

The triggers table in the page Project Settings > Triggers previously listed triggers by “Trigger Name”, now they are listed by “Trigger source”. This column shows:

  • For VCS triggers, the name of the triggering repository
  • For Custom Webhooks, the user-defined “trigger source” that was defined on trigger creation

Add error message when "Authorize" fails in GitHub App pipeline and trigger creation    

When attempting to create a GitHub App pipeline or trigger, clicking on the “Authorize” button fails if the user’s GitHub account is already connected to a different CircleCI account. Until now, no error message was shown when this happened, making it difficult to troubleshoot the issue. We now surface an error message when this situation occurs.

While for now this message instructs users to “contact support”, in the future we plan to provide a self-serve solution to this problem.

CircleCI Go orb v2.0.0    

CircleCI Go orb version 2.0.0 introduces the with-cache command that lets customers store the Go build cache, golangci-lint cache, and Go module cache. Save-cache and load-cache have been renamed. https://github.com/CircleCI-Public/go-orb/pull/90

Update to Scheduled Pipelines and improvements within Project Settings    

Updates:

Fixed issue preventing the same GitHub App pipeline being triggered via multiple event sources    

The pipeline value pipeline.trigger_parameters.webhook.body is now present for all GitHub App and Bitbucket Data Center pipelines, no matter how they are triggered.

Bug fixed that was causing CircleCI UI to crash    

We have fixed an issue that was causing the Contexts page in the CircleCI web app to crash.

Xcode 16.2 beta 3 available    

The Xcode 16.2 beta 3 image is now available to be used in CircleCI pipelines.

Fixed the 404 error in the project creation flow    

When users clicked the ‘Go back’ button on the repo selection page during project creation, they were being redirected to a 404 error. This issue has been resolved so users are now correctly taken to the pipeline setup page.

Bug fixed that caused auto-cancellation of workflows on the default branch (GitHub App only)     

We fixed an issue which caused GitHub App pipelines running on the default branch to be incorrectly subject to auto-cancellation if triggered in close sequence. This issue did not affect organizations integrated through GitHub OAuth.

Additional improvements to the Trigger Pipeline experience in the CircleCI web app    

Updates:

Server releases moving to twice yearly    

CircleCI will be moving to twice-yearly major and minor version releases of Server. Releases will be targeted for Spring (April) and Fall (October). Patch releases for bugs and security updates will be made monthly as needed.

Bug fix in CircleCI web app - Self-hosted Runners    

The Self-hosted Runners section of the CircleCI web app showed the self-hosted runner’s hostname instead of the self-hosted runner’s name. This has been fixed to show the name.

Updated copy in Project Settings to reduce confusion    

In the CircleCI web app under Project Settings > Triggers > Add Trigger > GitHub App > “Select configuration to run” has been switched to “Select pipeline to run” for consistency.

Bug fixed when creating a Bitbucket Data Center pipeline within the project creation flow     

Removed the extra project name page for users going through the project creation flow for Bitbucket Data Center. Users integrating with Bitbucket Data Center will now be correctly redirected to the Project Settings > Pipelines page after creating their project.

Commit messages truncated in CircleCI UI    

In various pages of the CircleCI web app, the commit messages that are shown in the “Trigger Event” column are now truncated for pipelines that use GitHub App to improve the page design.

Fixed issue preventing auto-cancellation of redundant workflows for GitHub App pipelines    

Due to a bug, auto-cancellation of redundant workflows was disabled for all GitHub App pipelines from October 14th to November 18th. This issue has now been resolved. This bug did not affect organizations integrated through GitHub OAuth.

CMD + K fixed when redirecting to an organization    

A bug has been fixed which prevented navigating to an organization when using “cmd + k” in the CircleCI web app.

Update to CircleCI web app infrastructure - User Settings    

CircleCI is updating the underlying infrastructure for its CircleCI web app that powers the User Settings pages. No negative impact is expected, however, if you see anything that looks like unexpected behavior in the User Settings pages, email me at sebastian@circleci.com.

Dynamic When Statements for Workflows (Breaking Change)    

We are making some changes to when statements for workflows December 3rd. We will be adding conditional support to when statements so customers can do things like when: pipelines.git.tag == release. This conditional support allows for customers to run workflows based on pipeline parameters and values.

Pre-populate pipeline parameters when triggering a pipeline in the CircleCI web app    

For organizations that integrate with GitHub App, GitHub OAuth App, Bitbucket Cloud, and Bitbucket Data Center, we now pre-populate pipeline parameters when triggering pipelines in the CircleCI web app.

"Delete Docker Layer Cache Content" button fixed in Project Settings    

The “Delete Docker Layer Cache Content” button in Project Settings of the CircleCI web app was occasionally not working as expected. This has now been fixed.

Introduce ability to edit GitHub App triggers    

GitHub App triggers, previously uneditable, can now be edited.

Improved Trigger Pipeline experience in the CircleCI web app    

Updates:

UI fix for approval job boxes on the workflow page    

We have rolled out a fix to remove the extra whitespace for jobs that need approval on the workflow page.

Display "Project slug" on Project Settings page    

The page Project Settings > Overview now includes a new “Project Slug” section, which lets users view and copy in one click the slug of their project.

Changes to CircleCI web app infrastructure - tooltips    

A change has been made to the underlying infrastructure that powers the “Pipelines” page of the CircleCI web app, specifically the infrastructure that powers the tooltips on the page. Reach out to sebastian@circleci.com if you are experiencing any issues with the tooltips on the page.

Fixed the UI for approval job boxes on the workflow page    

We’ve removed the extra whitespace for jobs requiring approval on the workflow page.

Server Release 4.7.0    

Before Upgrading

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

Docker Executor Infrastructure Upgrade    

The host OS that Docker jobs run on has been upgraded to support new features and ongoing security and bug patches. This upgrade will roll out to all customers over the next few weeks. We do not expect any negative impact. Learn more about this change in Discuss: Docker Executor Infrastructure Upgrade.

Xcode 16.2 Beta 2 available    

The Xcode 16.2 beta 2 image is now available to be used in CircleCI pipelines.

IP Ranges Conditional Parameter Support    

IP Ranges now support parameters providing more dynamic control of when ip ranges is used in builds.

Bug fixed when triggering a pipeline in the CircleCI web app    

We resolved a bug that was preventing users from clicking the ‘Run Pipeline’ button on smaller screen sizes. All users can now access the button by scrolling within the modal.

Triggering GitHub App/Bitbucket Data Center pipelines now available in the CircleCI web app    

The ability to trigger pipelines in the CircleCI web app is now available for organizations that integrate through GitHub App and Bitbucket Data Center. Users can access this functionality by navigating to the Pipelines page and clicking the ‘Trigger Pipeline’ button, located on the top right of the page. This functionality is not yet available to organizations that integrate through GitLab.

Organizations that integrate with GitHub OAuth and Bitbucket Cloud will see a revamped experience to the existing modal.

Repository used to checkout code now included in step output of CircleCI web app    

As part of enabling users to more flexibly trigger work, the output of the “checkout step” in the CircleCI web app now shows the repository that is being checked out during the execution of the job. This is helpful for scenarios where the repository being checked out does not match the repository where the configuration file lives and/or the repository of the trigger event.

GitHub OAuth App "triggers" reflected in Triggers tab of Project Settings    

As a continuation of CircleCI’s update to enable access to “GitHub App functionality” to all CircleCI users (including users of the GitHub OAuth App integration), the “Triggers” tab in Project Settings of the CircleCI web app now shows a “GitHub OAuth App” trigger and a badge to indicate the integration type. This is intended to make it easier for all users to understand what is currently set up within their CircleCI project.

Bug fixed when creating Bitbucket Data Center trigger in Project Settings of CircleCI web app    

A bug has been fixed which prevented users from viewing all Bitbucket Data Center pipelines as options when creating a Bitbucket Data Center trigger. All pipelines are now available to be selected. 

Link from GitHub to CircleCI web app fixed when using GitHub App triggers in a GitHub OAuth App org    

Config source column no longer includes org name when displaying the repo in Project Settings of CircleCI web app    

In Project Settings > Pipelines of the CircleCI web app, the org name has been removed from the “Config Source” column to remove unnecessary information and improve the readability of the page.

Minor change to "Edit Pipeline" form in Project Settings    

The “checkout source” is no longer editable if a pipeline has associated triggers in the “Edit Pipeline” form in Project Settings of the CircleCI web app.

This was done to avoid getting into a state which would result in error pipelines being generated if the pipeline’s checkout source was edited to use a different repo.

Single Sign On for GitHub App, Gitlab, and Bitbucket Data Center    

Single sign on (SSO) is now available for Scale plan customers with CircleCI organizations connected to GitHub App, Gitlab, or Bitbucket Data Center. Learn how to connect your identity provider and enforce SSO for users in your org.

GitHub OAuth App & Bitbucket Cloud "pipelines" reflected in Pipelines tab of Project Settings    

As part of CircleCI’s update to enable access to “GitHub App functionality” to all CircleCI users (including users of the GitHub OAuth App integration), the “Pipelines” tab in Project Settings of the CircleCI web app now shows a “GitHub OAuth App” or “Bitbucket Cloud” pipeline and a badge to indicate the integration type. This is intended to make it easier for all users to understand what is currently set up within their CircleCI project. A subsequent update will do the same for the “Triggers” tab.

"Add" & "Edit" pipeline/trigger forms updated     

Minor changes have been made to the order in which items are presented in the “Add” and “Edit” forms for Pipelines & Triggers in Project Settings of the Circle web app to streamline the user experience.

New v2 API endpoint for triggering pipelines    

A new v2 API endpoint for triggering pipelines via API is now available to all organizations that integrate through GitHub (GitHub OAuth and GitHub App) and Bitbucket (Cloud and Data Center). This functionality is not yet available to organizations that integrate through GitLab.

Update to "Edit Pipeline" form in Project Settings of the CircleCI web app    

The “Edit Pipeline” form in Project Settings of the CircleCI web app did not have a field to show whether a user can properly use the rest of the form via a VCS connection. This led to confusing error messages when users were not properly connected.

This issue has been fixed by putting the “connection” field in the form.

Machine-readable IP Ranges for macOS    

A machine-readable list of IP ranges used by CircleCI’s macOS cloud is now available. Learn how to automate retrieval the latest IP ranges.

Unlocking any cross-repo pipeline and trigger setups, including central config management    

Historically, CircleCI users have been limited to setting up validation systems that only worked within the scope of a single repository.

Job Filters Now Support Pipeline Value Conditionals     

Job Filters now support expression based conditions, much like contexts. This enables you to conditionally run jobs based on pipeline values. This supports you optimizing pipelines to lower costs, decrease time to feedback, or run specific jobs based on context of the source of change. Previously filtering was extremely limited to branches and evaluating to only and ignore.