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.

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

With the launch of our release agent 1.0.0, CircleCI releases is now generally available. Installing the release agent in your kubernetes cluster gives users org-wide visibility into all components and releases via the Releases UI.

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

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.

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.

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.

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.

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

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 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.

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

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.

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.

New users joining an organization that uses CircleCI’s GitLab or GitHub App integration can connect their Version Control Systems (VCS) to their CircleCI account during the sign-up process. By linking their VCS, users gain access to enhanced functionality within the app, including the ability to toggle the ‘My Pipelines’ filter.

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.

Users who integrate with CircleCI’s GitHub App can now edit their configuration sources in Project Settings –> Configuration.

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:

When using the built-in store_artifacts step in a job, CircleCI now parallelizes the upload of individual files instead of uploading them sequentially to reduce the time that it takes for the entire upload operation to happen.

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

Changes

• Fixed a bug where the Task lifecycle and service container steps appear to run indefinitely, even after the task has already completed.

Before upgrading

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

CircleCI’s Visual Studio Code extension now lets customers trigger pipelines from VS Code based on local, unversioned configuration files. Users can choose to run a full pipeline, or select only the individual jobs and workflows they want to run by using checkboxes. This will shorten the feedback cycle and enable developers to iterate fast on their configuration, without having to commit their trial and error changes to the VCS.