Keep cloud-sql-jdbc-socket-factory (postgres-socket-factory) up to date in managed dependencies

[mzeijen]

I noticed that the version of cloud-sql-jdbc-socket-factory (e.g. postgres-socket-factory) managed by Spring Cloud GCP is lagging behind upstream releases:

• Spring Cloud GCP 7.x provides 1.25.0
• Spring Cloud GCP 8.x provides 1.28.0

The latest upstream release is 1.28.4.

This matters to us because of a bug in cloud-sql-jdbc-socket-factory that can leave the certificate refresh stuck, eventually causing TLS handshake failures. It left an application pod in a broken state that did not recover automatically and required a manual restart. The bug was fixed in 1.28.1, so consumers stuck on the Spring Cloud GCP managed version do not get the fix without overriding it themselves.

cloud-sql-jdbc-socket-factory follows semantic versioning, so minor and patch upgrades are expected to be backwards compatible, and we did not find any breaking changes in the changelog between 1.25.0 and 1.28.4.

Questions:

1. Would you be willing to bump the managed cloud-sql-jdbc-socket-factory version to the latest (currently 1.28.4) on the actively maintained branches?
2. If you are intentionally pinning to an older version, could you share the reasoning? That would help us decide whether overriding the version on our side is safe and appropriate as a longer-term approach.

[mzeijen]

Ok, I have noticed that there is a compatibility issue between Spring Cloud GCP 7.x, Spring Boot 3.5 and cloud-sql-jdbc-socket-factory 1.28.0. Namely in 1.28.0 they now require r2dbc-postgresql version 1.1.1 and Netty 4.2.x, which is not provided by Spring Boot 3.5. So they broke backwards compatibility with that version :(. With this I can understand it is not possible to upgrade Spring Cloud GCP 7.x and older versions to 1.28.4.

However Spring Cloud GCP 8.x could be on 1.28.4 and be backwards compatible.

[jinseopkim0]

Thanks for opening the issue. If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.