Version Packages (beta) - #3216
Closed
github-actions[bot] wants to merge 0 commit into
Closed
Conversation
Contributor
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 19:24
65b6e27 to
f05f642
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 20:19
2f96d43 to
9cc11f5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 30, 2026 20:39
58dced0 to
8bda7ce
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
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/core@5.0.0-beta.39
Minor Changes
#3186
4a9d26bThanks @alangenfeld! - Record the compute instance that ran each step attempt:CreateEventParams.computeInstanceIdis stamped onstep_startedwrites, forwarded in the world-vercel v4 frame meta alongsidevercelId, read back onAnalyticsEvent/AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.#2989
9cc11f5Thanks @alangenfeld! - Emit afaas.instanceOTEL span attribute (a synthesized per-warm-instance id) on the flow and step route spans, so traces can distinguish which compute instance handled each request.Patch Changes
4a9d26b,c93f6f7,f05f642]:@workflow/web-shared@5.0.0-beta.39
Minor Changes
4a9d26bThanks @alangenfeld! - Record the compute instance that ran each step attempt:CreateEventParams.computeInstanceIdis stamped onstep_startedwrites, forwarded in the world-vercel v4 frame meta alongsidevercelId, read back onAnalyticsEvent/AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.Patch Changes
4a9d26b,9cc11f5]:@workflow/world@5.0.0-beta.24
Minor Changes
4a9d26bThanks @alangenfeld! - Record the compute instance that ran each step attempt:CreateEventParams.computeInstanceIdis stamped onstep_startedwrites, forwarded in the world-vercel v4 frame meta alongsidevercelId, read back onAnalyticsEvent/AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.@workflow/world-vercel@5.0.0-beta.35
Minor Changes
4a9d26bThanks @alangenfeld! - Record the compute instance that ran each step attempt:CreateEventParams.computeInstanceIdis stamped onstep_startedwrites, forwarded in the world-vercel v4 frame meta alongsidevercelId, read back onAnalyticsEvent/AnalyticsStep, and surfaced as "Compute Instance ID" in the observability attribute panel.Patch Changes
#3212
c93f6f7Thanks @VaguelySerious! - Raise HTTP/2 receive windows on the events client, slightly decreasing read latencyUpdated dependencies [
4a9d26b]:@workflow/astro@5.0.0-beta.39
Patch Changes
@workflow/builders@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5]:@workflow/cli@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5,c93f6f7,f05f642]:@workflow/nest@5.0.0-beta.39
Patch Changes
@workflow/next@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5]:@workflow/nitro@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5]:@workflow/nuxt@5.0.0-beta.39
Patch Changes
@workflow/rollup@5.0.0-beta.39
Patch Changes
@workflow/sveltekit@5.0.0-beta.39
Patch Changes
@workflow/vite@5.0.0-beta.39
Patch Changes
@workflow/vitest@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5,f05f642]:@workflow/web@5.0.0-beta.39
Patch Changes
f05f642]:workflow@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5]:@workflow/world-local@5.0.0-beta.33
Patch Changes
#3215
f05f642Thanks @AndrewBarba! - Retry transientEPERMunlink failures on Windows when deleting hook and entity JSON files. A concurrent reader briefly holding a file open madedeleteJSONthrow a share-violationEPERM, which surfaced as a failed operation — for example a failedrun.cancel()whiledeleteAllHooksForRunraced hook polling.Updated dependencies [
4a9d26b]:@workflow/world-postgres@5.0.0-beta.31
Patch Changes
4a9d26b,f05f642]:@workflow/world-testing@5.0.0-beta.39
Patch Changes
4a9d26b,9cc11f5]: