Upgrading Hybrid Manager Innovation Release

Hybrid Manager (HM) offers a dual release strategy: LTS (Long-Term Support) and Innovation Releases (IR). Because these streams follow different versioning logic, the supported paths for moving between them depend on your current version and the target environment.

Service availability during upgrades

The impact of upgrades on your HM-managed Postgres database clusters depends on your specific upgrade path and the components being updated.

While many upgrades are designed to be non-disruptive to database traffic, certain system updates may trigger an automatic restart of your HM-managed Postgres database clusters. To avoid unexpected service interruptions, verify the specific requirements of your upgrade path.

Supported LTS upgrade paths

LTS releases follow standard semantic versioning (e.g., 1.3.x). These versions focus on stability and are intended for production environments requiring a long support lifecycle.

Minor version upgrades

Following major.minor.patch versioning, you can upgrade from one minor version to the immediate next minor version. You must ensure you are on the latest patch version of your current minor release before moving forward.

Supported: 1.3.x to 1.4.y (where x is the latest available patch at the time of upgrade).

Not supported: 1.3.x to 1.5.y (You must upgrade to 1.4.y first).

Major version upgrades

When a new major version (e.g., 2.0) is released, you must be running the latest available 1.x minor release to perform the upgrade.

Supported IR upgrade paths

Innovation Releases follow a date-based versioning scheme (e.g., 2025.11). These releases provide the latest features and platform hardening at a faster cadence.

Sequential upgrades

Innovation Releases require a strict sequential upgrade pattern. You cannot skip a monthly release.

Supported: 2025.11 to 2025.12.

Not supported: 2025.11 to 2026.01 (You must upgrade to 2025.12 first).

Supported cross-stream upgrade paths

Moving between LTS and Innovation Releases is possible, but subject to specific constraints regarding version numbering and platform limitations.

Innovation Release to LTS

Innovation Releases (IR) eventually converge into a new Long-Term Support (LTS) version. This is known as a consolidation point. You can move from the final Innovation Release of a cycle (two cycles in a year) to the LTS release that consolidates those features, but you can't move to an LTS release from any other Innovation Release.

Supported: You can only upgrade to a new LTS version from the specific Innovation Release that immediately precedes it.

Unsupported: You cannot move to an LTS release from an older or mid-cycle Innovation Release. If you are on an earlier IR, you must first upgrade sequentially through the IR stream until you reach the consolidation point.

Because consolidation points (that take place twice a year) are scheduled based on feature readiness, they don't occur on fixed dates. To determine if your current Innovation Release can move to an LTS version, refer to the documented upgrade instructions provided with each new release. These release-specific instructions will explicitly state if a version is an Innovation Release and whether it supports a transition to the LTS stream.

LTS to Innovation Release

You can upgrade an LTS release to its immediate succeeding Innovation Release.