Quay Enterprise is regularly released, containing new features, bug fixes, and software updates. We highly recommend deploying the latest version of Quay Enterprise.
Documentation is versioned along with each release. Each set is maintained on this site and can be accessed by using the dropdown on the main documentation page.
Fixed:
IMPORTANT NOTE: This release fixes a bug in which the deletion of namespaces did not result in the deletion of robot accounts under that namespace. While this is not a security issue (no permissions or credentials are leaked), it can appear unusual to users, so an upgrade is highly recommended. This change also includes a migration that cleans up the aforementioned robot accounts, so the migration step can take several minutes. Please plan accordingly.
Added:
Fixed:
IMPORTANT NOTE: This release fixes the 2.9.0 migration. If you experienced an error during the 2.9.0 migration, manually rollback and then upgrade your quay instance to 2.9.1.
Fixed:
Added:
Fixed:
Added:
Fixed:
NOTE: This release removes support for the OIDC token internal authentication mechanism and replaces it with support for a new app-specific token system. All customers using the old OIDC token auth mechanism must change their configuration after updating manually in config.yaml.
Added:
Fixed:
Added:
Fixed:
Added:
Fixed:
Added:
Fixed:
Added:
quay.expires-after label (#2718)Fixed:
Added:
Fixed:
Added:
Fixed:
Added:
Fixed:
IMPORTANT NOTE: This release fixes the 2.3.0 migration. If you experienced an error during the 2.3.0 migration, manually rollback and then upgrade your quay instance to 2.3.1.
Fixed:
IMPORTANT NOTE: This release has known issues, related to database migrations, and will not work for many customers. If you are using his release, please upgrade your Quay cluster to 2.3.4 or later.
Added:
Fixed:
IMPORTANT NOTE: This release contains a migration which adds a new feature to the build system. This requires shutting down the entire cluster including builders and running one instance to migrate the database forward. You must use a v2.2.0 builder with a v2.2.0 Quay cluster.
Added:
Fixed:
POSTGRESQL USERS: This release adds full-text searching capabilities to Quay Enterprise. In order to support this feature, the upgrade migration will attempt to create the pg_trgm extension in the database. This operation requires superuser access to run, and requires the PostgreSQL Additional Modules to be installed. See https://coreos.com/quay-enterprise/docs/latest/postgres-additional-modules.html to learn how to install the extensions.
Added:
Fixed:
Added:
Fixed:
Added:
Fixed:
Regressed:
Added:
Fixed:
Added:
docker login commands (#2146)Fixed:
Regressed:
Added:
Fixed:
Regressed:
This release is a required release and must be run before attempting an upgrade to v2.0.0+.
In order to upgrade to this version, your cluster must contain a valid license, which can be found and downloaded at: tectonic.com
Added:
Fixed:
Regressed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
Fixed:
Changed:
Fixed:
Changed:
Fixed:
This release tracks changes in the Docker v2 image format and adds official support for library repositories.
Changed:
Fixed:
This release repairs a bug in torrent hash calculations.
Fixed:
This release is primarily to address a bug in a migration found in v.1.14.0 related to migrating v1 data to the new format for v2 in the database.
Changes:
Bug Fixes:
This new release introduces Docker Registry v2 support and makes Quay Enterprise fully backward and forward compatible with both v1 and v2. Push and pull your images securely with any version of Docker Engine (≥0.10) and enjoy the performance boost that registry v2 delivers.
Changes:
Bug fixes:
Bug Fixes:
Quay Enterprise v1.13.x contains long-running migrations and should be updated during a maintenance window where administrators will have several hours of time to dedicate to the database migrating. Quay Enterprise will not be available while these migrations run.