{"id":"6a1feb615a2e00be57ce3927","title":"2026 06 03 Issue 260","path":"how-to/committee/release-notes/2026-06-03-issue-260","contentMarkdown":"# 03-Jun-2026 — self-heal missing NODE_ENV when resuming an environment [ref: #260](https://github.com/nbarrett/ngx-ramblers/issues/260)\n\n## [build 665](https://github.com/nbarrett/ngx-ramblers/actions/runs/26873625529) — [commit 22bb46e](https://github.com/nbarrett/ngx-ramblers/commit/22bb46e10d9c1bc096f69c9d8d041e0c6e7d415f)\n\n_____\n\n#260 made resumeEnvironment self-healing for AUTH_SECRET but classified\nevery other missing REQUIRED_SECRET as unrecoverable. NODE_ENV was added to\nREQUIRED_SECRETS and so fell into that bucket alongside AWS_* and MONGODB_URI,\naborting any resume with \"missing required secrets [NODE_ENV] that cannot be\nauto-generated\" - despite NODE_ENV having a known constant value (\"production\",\nthe same value the create wizard hardcodes at environment-setup-service.ts:145).\n\nAdd a STATIC_SECRET_DEFAULTS registry for required secrets that have a fixed\ndefault rather than a generated one. NODE_ENV now self-heals to \"production\"\nand is persisted to the environment record, while AUTH_SECRET keeps its random\ngenerator and AWS_*/MONGODB_URI stay unrecoverable. Any future constant-valued\nrequired secret just needs one line in the registry.","contentHtml":"<h1>03-Jun-2026 — self-heal missing NODE_ENV when resuming an environment <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/260\">ref: #260</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/26873625529\">build 665</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/22bb46e10d9c1bc096f69c9d8d041e0c6e7d415f\">commit 22bb46e</a></h2>\n<hr>\n<p>#260 made resumeEnvironment self-healing for AUTH_SECRET but classified\nevery other missing REQUIRED_SECRET as unrecoverable. NODE_ENV was added to\nREQUIRED_SECRETS and so fell into that bucket alongside AWS_* and MONGODB_URI,\naborting any resume with &quot;missing required secrets [NODE_ENV] that cannot be\nauto-generated&quot; - despite NODE_ENV having a known constant value (&quot;production&quot;,\nthe same value the create wizard hardcodes at environment-setup-service.ts:145).</p>\n<p>Add a STATIC_SECRET_DEFAULTS registry for required secrets that have a fixed\ndefault rather than a generated one. NODE_ENV now self-heals to &quot;production&quot;\nand is persisted to the environment record, while AUTH_SECRET keeps its random\ngenerator and AWS_*/MONGODB_URI stay unrecoverable. Any future constant-valued\nrequired secret just needs one line in the registry.</p>\n"}