A bug that was causing the “Timing” tab in the CircleCI web app to show UUIDs instead of a string of the step name has been fixed.

A bug that caused a nearly full dark screen when creating a new project in organizations that integrate with CircleCI’s GitHub App has now been fixed.

Changes:

• Patched critical CVEs

See more details here.

• Added quick-start options to make it easier to understand what types of questions can be asked
• Loading screen adjusted to be smoother when a new pipeline is triggered
• Minor copy changes

CircleCI periodically updates the keys used to sign OIDC tokens in alignment with security best practices. No customer action is required to continue using OIDC with previously configured services.

Changes:

• Patched critical CVEs

See more details here.

Runner Release 3.1.2

Container Runner:

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. Affected customers have been notified via email. Learn more about this change in Discuss: Docker Executor Infrastructure Upgrade.

Updates

• Patched critical CVEs in web-ui-insights and webhook-service.

Bug fixes

• Fixed a vulnerability that allowed unauthenticated access to artifacts associated with public repositories.
• Resolved a bug that prevented a job from being rerun using SSH.

Updates

• Patched critical CVEs in web-ui-insights and webhook-service.

Bug fixes

• Fixed a vulnerability that allowed unauthenticated access to artifacts associated with public repositories.

Updates

• Updated the library dependencies for runner-admin
• CVE patches for web-ui-insights and webhook-service

Bug fixes

• Fixed a vulnerability where artifacts relating to public repositories could be accessed without authentication
• Fixed a bug where workflows in a terminal state with blocked jobs were incorrectly cancelled when a new workflow was triggered with redundant pipeline cancellation enabled.

Updates

• Patched critical CVEs in webhook-service.

Bug fixes

• Fixed a vulnerability that allowed unauthenticated access to artifacts associated with public repositories. Server Release 4.5.8

Bug fixes

• Fixed a vulnerability that allowed unauthenticated access to artifacts associated with public repositories.

Runner Release 3.1.1

Container Runner:

We fixed a bug where the organization name would flicker in the org picker when refreshing the Pipelines and Releases pages.

Bug fixes

• Resolved a bug where machine_provisioner.providers.gcp.network_tags were incorrectly assigned as labels on VM instances instead of as tags.

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 where OIDC tokens failed to be injected into a job, causing the environment variables $CIRCLE_OIDC_TOKEN and $CIRCLE_OIDC_TOKEN_V2 being missing.
• Resolved a bug where machine_provisioner.providers.gcp.network_tags were incorrectly assigned as labels on VM instances instead of as tags.
• 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 GovCloud, 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.

The role description was not rendering properly in the CircleCI web app when sending an invitation to a new user. This 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

• Resolved a bug where machine_provisioner.providers.gcp.network_tags were incorrectly assigned as labels on VM instances instead of as tags.
• 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 GovCloud, 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.

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.