This page documents releases and patches for Apigee Edge for Private Cloud. We recommend that users periodically check this list for any new announcements, or subscribe to this page using a feed reader to get notifications of updates.
What is a feed reader?
Really simple syndication (RSS) feed readers aggregate content from websites that you specify.
Feed reader notifications can be email-, browser-, desktop-, or mobile-based. Some readers are free, or have free versions, and some require a subscription.
A few examples:
More information on RSS:
See also:
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
October 15, 2026
Released Apigee Edge for Private Cloud 4.54.00.
Designated Apigee Edge for Private Cloud 4.54.00.00 a long-term support (LTS) release: 18 months of full support ending April 2028, then 18 months of maintenance ending October 2029. After October 2029, 4.54.00.00 receives no software updates, security mitigations, or technical support.
Installing a later 4.54 minor release or patch does not change those dates. To extend the support lifecycle, upgrade to the next LTS release.
For the support lifecycle phases, release cadences, and version numbering, see Apigee Edge for Private Cloud release and lifecycle policy.
This release replaces Java 8 with Java 17 and Java 21, removes the Classic UI
and the apigee-sso component, and updates the bundled Cassandra, Postgres,
OpenLDAP, ZooKeeper, Qpid Broker-J, Nginx, and Consul versions. These changes
are not backward-compatible.
For the 4.54.00 versions and the 4.53.01 versions they replace, see Supported software and supported versions.
Before upgrading, read Changes in Edge for Private Cloud 4.54.00, then Update Apigee Edge 4.53.00 or 4.53.01 to 4.54.00 or New installation overview. For known issues, see Known issues with Edge for Private Cloud.
Replaced the Classic UI (edge-ui) with the
New Edge UI
(edge-management-ui).
The New Edge UI is the only management UI in 4.54.00 and is installed by
default. Deployments running the Classic UI must transition to it before
upgrading. Custom Classic UI properties do not carry over automatically. The
default port also changes from 9000 to 3001, configurable with
conf_uebe_port, so firewall rules and load balancer target ports that point
at 9000 fail until they are updated.
For the migration steps and the supported feature list, see Migrate to the New Edge UI and What features are supported?.
In deployments with Apigee SSO enabled, an integrated OIDC identity broker in
apigee-openldap replaces the standalone apigee-sso component and Apache
Tomcat 9.0.x. Before upgrading, take a complete and validated LDAP backup;
existing apigee-sso configurations do not migrate automatically. Deployments
not using Apigee SSO require no action.
For migration prerequisites, validation checks, and rollback constraints, see Option 2: Upgrade UI (with Apigee SSO).
4.54.00 runs Java in mixed mode: Java 17 for Cassandra and ZooKeeper, Java 21 for the Management Server, Message Processor, Router, and Qpid Broker-J. Both Oracle JDK and OpenJDK are supported at those versions.
Oracle JDK 8 and OpenJDK 8 are no longer supported.
API proxies with custom JavaCallout policies or custom resource JARs can break on Java 21. For details, see Changes in Edge for Private Cloud 4.54.00.
Upgraded Nginx on the Edge Router to 1.30.0.
If you are upgrading from Nginx 1.20.x, see Nginx 1.30 changes in Apigee Edge 4.54.00 for the full list of changes.
Changed the TLS defaults on Message Processors to the Java 21 cryptographic baseline.
Message Processors run on Java 21, which enables TLS 1.3 by default (JEP 332) and prefers it for outbound backend connections, falling back to TLS 1.2. No configuration change is required if your target servers and load balancers negotiate TLS 1.3, or negotiate TLS 1.2 with forward-secret (ECDHE) cipher suites.
Java 21 also disables the non-forward-secret static RSA key-exchange suites
(TLS_RSA_*). If you have overridden
conf_http_HTTPTransport.ssl.cipher.suites.whitelist or
conf_message-processor-communication_local.http.ssl.ciphers with static RSA
suites only, backend calls fail with no cipher suites in common and the
Router cannot complete a TLS handshake with the Message Processor. Replace the
TLS_RSA_* entries with modern cipher suites and restart the Message
Processor.
For the remediation path, see Legacy backend requirements and remediation.
Added Basic authentication to the New Edge UI, which lets you sign in without configuring an identity provider.
The New Edge UI supports Basic authentication without additional configuration. You can also configure Apigee SSO, or an external identity provider such as SAML or OIDC. This feature is generally available in 4.54.00.
Added automated pre-flight validation checks to apigee-setup and
apigee-service, which surface environment configuration problems before a
component is installed.
This feature is generally available in 4.54.00.
Fixed multiple security vulnerabilities in Apigee Edge for Private Cloud 4.54.00.
These fixes ship as part of the component upgrades in this release; see Changes in Edge for Private Cloud 4.54.00.
Changed the default garbage collector on Message Processors to the Garbage-First garbage collector.
Message Processors set useG1GC=true and useStringDeduplication=true by
default in 4.54.00. In 4.53.01 neither was set by default. To configure garbage
collection, see
Configure the garbage collector for Message Processors.
September 02, 2026
Apigee Edge for Private Cloud release notes are now published on Google Cloud documentation.
Release notes and patch announcements for Apigee Edge for Private Cloud are published on the Apigee Edge for Private Cloud release notes page from September 2026 onward. You can subscribe to that page with a feed reader to be notified when a new release or patch is published.
Release notes published before September 2026 remain available in the Apigee Edge release notes archive.