Bump the dependencies group with 3 updates

[dependabot]

Bumps the dependencies group with 3 updates: @effect/platform-node, effect and adamantite.

Updates @effect/platform-node from 4.0.0-rc.108 to 4.0.0-rc.109

Release notes

Sourced from @​effect/platform-node's releases.

@​effect/platform-node@​4.0.0-rc.109

Patch Changes

• #7221 d8d3fdc Thanks @​WikiRik! - Migrate NodeRedis from ioredis to redis (node-redis), replacing the peer dependency with redis: >=5.0.0 <7.0.0.

  layer and layerConfig now accept RedisClientOptions: socket settings move under socket, db becomes database, command methods are camelCase, and arbitrary commands use sendCommand. Protocol selection follows the installed node-redis version's default.

  Layers connect while being built and can fail with RedisError. Initial connections fail fast unless a socket.reconnectStrategy is provided; after ready, the default reconnect behavior applies. Scope finalization uses close(), so in-flight or blocking commands can delay closure.

• Updated dependencies [a0743f2, 17892e7, 4d8a230, 2ae5a96, f21f9c9, 18270dd, 26db404, 2670398, 3702bed, ccae60e, 6ff5396]:

  • effect@4.0.0-rc.109
  • @​effect/platform-node-shared@​4.0.0-rc.109

@​effect/platform-node-shared@​4.0.0-rc.109

Patch Changes

• #7233 2ae5a96 Thanks @​AnnaSuSu! - Enforce zero-byte limits when consuming Node readable streams.
• Updated dependencies [a0743f2, 17892e7, 4d8a230, f21f9c9, 18270dd, 26db404, 2670398, 3702bed, ccae60e, 6ff5396]:
  • effect@4.0.0-rc.109

Commits

• See full diff in compare view

Updates effect from 4.0.0-rc.108 to 4.0.0-rc.109

Release notes

Sourced from effect's releases.

effect@4.0.0-rc.109

Patch Changes

• #7219 a0743f2 Thanks @​tim-smart! - Add SQL, HttpApi testing, and CLI schema examples to the published AI documentation.

• #7241 17892e7 Thanks @​tim-smart! - Use Context mapUnsafe in less call sites

• #7240 4d8a230 Thanks @​tim-smart! - Fix Effect.fromOption data-first inference for inline Option expressions.

• #7216 f21f9c9 Thanks @​tim-smart! - Add a HttpStatus module to effect/unstable/http that centralizes the mapping from HTTP status literal names to numeric codes and exports HttpStatus.fromLiteral. HttpApiSchema.status now consumes the new module.

• #6829 18270dd Thanks @​lloydrichards! - MCP servers now support the 2024-11-05 and 2025-03-26 RPC revisions through version-specific protocol adapters.

• #7218 26db404 Thanks @​tim-smart! - Run SQL PersistedQueue table creation through versioned migrations so future schema changes can be applied safely.

• #7210 2670398 Thanks @​tim-smart! - Preserve nanosecond precision when adjusting TestClock with large durations.

• #7205 3702bed Thanks @​tim-smart! - Remove the kubernetes-types dependency by vendoring the Kubernetes Pod declarations used by the cluster helpers and exporting them from effect/unstable/cluster/K8sTypes.

• #7236 ccae60e Thanks @​roninjin10! - Propagate a failed BEGIN or SAVEPOINT from SqlClient.withTransaction as a typed SqlError.

  makeWithTransaction wrapped the begin step together with the transaction body, so a failed BEGIN took the rollback branch. No transaction was active at that point, the ROLLBACK failed, and its Effect.orDie wrapper replaced the original typed error with a defect (cannot rollback - no transaction is active). Callers could no longer classify the failure as retryable. The path became reachable when the sqlite client started using BEGIN IMMEDIATE, which acquires a write lock and can fail with SQLITE_BUSY.

  Commit and rollback now run only after begin or savepoint succeeds. A failed begin or savepoint fails with its original SqlError, leaves the wrapped effect unexecuted, and still closes the acquired connection scope.

