Skip to content

workflow@4.8.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 31 Jul 18:13
Immutable release. Only release title and notes can be modified.
workflow@4.8.0
328653a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

@workflow/core@4.8.0

@workflow/world@4.3.1

@workflow/world-local@4.2.4

  • #3215 2fe2d88 @AndrewBarba - Retry transient EPERM unlink failures on Windows when deleting hook and entity JSON files. A concurrent reader briefly holding a file open made deleteJSON throw a share-violation EPERM, which surfaced as a failed operation — for example a failed run.cancel() while deleteAllHooksForRun raced hook polling.

@workflow/world-vercel@4.6.1

  • #3233 7fd2e4a @VaguelySerious - Cancel the v4 event frame stream when a reader stops early, so the response body's undici connection returns to the pool instead of leaking.
  • #2986 72ea6c8 @shalabhc - Enforce a server-supplied per-run event limit (default 25K)
  • #3233 7fd2e4a @VaguelySerious - Event-log requests now multiplex over a single HTTP/2 connection instead of opening one connection per in-flight request
  • #3233 7fd2e4a @VaguelySerious - Raise HTTP/2 receive windows on the events client, slightly decreasing read latency
  • #3233 7fd2e4a @VaguelySerious - Retry stream close on retriable 5xx. Close is idempotent on the server (unlike chunk appends, which keep their no-5xx retry policy), and the server may return retriable 503s expecting the writer to close again.
  • #3233 7fd2e4a @VaguelySerious - Enable HTTP/2 for the events API and stream write requests.
  • #3233 7fd2e4a @VaguelySerious - Unify HTTP request handling into a shared core, extending OTEL client spans, trace-context propagation, and DEBUG logging to the v4 events, stream, and Vercel API request paths

@workflow/web@4.1.16

  • #3233 7fd2e4a @VaguelySerious - Fix run and event observability pages hanging (~16s) and showing no data in the bundled server build, caused by HTTP/2 requests failing to reach node:http2.

@workflow/nitro@4.1.6

  • #3233 7fd2e4a @VaguelySerious - Fix HTTP/2 requests failing in production builds (Vite/Nitro, TanStack Start) where undici's bundled node:http2 could not load and fell back to a stub.

@workflow/sveltekit@4.0.15

  • #3233 7fd2e4a @VaguelySerious - Fix HTTP/2 requests failing in SvelteKit production builds (undici's bundled node:http2 could not load, falling back to a stub).

@workflow/errors@4.2.1

Assets 3
Loading