Support status change coming 13.09.2026

A heads-up on an upcoming support-lifecycle change: on 13.09.2026, a few older builds move down a support tier, per the build-lifecycle policy on the Version Overview page. If you’re using one of them from our CDN, please switch your links to a currently supported version before then.

• 0.1.0.0 “Cactus” [Build 1027]: Fully-fledged support → Unsupported.
• 0.1.0.0 “Cactus” [Build 1000, Cleanup]: Limited support → Unsupported.
• 0.0.1.8 “Hyacinth” [Build 0202]: Limited support → Unsupported.
• 0.0.2.0 “Barberry” [Build 0797]: Limited support → Unsupported.

Once a version is unsupported, it’s removed from the PanPlay CDN and no longer receives patches or developer assistance — self-hosted copies aren’t affected and can keep running them. The current state of every release is always on the Version Overview page.

While going through this, we also found a few older versions that should have been retired a while ago, but were still accidentally reachable directly on the CDN. Those have now been cleaned up too — they redirect straight to a supported version instead of quietly continuing to serve outdated, unmaintained code. We’d rather be upfront about the oversight than leave it silently fixed.

That oversight came down to this simply being a manual step before — easy to forget once a version’s actual retirement date arrives. To make sure it doesn’t happen again, we’ve built retirement directly into the CDN server itself, driven by a single configured date per version instead of a manual cleanup step:

• Starting 20 days before a version’s cutoff date, players on that version show a small, dismissible notice explaining what’s coming, with a direct link to switch.
• From 10 days before cutoff, that becomes a larger banner that has to be acknowledged before the player can be used further.
• Once the cutoff date itself arrives, the version stops being served entirely — every request to it is automatically redirected to a currently supported version, query parameters and all.

No manual step is required anymore to actually retire a version once its date is set — the server handles the whole timeline on its own from here on.