chore(deps): bump effect and prisma

[dependabot]

Bumps effect to 3.20.0 and updates ancestor dependency prisma. These dependencies need to be updated together.

Updates effect from 3.18.4 to 3.20.0

Changelog

Sourced from effect's changelog.

3.20.0

Minor Changes

• #6124 8798a84 Thanks @​mikearnaldi! - Fix scheduler task draining to isolate AsyncLocalStorage across fibers.

Patch Changes

• #6107 fc82e81 Thanks @​gcanti! - Backport Types.VoidIfEmpty to 3.x

• #6088 82996bc Thanks @​taylorOntologize! - Schema: fix Schema.omit producing wrong result on Struct with optionalWith({ default }) and index signatures

  getIndexSignatures now handles Transformation AST nodes by delegating to ast.to, matching the existing behavior of getPropertyKeys and getPropertyKeyIndexedAccess. Previously, Schema.omit on a struct combining Schema.optionalWith (with { default }, { as: "Option" }, etc.) and Schema.Record would silently take the wrong code path, returning a Transformation with property signatures instead of a TypeLiteral with index signatures.

• #6086 4d97a61 Thanks @​taylorOntologize! - Schema: fix getPropertySignatures crash on Struct with optionalWith({ default }) and other Transformation-producing variants

  SchemaAST.getPropertyKeyIndexedAccess now handles Transformation AST nodes by delegating to ast.to, matching the existing behavior of getPropertyKeys. Previously, calling getPropertySignatures on a Schema.Struct containing Schema.optionalWith with { default }, { as: "Option" }, { nullable: true }, or similar options would throw "Unsupported schema (Transformation)".

• #6097 f6b0960 Thanks @​gcanti! - Fix TupleWithRest post-rest validation to check each tail index sequentially.

3.19.19

Patch Changes

• #6079 4eb5c00 Thanks @​tim-smart! - add short circuit to fiber.await internals

• #6079 4eb5c00 Thanks @​tim-smart! - build ManagedRuntime synchronously if possible

• #6081 2d2bb13 Thanks @​tim-smart! - fix semaphore race condition where permits could be leaked

3.19.18

Patch Changes

• #6062 12b1f1e Thanks @​tim-smart! - prevent Stream.changes from writing empty chunks

3.19.17

Patch Changes

• #6040 a8c436f Thanks @​jacobconley! - Fix Stream.decodeText to correctly handle multi-byte UTF-8 characters split across chunk boundaries.

3.19.16

Patch Changes

• #6018 e71889f Thanks @​codewithkenzo! - fix(Match): handle null/undefined in Match.tag and Match.tagStartsWith

  Added null checks to discriminator and discriminatorStartsWith predicates to prevent crashes when matching nullable union types.

... (truncated)

Commits

• aa47393 Version Packages (#6089)
• 8798a84 fix(effect): isolate scheduler runners per fiber (#6124)
• fc82e81 Backport Types.VoidIfEmpty to 3.x (#6107)
• f6b0960 Backport: Fix TupleWithRest post-rest index drift validation bug (#6097)
• 82996bc fix(Schema): handle Transformation in getIndexSignatures for correct omit beh...
• 4d97a61 Schema: fix getPropertySignatures crash on Struct with optionalWith({ default...
• ab3b64c Version Packages (#6080)
• 2d2bb13 fix semaphore race condition where permits could be leaked (#6081)
• 4eb5c00 build ManagedRuntime synchronously if possible (#6079)
• 4f21075 Version Packages (#6063)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for effect since your current version.

Updates prisma from 7.5.0 to 7.9.1

Release notes

Sourced from prisma's releases.

7.9.1

Today, we're issuing a patch release to resolve a security advisory in a transitive dependency of Prisma CLI (via @prisma/dev).

This fixes prisma/prisma#29780.

It does not actually affect @prisma/dev or Prisma CLI so no urgent action is required, but it is recommended to upgrade nevertheless to avoid false positives from security scanners.

7.9.0

Today, we are excited to share the 7.9.0 stable release 🎉

🌟 Star this repo for notifications about new releases, bug fixes & features — or follow us on X!

Highlights

ORM

Tab completions for the Prisma CLI

Typing out CLI commands from memory is now optional. Prisma ships shell tab completions for bash, zsh, fish, and PowerShell, covering commands, subcommands, options, flags, and even option values.

Setting it up. Most projects run Prisma through a package manager, so completions are enabled through @bomb.sh/tab's package-manager integration — install it once, then source the completion for your package manager and shell:

# 1. Install @bomb.sh/tab globally
npm install -g @bomb.sh/tab
2. Wire up your package manager + shell (pnpm shown; swap in npm / yarn / bun):
echo 'source <(tab pnpm zsh)'  >> ~/.zshrc            # zsh
echo 'source <(tab pnpm bash)' >> ~/.bashrc           # bash
tab pnpm fish > ~/.config/fish/completions/pnpm.fish  # fish
tab pnpm powershell > ~/.tab-pnpm.ps1                 # PowerShell (then dot-source it from $PROFILE)

@bomb.sh/tab delegates to any locally-installed CLI that ships completions, so pnpm prisma <TAB>, pnpm exec prisma <TAB>, yarn prisma <TAB>, and bun x prisma <TAB> all complete Prisma's commands, options, and values — no per-project setup. (npx and bunx don't support completion themselves; use npm exec and bun x.)

If instead you have Prisma installed globally on your PATH, source its own completion directly: source <(prisma complete zsh) (or the bash / fish / powershell variant).

This is built on @bomb.sh/tab, the same completion library that powers other CLIs in the ecosystem — including Cloudflare, Nuxt, and Vitest — so the package-manager completions you enable for Prisma work for those tools too. A wonderful community contribution from @​AmirSa12 (#28351) — thank you!

prisma.mp4

Prisma ORM, ready for AI agents

Coding agents are now a first-class audience for Prisma, and 7.9.0 brings the first wave of work to make Prisma projects safe and productive for them to work in.

Agent skills installed with prisma init (#29689)

prisma init now installs the prisma/skills catalog into freshly scaffolded projects. Agents such as Claude Code, Cursor, Codex, and Windsurf start out with current, version-relevant Prisma knowledge instead of relying on whatever happened to be in their training data. The install is best-effort and never blocks scaffolding; opt out at any time with --no-skills.

</tr></table> 

... (truncated)

Commits

• 3f492ab chore(deps): update @​prisma/dev to 0.24.17 (7.9.x backport) (#29795)
• 537583c feat(cli): add @bomb.sh/tab completions (#28351)
• bf7c40f fix(cli): update Studio to 0.33.0 and suppress aborted response errors (#29720)
• 9acd8dc feat(cli): install Prisma agent skills during prisma init (#29689)
• aef8cb5 fix(cli): remove the migrate-reset tool from the MCP server (#29691)
• cdca333 chore(deps): update @​prisma/dev to 0.24.14 (#29686)
• fda8fbc chore(deps): bump @​prisma/dev to 0.24.9 (resolves hono GHSA-92pp-h63x-v22m) (...
• 5723406 fix(cli): route bootstrap telemetry to Prisma Web Properties project (#29473)
• 8e71aa7 fix(cli): install missing @prisma/client in prisma bootstrap (#29444)
• ada077b fix(cli): bootstrap UX — auto-install deps, resumable flow, timeout handling ...
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.