You're viewing **Apigee Edge** documentation. [Go to the **Apigee X** documentation](http://cloud.google.com/apigee/docs). info This topic describes the release process for Apigee products. > [!CAUTION] > **This page applies to 4.53.01 and earlier.** For Apigee Edge for Private Cloud > version 4.54.00 and later, see the > [Edge for Private Cloud > release and lifecycle policy](https://docs.apigee.com/release/private-cloud-release-lifecycle-policy). ## Introduction Apigee Edge follows a continuous release model for the Public Cloud, Private Cloud, and Edge Microgateway products to ensure our users can access product innovations and enhancements quickly, at the highest level of quality possible. All releases are expected to be free of interruption to the products, unless it is a planned downtime which will be done with at least five business days notification. As Apigee products provide a mission-critical infrastructure that enables access to enterprise services by developers, customers, employees and partners, new releases often require our customers to perform advance planning with internal and external stakeholders. We believe a clearly communicated release cadence will assist in this planning. ## Getting release notifications Apigee publishes release notes for each deployment on Google Cloud documentation. Each page carries an RSS feed you can subscribe to. - [Apigee Edge for Private Cloud release notes](https://docs.cloud.google.com/apigee/docs/edge-private-cloud/release-notes) - [Apigee Edge for Public Cloud release notes](https://docs.cloud.google.com/apigee/docs/edge-public-cloud/release-notes) For release notes published before September 2026, and for Apigee on GDC air-gapped and Drupal 7, see [Apigee Edge release notes](https://docs.apigee.com/release/notes/apigee-release-notes). ## Release 4.54.00 and later Apigee Edge for Private Cloud 4.54.00 was released in October 2026. Beginning with 4.54.00, releases follow a 36-month lifecycle. For the support timeline and the policy governing 4.54.00 and later releases, see the [Edge for Private Cloud release and lifecycle policy](https://docs.apigee.com/release/private-cloud-release-lifecycle-policy). For 4.54.00 release notes and patch announcements, see the [Apigee Edge for Private Cloud release notes](https://docs.cloud.google.com/apigee/docs/edge-private-cloud/release-notes). ## Apigee Edge for Private Cloud release process ### Versioning numbering scheme Releases 4.50.00 through 4.53.01 use the following version numbering scheme: `4.5N.XX.YY-ZZ`, where: | Number part | Description | |---|---| | `5N` | Starting with 50, this number will increment by 1 for each *major* release. | | `XX` | Starting with 00, this number will increment by 1 for each *minor* release. | | `YY` | Starting with 00, this number will increment by 1 for each *patch* release. | | `ZZ` | Starting with 00, this number is reserved for *hotfixes* only. | For example, after release 4.50.00, the next patch release is 4.50.00.01. Releases 4.54.00 and later drop the `ZZ` hot fix part. For that scheme, see [Version numbers](https://docs.apigee.com/release/private-cloud-release-lifecycle-policy#version-numbers) in the Edge for Private Cloud release and lifecycle policy. ### Types of releases and their cadences Apigee Edge for Private Cloud has the following types of releases: | Release type | Description | Cadence | |---|---|---| | Major versions | May include significant changes to the architecture, rewrites of components, and upgrades to software components. Upgrade paths from the currently supported versions will be provided. | As needed. | | Minor versions | May include cumulative bug fixes, configuration changes, installer changes, documentation changes, enhancements, features, and security vulnerability mitigation. | Once per year. | | Patches | Priority issues that are resolved for customers. | As needed, up to four times per year, if there are priority issues to be resolved for customers. | | Hot fixes | Targeted critical bug fixes and security vulnerability mitigation. | As soon as possible, depending on the severity of the issue. | ### Installer downloads For Apigee Edge for Private Cloud, use the credentials you received from Apigee to: - Download all product installers as a set of RPM files. See - Documentation is available on this site ([docs.apigee.com](https://docs.apigee.com)) under "Edge for Private Cloud" ## Apigee Edge for Private Cloud support timeline for 4.53.01 and earlier This support timeline applies to releases through **version 4.53.01** . Beginning with **4.54.00 LTS** , releases follow a 36-month lifecycle. For support dates and policy for version 4.54.00 and later, see the [Edge for Private Cloud release and lifecycle policy](https://docs.apigee.com/release/private-cloud-release-lifecycle-policy). The following sections describe the Apigee Edge for Private Cloud support timeline. For supported versions of third-party software, see [Edge for Private Cloud supported versions](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions). ### How support works and the end-of-life process for 4.53.01 and earlier Each major and minor software version of Apigee Edge for Private Cloud receives full support for approximately 18 months from its initial release date. During this window, Apigee provides all security patches, bug fixes, and hotfixes. At the end-of-life date, a version line enters the end-of-life phase. After this date, Apigee stops providing new bug fixes, security updates, hotfixes, or patches for that specific version line. While the software continues to run, Apigee no longer actively maintains it. > [!IMPORTANT] > **Key point:** An end-of-life date applies only to the version line it names. Other listed versions stay within their own support windows, and Apigee continues to release new versions of Apigee Edge for Private Cloud. > [!NOTE] > **Note:** Unless otherwise explicitly stated, the default support timeline for a major or minor version of Apigee Edge for Private Cloud is 18 months. A patch version (for example, 4.53.00.04) does not extend the support timeline for the major or minor version (for example, 4.53.00.x). ### Contract versus software version lifecycle Your commercial contract (typically a 2- or 3-year agreement) remains active and valid regardless of the support lifecycle of the specific Apigee Edge for Private Cloud software version you are running. The end of life of a specific software version does not terminate your contract. Instead, your contract grants you the ongoing right to use the software and access support services across supported product releases; it is not tied to a single software version. ### Maintaining full support and upgrade planning for 4.53.01 and earlier To receive continuous support---including critical security updates, hotfixes, and bug fixes---you must run your environment on an Apigee Edge for Private Cloud version that is within its 18-month full support window. Maintaining a supported and secure environment is a shared responsibility between you and Apigee, as detailed in the [Edge for Private Cloud shared responsibility model](https://docs.apigee.com/api-platform/troubleshoot/shared-responsibility). Apigee releases new versions regularly, typically at least one minor version per year, along with periodic patch releases. When an end-of-life date approaches for your current version, plan an upgrade to a more recent release. Upgrading your environment starts a fresh 18-month full support window from that release's initial release date. By planning for regular upgrades---generally once a year---you maintain continuous full support for the entire duration of your multi-year agreement. This ensures uninterrupted access to the latest security updates, bug fixes, and features. To stay informed and plan your upgrades smoothly: - Subscribe to [release notifications](https://docs.apigee.com/release/get-release-notifications). - Check the [Apigee Edge release notes](https://docs.apigee.com/release/notes/apigee-release-notes). - Review upgrade paths in the [upgrade compatibility matrix](https://docs.apigee.com/release/apigee-edge-release-process#upgrade-compatibility-matrix-for-edge-for-private-cloud-releases). **Example: Extending support through annual upgrades** Whenever a new release of Apigee Edge for Private Cloud becomes available (such as version 4.54.00), an end-of-life date is announced for earlier supported versions. Upgrading your environment to the newer release prior to this date ensures continued full support. Performing these regular annual upgrades allows you to maintain continuous support throughout a multi-year contract. ### End-of-life dates for 4.53 The following table lists the end-of-life dates for version 4.53, based on the latest version or patch you upgraded to. > [!NOTE] > **Note:** The end-of-life dates are as follows: for version 4.53, 04/11/2026; for version 4.53.01, 06/30/2027. | Version | Release | End-of-life | |---|---|---| | 4.53.01.02 | 06/17/2026 | 06/30/2027 | | 4.53.01.01 | 03/27/2026 | 06/30/2027 | | **4.53.01 (initial release)** | **08/26/2025** | **06/30/2027** | | 4.53.00.06 | 12/11/2025 | 04/11/2026 | | 4.53.00.05 | 07/21/2025 | 04/11/2026 | | 4.53.00.04 | 05/05/2025 | 04/11/2026 | | 4.53.00.03 | 04/21/2025 | 04/11/2026 | | 4.53.00.02 | 12/19/2024 | 04/11/2026 | | 4.53.00.01 | 11/21/2024 | 04/11/2026 | | **4.53.00 (initial release)** | **10/11/2024** | **04/11/2026** | ### Previously supported versions #### Table: End-of-life dates in detail > [!NOTE] > **Note:** The end-of-life date for version 4.52.00 is 08/31/2024; for version 4.52.01, 09/30/2025; and for version 4.52.02, 12/31/2025. | Version | Release | End-of-life | |---|---|---| | 4.52.02.03 | 04/28/2025 | 12/31/2025 | | 4.52.02.02 | 04/14/2025 | 12/31/2025 | | 4.52.02.01 | 12/06/2024 | 12/31/2025 | | **4.52.02 (initial release)** | **06/27/2024** | **12/31/2025** | | 4.52.01.02 | 07/25/2024 | 09/30/2025 | | 4.52.01.01 | 05/23/2024 | 09/30/2025 | | **4.52.01 (initial release)** | **03/28/2024** | **09/30/2025** | | 4.52.00.04 | 02/13/2024 | 02/13/2025 | | 4.52.00.03 | 10/25/2023 | 10/25/2024 | | 4.52.00.02 | 07/25/2023 | 08/31/2024 | | 4.52.00.01 | 04/19/2023 | 08/31/2024 | | **4.52.00 (initial release)** | **02/14/2023** | **08/31/2024** | | 4.51.00.12 | 03/20/2023 | 03/20/2024 | | 4.51.00.11 | 10/26/2022 | 10/26/2023 | | 4.51.00.10 | 09/28/2022 | 09/28/2023 | | 4.51.00.09 | 08/25/2022 | 08/25/2023 | | 4.51.00.08 | 06/27/2022 | 06/27/2023 | | 4.51.00.07 | 05/26/2022 | 05/26/2023 | | 4.51.00.06 | 04/28/2022 | 04/28/2023 | | 4.51.00.05 | 03/28/2022 | 03/28/2023 | | 4.51.00.04 | 02/16/2022 | 02/16/2023 | | 4.51.00.03 | 01/13/2022 | 01/31/2023 | | 4.51.00.02 | 11/03/2021 | 01/31/2023 | | 4.51.00.01 | 09/28/2021 | 01/31/2023 | | **4.51.00 (initial release)** | **07/29/2021** | **01/31/2023** | | 4.50.00.14 | 02/22/2022 | 02/22/2023 | | 4.50.00.13 | 01/13/2022 | 01/13/2023 | | 4.50.00.12 | 11/03/2021 | 11/03/2022 | | 4.50.00.11 | 09/23/2021 | 09/23/2022 | | 4.50.00.10 | 08/26/2021 | 08/26/2022 | | 4.50.00.09 | 08/18/2021 | 08/18/2022 | | 4.50.00.08 | 03/30/2021 | 03/30/2022 | | 4.50.00.07 | 02/19/2021 | 02/23/2022 | | 4.50.00.06 | 01/22/2021 | 02/23/2022 | | 4.50.00.05 | 10/28/2020 | 02/23/2022 | | 4.50.00.04 | 10/08/2020 | 02/23/2022 | | 4.50.00.03 | 09/29/2020 | 02/23/2022 | | 4.50.00.02 | 08/20/2020 | 02/23/2022 | | 4.50.00.01 | 08/06/2020 | 02/23/2022 | | **4.50.00 (initial release)** | **06/26/2020** | **02/23/2022** | ## Upgrade compatibility matrix for Edge for Private Cloud releases The following table outlines the available direct upgrade paths for various Apigee Edge for Private Cloud versions. Where a direct upgrade path exists, you can perform an in-place, zero-downtime upgrade to the specified Private Cloud version. For detailed steps on performing the upgrade, refer to the relevant upgrade documentation. If a direct upgrade path is not available, multiple intermediate upgrades are required to reach the target version. For example, if you are currently using Edge for Private Cloud version 4.52.00 and want to upgrade to version 4.53.00, you must perform the upgrade in two steps: first, upgrade from 4.52.00 to 4.52.02, and then from 4.52.02 to 4.53.00. Regardless of the upgrade paths listed below, you can migrate from any Private Cloud version to another by setting up a new Apigee cluster on the newer version and using Management APIs to transfer data from the older to the newer version. However, this approach may not be zero-downtime and is not considered an in-place upgrade. | Edge for Private Cloud version | Release date | Direct upgrade paths from | Upgrade documentation | |---|---|---|---| | 4.53.01 | 08/26/2025 | 4.52.02 or 4.53.00 | [4.53.01 upgrade documentation](https://docs.apigee.com/private-cloud/v4.53.01/update-apigee-edge-45202-45301) | | 4.53.00 | 10/11/2024 | 4.52.02 | [4.53.00 upgrade documentation](https://docs.apigee.com/private-cloud/v4.53.00/update-apigee-edge-45202-45300) | | 4.52.02 | 06/27/2024 | 4.52.01 or 4.52.00 or 4.51.00 | [4.52.02 upgrade documentation](https://docs.apigee.com/private-cloud/v4.52.02/update-apigee-edge-45100-45200) | | 4.52.01 | 03/28/2024 | 4.51.00 or 4.52.00 | [4.52.01 upgrade documentation](https://docs.apigee.com/private-cloud/v4.52.01/update-apigee-edge-45100-45200) | | 4.52.00 | 02/14/2023 | 4.51.00 or 4.50.00 | [4.52.00 upgrade documentation](https://docs.apigee.com/private-cloud/v4.52.00/update-apigee-edge-45100-45200) | ## Edge Microgateway release process This section describes the versioning scheme, release cadence, and support timelines for [Edge Microgateway](https://docs.apigee.com/api-platform/microgateway/edge-microgateway-home). For more information, see the [Release notes](https://docs.apigee.com/release/notes/edge-microgateway-release-notes-0). ### Release versioning scheme Releases for Edge Microgateway use the following numbering scheme: Major.Minor.Patch. For example, 3.2.1, where the major number is 3, the minor number is 2, and the patch number is 1. | Release degree | Description | |---|---| | Major | Major releases may contain new features and enhancements, cumulative bug fixes, security vulnerability mitigation, configuration changes, and infrastructure/architecture changes. | | Minor | Minor releases may contain existing feature enhancements, cumulative bug fixes, and security vulnerability mitigation. | | Patch | Patch releases may contain bug fixes and targeted security vulnerability mitigation. | ### Release cadence Apigee will release a new version of Edge Microgateway **approximately** once a month; however, this monthly release cadence is subject to change and may be longer or shorter as circumstances require. A release may be a Major, Minor, or Patch version. ### Support timelines The current version of Edge Microgateway will continue to be supported for one year after the next version becomes available. For example, if version 3.1.0 is released on January 17, 2020 and version 3.1.1 is released on February 17, 2020, version 3.1.0 will be supported until February 17, 2021. After the support window expires, Apigee requires customers to upgrade to a current release. No support tickets will be accepted for any releases that are outside the support window.