Changelog

The “Notification Center” in the top right corner of the CircleCI web app no longer lets a user click the “Dismiss All” option if there are no notifications to dismiss.

When a user clicked “Go back” from the flow to create a project with CircleCI’s GitHub App or GitLab integrations, the web app would not redirect the user back to the previous page that they were on. This has now been fixed.

The “Create Project” button in the CircleCI web app has been updated to look the same in every occurence of the button for consistency.

Change Log

• Suspended users will receive a more descriptive error upon failure to log in.
• Bug fixes for SMPT email value.

Change Log

• Suspended users will receive a more descriptive error upon failure to log in.
• Bug fixes for SMPT email value.

The “Cancel Workflow” option in the CircleCI web app had an issue where only part of it was clickable. This has now been fixed.

The “Ask AI” option in the CircleCI web app is now functioning as expected.

The “Filter” button in the CircleCI web app overlapped with the “Pipelines” drop box on the “All Pipelines” page. This has been fixed.

All users are now directed to app.circleci.com/home when navigating to the CircleCI web app.

The org picker on the left-hand nav of the CircleCI web app had an issue where it was not rendering properly when a user selected the “Everyone’s Pipelines” dropdown on the “All Pipelines” page. This has now been fixed.

CircleCI’s VSCode extension had an issue where it would inconsistently auto-complete certain Windows resource classes & images. This has been fixed. Users do not need to update their VSCode Extension for the fix to be reflected.

Long org names are now truncated properly with an ellipses when shown in the left-hand nav’s org picker in the CircleCI web app.

To simplify the CircleCI web app’s user interface, we have removed the badge in the left-hand navigation that said “Follow x new” which indicated to users that new projects in their organization were available for following.

New release of the CircleCI VSCode extension. This fixes an issue where SSH reruns initiated from the CircleCI VSCode extension would intermittently fail.

A new range of IPs has been added to CircleCI’s macOS Cloud. See the latest IP ranges for macOS.

In the past CircleCI has shown up to three commits for a specific pull request in the UI and returned in “all commit_details” for the jobs API. The commits in the UI linked back to the commit history in the VCS so users could review the commits from the source.

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.

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

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.

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.

Change Log

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

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.

CHANGES:

CHANGES:

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

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

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.

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

To maintain styling consistency across the platform, we have removed card shadows from our Settings pages, including Organization Settings, Project Settings, and User Settings.

We’ve removed the full page refresh behavior that was triggered when users were clicking between tabs in Organization Settings.

We have fixed the behavior of the toggles on the Advanced Settings tab in Organization Settings. If you’re not an organization admin, we now display a tooltip indicating that only organization admins can modify these settings.

Users of CircleCI’s GitHub App integration can now successfully use multiple configuration files within their project. See our community forum for more.

We have fixed a bug that previously prevented users of CircleCI’s GitHub App integration from creating a new trigger from Project Settings

We have increased the in-app tooltip text size and line height for accessible readability.

The color of the parallel runs indicator on the Jobs page is now accessible to match the rest of our in-app failed status elements.

Users were experiencing issues with the estimated runtime tooltip not displaying properly on the Dashboard tab. We have resolved this issue, so now when users hover over the ‘i’ icon under the Status column for a running pipeline, the tooltip will appear as intended.