Version Packages (beta)#2788
Closed
github-actions[bot] wants to merge 2 commits into
Closed
Conversation
Contributor
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
6df144d to
8a76688
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
c79efbc to
239031a
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
2 participants
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.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.Updated dependencies [
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/builders@5.0.0-beta.28
Patch Changes
#2799
2ca34acThanks @NathanColosimo! - Fix SvelteKit production server crash at boot if a world package pulls cosmiconfig into the server bundle.#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
c1d29f1,c1d29f1,7637196,7637196,239031a,0f557d5,49a50e8,03862ed]:@workflow/cli@5.0.0-beta.28
Patch Changes
#2648
17d4ce2Thanks @karthikscale3! -inspectlist views (runs, steps, events, sleeps) now read from the optionalworld.analyticsnamespace when the backend provides one, falling back to the runtime storage APIs otherwise. Hook listing stays on the runtime storage APIs (the analytics rows omitownerIdand the hook token). Payload/detail views are unchanged. The--withDataflag is deprecated for list views; useworkflow inspect <resource> <id>to view payloads for a single resource.#2806
54f46f9Thanks @karthikscale3! - Ensure the CLI can resolve community world packages if not statically injected. Fixes "Unsupported workflow backend" error.Updated dependencies [
2ca34ac,c1d29f1,c1d29f1,7637196,7637196,239031a,0f557d5,1518c48,ae51f45,cdfac39,49a50e8,03862ed]:@workflow/core@5.0.0-beta.28
Patch Changes
#2779
7637196Thanks @VaguelySerious! - FixcreateHook()conflicting with the run's own disposed hook when a token is reused afterdispose()within the same run#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
c1d29f1,c1d29f1,7637196,239031a,0f557d5,49a50e8,03862ed]:@workflow/errors@5.0.0-beta.10
Patch Changes
239031a,0f557d5]:@workflow/nest@5.0.0-beta.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/next@5.0.0-beta.28
Patch Changes
#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
2ca34ac,7637196,239031a,0f557d5,49a50e8]:@workflow/nitro@5.0.0-beta.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.Updated dependencies [
2ca34ac,7637196,239031a,0f557d5,1518c48,ae51f45,cdfac39,49a50e8]:@workflow/nuxt@5.0.0-beta.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.Updated dependencies [
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/rollup@5.0.0-beta.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.Updated dependencies [
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/sveltekit@5.0.0-beta.28
Patch Changes
#2799
2ca34acThanks @NathanColosimo! - Fix SvelteKit production server crash at boot if a world package pulls cosmiconfig into the server bundle.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.Updated dependencies [
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/utils@5.0.0-beta.6
Patch Changes
#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.@workflow/vite@5.0.0-beta.28
Patch Changes
2ca34ac,239031a,0f557d5,49a50e8]:@workflow/vitest@5.0.0-beta.28
Patch Changes
2ca34ac,c1d29f1,c1d29f1,7637196,7637196,239031a,0f557d5,49a50e8]:@workflow/web@5.0.0-beta.28
Patch Changes
#2647
1518c48Thanks @karthikscale3! - The runs, steps, and events observability list views now read from themetadata-only
world.analyticsnamespace when the configured backend providesone, and fall back to the runtime storage APIs otherwise. Event payloads are
still loaded lazily per event on the runtime path. Hooks listing, detail views,
payload resolution, streams, and mutations are unchanged.
#2652
ae51f45Thanks @karthikscale3! - The hooks list now reads from the metadata-onlyworld.analyticsnamespace when the backend provides one (falling back to the runtime storage APIs otherwise). A hook's secret token is no longer included in list rows — it is fetched one hook at a time viaworld.hooks.getonly when the user copies the token or resumes the hook.#2804
cdfac39Thanks @karthikscale3! - Fixworkflow webfor local and postgres backends after static world-target injection. The web server now constructs the local world directly and resolves other world packages from the inspected project, instead of calling thecreateWorld()static-injection stub (which throws when no build plugin aliased it).Updated dependencies [
c1d29f1,c1d29f1,7637196,239031a,0f557d5,49a50e8]:@workflow/web-shared@5.0.0-beta.28
Patch Changes
#2775
8a76688Thanks @mitul-s! - Fix duplicate sub-second tick labels on the trace viewer timeline ruler, and trim trailing zeros from precise duration labels ("2.00s" → "2s").Updated dependencies [
7637196,239031a,0f557d5,49a50e8]:workflow@5.0.0-beta.28
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
17d4ce2,54f46f9,2ca34ac,7637196,239031a,0f557d5,49a50e8]:@workflow/world-local@5.0.0-beta.24
Patch Changes
#2808
c1d29f1Thanks @VaguelySerious! - Fix a stalled hook token claim release deleting the next claimant's live claim#2808
c1d29f1Thanks @VaguelySerious! - Fix aresumeHookracinghook.dispose()being recorded after the disposal, which corrupted the receiving run's replay#2779
7637196Thanks @VaguelySerious! - Fix hook token claims of disposed hooks and finished runs not being released to the next claimant#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
239031a,0f557d5]:@workflow/world-postgres@5.0.0-beta.22
Patch Changes
#2732
239031aThanks @NathanColosimo! - Respect framework base paths when routing workflow traffic and expose health checks on generated Next.js workflow routes.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.Updated dependencies [
c1d29f1,c1d29f1,7637196,239031a,0f557d5,49a50e8]:@workflow/world-testing@5.0.0-beta.28
Patch Changes
17d4ce2,54f46f9,c1d29f1,c1d29f1,7637196,7637196,239031a,0f557d5,49a50e8]:@workflow/world-vercel@5.0.0-beta.24
Patch Changes
#2752
0f557d5Thanks @ijjk! - Statically inject the configured world package into host bundles instead of selecting worlds dynamically at runtime.#2468
49a50e8Thanks @NathanColosimo! - Standardize first-party World packages oncreateWorld(), support relative target World modules consistently, and align the Postgres WorldDATABASE_URLfallback with bootstrap.#2789
03862edThanks @TooTallNate! - Send thex-vercel-queue-regionheader on proxy-mode queue sends so they route to the region's VQS dataplane host like direct in-function sends do.Updated dependencies []: