Changelog

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

Note: If you are running CircleCI Server, you will need version 4.4.3 of server to take advantage of these runner features.

Keep reading

Change Log

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

Changes:

• Add logs to capture previous rollout state
• Fix invalid steps bug
• Fix bug when executing commands when Argo Rollouts was missing

Get access to all your CircleCI usage data via our Usage API.

Keep reading

Changes:

• Added support for proprietary labels circleci.com/component-name and circleci.com/version that will replace app and version. Currently the old labels are still supported, but it is recommended to migrate to the new ones as soon as possible, since support for them will be dropped in an upcoming releases. NOTE When migrating to the new circleci.com/component-name and circleci.com/version labels, rolling back to a version with the old app and version labels is supported only if the deployment or rollout is managed by Helm.
• Fixed an issue with rollbacks failing when the deployment was managed by Argo Rollout and Helm was not being used.

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.