As of June 28 24:00 UTC, the Intel-based macOS Gen2 macos.x86.medium.gen2 resource class is no longer available. Jobs that specify this resource will fail with an Invalid resource class error.
Organizations that integrate with GitHub App or GitLab will see minor updates to the CircleCI web app after the “Create Project” button is clicked. There is now a “project type” selection page.
m1 medium is now the default resource class for Performance and Scale Plan customers. This applies only to jobs that do not have a resource class specified.
m1 medium is now the default resource class for Performance and Scale Plan customers. This applies only to jobs that do not have a resource class specified.
Update jobs using gen2 medium by June 28 to avoid failing builds. Learn more.
m1 medium is now the default resource class for free plan customers. Jobs that previously used medium Gen2 will automatically be upgraded to m1 medium as of June 27. Learn more.
NOTE: Release 3.0.23 has been removed from our package repository. It contained bug breaking OIDC token injection for Cloud Runner users. Please use this release 3.0.24 instead.
NOTE: Release 3.0.23 has been removed from our package repository. It contained bug breaking OIDC token injection for Cloud Runner users. Please use this release 3.0.24 instead.
Container Runner
Added support for customizable service containers, allowing users more control over a service’s resource usage on a per-image basis. For additional details, refer to the docs.
Introduced configuration validation to avoid setting the garbage collection threshold below the max task runtime, preventing premature Pod removal and task interruptions.
Modified the task agent directory to avoid conflicts with existing directories in the PATH variable.
Both Machine and Container Runner:
Added injection of the CIRCLE_URL variable into task environments. This will resolve to https://runner.circleci.com on cloud, or to the host URL of your server installation on enterprise server.
The Plan card on the Organization Homepage in the CircleCI web app was not including credits charged for using CircleCI’s Releases functionality. This has been fixed.
When one organization shares a plan with another organization, the plan tier of the parent organization is shown on the User Homepage (/home) of the CircleCI web app. Previously, this showed Free.
On certain pages of the CircleCI web app, the organization ID was shown in the title of the page in the browser instead of the actual title of the page. This has been fixed.
The “project cards” on the “Organization Home” of the CircleCI web app now say “< 1 minute ago” instead of “less than one minute ago” to avoid wrapping onto the second line of the card.
Users will now see a message in the CircleCI web app requesting that they submit a form if they have been marked as suspended for suspected abuse in order to have the suspension removed.
Users will now see a message in the CircleCI web app requesting that they submit a form if they have been marked as suspended for suspected abuse in order to have the suspension removed.
Note that this currently only applies to organizations that integrate with CircleCI’s GitHub OAuth App and Bitbucket integrations.
If a user is not logged in to CircleCI but is attempting to view something in the CircleCI web app, the left-hand navigation’s text is now readable. It was previously using a font color that made it unreadable.
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 “Organization Homepage” in the CircleCI web app now shows all projects for organizations that use CircleCI’s GitHub App or GitLab integrations instead of only showing projects that have been followed.
There have been several updates to the CircleCI web app
The term “Dashboard” has been replaced by “Pipelines” in the left-hand navigation
There is a new “Organization Home” option that will show an overview of the organization that you have currently selected including the projects in that organization that you have followed
Upon clicking on an org from the “User Homepage”, you will be taken to the “Organization Home” instead of the “All Pipelines” page
When creating a new organization on CircleCI, there is no longer a question asking to connect a VCS
Ubuntu 24.04 LTS Linux images now available for preview. The candidate images for amd64 and arm64 have been published as edge releases. Read the Discuss post.
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.
For customers trying to find cost efficiencies in their runner environment we now support spot instances. The feature can also improve reliability when there are unexpected failures. It comes with some risks and we have documented risks and usage. This release also includes some enhancements and security fixes.
For customers trying to find cost efficiencies in their runner environment we now support spot instances. The feature can also improve reliability when there are unexpected failures. It comes with some risks and we have documented risks and usage. This release also includes some enhancements and security fixes.
Container Runner:
Support for unsafe retries, which enable container-agent to automatically rerun tasks that get interrupted during their execution. For example, unsafe retries can be used to run idempotent workloads on spot instances for cost-saving benefits without the worry of Pod preemption causing unexpected job failures. For important information and risk assessment on setting up and using unsafe retries, please read the docs: https://circleci.com/docs/container-runner/#unsafe-retries
Changed the format of the arbitrary suffix appended to the names of Kubernetes objects that are managed by container-agent. This change has no operational impact on runner.
Both Machine and Container Runner:
The CircleCI CLI is now prioritized over task agent on the $PATH. That is, invoking the circleci command within a task will point to the CLI binary, if present.
Patched with Go v1.21.10 for security fixes in Go: https://groups.google.com/g/golang-announce/c/wkkO4P9stm0
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.
Users getting started with Releases now have a new guided onboarding flow in the UI to make it easier to install and configure the Release Agent. This new experience simplifies some of the steps and provides instant feedback on whether steps have been successfully completed. With this improved onboarding experience, users can start seeing their releases more quickly.
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.
We have released changes to the CircleCI Web App including a new “User Homepage”, refreshed styling for our left-hand navigation bar, and a top navigation bar that provides shortcuts for user-level actions. To view these updates, log in or navigate directly to app.circleci.com.
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.
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.
Example
In 30 days commit history will change. We will only store and report back the last commit. This impacts the API response for jobs (all_commit_details) and the applications pipeline views.
Example
For feedback or questions please reach out to Nathan Fish (nathan.fish@circleci.com).
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.
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.
The “rerun job with SSH” button is now disabled if no SSH keys are detected. Previously, attempting to “rerun job with SSH” would result in a standard rerun if no SSH keys were detected.
