# 11-Jun-2026 — guard the integration worker against deploying the website image [ref #114](https://github.com/nbarrett/ngx-ramblers/issues/114)

## [build 688](https://github.com/nbarrett/ngx-ramblers/actions/runs/27380293796) — [commit 9c77ce9](https://github.com/nbarrett/ngx-ramblers/commit/9c77ce9d668f41df7dcfb1e753998e371ac6405d)

_____

Dispatching build-and-deploy-integration-worker.yml with a bare run
number (e.g. 687) deployed nbarrett36/ngx-ramblers:687 - the website
image, which ships no browser, no JDK and no PLAYWRIGHT_BROWSERS_PATH.
The deploy succeeded and health checks stayed green because the website
image serves the same endpoints, but the first walks upload then failed
at Playwright browser launch with "Executable doesn't exist". The
worker variant of the same build is pushed as integration-worker-687,
and the workflow input description actively suggested passing the bare
run number.

deploy-integration-worker.ts now normalises a bare numeric tag to
integration-worker-<n> with a log line explaining why, passes
integration-worker-* tags through unchanged, and rejects anything else
with an error stating how worker images are tagged. The workflow input
description now gives the prefixed form as the example and warns that
plain run-number tags are the browserless website image.