Version Packages (beta) - #332
Closed
github-actions[bot] wants to merge 0 commit into
Closed
Conversation
github-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 9, 2026 14:08
1af78fa to
f20c706Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 10, 2026 11:56
a74d9c0 to
72911f7Comparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 11, 2026 04:06
9c3f9f5 to
09a0c1dComparegithub-actionsBotforce-pushed
the
changeset-release/main
branch
from
May 15, 2026 23:05
a787ac5 to
4753abbCompare
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 freeto 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/astro@5.0.0-beta.6
Patch Changes
@workflow/builders@5.0.0-beta.6
Patch Changes
@workflow/cli@5.0.0-beta.6
Patch Changes
c145bf5,22b5a12]:@workflow/core@5.0.0-beta.6
Patch Changes
c145bf5,22b5a12]:@workflow/nest@5.0.0-beta.6
Patch Changes
@workflow/next@5.0.0-beta.6
Patch Changes
@workflow/nitro@5.0.0-beta.6
Patch Changes
@workflow/nuxt@5.0.0-beta.6
Patch Changes
@workflow/rollup@5.0.0-beta.6
Patch Changes
@workflow/sveltekit@5.0.0-beta.6
Patch Changes
#1995
4753abbThanks @pranaygp! - Fix duplicate Workflow queue consumers in SvelteKit deployments by removing stale workflow queue triggers from shared Vercel function configs.Updated dependencies []:
@workflow/vite@5.0.0-beta.6
Patch Changes
@workflow/vitest@5.0.0-beta.6
Patch Changes
c145bf5]:@workflow/web-shared@5.0.0-beta.6
Patch Changes
workflow@5.0.0-beta.6
Patch Changes
4753abb]:@workflow/world-local@5.0.0-beta.5
Patch Changes
c145bf5Thanks @pranaygp! - Improve the local queue error message when a Next.js proxy intercepts workflow routes.@workflow/world-postgres@5.0.0-beta.5
Patch Changes
c145bf5]:@workflow/world-testing@5.0.0-beta.6
Patch Changes
@workflow/world-vercel@5.0.0-beta.5
Patch Changes
22b5a12Thanks @karthikscale3! - Update to new queue client version@workflow/web@5.0.0-beta.6
tarballs@0.0.1-beta.1
Patch Changes
c145bf5,4753abb,22b5a12]: