Previously: The pipeline.trigger_parameters.webhook.body pipeline value was only populated when a custom webhook triggered the pipeline. If a config used pipeline.trigger_parameters.webhook.body and the pipeline was triggered with a GitHub App event, an errored pipeline would occur. This made it difficult to use one configuration file with a custom webhook & GitHub App triggers.

Changes:

• Improved error logging
• Fixed issue with handling of restarts for Deployment objects

More details can be found here.

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

Fixes

• Fixed a broken helm template when an imagePullSecret is not set
• Fixed self signed certificates support

What’s New

• Added support for absolute paths in defining a GCP network under the machine provisioner configuration. This feature is particularly useful for VM jobs using shared networks, enabling explicit network selection. This corrects a regression from the previous VM service architecture.

NOTE: The above was incorrectly included in the 4.3.6 release but was not part of that release.

Fixes

• Fixed a broken helm template when an imagePullSecret is not set
• Fixed self signed certificates support

Three new fields will be introduced to the Usage API on August 23, 2024 to help you better understand how your builds are running. These fields are:

Job names greater than 10 characters were previously truncated on the workflows page. We’ve resolved this issue by increasing the box height to display the full job name.

For users integrating with Gitlab, clicking on the commit hash on the job page now correctly redirects to the Gitlab page showing detailed information on that specific commit, rather than a page listing a history of commits.

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

Changes:

• Improved updates of component status
• Security updates
• Minor bug fixes

The newest macOS orb version 2.5.2 resolves an intermittent issue where the wrong IP address was shown in the ssh command string after running a Rebuild with SSH job.

When creating a new Inbound Webhook trigger, CircleCI automatically creates a GitHub App configuration source to be used by the trigger. With this fix, the config source is automatically created when saving the trigger, rather than when entering the creation flow.

Users visiting the Releases UI for the first time can now explore our Product Tour, which highlights the various features and value of CircleCI Releases. It also includes a demo video to walk users through different use cases that can be solved using Releases.

Admins must now opt in their organization to use the experimental intelligent error summaries. Enable this experiment in the Advanced section of Organization Settings.

Organizations that integrate with GitHub App or GitLab will see minor updates to the CircleCI web app after the “Create Project” button is clicked. There is now a “project type” selection page.

Bug Fixes

• Fix for issue in runner UI were a resource class may show up as undefined
• Fixed broken insights UI and API due to missing table data
• Removed unnecessary ingress
• Fixed missing CORS for job cancel API endpoints. v1.1 and v2 job cancel endpoints will now work as expected
• Removed hardcoded notification email in frontend and workflows-conductor services

NOTE: Release 3.0.23 has been removed from our package repository. It contained bug breaking OIDC token injection for Cloud Runner users. Please use this release 3.0.24 instead.

The “Organization Homepage” in the CircleCI web app now shows all projects for organizations that use CircleCI’s GitHub App or GitLab integrations instead of only showing projects that have been followed.

There have been several updates to the CircleCI web app

For customers trying to find cost efficiencies in their runner environment we now support spot instances. The feature can also improve reliability when there are unexpected failures. It comes with some risks and we have documented risks and usage. This release also includes some enhancements and security fixes.

Users getting started with Releases now have a new guided onboarding flow in the UI to make it easier to install and configure the Release Agent. This new experience simplifies some of the steps and provides instant feedback on whether steps have been successfully completed. With this improved onboarding experience, users can start seeing their releases more quickly.

We have released changes to the CircleCI Web App including a new “User Homepage”, refreshed styling for our left-hand navigation bar, and a top navigation bar that provides shortcuts for user-level actions. To view these updates, log in or navigate directly to app.circleci.com.

For more details, visit our community forum.

GCP-CLI orb version 3.2.0 has been published. This version introduces support for Windows.

The “rerun job with SSH” button is now disabled if no SSH keys are detected. Previously, attempting to “rerun job with SSH” would result in a standard rerun if no SSH keys were detected.

Before upgrading

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

Projects integrated through GitHub App now support Auto-Cancel Redundant Workflows.

We are introducing parameter limits to improve responsiveness of the trigger pipeline API and limit potential abuse. The new limits will be as follows:

Note: If you are running CircleCI Server, you will need version 4.4.3 of server to take advantage of these runner features.

Changes:

• Add logs to capture previous rollout state
• Fix invalid steps bug
• Fix bug when executing commands when Argo Rollouts was missing

Changes:

