{"id":"6afcf8cd2a4d560df93624b4","title":"2026 11 18 Issue 231","path":"how-to/committee/release-notes/2026-11-18-issue-231","contentMarkdown":"# 18-Nov-2026 — copy from the database a site really uses and keep it on the new cluster after later [#231](https://github.com/Ramblers-GB/ngx-ramblers/issues/231)\n\n## [build 1101](https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44210594630) — [commit e3d7e19](https://github.com/Ramblers-GB/ngx-ramblers/commit/e3d7e191b31387f68c2267a373dfd82746286457)\n\n_____\n\n## What's new\n\n- Environment Migration now refuses to start when an environment's stored connection string names a different cluster or database from its MongoDB settings, and says which one the site is really using. Correct the MongoDB settings to match the live database first; otherwise the copy would come from an old database and the cutover would put the site onto stale data.\n- After a cutover, a later deploy-to-all keeps the site on its new cluster. Previously a stored connection string could put the site back onto the old cluster on the next deploy.","contentHtml":"<h1>18-Nov-2026 — copy from the database a site really uses and keep it on the new cluster after later <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/issues/231\">#231</a></h1>\n<h2><a href=\"https://github.com/Ramblers-GB/ngx-ramblers/actions/runs/44210594630\">build 1101</a> — <a href=\"https://github.com/Ramblers-GB/ngx-ramblers/commit/e3d7e191b31387f68c2267a373dfd82746286457\">commit e3d7e19</a></h2>\n<hr>\n<h2>What&#39;s new</h2>\n<ul>\n<li>Environment Migration now refuses to start when an environment&#39;s stored connection string names a different cluster or database from its MongoDB settings, and says which one the site is really using. Correct the MongoDB settings to match the live database first; otherwise the copy would come from an old database and the cutover would put the site onto stale data.</li>\n<li>After a cutover, a later deploy-to-all keeps the site on its new cluster. Previously a stored connection string could put the site back onto the old cluster on the next deploy.</li>\n</ul>\n"}