The formatting was not working as expected when viewing “Config Policies” in the CircleCI web app. This has been fixed.

An issue that was causing the “Edit Config” button in the CircleCI web app to lead to a “config not found” error has been fixed.

Updates

• The provider manager’s connection pool size is now configurable under domain_service.providersMangerMaxPoolSize. The default is set to 10.

Bug Fixes

• Network tags in GCP now function as expected.
• Fixed a bug that prevented remote Docker from working in air-gapped environments. An external reaper container repository has been exposed for this and can be configured via docker_provisioner.reaperContainerRepository.
• Improved handling of AWS errors by machine-provisioner

Bug Fixes

• Network tags in GCP now function as expected.

Updates

• The provider manager’s connection pool size is now configurable under domain_service.providersMangerMaxPoolSize. The default is set to 10.

Bug Fixes

• Fixed a bug that prevented remote Docker from working in air-gapped environments. An external reaper container repository has been exposed for this and can be configured via docker_provisioner.reaperContainerRepository.
• Fixed an issue with IRSA roles on AWS Gov Cloud, which uses the S3 partition aws-us-gov instead of the default aws. This is now exposed in the values file under s3.partition.

New Known Issues

• Setting a custom reaper container repository (via docker_provisioner.reaperContainerRepository) is currently incompatible with Windows VMs and prevents Windows jobs from running.

In the Manage tab of the Plan page in the CircleCI web app, the copy has been updated for clarity.

We fixed a bug that caused pipelines not to be triggered on force push events that reset the branch or tag to an older commit in the commit history.
This bug only affected GitHub App pipelines.

CircleCI is making an upgrade to its local CLI which will require all local CLI users to upgrade major versions. There are no expected breaking changes to the CLI’s functionality, however, a version upgrade will be required as the existing versions will no longer be supported.

Exact timing is to be determined, follow this community forum post for more details.

Runner Release 3.0.26

Both Machine and Container Runner:

• Patched several high and critical vulnerabilities in indirect Go dependencies.

When a user accepts an invitation to a CircleCI organization that has an org slug that follows the pattern circleci/<UID>, we now send an automated email to the user who sent the invite letting them know that the invitation has been accepted.

You can view your org slug in Organization settings > Overview.

Updates:

• Ability to specify the AWS partition with .object_storage.s3.partition.
• Ability to specify the reaper image (pause:3.6) with .docker_provisioner.reaperContainerRepository.

The component that renders log output on the Job Details page of the CircleCI web app has been updated. If you are seeing issues with the log output when using Firefox, please ensure that you do have disabled any browser extensions that alter page content.

Additionally, the “accessible step output” toggle has moved from the Job Details page to User Settings > Accessibility.

Updates:

• Improved handling of AWS errors by machine-provisioner

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.

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

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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. 

A bug has been fixed which was causing a 404 error when clicking on the CircleCI status in GitHub when using GitHub App triggers in an org that integrates with the GitHub OAuth App. The link now properly takes you to the 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.

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.

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.

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.

Users could only view the first 20 scheduled pipelines within Project Settings in the Triggers tab.

This bug has now been fixed.

Updates:

• frontend pod will now redeploy when the circleci license has been changed
• the timeout for windows and linux machine instances can now be configured using machine_provisioner.terminatePendingWindowsAfter and machine_provisioner.terminatePendingLinuxAfter respectively in your values.yaml
• fixed table ownership issue which prevented insights data from loading

Updates:

• frontend pod will now redeploy when the circleci license has been changed
• the timeout for windows and linux machine instances can now be configured using machine_provisioner.terminatePendingWindowsAfter and machine_provisioner.terminatePendingLinuxAfter respectively in your values.yaml
• nomad server pod replica count will now default to 5

Image Updates:

• builds-service
• ciam-gateway
• authentication-svc
• orb-service
• workflows-conductor
• machine-provisioner
• api-service
• domain-service
• permissions-service

Updates:

• Frontend pod will redeploy when license updates are made
• The timeout for windows and linux machine instances can now be configured using machine_provisioner.terminatePendingWindowsAfter and machine_provisioner.terminatePendingLinuxAfter respectively in your values.yaml

The list of IP ranges for CircleCI’s macOS cloud has been updated.

The “review your setup” step of project onboarding had stopped displaying the repository name under “code”. This issue has now been fixed.

Fixed an issue that prevented saving edits to GitHub App pipelines (Project Settings > Pipelines).

There was an edge case where the “Branch” field in the Releases UI in the CircleCI web app was not getting populated correctly. This has now been fixed.

On the “All Pipelines” page of the CircleCI web app, the “Trigger Event” column now has slightly different formatting for pipelines that are triggered via CircleCI’s GitHub App integration.

The list of IP ranges for CircleCI’s macOS cloud has been updated with new additions.

When using custom webhooks in an org that integrates with CircleCI’s GitHub OAuth App integration, the “Trigger Event” column in the CircleCI web app is now correctly populated.

The font is no longer unexpectedly bold on certain pages of the CircleCI web app when using Safari

Runner Release 3.0.25

Both Machine and Container Runner:

Previously, when processing a configuration file, CircleCI would process all workflows defined in the workflow. Upon completion of processing, errors such as missing or undefined parameters would be included in feedback.

As previously reported https://circleci.com/changelog/launch-agent-1-x-variants-eol/.

We were incorrectly displaying the project creation date as the ‘Last Run’ date for projects that have 0 pipelines on the Organization Home project cards. This has now been fixed.