{"id":"6a2b3433a160c4ace4a5be05","title":"2026 06 11 Issue 114","path":"how-to/committee/release-notes/2026-06-11-issue-114","contentMarkdown":"# 11-Jun-2026 — guard the integration worker against deploying the website image [ref #114](https://github.com/nbarrett/ngx-ramblers/issues/114)\n\n## [build 688](https://github.com/nbarrett/ngx-ramblers/actions/runs/27380293796) — [commit 9c77ce9](https://github.com/nbarrett/ngx-ramblers/commit/9c77ce9d668f41df7dcfb1e753998e371ac6405d)\n\n_____\n\nDispatching build-and-deploy-integration-worker.yml with a bare run\nnumber (e.g. 687) deployed nbarrett36/ngx-ramblers:687 - the website\nimage, which ships no browser, no JDK and no PLAYWRIGHT_BROWSERS_PATH.\nThe deploy succeeded and health checks stayed green because the website\nimage serves the same endpoints, but the first walks upload then failed\nat Playwright browser launch with \"Executable doesn't exist\". The\nworker variant of the same build is pushed as integration-worker-687,\nand the workflow input description actively suggested passing the bare\nrun number.\n\ndeploy-integration-worker.ts now normalises a bare numeric tag to\nintegration-worker-<n> with a log line explaining why, passes\nintegration-worker-* tags through unchanged, and rejects anything else\nwith an error stating how worker images are tagged. The workflow input\ndescription now gives the prefixed form as the example and warns that\nplain run-number tags are the browserless website image.","contentHtml":"<h1>11-Jun-2026 — guard the integration worker against deploying the website image <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/114\">ref #114</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/27380293796\">build 688</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/9c77ce9d668f41df7dcfb1e753998e371ac6405d\">commit 9c77ce9</a></h2>\n<hr>\n<p>Dispatching build-and-deploy-integration-worker.yml with a bare run\nnumber (e.g. 687) deployed nbarrett36/ngx-ramblers:687 - the website\nimage, which ships no browser, no JDK and no PLAYWRIGHT_BROWSERS_PATH.\nThe deploy succeeded and health checks stayed green because the website\nimage serves the same endpoints, but the first walks upload then failed\nat Playwright browser launch with &quot;Executable doesn&#39;t exist&quot;. The\nworker variant of the same build is pushed as integration-worker-687,\nand the workflow input description actively suggested passing the bare\nrun number.</p>\n<p>deploy-integration-worker.ts now normalises a bare numeric tag to\nintegration-worker-<n> with a log line explaining why, passes\nintegration-worker-* tags through unchanged, and rejects anything else\nwith an error stating how worker images are tagged. The workflow input\ndescription now gives the prefixed form as the example and warns that\nplain run-number tags are the browserless website image.</p>\n"}