The CloudNativePG community is releasing maintenance updates for both currently supported series: 1.30.1 and 1.29.3.

These are routine updates, and CloudNativePG remains as stable as ever. The main thread running through both releases is continued polish to failover and primary-election behavior, part of our ongoing investment in making replication, including asynchronous setups, more predictable under real-world conditions. A pending failover that could previously stall or get silently reverted is now handled correctly (#11336), and in 1.30.1, PostgreSQL startup is now gated on the instance manager actually holding the primary Lease introduced in 1.30, closing a small timing window during restarts (#11356).

Alongside that, both releases pick up a handful of smaller enhancements, such as a configurable auth_user for the connection pooler and a --dry-run option for cnpg backup, plus a number of correctness and robustness fixes. Full details, as always, are in the release notes linked below.

Both releases also bump google.golang.org/grpc to fix CVE-2026-84304 (GHSA-vp52-pcj8-j9qc), a heap-exhaustion issue in gRPC-Go’s HTTP/2 frame handling.

This kind of groundwork is also paving the way for 1.31.0, which will further solidify failover and High Availability.

Upgrade

Follow the upgrade instructions for a smooth transition.

For the complete list of changes, see the release notes:

• Release notes for 1.30.1
• Release notes for 1.29.3

Get involved with the community

Join us to help shape the future of cloud-native Postgres!

We’re also actively working with the CNCF TOC toward CloudNativePG’s acceptance into Incubation. As part of that effort, we’re pleased to share that we’ve been evolving our governance model to better reflect the project’s community. You can read the current governance model to learn more, as well as our new contributor ladder.

If you’re using CloudNativePG in production, consider adding your organization as an adopter to support the project’s growth and evolution.

We’d also like to thank everyone who contributed a pull request to this release. The number of community contributions keeps growing, and we couldn’t be happier about it.

Thank you for your continued support!