• Added support for proprietary labels circleci.com/component-name and circleci.com/version that will replace app and version. Currently the old labels are still supported, but it is recommended to migrate to the new ones as soon as possible, since support for them will be dropped in an upcoming releases. NOTE When migrating to the new circleci.com/component-name and circleci.com/version labels, rolling back to a version with the old app and version labels is supported only if the deployment or rollout is managed by Helm.
• Fixed an issue with rollbacks failing when the deployment was managed by Argo Rollout and Helm was not being used.

Gitlab projects now support Auto-Cancel Redundant Workflows. Reducing spend and queuing for highly active projects. For more information on see our documentation.

We have removed the ability to generate in-app invites for GitHub OAuth and Bitbucket integrated organizations. Users trying to join existing CircleCI organizations with a GitHub OAuth or Bitbucket integration will no longer need an invitation from an existing team member.

For more information on the updated steps, see our documentation.

We have optimized config compilation, with up to 40% improvement in compilation times for very large configs.

Following the adoption of HTTPS checkout in place of SSH-based checkout for projects that connect to GitHub App, the project creation page and the trigger creation page have been updated so users are no longer required to enter a SSH key.

Projects integrated through GitHub App that have public repositories as trigger sources are now correctly recognized as Open Source in CircleCI. This has two implications:

• Job links are accessible to anyone, including users who are not logged in.
• Open Source projects on a free plan are no longer capped by the 30,000 free credit limit.

Projects setup using the GitHub App integration no longer show “Not Run” pipelines in the pipelines page on commits labeled with [skip ci] or [ci skip]. Instead, CI is skipped silently.

Three new environment variables have been added, making it easier to use common identifiers in jobs: CIRCLE_PROJECT_ID, CIRCLE_ORGANIZATION_ID, and CIRCLE_PIPELINE_ID. https://circleci.com/docs/variables/#built-in-environment-variables

Orgs that use CircleCI’s GitHub App integration now use a different mechanism for checking out code. Instead of using an SSH-based deploy key, a more secure method, HTTPS, is now used to clone source code from GitHub.

Customers using CircleCI with GitHub App and GitLab now have the option to debug builds using rerun with SSH. https://circleci.com/docs/ssh-access-jobs/

Changes:

• Added support for missing progressive canary step types. These include:
  • Experiment
  • Set canary scale
  • Set header route
  • Set mirror route
• Fixed a bug where a CANCEL RELEASE command canceled the wrong release

Deprecation Note:

• After April 1, 2024 all Release Agent versions prior to 1.0.0 will no longer be supported. Please update your agent before then to continue seeing your releases in the CircleCI UI.
• For update instructions, review the Release Agent documentation.

An “unauthorized” error message is shown when a user does not have access to contexts required to run the job.

Changes:

• The circleci.com/project-id annotation is now required in order for components and releases to be tracked and displayed in the UI
• Removed the ROLLBACK type releases in favor of the true underlying type (PROGRESSIVE or DEPLOYMENT) and have added a RERELEASE tag
• Improved clarification notes on RESTORE_VERSION command output
• Avoid retrying calls to the cloud in case of 400 and 401 status code responses

Deprecation Note:

• After April 1, 2024 all Release Agent versions prior to 1.0.0 will no longer be supported. Please update your agent before then to continue seeing your releases in the CircleCI UI.
• For update instructions, review the Release Agent documentation.

Runner Release

• Fix bug causing the kube-api server to sometimes prematurely terminate task pods for containerized jobs.
• Improve Task Lifecycle step with dynamic Kubernetes pod lifecycle status for containerized jobs. Providing more detailed information on each step in the lifeycle, making it easier to debug issues if they arise.

Experimental Contexts Restriction API change:

We have updated our current onboarding survey by reducing the number of questions and introducing dynamic capabilities that tailor the survey based on the user’s responses.

Users can now name their CircleCI organization when using CircleCI’s GitHub App or GitLab integration.

We have resolved a bug which prevented users from creating GitHub App triggers if they had previously deleted all of their triggers.

For projects that integrate with CircleCI’s GitHub App, you can now specify a custom configuration source when creating a GitHub App trigger.

This enables you to use modular configuration files within the same project (ie. a build-and-test.yml and a deploy.yml that have different definitions).

The CircleCI UI now uses the language “Needs Approval” instead of “On Hold” to denote that an approval job is pending approval.

Users can now track changes in their systems across their various development environments in our Releases UI, which is in open preview. With this update, users can see which environment a release is associated with, what version of a component is in different environments, and the latest version of every component within a single environment.