Before Upgrading

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.

What’s New in Release 4.6.0

The v4.6 release introduces various UI refreshments and improvements.

Several enhancements to the CircleCI web app, including:
- A new “User Homepage”.
- Updated styling for the left-hand navigation bar.
- Top navigation bar that allows easy access to user-level actions.
Pipelines are now labeled whenever they are rerun from start or fail, or with SSH.
Project-based context restrictions. For more information see the docs.

Old, expired workflows are now automatically canceled after 90 days.
The 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.

Fixed a bug that prevented jobs from being rerun with SSH.
Resolved an issue that prevented project loading on the Insights dashboard.
Addressed regressions from server 4.2:
- Introduced a configuration option at the organization level to set the default resource class for a Docker job. In server 4.3, this was previously hardcoded to large.
- Added support for absolute paths in defining a GCP network under the machine provisioner configuration. This feature is particularly useful for VM jobs using shared networks, enabling explicit network selection. This corrects a regression from the previous VM service architecture.

New services introduced with this release:

authentication-service - provides an interface for user and identity management in the CircleCI system

The following databases will run migrations when upgrading to this version:

SSH reruns in air-gap will time out, leaving the job in an error state
Vault may not refresh its client token after a month of uptime. Migrate to Tink to resolve this issue.
Retry with SSH for jobs using the machine executor advertises a private IP address. For this reason, retry with SSH for jobs using the machine executor works as standard for public installations, but for private installs you would need to ensure that you can access the private IP advertised. For example, by using a VPN into your VPC.
CircleCI 1.0 builds are not supported. If an attempt is made to run a 1.0 build, no feedback will be available in the application to indicate the cause of the issue. If a build is run on your installation and does not show up in the CircleCI application, use the CircleCI CLI to validate the project configuration and get details of the possible cause of the issue.

To learn more about Server 4.6 installation, migration, or operations please review our documentation.