Changelog

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.

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.

When we detect that a configuration file is missing, an error message is shown with a shortcut for you to add it.

We fixed the 404 error that occurred when users were navigating to our Japanese login page.

We added back the ability for users to select ‘Public Repos Only’ when logging into an existing GitHub organization.

We observed an issue where the GitLab dropdown was mistakenly redirecting users when switching between the two dropdown options. This has now been resolved.

We have removed the outdated ‘temporary expanded access’ alert banner from the Audit log card on the Organization Settings > Security page.

The previous hyperlink for ‘Learn more about managing people in CircleCI’ on the Organization Settings > People page was navigating to the incorrect Docs link. We have now updated this to navigate to the correct Manage roles and Permissions page.

The repository dropdown is no longer editable when you attempt to edit a configuration source from the Project Settings UI.

When viewing SSH keys via Project Settings in the CircleCI UI, the “GitHub” icon is now shown if the URL uses “gh” instead of “github”. It previously showed a Bitbucket icon if the URL used “gh”.

Fixes

• Fix Windows machine executors on EC2
• Allow disabling statsd collection for build agent to decrease startup time
• Configure remote Docker engine with proxy settings if present

Fixes

Fix incorrect build-agent version

Projects that integrate with CircleCI’s GitHub App or GitLab can now delete “Configuration Sources” via the Project Settings UI.

On the self-hosted runner page in the CircleCI UI:

Fixes

• Fix Windows machine executors on EC2
• Allow disabling statsd collection for build agent to decrease startup time
• Fix bug in the postgres image which threw an error when Postgres triggered JIT compilation for a query

Following the bug fix to getAllInsightsBranches, we have updated our docs with a proper response schema and example, including the fields org_id and project_id.

In Organization Settings > Contexts, the dialogue box used to add a security group to a context was too small, not resizable, and displayed security groups in a random order. We updated the dialogue box to now sort security groups alphabetically, and for the size to be more responsive to the number of security groups available.

There was a bug that caused the UI to display a loading “spinner” indefinitely. This happened with no clear indication that the page would not be presented when you visited a job URL while unauthenticated or for a project you’re not authorized to view. We have fixed this by directing unauthenticated or unauthorized users instead to a 404 error.

The pipeline that creates an auto-generated configuration file now shows up as “Triggered by: circlebot” in the CircleCI UI. This change is only applicable to users of the CircleCI GitHub App integration.

Commit and off-site links on “Workflow Details” page open in a new tab.

The CircleCI UI no longer shows redundant instances of the phrases “All Pipelines” and “Dashboard”.

A link to the “legacy” jobs view that was empty for for projects that integrate with GitHub App or GitLab is no longer shown in the UI.

Orgs integrated with GitLab or the CircleCI GitHub App can be renamed in Organization Settings. Renaming organizations can only be done by users with the Organization Admin role.

The “Triggers” tab in Project Settings for orgs that integrate with CircleCI’s GitHub App now uses consistent language of “Trigger Name” everywhere instead of mismatching language between “Trigger Name” and “Trigger Source”.

Description:

Before: The getAllInsightsBranches API returned org-id and project-id as null.

The deprecated notify feature will be end-of-life on or after Feb 1, 2024. See our community forum for more details.

The “Tests tab” has been updated so that the success/failure state is indicated by an icon in addition to the color red or green. Previously, the only way to tell if tests failed or succeeded on the “Tests tab” in CircleCI UI was the color.

Fixes

• Security updates
• Removed the unused distributor_dispatcher.disable_concurrency value

Fixes

• Updated Go version to 1.21.5 in init-known-hosts to address CVEs
• Concurrency is disabled by default in distributor-dispatcher. Previously, disabling/enabling concurrency limits was a configurable option.
• Bump Go version to 1.20.12 in distributor to address CVEs

Changes

• The default 2500 job concurrency limit per organization is now configurable with the Helm value execution_gateway.plan_concurrency.
• The timeout for downloading machine provisioner agents is now configurable with the Helm values machine_provisioner.machine_agent_download_timeout_seconds and machine_provisioner.agent_download_timeout_seconds.

Fixes

• Bump Go version to 1.21.5 in Go-based services to address CVEs.