NOTE: Future Breaking Changes lists anticipated breaking changes in the upcoming 4.x release. This release is scheduled for 2027-12 or 2028-01.
NOTE: Please refer to the V3 Migration Guide for details on updating existing applications using v1.x.y or v2.x.y.
- Dynamic Channel Pool support has been added as an opt-in feature. It can be enabled via the InstanceChannelAffinityOption and configured via the DynamicChannelPoolSizingPolicyOption.
- Added Data Lineage Config Management library.(#16069)
- Added Business Glossary library.(#16072)
- Added CMEK library.(#16072)
- Added Data Products library.(#16072)
- feat(spanner): set read lock mode at client level (#16068)
- feat(storage): add IsOpen API for zonal read operation (#16063)
- This release is based on definitions as of 2026-04-02T09:44:56-07:00
We are happy to announce the following GA libraries. Unless specifically noted, the APIs in these libraries are stable, and are ready for production use.
- Gemini Enterprise for Customer Experience API
- Cluster Director API
- Vector Search API
- Vision AI API
- Workload Manager
- feat(storage): Get/Insert/Update/Patch Object contexts (#15933)
- This release is based on definitions as of 2026-02-23T01:04:53-08:00
- feat: Added DeleteCryptoKey and DeleteCryptoKeyVersion RPCs to permanently remove resources.
- feat: Introduced the RetiredResource resource to track records of deleted keys and prevent the reuse of their resource names.
- feat: Added ListRetiredResources and GetRetiredResource RPCs to manage and view these records.
All libraries except Bigtable, PubSub, Spanner, and Storage have had their default maximum retry policy duration reduced from 30 minutes to 10 minutes.
BREAKING CHANGES
As previously announced, google-cloud-cpp now requires C++ >= 17. This is
motivated by similar changes in our dependencies, and because C++ 17 has been
the default C++ version in all the compilers we support for several years.
We think this change is large enough that deserves a major version bump to signal the new requirements. Additionally, we have decommissioned previously deprecated API features and have also made some previously optional dependencies required.
NOTE: Please refer to the V3 Migration Guide for details on updating existing applications using v1.x.y or v2.x.y.