1.15.20 — Reliable legacy WebApp restore and honest offline state
Editorial identity incomplete
2026-08-22
Legacy WebApps can now be put back on their managed address without profile or DNS dead ends, while the Admin accurately reports apps that are offline.
Changed
- Managed address setup migrates legacy A or AAAA records to the current platform CNAME only when every address exactly matches the platform destination; foreign or mixed DNS remains refused.
Fixed
- Addressless legacy WebApps with a blank display name can be adopted and restored without a false profile-mismatch error.
- Offline WebApp pages no longer claim that the latest deploy is serving.
- The offline Danger panel no longer renders a literal
nullvalue when the Take offline action is absent.