what stackpulse tracks
Effect releases from GitHub
StackPulse watches Effect release notes and keeps the original source link close to every summary.
A fully-fledged functional effect system for TypeScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
what stackpulse tracks
StackPulse watches Effect release notes and keeps the original source link close to every summary.
upgrade risk
Risky changes are separated from normal feature notes so you can scan upgrade impact before changing production dependencies.
migration notes
Migration steps and recommended actions are only shown when the upstream release notes support them.
This patch release updates the package’s Effect dependency to effect@4.1.4. The release notes provide no further details about the dependency changes.
Users of @effect/vitest are affected through its updated Effect dependency.
This patch release updates the package's dependencies, including effect@4.1.4. The release notes provide no further details about the dependency changes.
Users of @effect/sql-sqlite-wasm receive updated dependencies, including effect@4.1.4.
This patch release updates the package’s dependencies, including effect to version 4.1.4. The release notes provide no further details about the changes.
Users of @effect/sql-sqlite-react-native receive updated dependencies, but the specific impact is not described.
This patch release updates the `effect` dependency to version 4.1.4. The release notes provide no further details about changes included in that dependency update.
Users of `@effect/sql-sqlite-node` receive an updated `effect` dependency; specific behavior changes are not described.
This patch adds AI authentication and structured-output helpers, HTTP API tracing redaction annotations, and additional schema inspection APIs, while restoring MCP Skills support on supported protocol revisions. It also includes fixes across the CLI, schema generation, AI clients, and TestClock; OpenRouter schema updates introduce compatibility-breaking changes for generated exports, data, and fixtures.
OpenRouter schema consumers and fixtures may require updates, while AI integrations, HTTP API tracing users, MCP Skills users, and CLI users receive new helpers or fixes.
If you consume the affected OpenRouter schemas, update removed-export references and ensure data and fixtures include the newly required fields.
This patch release updates @effect/vitest’s dependency on effect to version 4.1.3. The release notes provide no further details about changes included in that dependency update.
Users of @effect/vitest receive the updated effect@4.1.3 dependency; any other impact is unclear from the release notes.
This patch fixes a runtime failure when providing a generic `SqlClient` layer: the effect could incorrectly appear runnable after a driver service requirement was removed, then fail with `Service not found`. Driver clients are no longer subtypes of `SqlClient.SqlClient`; the release also updates the dependency to `effect@4.1.3`.
Users providing generic SQL client layers, especially those selecting between driver layers, may need to adjust type annotations; the fix prevents a runtime `Service not found` failure.
Review code that selects between driver layers and add the documented explicit layer annotation if required.
This patch fixes a runtime `Service not found` failure when providing a generic `SqlClient` layer that removes a driver service from an effect's requirements. It also changes the type relationship so driver clients are no longer subtypes of `SqlClient.SqlClient`; code selecting between driver layers may need an explicit layer type annotation.
Users providing generic SQL client layers or selecting between driver layers may be affected, particularly if their code relied on the former subtype relationship.
Check conditional or otherwise combined driver-layer expressions and add the documented explicit layer annotation if required.
This patch fixes a runtime `Service not found` failure where providing a generic `SqlClient` layer incorrectly removed a driver service from an effect’s requirements. Driver clients are no longer subtypes of `SqlClient.SqlClient`; conditional selection between driver layers may require an explicit layer type annotation. The release also updates the `effect` dependency to 4.1.3.
Users providing generic SQL client layers, especially those conditionally selecting between database driver layers, may need to update type annotations to avoid runtime service lookup failures.
Review generic SQL client layer usage and add the stated explicit layer annotation where driver-layer selection requires it.
Effect 4.1.3 adds exact rational numbers and schema codecs, experimental AG-UI and Cloudflare Cluster support, and richer CLI command metadata. It also includes numerous fixes across CLI completions, workflows, HTTP handling, codecs, and other modules; the provided release notes end mid-entry, so this summary covers only the visible content.
The release affects Effect users adopting the new numeric, AI, CLI, and Cluster APIs, as well as applications using custom message storage or affected CLI error typing.
Review the `MessageStorage` and CLI error-type changes before upgrading, and meet the stated MySQL/MariaDB requirements if using SQL message storage.
This patch release updates @effect/vitest’s dependency on effect to version 4.1.2. The release notes provide no further details about changes included in that dependency update.
Users of @effect/vitest receive the updated effect@4.1.2 dependency.
This patch release updates dependencies, including effect@4.1.2. The notes provide no additional details about behavior changes or other package-specific updates.
Users of @effect/sql-sqlite-wasm receive the updated effect dependency.
This patch release updates the package's dependency on effect to version 4.1.2. The notes provide no details about changes beyond the dependency update.
Users of @effect/sql-sqlite-react-native are affected through its updated effect dependency.
This patch release updates the package’s dependencies, including effect@4.1.2. The notes do not describe any package-specific changes.
Users of @effect/sql-sqlite-node receive updated dependencies, including effect@4.1.2.
This patch release adds JSON5 and JSONC parsing and opt-in fixed-width integer schemas, alongside broad fixes across clustering, workflows, MCP, HTTP, iterators, and other modules. It also improves SQL transaction tracing and corrects behaviors involving fractional byte quantities, Redis rate-limiter key isolation, and idle OTLP exporters.
Effect users relying on the affected utilities, clustering and workflow engines, HTTP and MCP clients or servers, SQL tracing, and binary schemas may benefit from these fixes and additions.
Upgrade to 4.1.2 to receive the fixes and opt-in additions; review SQL tracing dashboards or consumers if they depend on the replaced transaction events.
This patch release updates the package’s Effect dependency to effect@4.1.1. The release notes provide no details about the underlying changes.
Users of @effect/vitest receive the updated effect@4.1.1 dependency.
This patch release updates the package's dependency on effect to version 4.1.1. The release notes do not describe specific package-level changes.
Users of @effect/sql-sqlite-wasm receive the updated effect dependency; no further impact is specified.
This patch release updates the package’s dependency on effect to version 4.1.1. The release notes do not describe any package-specific features, fixes, or other changes.
Users of @effect/sql-sqlite-react-native receive the updated effect@4.1.1 dependency.
This patch release updates the package’s dependency on effect to version 4.1.1. The release notes provide no further details about functional changes.
Users of @effect/sql-sqlite-node receive the updated effect@4.1.1 dependency.
This patch release fixes bugs across atom subscriptions, schemas, migrations, cluster persistence, DateTime, and other APIs, and improves Base64Url decoding and DateTime construction. It also adds circuit-breaker controls and limits BigDecimal scales and buffered HTTP request bodies to reduce resource-exhaustion risks.
Users of BigDecimal, buffered HTTP request handling, EventLog authentication, circuit breakers, atoms, and cluster persistence may be affected by the fixes and behavior changes.
Review BigDecimal inputs and scale-alignment operations for values beyond the new limits before upgrading.