Version Packages - #4092
Merged
Merged
Version Packages#4092
Conversation
Contributor
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 11, 2026 16:00
5badacf to
ee927eb
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 11, 2026 17:24
5a064c8 to
75c5904
Compare
github-actions
Bot
force-pushed
the
changeset-release/stable
branch
from
September 11, 2026 20:17
75c5904 to
205b519
Compare
VaguelySerious
approved these changes
Sep 15, 2026
Contributor
Author
🧪 E2E Test Results❌ Some tests failed Summary
❌ Failed Tests🌍 Community Worlds (106 failed)redis (21 failed):
turso (85 failed):
Details by Category✅ ▲ Vercel Production
✅ 💻 Local Development
✅ 📦 Local Production
✅ 🐘 Local Postgres
✅ 🪟 Windows
❌ 🌍 Community Worlds
✅ 📋 Other
|
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
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/astro@4.0.24
Patch Changes
46851a3]:@workflow/builders@4.1.14
Patch Changes
#3795
46851a3Thanks @TooTallNate! - Deduplicate identical pnpm peer-variant copies of a package instead of failing the build with a duplicate step/workflow ID error. Different implementations that map to the same ID still fail.Updated dependencies [
b7385f0,284d7c0,a158f81]:@workflow/cli@4.3.13
Patch Changes
b7385f0,46851a3,284d7c0,a158f81]:@workflow/core@4.8.9
Patch Changes
#3882
b7385f0Thanks @ctgowrie! - Stop framed stream reconnects after the consumer cancels, including while completion checks or reconnect acquisition are still pending.#3843
284d7c0Thanks @Rich-Harris! - Bumpdevalueto 5.9.2 to address published security advisory.#4070
a158f81Thanks @torsello! - Allow parentheses and square brackets in workflow namesA workflow name is derived from the module path it is defined in, so Next.js App
Router conventions end up in the name verbatim.
SAFE_WORKFLOW_NAME_PATTERNdidnot permit
(,),[or], so any workflow inside a route group(
app/(dashboard)/…) or a dynamic segment (app/[teamId]/…,app/[...slug]/…)threw
Invalid workflow namebefore it could be enqueued, with no way tooverride the generated name.
These characters are inert in the queue name the pattern guards:
ValidQueueNamealready accepts any suffix after its prefix, and the name is never interpolated
into a URL or a SQL identifier.
@workflow/nest@4.0.25
Patch Changes
46851a3]:@workflow/next@4.1.13
Patch Changes
b7385f0,46851a3,284d7c0,a158f81]:@workflow/nitro@4.1.15
Patch Changes
b7385f0,46851a3,284d7c0,a158f81]:@workflow/nuxt@4.0.25
Patch Changes
@workflow/rollup@4.0.24
Patch Changes
46851a3]:@workflow/sveltekit@4.0.24
Patch Changes
46851a3]:@workflow/vite@4.0.24
Patch Changes
46851a3]:@workflow/vitest@4.0.25
Patch Changes
b7385f0,46851a3,284d7c0,a158f81]:@workflow/web-shared@4.1.25
Patch Changes
b7385f0,284d7c0,a158f81]:workflow@4.8.9
Patch Changes
b7385f0,284d7c0,a158f81]:@workflow/world-postgres@4.3.7
Patch Changes
#4111
f72c6a6Thanks @komly! - Fix run creation and slot allocation not happening transactionally#4114
9595a5aThanks @komly! - Queue deliveries no longer inheritfetch's 300s headers/body deadlines, which redelivered healthy long-running inline work while it was still executing. Deadlines can be set withWORKFLOW_POSTGRES_HEADERS_TIMEOUT_MSandWORKFLOW_POSTGRES_BODY_TIMEOUT_MS.#4117
ee29d15Thanks @komly! - Preserve error names, messages, stacks, and nested causes in Graphile Worker log metadata.#4113
73465bcThanks @komly! - Fix stream cursors not being advanced for skipped chunks, so repeated notifications cannot consume the requested start offset twice#4125
d86d752Thanks @VaguelySerious! - Fix stream readers leaking EventEmitter listeners on EOF, initial query failure, and World close, and fail pending readers when the World is closed.#3712
e3862bcThanks @himself65! - FixreadFromStreamerroring when rows were written after the stream's first EOF marker. Rows past the first EOF are now ignored consistently acrossreadFromStream(),getStreamChunks(), andgetStreamInfo().@workflow/world-testing@4.1.24
Patch Changes
b7385f0,284d7c0,a158f81]:@workflow/web@4.1.25