Version Packages (beta) - #3466
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 11, 2026 19:53
fc9e588 to
c1a5c74
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 11, 2026 20:28
4c027ce to
9add9d7
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 13:57
61c47ab to
600b096
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 16:18
a06aa5c to
efbc408
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 18:15
40fe21f to
a0ccfe0
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 19:14
f3ed6ee to
14b52ac
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 20:09
0b65dfb to
b589460
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 12, 2026 21:37
48f52fc to
f1ef0cb
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 07:07
28a4531 to
01991ed
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 15:59
5e21336 to
3450c86
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 18:01
eaf9c61 to
0b7c967
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 18:34
d329688 to
8d8b7b3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 19:08
4f0c2a7 to
834d1f9
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 13, 2026 22:58
b2665bd to
dc85865
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@workflow/core@5.0.0-beta.42
Minor Changes
7683130Thanks @TooTallNate! - Resilient step dispatch: newly created steps are published to the queue in parallel with theirstep_createdevent write, with the serialized input carried on the message (stepInput) so the consumer re-ensures the event if the direct write failed transiently — mirroring resilient start (runInput) and resilient hook resume (hookInput). Worlds that enforce the precondition guard keep the sequential create-then-publish dispatch (only sequencing gives the message a happens-after edge over the create's guard verdict); step-dispatch idempotency keys are now step-identity-scoped. Disable viaWORKFLOW_RESILIENT_STEP_DISPATCH=0.Patch Changes
#3462
9add9d7Thanks @NathanColosimo! - Reject compact sparse-array payloads with logical lengths above 100,000 during hydration.#3519
dc85865Thanks @VaguelySerious! - Remove thepreconditionGuardWorld capability. A stale replay-context write no longer needs to be rejected: a reader holds a prefix of the log, replay is deterministic on a prefix, and the writer's next write reports the events it was pushed past.#3381
efbc408Thanks @VaguelySerious! - Ignore duplicate events that a concurrent replay wrote for an entity the event log already records, instead of failing the run with a corrupted event log#3437
a0ccfe0Thanks @karthikscale3! - Add OTEL telemetry for hook-triggered time-to-resume:workflow.resume.total_msplus a non-overlapping phase breakdown, on the first durable step after a resume.#3519
dc85865Thanks @VaguelySerious! - Require every event id the runtime reads to be a log position.requireEventSlotreplaces the lenient decode that returned "no position" for an id that is not a slot.#3519
dc85865Thanks @VaguelySerious! - Turn resilient step dispatch off by default. SetWORKFLOW_RESILIENT_STEP_DISPATCH=1to opt back in.#3479
b589460Thanks @VaguelySerious! - Replay-context event writes now always report the log position they replayed from, and theWORKFLOW_PRECONDITION_GUARDflag is removed.#3410
c1a5c74Thanks @alangenfeld! - Surface typed terminal errors when stream retention expires.Updated dependencies [
600b096,dc85865,efbc408,a0ccfe0,dc85865,7683130,dc85865,b589460,c1a5c74,8d8b7b3,0f4b35f,01991ed]:@workflow/world@5.0.0-beta.27
Minor Changes
#3390
600b096Thanks @alangenfeld! - Add a bounded batch analytics event lookup for enriching canonical event pages.#3365
7683130Thanks @TooTallNate! - Resilient step dispatch: newly created steps are published to the queue in parallel with theirstep_createdevent write, with the serialized input carried on the message (stepInput) so the consumer re-ensures the event if the direct write failed transiently — mirroring resilient start (runInput) and resilient hook resume (hookInput). Worlds that enforce the precondition guard keep the sequential create-then-publish dispatch (only sequencing gives the message a happens-after edge over the create's guard verdict); step-dispatch idempotency keys are now step-identity-scoped. Disable viaWORKFLOW_RESILIENT_STEP_DISPATCH=0.Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Remove thepreconditionGuardWorld capability. A stale replay-context write no longer needs to be rejected: a reader holds a prefix of the log, replay is deterministic on a prefix, and the writer's next write reports the events it was pushed past.#3381
efbc408Thanks @VaguelySerious! - Ignore duplicate events that a concurrent replay wrote for an entity the event log already records, instead of failing the run with a corrupted event log#3437
a0ccfe0Thanks @karthikscale3! - Add OTEL telemetry for hook-triggered time-to-resume:workflow.resume.total_msplus a non-overlapping phase breakdown, on the first durable step after a resume.#3519
dc85865Thanks @VaguelySerious! - Require every event id the runtime reads to be a log position.requireEventSlotreplaces the lenient decode that returned "no position" for an id that is not a slot.#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.#3479
b589460Thanks @VaguelySerious! - Replay-context event writes now always report the log position they replayed from, and theWORKFLOW_PRECONDITION_GUARDflag is removed.@workflow/world-vercel@5.0.0-beta.38
Minor Changes
#3390
600b096Thanks @alangenfeld! - Add a bounded batch analytics event lookup for enriching canonical event pages.#3365
7683130Thanks @TooTallNate! - Resilient step dispatch: newly created steps are published to the queue in parallel with theirstep_createdevent write, with the serialized input carried on the message (stepInput) so the consumer re-ensures the event if the direct write failed transiently — mirroring resilient start (runInput) and resilient hook resume (hookInput). Worlds that enforce the precondition guard keep the sequential create-then-publish dispatch (only sequencing gives the message a happens-after edge over the create's guard verdict); step-dispatch idempotency keys are now step-identity-scoped. Disable viaWORKFLOW_RESILIENT_STEP_DISPATCH=0.Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Remove thepreconditionGuardWorld capability. A stale replay-context write no longer needs to be rejected: a reader holds a prefix of the log, replay is deterministic on a prefix, and the writer's next write reports the events it was pushed past.#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.#3479
b589460Thanks @VaguelySerious! - Replay-context event writes now always report the log position they replayed from, and theWORKFLOW_PRECONDITION_GUARDflag is removed.#3410
c1a5c74Thanks @alangenfeld! - Surface typed terminal errors when stream retention expires.#3504
8d8b7b3Thanks @TooTallNate! - Retry 429 (ThrottleError) event writes in-process, honoring the server'sRetry-After, bounded by a 30s cumulative wait budget per write. Previously a throttled event write escaped to the queue handler, whose retry directive can be delayed up to ~5 minutes by queue redelivery scheduling.#3452
01991edThanks @shalabhc! - Restore the per-event client span on the WebSocket events transport (WORKFLOW_EVENTS_TRANSPORT=ws), and add aworkflow.events.ws.connectspan for the handshake. Event write spans now carryworkflow.events.transportandworkflow.event.typeon both transports.Updated dependencies [
600b096,dc85865,efbc408,a0ccfe0,dc85865,7683130,dc85865,b589460,c1a5c74]:@workflow/astro@5.0.0-beta.42
Patch Changes
@workflow/builders@5.0.0-beta.42
Patch Changes
9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,b589460,c1a5c74]:@workflow/cli@5.0.0-beta.42
Patch Changes
600b096,9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,dc85865,b589460,c1a5c74,8d8b7b3,0f4b35f,01991ed]:@workflow/errors@5.0.0-beta.17
Patch Changes
#3479
b589460Thanks @VaguelySerious! - Replay-context event writes now always report the log position they replayed from, and theWORKFLOW_PRECONDITION_GUARDflag is removed.#3410
c1a5c74Thanks @alangenfeld! - Surface typed terminal errors when stream retention expires.@workflow/nest@5.0.0-beta.42
Patch Changes
@workflow/next@5.0.0-beta.42
Patch Changes
9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,b589460,c1a5c74]:@workflow/nitro@5.0.0-beta.42
Patch Changes
9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,b589460,c1a5c74]:@workflow/nuxt@5.0.0-beta.42
Patch Changes
@workflow/rollup@5.0.0-beta.42
Patch Changes
@workflow/sveltekit@5.0.0-beta.42
Patch Changes
@workflow/vite@5.0.0-beta.42
Patch Changes
@workflow/vitest@5.0.0-beta.42
Patch Changes
600b096,9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,dc85865,b589460,c1a5c74,0f4b35f]:@workflow/web@5.0.0-beta.42
Patch Changes
dc85865,0f4b35f]:@workflow/web-shared@5.0.0-beta.42
Patch Changes
#3295
14b52acThanks @mitul-s! - Replace hard-coded shared observability component styles with Tailwind utilities.#3295
14b52acThanks @mitul-s! - Replace static trace viewer styles with Tailwind theme utilities.#3467
834d1f9Thanks @VaguelySerious! - Mark ignored duplicate events in the observability UI and, when the whole event log is loaded, exclude them from derived step status, durations, and trace spansUpdated dependencies [
600b096,9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,dc85865,b589460,c1a5c74]:workflow@5.0.0-beta.42
Patch Changes
9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,b589460,c1a5c74]:@workflow/world-local@5.0.0-beta.36
Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.#3492
0f4b35fThanks @VaguelySerious! - FixCORRUPTED_EVENT_LOGafter a hook resume that raced another writer or was interrupted mid-write, and deliver a raced resume exactly once instead of duplicating it or reporting a conflict.Updated dependencies [
600b096,dc85865,efbc408,a0ccfe0,dc85865,7683130,dc85865,b589460,c1a5c74]:@workflow/world-postgres@5.0.0-beta.34
Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.Updated dependencies [
600b096,dc85865,efbc408,a0ccfe0,dc85865,7683130,dc85865,b589460,c1a5c74,0f4b35f]:@workflow/world-testing@5.0.0-beta.42
Patch Changes
#3519
dc85865Thanks @VaguelySerious! - Slot-numbered event ids are a requirement of the World contract, not a capability. TheslotEventIdsflag is gone, and the conformance suite now fails a World whose event ids are not positions.Updated dependencies [
600b096,9add9d7,dc85865,efbc408,a0ccfe0,dc85865,dc85865,7683130,dc85865,b589460,c1a5c74]: