mirror of
https://github.com/vercel/workflow.git
synced 2026-09-14 19:59:43 +08:00
5e281607d3
Second review round on #2970: - Guard-enforced batches with an open hook (or hooks created by the same suspension) now take the await-then-run path even when optimistic inline start is enabled: the step_started claim carries the snapshot and is awaited before user code runs, so a claim the backend rejects as stale (412) never executes the step body — the fence covers side effects, not just durable writes. - Retract the WORKFLOW_SEQUENTIAL_REPLAYS waiver of turbo's hook/wait latch: the env var cannot prove the built flow trigger carries maxConcurrency: 1 (it must also be set at build time, and some integrations write their own trigger config), and capabilities.maxConcurrency only declares queue support. The conservative latch stays until the build emits a verifiable serialization signal; the capability remains declared for that follow-up. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@workflow/world
Core interfaces and types for Workflow SDK storage backends.
This package defines the World interface that abstracts workflow storage, queuing, authentication, and streaming operations. Implementation packages like @workflow/world-local and @workflow/world-vercel provide concrete implementations.
Used internally by @workflow/core and world implementations. Should not be used directly in application code.