• #7206 6ff5396 Thanks @​tim-smart! - Bound cluster runner entity residency and storage reads.

  ShardingConfig gains two knobs:

  • maxResidentEntities (default 10_000): the maximum number of entities that can be resident on a runner at the same time. At the cap, the storage read loop stops admitting messages for new entity addresses (they stay in storage until a slot frees up) and volatile sends to new addresses fail with MailboxFull. Persisted sends still succeed. "unbounded" restores the previous behaviour and can only be set programmatically.
  • unprocessedMessageBatchSize (default 1024): the maximum number of unprocessed messages read from storage in a single poll.

  MessageStorage.unprocessedMessages accepts an optional { limit, addresses } argument, and only claims the messages it actually returns. The memory implementation now applies the same ten-minute claim window as SQL, so bounded reads advance past in-flight requests; resetting an address or shard makes its claimed messages immediately eligible again.

... (truncated)

Changelog

Sourced from effect's changelog.

4.0.0-rc.109

Patch Changes

• #7219 a0743f2 Thanks @​tim-smart! - Add SQL, HttpApi testing, and CLI schema examples to the published AI documentation.

• #7241 17892e7 Thanks @​tim-smart! - Use Context mapUnsafe in less call sites

• #7240 4d8a230 Thanks @​tim-smart! - Fix Effect.fromOption data-first inference for inline Option expressions.

• #7216 f21f9c9 Thanks @​tim-smart! - Add a HttpStatus module to effect/unstable/http that centralizes the mapping from HTTP status literal names to numeric codes and exports HttpStatus.fromLiteral. HttpApiSchema.status now consumes the new module.

• #6829 18270dd Thanks @​lloydrichards! - MCP servers now support the 2024-11-05 and 2025-03-26 RPC revisions through version-specific protocol adapters.

• #7218 26db404 Thanks @​tim-smart! - Run SQL PersistedQueue table creation through versioned migrations so future schema changes can be applied safely.

• #7210 2670398 Thanks @​tim-smart! - Preserve nanosecond precision when adjusting TestClock with large durations.

• #7205 3702bed Thanks @​tim-smart! - Remove the kubernetes-types dependency by vendoring the Kubernetes Pod declarations used by the cluster helpers and exporting them from effect/unstable/cluster/K8sTypes.

• #7236 ccae60e Thanks @​roninjin10! - Propagate a failed BEGIN or SAVEPOINT from SqlClient.withTransaction as a typed SqlError.

  makeWithTransaction wrapped the begin step together with the transaction body, so a failed BEGIN took the rollback branch. No transaction was active at that point, the ROLLBACK failed, and its Effect.orDie wrapper replaced the original typed error with a defect (cannot rollback - no transaction is active). Callers could no longer classify the failure as retryable. The path became reachable when the sqlite client started using BEGIN IMMEDIATE, which acquires a write lock and can fail with SQLITE_BUSY.

  Commit and rollback now run only after begin or savepoint succeeds. A failed begin or savepoint fails with its original SqlError, leaves the wrapped effect unexecuted, and still closes the acquired connection scope.

• #7206 6ff5396 Thanks @​tim-smart! - Bound cluster runner entity residency and storage reads.

  ShardingConfig gains two knobs:

  • maxResidentEntities (default 10_000): the maximum number of entities that can be resident on a runner at the same time. At the cap, the storage read loop stops admitting messages for new entity addresses (they stay in storage until a slot frees up) and volatile sends to new addresses fail with MailboxFull. Persisted sends still succeed. "unbounded" restores the previous behaviour and can only be set programmatically.
  • unprocessedMessageBatchSize (default 1024): the maximum number of unprocessed messages read from storage in a single poll.

  MessageStorage.unprocessedMessages accepts an optional { limit, addresses } argument, and only claims the messages it actually returns. The memory implementation now applies the same ten-minute claim window as SQL, so bounded reads advance past in-flight requests; resetting an

... (truncated)

Commits

