Version Packages - #4182
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#4182github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Contributor
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 16, 2026 01:16
fccd800 to
4c0e967
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 16, 2026 01:48
4c0e967 to
6164993
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 16, 2026 16:36
6164993 to
06b188b
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 16, 2026 21:50
06b188b to
eabed46
Compare
This branch had an error being deployed
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 stable, this PR will be updated.
Releases
@workflow/astro@4.0.25
Patch Changes
@workflow/builders@4.1.15
Patch Changes
e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32]:@workflow/cli@4.3.14
Patch Changes
3699c30Thanks @TooTallNate! - Add aDataViewreviver so run payloads containing one still hydrate in the observability UI and CLI.42c9810,e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32,42c9810]:@workflow/core@4.8.10
Patch Changes
#4176
e1f712bThanks @pranaygp! - Fix an unhandled rejection that could exit the process when the encryption-key lookup for a forwarded writable stream failed (for example a run metadata read that timed out) before anything was written to that stream. The lookup now starts on the first write, and a failure rejects that stream instead.#4443
3699c30Thanks @TooTallNate! - Serialize aDataViewas the bytes it views. It previously fell through to devalue's built-in encoding, which persists the whole backingArrayBuffer— for a view onto Node's pooledBufferallocator, unrelated process memory.#4422
bc6a97fThanks @TooTallNate! - Retry the max-deliveriesrun_failed/step_failedwrite and the step handler's workflow re-queue through queue redelivery when they fail transiently (429, 5xx, transport) instead of acking and leaving the run stuckrunning.#4408
b23170dThanks @pranaygp! -start()with an explicitdeploymentId(and sorecreateRunFromExisting, i.e. Replay Run) no longer fails in a process that is not itself a deployment; it takes the cross-deployment path instead.#4326
5e6c79cThanks @pranaygp! - MarkWorkflowRunFailedErrorandWorkflowRunCancelledErroras non-retryable, and makeFatalError.is()honor thefatalmarker, so a step that reads a terminal run'sreturnValuefails on its first attempt with the error intact instead of exhausting its retry budget first.#4179
d437c32Thanks @karthikscale3! - Route unrecognized backend connection and stream failures through existing retry policies, rebuilding shared event connections after repeated HTTP/2 failures. Keep invalid backend URLs, blocked ports, and unsupported request headers out of those retries. Include error cause chains in run-failure logs to expose underlying socket, DNS, and TLS failures.Updated dependencies [
42c9810,5e6c79c,d437c32,42c9810]:@workflow/errors@4.2.2
Patch Changes
5e6c79cThanks @pranaygp! - MarkWorkflowRunFailedErrorandWorkflowRunCancelledErroras non-retryable, and makeFatalError.is()honor thefatalmarker, so a step that reads a terminal run'sreturnValuefails on its first attempt with the error intact instead of exhausting its retry budget first.@workflow/nest@4.0.26
Patch Changes
@workflow/next@4.1.14
Patch Changes
#4337
304e5dcThanks @pranaygp! - Fixnext devsometimes running the workflow build (and starting a second watcher) twice on startup when Next.js resetsprocess.envbetweennext.configevaluationsUpdated dependencies [
e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32]:@workflow/nitro@4.1.16
Patch Changes
e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32]:@workflow/nuxt@4.0.26
Patch Changes
@workflow/rollup@4.0.25
Patch Changes
@workflow/sveltekit@4.0.25
Patch Changes
@workflow/vite@4.0.25
Patch Changes
@workflow/vitest@4.0.26
Patch Changes
e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32,42c9810]:@workflow/web-shared@4.1.26
Patch Changes
3699c30Thanks @TooTallNate! - Add aDataViewreviver so run payloads containing one still hydrate in the observability UI and CLI.e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32]:workflow@4.8.10
Patch Changes
e1f712b,3699c30,bc6a97f,304e5dc,b23170d,5e6c79c,d437c32,3699c30]:@workflow/world-local@4.4.2
Patch Changes
#4458
42c9810Thanks @pranaygp! - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.Updated dependencies [
5e6c79c]:@workflow/world-postgres@4.3.8
Patch Changes
#4458
42c9810Thanks @pranaygp! - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.Updated dependencies [
5e6c79c,42c9810]:@workflow/world-testing@4.1.25
Patch Changes
e1f712b,3699c30,bc6a97f,b23170d,5e6c79c,d437c32,3699c30]:@workflow/world-vercel@4.7.5
Patch Changes
#4458
42c9810Thanks @pranaygp! - Send event requests with bodies too large to re-buffer over HTTP/1.1 so they no longer stall behind in-flight HTTP/2 streams, and retry event-log reads whose HTTP/2 stream the peer reset.#4179
d437c32Thanks @karthikscale3! - Route unrecognized backend connection and stream failures through existing retry policies, rebuilding shared event connections after repeated HTTP/2 failures. Keep invalid backend URLs, blocked ports, and unsupported request headers out of those retries. Include error cause chains in run-failure logs to expose underlying socket, DNS, and TLS failures.#4458
42c9810Thanks @pranaygp! - Upgrade undici to 7.30.0, which stops a failed HTTP/2 stream from leaving a phantom in-flight request on its connection.Updated dependencies [
5e6c79c]:@workflow/web@4.1.26