Filter by status:
Server 4.8.0 Changelog
Server 4.8.0 Changelog
See the CircleCI server 4.8 release notes and upgrade guide for this release.
NOTE: Vault is being deprecated and will no longer be supported in server 5.0. Refer to our script for steps to migrate to Tink.
The v4.8 release introduces further security improvements and support for flexible job dependencies.
public-api-service
web-ui-user-settings
web-ui-org-settings
web-ui-insights
web-ui-project-settings
web-ui-runners
runAsNonRoot: true
circleci_server_version
in all the metrics it collects.frontend
container now uses the circleci-www-api
image instead of the previously named frontend
image.3.4.2
server-terraform
, the included Nomad images are now based on Ubuntu 22.04 with CgroupsV1 enabled. CgroupsV2 is currently unsupported. These nomad AMIs are built automatic security updates enabled.The following services will run migrations when upgrading to this version:
workflows-conductor
authentication-svc
builds-service
branch-service
contexts-service
cron-service
distributor
domain-service
insights-service
machine-provisioner
orb-service
permissions-service
runner-admin
Customers that are using “S3-compatible” object storage should ensure that their object storage supports S3’s default data integrity protections. This includes (but is not limited to) Minio RELEASE.2025-01-20T14-49-07Z and Nutanix Objects v5.1.1.
To learn more about Server 4.8 installation, migration, or operations please review our documentation.
See the CircleCI server 4.7 release notes and upgrade guide for this release.
See the CircleCI server 4.7 release notes and upgrade guide for this release.
NOTE: Vault is being deprecated and will no longer be supported in server 5.0. Refer to our script for steps to migrate to Tink.
The v4.7 release introduces security improvements with the implementation of rootless containers.
ReplicaSet
is now scaled to 5 pods by default, which improves execution stability at scale.PersistantVolumeClaim
(PVC) is now exposed through server Helm values. For more details, see the docs.frontend
pods would not automatically detect and apply a new server license.machine_provisioner.machine_agent_base_url
. The correct template value should be machine_provisioner.agent_base_url
.Deprecated components removed with this release:
web-ui-404
: Previously served the 404 error page. Its functionality has now been merged into the main web-ui
component.The following databases will run migrations when upgrading to this version:
authenticationservice
conductor_production
To learn more about Server 4.7 installation, migration, or operations please review our documentation.
This version will reach EOL in August 2025 and can be skipped when upgrading from 4.3 or 4.4. We recommend upgrading directly to 4.7 for the latest security patches.
This version will reach EOL in August 2025 and can be skipped when upgrading from 4.3 or 4.4. We recommend upgrading directly to 4.7 for the latest security patches.
See the CircleCI server 4.6 release notes and upgrade guide for this release.
NOTE: Vault is being deprecated and will no longer be supported in server 5.0. Refer to our script for steps to migrate to Tink.
The v4.6 release introduces various UI refreshments and improvements.
pipeline.in_setup
pipeline parameter has been removed.Kong
, which is used for server API management, has been upgraded from 2.x
to 3.x
.New services introduced with this release:
authentication-service
- provides an interface for user and identity management in the CircleCI systemThe following databases will run migrations when upgrading to this version:
builds_service
conductor_production
permissions
To learn more about Server 4.6 installation, migration, or operations please review our documentation.
CircleCI server v4.0.0 is now generally available. The feature set for this release are equal to server v3.x. The installation and upgrade processes for v4.x have changed significantly.
CircleCI server v4.0.0 is now generally available. The feature set for this release are equal to server v3.x. The installation and upgrade processes for v4.x have changed significantly.
Server v4.x offers greatly improved security handling, installation, and update processes. Server v4.x is installed using helm charts and images that can be pulled ahead of time to comply with your security processes. Installation processes can also use artifacts pulled from customer-managed registries. Server v4.x makes improved use of Kubernetes secrets and removes the requirement to grant permissions and network access to third-party tools.
See the CircleCI server 4.x release notes for upgrade notes for this release.
xlarge
and 2xlarge
. For more information on using Arm, see the Arm docs.distributer-internal
pod.kong
is now placed behind NGINX to simplify loadbalancer setup.circleci-traefik
to circleci-proxy
.init
job and the workflows-conductor-event-consumer
and the workflows-conductor-grpc-handler
pods will not start until the migration completes. Customers with large PostgreSQL databases should plan accordingly. Migration time can be reduced by scaling the workflow-conductor
pods.To learn more about Server 4.x installation, migration, or operations please see our documentation.
Server 3.0 is now generally available. The newest version of server offers the ability to scale under heavy workloads, all within your own Kubernetes cluster and private network, while still enjoying the full CircleCI cloud experience. Server 3.0 includes the latest CircleCI features, such as orbs, scheduled workflows, matrix jobs, and more. For existing customers interested in migrating from 2.19 to 3.x, contact your customer success manager. Server 3.0 will receive monthly patch releases and quarterly feature releases.
Server 3.0 is now generally available. The newest version of server offers the ability to scale under heavy workloads, all within your own Kubernetes cluster and private network, while still enjoying the full CircleCI cloud experience. Server 3.0 includes the latest CircleCI features, such as orbs, scheduled workflows, matrix jobs, and more. For existing customers interested in migrating from 2.19 to 3.x, contact your customer success manager. Server 3.0 will receive monthly patch releases and quarterly feature releases.
To learn more about Server 3.0 installation, migration, or operations please see our documentation.
CircleCI 2.0 is a completely updated CI/CD platform that starts every run with a clean image which is automatically provisioned just-in-time for Linux jobs on the CircleCI application installed in your private cloud. The CircleCI 2.0 platform includes significant performance, stability, and reliability improvements along with first-class Docker support, Workflows (pipelines), Resource Allocation, and Contexts. The Management Console (Replicated) also includes new options for enabling 2.0 Builders and appropriate default settings.
CircleCI 2.0 is a completely updated CI/CD platform that starts every run with a clean image which is automatically provisioned just-in-time for Linux jobs on the CircleCI application installed in your private cloud. The CircleCI 2.0 platform includes significant performance, stability, and reliability improvements along with first-class Docker support, Workflows (pipelines), Resource Allocation, and Contexts. The Management Console (Replicated) also includes new options for enabling 2.0 Builders and appropriate default settings.
If you have CircleCI installed you may access CircleCI 2.0 features on your current installation with no restrictions under your current agreement and support level. However, you must contact your CircleCI account representative for assistance with upgrading, to obtain migration scripts, and to receive a new license channel.
.circleci/config.yml
file in their repositories to add new 2.0 projects incrementally while continuing to build 1.0 projects which use a circle.yml
configuration file.Documentation for the installable 2.0 application is available at CircleCI 2.0 Documentation for the following topics:
Filter by status: