Out-of-cycle release on 2025-02-20

Hi,

CVE-2025-1094[1]https://www.postgresql.org/support/security/CVE-2025-1094/ introduced a regression that was reported fairly
shortly after the release[2]/messages/by-id/Z64jD3u46gObCo1p@pryzbyj2023. Based on the nature of the report and the
fact it's in libpq, the release team was unsure of what the overall
prevalence of the issue given its client-facing, and decided to have an
out-of-cycle release on 2025-02-20[3]https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-20-2025-3016/ to handle this sooner than the
regularly scheduled release[4]https://www.postgresql.org/developer/roadmap/.

Per standard release process, any patches being committed for this
release must be in by 2025-02-15 12:00 UTC to ensure they have ample
time to get through the buildfarm.

Thanks,

Jonathan

[1]: https://www.postgresql.org/support/security/CVE-2025-1094/
[2]: /messages/by-id/Z64jD3u46gObCo1p@pryzbyj2023
[3]: https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-20-2025-3016/
https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-february-20-2025-3016/
[4]: https://www.postgresql.org/developer/roadmap/