Changelog

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.

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.

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.

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.

Keep reading

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.

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