Version Packages - #3105
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
July 25, 2026 00:01
dcf5562 to
1ad7866
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
July 28, 2026 21:15
47e7f3e to
17d4be9
Compare
VaguelySerious
approved these changes
Jul 28, 2026
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
1 participant
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 stable, this PR will be updated.
Releases
@workflow/core@4.7.0
Minor Changes
12e4ef7Thanks @VaguelySerious! - Add an optimistic-concurrency guard for event creation (on by default; opt out withWORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send astateUpdatedAtsnapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.Patch Changes
12e4ef7,9d8b293]:@workflow/errors@4.2.0
Minor Changes
12e4ef7Thanks @VaguelySerious! - Add an optimistic-concurrency guard for event creation (on by default; opt out withWORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send astateUpdatedAtsnapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.workflow@4.7.0
Minor Changes
12e4ef7Thanks @VaguelySerious! - Add an optimistic-concurrency guard for event creation (on by default; opt out withWORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send astateUpdatedAtsnapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.Patch Changes
12e4ef7,f2714c5]:@workflow/world@4.3.0
Minor Changes
12e4ef7Thanks @VaguelySerious! - Add an optimistic-concurrency guard for event creation (on by default; opt out withWORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send astateUpdatedAtsnapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.@workflow/world-vercel@4.6.0
Minor Changes
12e4ef7Thanks @VaguelySerious! - Add an optimistic-concurrency guard for event creation (on by default; opt out withWORKFLOW_PRECONDITION_GUARD=0): replay-context event creations send astateUpdatedAtsnapshot timestamp, and the runtime reloads the event log and retries (then falls back to a fresh re-invocation) when the backend reports a newer out-of-band event with a 412PreconditionFailedError. Backends without guard support ignore the snapshot, so this is backward-compatible and fails open.Patch Changes
#3169
9d8b293Thanks @VaguelySerious! - Bound HTTP requests with a 30s headers/body timeout instead of undici's 5-minute default, and retry transport timeouts and other transient failures in-process, so a stalled connection no longer leaves a run silently paused for ~5 minutes until the queue redelivers it. Override withWORKFLOW_VERCEL_HEADERS_TIMEOUT_MS/WORKFLOW_VERCEL_BODY_TIMEOUT_MS.Updated dependencies [
12e4ef7]:@workflow/astro@4.0.14
Patch Changes
#3166
f2714c5Thanks @TooTallNate! - The generated webhook route now passes the incoming request directly to its handler instead of copying it into a newRequest, so the request body is no longer read before the handler runs.Updated dependencies []:
@workflow/builders@4.1.4
Patch Changes
12e4ef7]:@workflow/cli@4.3.3
Patch Changes
12e4ef7,9d8b293]:@workflow/nest@4.0.15
Patch Changes
@workflow/next@4.1.3
Patch Changes
12e4ef7]:@workflow/nitro@4.1.5
Patch Changes
12e4ef7]:@workflow/nuxt@4.0.15
Patch Changes
@workflow/rollup@4.0.14
Patch Changes
@workflow/sveltekit@4.0.14
Patch Changes
#3166
f2714c5Thanks @TooTallNate! - The generated webhook route now passes the incoming request directly to its handler instead of copying it into a newRequest, so the request body is no longer read before the handler runs.Updated dependencies []:
@workflow/vite@4.0.14
Patch Changes
@workflow/vitest@4.0.15
Patch Changes
12e4ef7]:@workflow/web-shared@4.1.15
Patch Changes
12e4ef7]:@workflow/world-local@4.2.3
Patch Changes
12e4ef7]:@workflow/world-postgres@4.3.2
Patch Changes
12e4ef7]:@workflow/world-testing@4.1.14
Patch Changes
#3055
c77a82dThanks @VaguelySerious! - Fix flaky Local World tests caused by concurrent test servers sharing one data directory and re-enqueuing each other's in-flight runs on startupUpdated dependencies [
12e4ef7]:@workflow/web@4.1.15