What Effect-TS/effect shipped

This week in Effect: YAML parsing hardened with Yaml.stringify, a Supervisor for observing fiber lifecycles, PathFilter with glob and IgnoreFile, cluster request retention, and fixes for SqlClient requirements, automatic-yield livelocks and race loser interruption.

This week in Effect: Yaml parsing was hardened and extended with a Yaml.stringify printer, and a Supervisor was added for observing fiber lifecycles so programs can see the fibers they start and what each is waiting on. A general PathFilter module arrived, with FileSystem.glob now taking a filter plus root and new IgnoreFile parsers. Cluster users get opt-in retention that deletes completed requests and their replies. Fixes this week cover SQL driver services being dropped from requirements when SqlClient is provided, automatic-yield livelocks at small MaxOpsBeforeYield budgets, race losers not being interrupted when the race settles, Schema Record entries with transformed keys in equivalence and formatting, and Bun filesystem writes ignoring the cursor after a seek. @effect/opentelemetry

This week: Iterable.unfold and filterMapWhile stay done after completion, Schedule no longer loops on zero delays near window boundaries, and Yaml.parse returns a Result. Plus Json5.parse, Jsonc.parse, SchemaBinary int schemas and HttpClient.timeout.

What shipped in Effect this week: Iterable.unfold and Iterable.filterMapWhile now stay exhausted after completion, Schedule.fixed, windowed and cron no longer return repeated zero delays near a window boundary, and Stream.groupAdjacentBy emits its buffered group before an upstream failure. Yaml.parse now returns a Result like Toml.parse, and Json5.parse and Jsonc.parse are available under effect/encoding. SchemaBinary adds fixed-width int32, uint32, int64 and uint64 schemas, and HttpClient.timeout adds a per-request timeout. Remote libSQL clients can run concurrent statements, DateTime rounding preserves offsets inside a repeated DST hour, and cluster and persistence paths got fixes for transient failures and stalled entities.

This week: cluster shutdown no longer waits on queued persisted workflow activities, HttpClientError output stops exposing request headers, params and body, web server requests now enforce MaxBodySize, Schema.Record works with Enum keys, KeyValueStore gains keys, Redis.reserve an

This week's changes: cluster shutdown no longer holds the entity drain on persisted workflow activities that were saved but never started. HttpClientError serialization stopped exposing request headers, query parameters and body. The web HttpServerRequest now enforces MaxBodySize on buffered reads, matching the Node server. Schema.Record no longer throws for Enum key schemas, and KeyValueStore gained a required keys operation. Redis.reserve leases a dedicated pooled connection so blocking commands do not stall others. OtlpProxy forwards browser OTLP exports with credentials added server side, and the GraphQL generator now handles recursive input objects.

This week in Effect: typed recovery now keeps defects instead of dropping them, ignore options can log unhandled failures, PubSub replay no longer pins values until a full GC, and Deno and Node HTTP fixes stop requests from hanging.

This week in Effect: typed-error recovery now applies defect precedence so a failure holding both a typed error and a defect keeps the defect. The ignore and ignoreCause options on Effect, Stream and Channel gained a log setting for unhandled failures. PubSub replay buffers clear dropped nodes, so values are released without waiting for a full garbage collection. On the platform side, DenoHttpServer answers requests when building a Response throws, NodeHttpClient sends FormData through the installed undici instance, and all adapters share one rule for bodyless statuses and mismatched content-length. Iterable.dedupeAdjacent no longer overflows the stack on long equal runs.

Released effect 4.0.3 and SQL packages 4.0.3. Single-connection SQL clients now hold the shared connection for the whole statement or stream. Workflow callers wake as soon as a result is ready, and aborted web handler requests release their handlers and request scopes.

This week we released effect 4.0.3 and patch versions of the SQL packages. On single-connection SQL clients, the shared connection is now held for the whole statement or stream, so another fiber's transaction can no longer roll back an acknowledged write or expose uncommitted rows to a plain read. Workflow callers that receive Suspended now wake as soon as their workflow has a final result, instead of waiting for the next retry schedule step. We also fixed client abort handling in HttpEffect.toWebHandler so handlers and their request scopes stop running after the client is gone. Smaller fixes cover multipart uploads with dot or long multi-byte file names, UTF-8 BOMs in Node JSON bodies, and redundant taskkill calls on Windows.

Effect 4.0.1 ships fixes for caching interruptions, SQLite statement caching, Stream throttling, and pool idle timeouts. Plus new Cloudflare AI support and @effect/vitest assertion improvements.

Effect 4.0.1 is out with significant reliability improvements across the stack. Caching now properly handles interruptions, SQLite drivers fix statement result issues, database pools measure idle time correctly, and Stream operations respect rate limits. New support for Cloudflare Workers AI and improved test assertions round out the release.

Effect shipped fixes for infinite capacity streams, queued batches, SQL transactions, HTTP routing, and PostgreSQL deadlocks. Plus OpenAPI schema accuracy improvements and Schedule.once.

Effect's latest release addresses critical correctness issues: PubSub now handles infinite capacity properly, queue termination hangs are fixed, SQL transactions fail correctly when rolled back, and HTTP routing no longer interferes between servers. PostgreSQL deadlocks from shard locks are resolved, and OpenAPI schema generation is more accurate. These fixes span data structures, SQL, HTTP, and distributed systems—core reliability concerns for production applications.

Effect@4.0.0-rc.117: Schema JIT/AOT compilers, Entity registration timeouts, PostgreSQL CancelRequest fixes, SQL statement collisions resolved, HTTP QUERY support, and Stream/Effect API alignment.

Effect@4.0.0-rc.117 shipped this week with performance gains across Schema processing through experimental JIT and AOT compilation, critical reliability fixes for distributed entity registration and PostgreSQL connection handling, SQL prepared statement collision prevention, HTTP QUERY method support, and comprehensive alignment of Effect and Stream module APIs with type signature corrections.