ReleaseRun Badges for PostgreSQL

Why Use PostgreSQL Health Badges?

PostgreSQL’s 5-year support window means versions quietly drop off the patch list while teams assume they are still covered. A health badge shows your users — and your own team — whether the Postgres version in your stack is still getting security fixes.

ReleaseRun badges go beyond Shields.io. While Shields.io shows a version number, our badges show security posture: CVE counts, EOL countdowns, and a composite health grade based on freshness (35%), security (35%), and support status (30%).

PostgreSQL Release History & EOL Timeline

The PostgreSQL Global Development Group releases a new major version every year (typically in Q3/Q4) and provides five years of support for each major release. Minor releases with bug and security fixes ship quarterly. PostgreSQL’s long support window is generous, but it also means teams delay upgrades and then face a large version gap when forced to move.

• PostgreSQL 17 — released September 2024. Current stable release. Active support until November 2029.
• PostgreSQL 16 — released September 2023. Active support until November 2028.
• PostgreSQL 15 — released October 2022. Active support until November 2027.
• PostgreSQL 14 — released September 2021. Active support until November 2026.
• PostgreSQL 13 — released September 2020. Final release expected November 2025. If you are still on Postgres 13, start planning your upgrade path now.
• PostgreSQL 12 — released October 2019. Reached end-of-life November 2024. No further security patches. The ReleaseRun EOL badge turns red for this version.
• PostgreSQL 11 and earlier — end-of-life. Running these in production exposes you to unpatched CVEs.

With five concurrent major versions in active support, it can be hard to tell which ones are approaching EOL. Badges make the timeline visible at a glance — green for actively supported, amber for approaching EOL, red for unsupported.

Badge Customization Examples

Four badge types are available for PostgreSQL:

• Health badge — composite A–F grade. Embed: ![PostgreSQL Health](https://img.releaserun.com/badge/health/postgresql.svg)
• Freshness badge — how current your version is. Embed: ![Postgres 16](https://img.releaserun.com/badge/v/postgresql/16.7.svg)
• EOL badge — end-of-life status. Embed: ![Postgres 13 EOL](https://img.releaserun.com/badge/eol/postgresql/13.svg)
• CVE badge — vulnerability count. Embed: ![Postgres CVEs](https://img.releaserun.com/badge/cve/postgresql/16.7.svg)

Append ?style=flat-square or ?style=for-the-badge for alternative rendering. The embed builder above lets you preview all styles.

Common Use Cases

• ORM and driver maintainers: Show which PostgreSQL versions your library tests against and flag when any of them leave the support window. If you still test against Postgres 12, that badge will tell your users it is time to move.
• Platform teams: Embed badges in runbooks or internal dashboards to track Postgres versions across RDS instances, self-hosted clusters, and dev environments. Picking the right database starts with knowing what you are already running.
• Documentation sites: Add version health next to connection setup guides so developers verify their target Postgres version is still maintained.

Related ReleaseRun Tools

PostgreSQL badges work alongside specialised database management tools:

• PostgreSQL Extension Matrix — check which extensions are compatible with your Postgres version.
• Tech Stack Health Scorecard — get a holistic health grade across your entire stack, including your database layer.
• Dependency EOL Scanner — scan your infrastructure dependencies and flag anything approaching end-of-life.
• EOL Timeline Visualizer — see PostgreSQL EOL dates alongside your other dependencies on an interactive timeline.
• Upgrade Path Planner — plan your PostgreSQL major version upgrade with step-by-step guidance.
• Migration Effort Estimator — estimate the work involved in migrating from one Postgres version to another.
• CVE Dashboard — monitor known vulnerabilities across PostgreSQL and all your other tracked products.

What Makes These Different

Every badge pulls live data from the endoflife.date API and the NIST National Vulnerability Database. Data refreshes every 6 hours. Badges are edge-cached for 5 minutes — fast enough for CI pipelines, dashboards, and decision guides.