{"version":"2.1.219","anchor":"new-engine-prerelease-channel-recognized-for-worker-respawn","canonical_anchor":"new-engine-prerelease-channel-recognized-for-worker-respawn","heading":"New \"engine\" prerelease channel recognized for worker respawn","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/new-engine-prerelease-channel-recognized-for-worker-respawn","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### New \"engine\" prerelease channel recognized for worker respawn\n\nBackground workers now recognise a second build channel and won't respawn themselves across channels.\n\n**What**\n\nBackground worker and daemon respawn now understands a second prerelease channel and refuses to upgrade across channels.\n\n**Details**\n\n- The version regex accepts `engine` alongside `dev|alpha|beta|rc|test|nightly` as a prerelease tag\n- A new helper set `[\"dev\", \"engine\"]` classifies a version by which of those tags its build string contains\n- A `-dev.` worker is not respawned as `-engine.` or vice versa; previously only the dev tag was understood\n- This build reports VERSION \"2.1.219\"\n\n**Evidence**\n\n`nightly|engine`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}