New release of the CircleCI VSCode extension. This completes the fix of an issue with release 2.8.0 where workspace settings get updated without any action by the user.

If a user is logged in to the CircleCI web application, they will now see the correct version of circleci.com which includes a “Go to Application” button in the top-right corner. Previously, they would see a version of circleci.com that had “Sign up” and “Login” buttons in the top-right corner.

Bug Fixes

• fix for hardcoded smtp email in some services
• CVE fixes for web-ui deployment
• fix for duplicate volume in domain-service deployment

The newest macOS orb version 2.5.0 resolves an execution error, “AppleEvent timed out”, previously returned when using the add-safari-permissions command with Xcode 15.x images.

Previously, the “Releases” tab would not show in the left-hand navigation of the CircleCI web app when a user had selected “Projects” if the user was viewing an organization that integrated with CircleCI’s GitHub App or GitLab. This has been resolved and the “Releases” tab always shows up now.

New release of the CircleCI VSCode extension. This fixes an issue with release 2.8.0 where workspace settings were updated without any action by the user.

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

Flutter orb version 2.0.4 resolves an error installing the flutter SDK caused by an incorrect environment variable reference.

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.

New release of the CircleCI VSCode extension. We are aware of an issue where workspace settings are being updated without any action by the user. We are in the process of resolving this issue.

Container Runner:

• Support the user key in the docker executor configuration. This allows you to execute task-agent with a different user than the image’s default. Due to limitations of the Kubernetes API, this feature has some caveats:
  • This key is only supported on the primary container. Service containers will continue to run as the default user.
  • Some user environment variables, such as $PATH, may be reset.
• Further reduction in the memory footprint of Container Runner. This includes a fix for a memory leak that could cause the container-agent Pod to use excess memory and unexpectedly crash under certain workloads.
• Fix for a bug that caused tokens for private AWS ECR images to be cached beyond their expiry, potentially causing image pull errors.

Both Machine and Container Runner:

• Optimize the download and storage caching of new task agent versions.

The official CircleCI Evals Orb makes it easy to integrate LLM evaluations into a CI pipeline, and to review evaluation results without context switching. The output of evaluations run through the Evals Orb is stored in CircleCI, and is accessible as a job artifact and as a PR comment added automatically by CircleCI.

Before upgrading

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

The copy in the email that a user receives when being invited to an organization that integrates with CircleCI’s GitHub App or GitLab has been updated for clarity.

The favicon for CircleCI’s web app should now always render a CircleCI icon.

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

Previously, when users tried to connect their VCS with a GitHub account that was already linked to a separate CircleCI account, they would encounter a status 500 error. This would manifest in the CircleCI UI as an inability to list repositories on the form to create a project and the screen appeared frozen. Users that run into this scenario will now no longer see a frozen screen and instead be redirected to a page where they see an error message telling them remediation steps.

When a newly onboarded user has no data for the “Insights” part of the CircleCI UI, we now do not show the Insights link in the dropdowns on the All Pipelines page

If a user stops the onboarding process at either the onboarding survey, the “Connect Code” page, or the “Create Project” page; when they return back to CircleCI they will resume at the step where they stopped instead of starting again from the first step in the flow.

We have removed support for Release Agent versions older than v1.0.0. Users who haven’t updated their agent will no longer see their components or releases in the UI until they upgrade to the latest version.

We will end support for all 1.x variants of runner launch agent on July 31st 2024. It has been replaced with Machine Runner 3.0. You can learn more about machine runner and migration here.

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

Open policy agent for config policies has been bumped from v0.54 to v0.63.

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

Change Log

• updated task agent version
• bug fixes for oidc-service

Changes:

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

Get access to all your CircleCI usage data via our Usage API.

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.

Orgs that integrate with CircleCI’s GitHub App or GitLab had a check to ensure that the name being submitted did not already exist. We have modified this from being an exact check to a check that ignores the case.

For example, if an org named ‘test org’ has already been created, another org named ‘Test Org’ will not be permitted.

If a job name contains a “/” character (ie. “foo/bar”), CircleCI will correctly set the VCS commit status for the full job name as opposed to only the part after the “/”. This update applies to new projects created on or after April 5, 2024. Projects created before April 5, 2024 are not impacted.

If your project was created before April 5, 2024 and your job name has a “/” in its name, email sebastian@circleci.com to have the new behavior enabled for your project.

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.

CHANGES:

CHANGES:

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.

The “Stop Building” button in Project Settings now turns gray after it is clicked to avoid confusion on whether any action occurred.

Our configuration translator automates the switch of your GitHub Actions and GitLab pipelines to CircleCI, without requiring a CircleCI user account.

The methodology that is used to calculate outliers in CircleCI’s Insights offering has been updated to be more accurate.

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.

When triggering pipelines in the CircleCI web app, the modal now accurately displays the project name in the header, replacing the previously incorrect project slug.

Users clicking on the branch hyperlink on a single pipeline page previously encountered a ‘Something unexpected happened’ error. This has been resolved, and the hyperlink now correctly redirects to a page displaying all pipelines for the specified branch.

Expression based context restrictions enable developers to restrict contexts based on pipeline values such as branch, ssh rerun and other attributes of the pipeline. This provides greater control over context access for things like contexts only available to production branches, builds run by specific actors and more. For security concerned and complex workflows customers are able to limit access to contexts to meet their specific security needs.

We’ve resolved the issue where the UI displayed duplicate workflows on the Dashboard page.

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