Three support cut-offs this week came with dates, and each gave a different amount of warning
Victoria Shinder2 min readThree unrelated projects announced the end of support for something this week. What separates them is not the decision but how much time they left.
OpenJDK: one release of runway. JEP 541, targeted to JDK 28, deprecates the macOS/x64 port for removal. Oracle engineers stop maintaining it as of JDK 27, a build now fails by default unless a new --enable-deprecated-ports flag is passed, and the port is switched off in the JDK's own CI. The JEP leaves a door open: if credible developers step up to maintain the port, the deprecation can be withdrawn or reverted.
GitHub: a day. On GitHub Enterprise Cloud, self-hosted runners below 2.329.0 can no longer register, and older registered runners stop executing jobs. The changelog says the change shipped on 28 September with full enforcement on 29 September, a date that moved from the one announced earlier. GitHub pairs it with a REST API that reports the cut-off dates for any runner version.
Hono: a major version. The web framework moved its runtime adapters into separate packages in 4.13.10. The old import paths keep working throughout version 4 and disappear in version 5; one adapter, for Cloudflare Pages, gets no replacement package at all.
What connects them
Each is reasonable on its own terms. Together they show why a deprecation is only useful with a date and a way to find out about it. The JDK and Hono tie the cut-off to a release you choose to install, so you meet it when you upgrade. GitHub's is tied to the calendar on a service you do not control, so you meet it when jobs stop running. The practical habit is the same in all three cases: keep a list of platform versions you depend on, and subscribe to the one feed per platform that announces cut-offs, rather than learning about them from a failed build.