• b5946ec Version Packages (rc) (#7211)
• 17892e7 Use Context mapUnsafe in less call sites (#7241)
• 4d8a230 Fix Effect.fromOption inline inference (#7240)
• ccae60e fix(sql): propagate a failed transaction begin as a typed error (#7236)
• 18270dd feat: add mcp core for protocol versions (#6829)
• 3fba454 Use handleAll in HttpApi examples (#7225)
• 7018f96 Stabilize DurableDeferred race replay test (#7220)
• 26db404 Use migrations for SQL persisted queues (#7218)
• f21f9c9 Add HttpStatus module with fromLiteral and centralize status mappings (#7216)
• 6ff5396 feat(cluster): bound runner entity residency and storage reads (#7206)
• Additional commits viewable in compare view

Updates adamantite from 0.34.4 to 0.35.0

Changelog

Sourced from adamantite's changelog.

0.35.0

Minor Changes

• #360 8782acf Thanks @​adelrodriguez! - Support Bun 1.0 and Node.js 22.19 or later while using current runtimes for development.

  Generated GitHub Actions workflows now follow the target project's Node.js version declaration (.node-version, .nvmrc, .tool-versions, or package.json) through node-version-file, and fall back to node-version: "lts/*" when no declaration exists. adamantite update migrates existing managed workflows away from a hard-coded Node.js version.

• #361 04f5494 Thanks @​adelrodriguez! - Skip root tsconfig.json creation and updates during init in a detected monorepo. A catch-all root config makes TypeScript treat all workspace packages as one project and can try to emit over JavaScript input files. In a monorepo, init --typescript now prints guidance to add "extends": "adamantite/typescript" to each package's tsconfig.json or to a shared base config, and does not change any files.

  Stop overwriting an existing extends value when init updates a tsconfig.json. Adamantite now appends "adamantite/typescript" to the extends array instead, so a shared base config such as "@company/tsconfig" stays in place. The preset is appended last, so its compiler options override the earlier entries.

  The adamantite/typescript preset now sets "noEmit": true, so projects that extend it type-check without emitting output. If your project emits output with tsc through the preset, set "noEmit": false in your own tsconfig.json.

Patch Changes

• #370 dfb307b Thanks @​adelrodriguez! - Stop init from silently overwriting existing package scripts. Scripts whose commands differ from Adamantite's managed commands are now kept and reported: the interactive initializer asks once before overwriting, and non-interactive runs preserve them unless the new --overwrite-scripts flag is passed. Preserved scripts are omitted from AGENTS.md guidance.

• #369 943a1a9 Thanks @​adelrodriguez! - Skip root tsconfig.json creation and updates in the legacy-typecheck-script migration when a monorepo is detected. The migration, reachable through adamantite update and adamantite doctor --fix, previously wrote back the catch-all root config that init stopped writing in monorepos. It now prints the same guidance as init — add "extends": "adamantite/typescript" to each package's tsconfig.json or to a shared base config — and its validation no longer reports a failure for the deliberately absent file.

• #363 6270f58 Thanks @​adelrodriguez! - Show the captured package manager output when dependency installation fails during init. The error message now includes the underlying diagnostic, for example ERR_PNPM_UNSUPPORTED_ENGINE, instead of only the package list.

• #363 6270f58 Thanks @​adelrodriguez! - Include the underlying cause in file-system and extension error messages. Failed read, write, delete, and directory-creation operations now show the platform error detail, and a failed VS Code extension install reports the code CLI exit code.

Commits

• 54cb6a2 Version Packages (#364)
• 4701aa0 Restrict terminal output to commands: migrations report results, not print (#...
• dfb307b Preserve existing package scripts during init unless overwriting is confirmed...
• 943a1a9 Skip catch-all root tsconfig in monorepos during legacy typecheck migration (...
• ab7b1ce Dissolve lib/services into execution and workspace domain folders (#368)
• ab73a43 Move terminal interaction modules to top-level src/terminal folder (#366)
• b522044 Apply functional pipeline patterns to shared workspace helpers (#365)
• 8782acf Support current and minimum runtimes (#360)
• 6270f58 Show error causes in CLI failure messages (#363)
• 04f5494 Skip root tsconfig setup in monorepos and preserve existing extends (#361)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions