Changelog

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.

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