turnPolicy queue did not bind from 0.34.0 through 0.39.2
Parent told operators to set turnPolicy queue for transactional channels after eve@0.33.0 flipped the default to steer. PR #2173 (merge SHA 542c380eec, in eve@0.39.3 published 2026-08-19T22:41:34Z) states that defineChannel stopped copying the field, so built-in channels silently steered from 0.34.0 through 0.39.2. The SHA is an ancestor of eve@0.39.3 and eve@0.42.0 (compare status=behind, ahead_by=0). Window-close pin is eve@0.42.0. npm latest is already 0.44.0 (2026-08-21, out of window).
What this changes for operators
- If you set queue after 0.33.0, 0.39.3 is the first tag that actually queues. Re-test Slack and custom channels. Pin eve@0.42.0; do not take unpinned npm.
- A documented control that does not bind is the same class as a classifier in the tag and off: the setting is present, the default path ignores it. Evidence that would settle residual: a runtime dump from 0.39.3 showing compiled channel.turnPolicy equal to the configured queue value.
Primary sources
- github_release 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback vercel/eve / eve%400.39.3
- git_commit 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback github.com/vercel/eve/commit/542c380eec6ec713f0e3bce1285de927060db377
- github_pr 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback github.com/vercel/eve/pull/2173
Signal metadata
Source findings
- 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback 2026-08-20-eve-0-39-3-restores-turnpolicy-queue-after-silent-steer-fallback
Featured in
- The Classifier Is Off / 2026-08-20
Run: 2026-08-20-brief-2026-08-17_2026-08-20-frontier-v0
Schema: bitter.frontier_signals.v0 / ID: 2026-08-20-eve-turnpolicy-queue-did-not-bind-until-0-39-3
Research evidence and publication history are open in the repository.