Daniel Sutton b512583ee7 test(redis-worker): allow timer jitter in mollifier drainer stop-timeout test ...

Node's setTimeout can fire a millisecond or two early under CI load,
causing the existing `>= 500ms` lower bound to flake (saw 499ms in CI).
Loosen to `>= 450ms` — the behaviour being pinned is "stop honors the
deadline instead of waiting for the hung handler indefinitely", not
millisecond-precise timing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-18 11:57:14 +01:00

..

build

feat(sdk): chat.agent — runtime + browser transport

2026-05-14 15:09:25 +01:00

cli-v3

feat(webapp,core,sdk,cli): bound session.out via per-turn trim (#3644)

2026-05-18 10:21:56 +01:00

core

feat(webapp,core,sdk,cli): bound session.out via per-turn trim (#3644)

2026-05-18 10:21:56 +01:00

plugins

feat(webapp): consolidate auth path + add comprehensive auth tests (#3499)

2026-05-12 17:16:20 +01:00

python

chore: release v4.4.6 (#3501)

2026-05-12 11:33:00 +01:00

react-hooks

chore: release v4.4.6 (#3501)

2026-05-12 11:33:00 +01:00

redis-worker

test(redis-worker): allow timer jitter in mollifier drainer stop-timeout test

2026-05-18 11:57:14 +01:00

rsc

chore: release v4.4.6 (#3501)

2026-05-12 11:33:00 +01:00

schema-to-json

chore: release v4.4.6 (#3501)

2026-05-12 11:33:00 +01:00

trigger-sdk

feat(webapp,core,sdk,cli): bound session.out via per-turn trim (#3644)

2026-05-18 10:21:56 +01:00