{"id":"6a5d68e4b0487133513c11a0","title":"2026 07 20 Issue 319","path":"how-to/committee/release-notes/2026-07-20-issue-319","contentMarkdown":"# 20-Jul-2026 — prevent domain outages and image propagation failures [ref #319](https://github.com/nbarrett/ngx-ramblers/issues/319)\n\n## [build 783](https://github.com/nbarrett/ngx-ramblers/actions/runs/29708760511) — [commit 30d30f3](https://github.com/nbarrett/ngx-ramblers/commit/30d30f35f2c892d263ce4f8469b99d07d0060d3d)\n\n_____\n\n## What's new\n\nEnvironment domain management now prevents an incorrect apex or www redirect from taking a site offline and provides a clear recovery route when a redirect needs removing. Deployments also wait briefly for Fly to recognise a newly published image, avoiding intermittent failures caused by image propagation delays.\n\n## At a glance\n\n- Apex and www redirects are only offered for genuine zone-level hostname pairs\n- Redirect targets must resolve before a Cloudflare rule is created\n- New redirects use a recoverable temporary status and can be removed from Environment Management\n- Hostname health reports broken redirect targets and failed checks accurately\n- Deployments wait for newly published images to become visible to Fly before continuing","contentHtml":"<h1>20-Jul-2026 — prevent domain outages and image propagation failures <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/319\">ref #319</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/29708760511\">build 783</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/30d30f35f2c892d263ce4f8469b99d07d0060d3d\">commit 30d30f3</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<p>Environment domain management now prevents an incorrect apex or www redirect from taking a site offline and provides a clear recovery route when a redirect needs removing. Deployments also wait briefly for Fly to recognise a newly published image, avoiding intermittent failures caused by image propagation delays.</p>\n<h2>At a glance</h2>\n<ul>\n<li>Apex and www redirects are only offered for genuine zone-level hostname pairs</li>\n<li>Redirect targets must resolve before a Cloudflare rule is created</li>\n<li>New redirects use a recoverable temporary status and can be removed from Environment Management</li>\n<li>Hostname health reports broken redirect targets and failed checks accurately</li>\n<li>Deployments wait for newly published images to become visible to Fly before continuing</li>\n</ul>\n"}