Codeberg Pages v2 gets a December 31 shutdown date — migrate to the git-pages backend

One new entry tonight. Codeberg is shutting its original Pages v2 static-site backend off completely on December 31, 2026; sites whose repository never had a Pages webhook set up are the ones that stop being served, and they need to migrate to the new git-pages-backed Codeberg Pages before then. Nothing already on the board moved its date, and the monitored sources were quiet. One archive backfill was also added — GitLab removing its bundled Helm-chart Ingress controllers in 20.0. On the countdown: OpenSSL 3.4 and the Minimus shutdown are one day out, with OpenAI retiring GPT-4, GPT-3.5, o1 and o3 the day after.

A quiet night on the monitored sources — nothing new or changed from the registry — with one dated shutdown surfaced from discussion and verified against the vendor’s own announcement.

New tonight

Codeberg Pages v2 shuts down on December 31, 2026. Codeberg is retiring the original in-house backend behind *.codeberg.page static sites in favour of a new git-pages backend, and will shut v2 off completely at the end of the year. The sites that stop being served are specifically the ones whose repository never had a Pages webhook set up — typically pages configured long ago and never touched. The new backend is the free successor on the same domains, so this is a configuration migration, not a move to a different host. Codeberg has a migration-check tool that tells you which backend you’re on and a migration guide for the switch. Unmigrated sites simply 404 after the cutoff until they’re moved. Announced on Codeberg’s blog on October 7.

Also added to the archive

GitLab’s Helm chart is removing its bundled NGINX Ingress, HAProxy and Traefik controllers in 20.0. Self-managed GitLab installed via the Helm chart or Operator is standardising on the Kubernetes Gateway API with a bundled Envoy Gateway (the default since 19.0); the bundled Ingress controllers are deprecated and disabled by default now, with full removal planned for 20.0. GitLab hasn’t published a calendar date for 20.0, so this is a dateless signaled entry — but the bundled NGINX Ingress stops getting security patches after March 2026, which is the practical deadline. Plain Ingress resources aren’t going away; you’ll just need your own external controller. Verified against GitLab’s NGINX chart docs.

The next three weeks, every date verified against its primary source

22 Oct — OpenSSL 3.4 end of life and the Minimus shutdown
23 Oct — OpenAI removes GPT-4, GPT-3.5, o1 and o3 models
27 Oct — Kubernetes 1.34 end of life
30 Oct — Fitbit’s legacy Web API shutdown
31 Oct — Consul 1.22 end of life and OpenAI’s hosted Evals platform going read-only
1 Nov — Alpine 3.21 end of life, OpenSSL 3.6 end of life, and Azure Databricks Runtime 10.4 LTS
2 Nov — GitHub Actions macOS 14 runner retirement and Mullvad’s encrypted DNS shutdown
10 Nov — .NET 8 and 9 end of support, Windows 11 23H2 end of servicing and Azure Functions PowerShell 7.4
12 Nov — PostgreSQL 14 end of life

The two imminent Azure dates on the board (Databricks Runtime 10.4 LTS on November 1, PowerShell 7.4 on November 10) remain confirmed against Microsoft’s release-communications API; their notices live on JavaScript-rendered pages our fetcher can’t read directly.

Full board with live countdowns on the calendar.