End dates on patch day: PostgreSQL 14 retires, GitHub drops ARM32, Micronaut fixes 38 flaws
Three announcements in two days read like routine maintenance and are not. On 12 November the PostgreSQL project shipped 18.7, 17.12, 16.16, 15.20 and 14.25 with 52 security fixes and said that 14.25 is the last release of PostgreSQL 14. The same day GitHub said its hosted Actions runners will stop running ARM32 jobs on Linux and Windows on 8 December. A day earlier Micronaut Core 5.2.23 went out as a patch release linking 38 security advisories, alongside new tags for the 4.10 and 3.10 lines.
What links them is that the number on the release says little about the work. A PostgreSQL minor update is normally a package swap and a restart. This one asks operators to reindex pg_trgm GiST indexes and B-tree indexes on bpchar columns without a length, to check TOAST indexes rebuilt concurrently, and to take a new full backup before relying on incremental backups again. A Micronaut patch is normally a dependency bump. This one changes how route filters, CORS preflight checks and TLS listeners behave, which is exactly the behaviour applications rely on for access control.
The end dates are the second thread. PostgreSQL 14 users have now received the final fix for their branch, and any vulnerability found from here on stays open for them. The GitHub notice is a different kind of end date, set by a dependency: Node 24 has no ARM32 build, so the runner cannot run there, so the jobs stop. Neither the database users nor the CI users chose the timing, and both now have a fixed point to plan around.
The practical habit these suggest is to read release notes as a work order rather than a summary. The PostgreSQL announcement has an Updating section for a reason, and the Micronaut notes group the advisories by area so that a team can see whether it uses the affected features. For CI, the useful check is where jobs actually run, by label and architecture, before a provider retires a platform.

Why it matters
Version numbers promise compatibility, and they mostly keep that promise. They do not promise that an upgrade is effortless, and they say nothing about how long a branch will keep receiving fixes. This week's notices are a small reminder to track support windows and post-upgrade steps as carefully as the versions themselves.