chore(deps): update effect

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@effect/cli (source)	0.75.2 → 0.76.0
@effect/language-service	0.86.2 → 0.87.1
@effect/platform (source)	0.96.2 → 0.97.0
@effect/platform-node (source)	0.107.0 → 0.108.0
effect (source)	3.21.4 → 3.22.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

Effect-TS/effect (@​effect/cli)

v0.76.0

Compare Source

Patch Changes

• Updated dependencies [fffdee0]:
  • effect@​3.22.0
  • @​effect/platform@​0.97.0
  • @​effect/printer@​0.50.0
  • @​effect/printer-ansi@​0.50.0

Effect-TS/language-service (@​effect/language-service)

v0.87.1

Compare Source

Patch Changes

• #​765 6b9dab5 Thanks @​mattiamanzati! - Ignore Effect v4 local Effect.provide(..., { local: true }) calls when reporting chained provides with the multipleEffectProvide diagnostic.

v0.87.0

Compare Source

Minor Changes

• #​760 f1fca78 Thanks @​mattiamanzati! - Add the flatMapToMap style diagnostic, which suggests replacing Effect.flatMap((value) => Effect.succeed(f(value))) with Effect.map((value) => f(value)).

Patch Changes

• #​762 5e71871 Thanks @​mattiamanzati! - Enable skipLibCheck in the diagnostics test harness to reduce test runtime and memory usage.

• #​763 0dc8034 Thanks @​mattiamanzati! - Update the setup command to configure VS Code with the unified js/ts TypeScript settings.

• #​742 939a049 Thanks @​RezaOwliaei! - Update README to replace deprecated VSCode TypeScript settings (typescript.tsdk and typescript.enablePromptUseWorkspaceTsdk) with the current recommended configuration.

v0.86.6

Compare Source

Patch Changes

• #​758 6ef9a46 Thanks @​mattiamanzati! - Skip Effect diagnostics for external library files in patched tsc runs when TypeScript skipLibCheck is enabled.

v0.86.5

Compare Source

Patch Changes

• #​751 8d0b85a Thanks @​mattiamanzati! - Reject unsupported TypeScript versions when loading or patching TypeScript, directing TypeScript 7 users to @​effect/tsgo.

• #​754 1dce66b Thanks @​mattiamanzati! - Update the Effect v4 harness and language-service development dependencies to Effect 4.0.0-beta.94, including compatibility updates for the latest Effect API and Schema type output.

v0.86.4

Compare Source

Patch Changes

• #​746 5da9914 Thanks @​mattiamanzati! - Avoid suggesting removal of Effect.gen when a single return statement contains multiple yield* expressions, which would produce invalid code.

v0.86.3

Compare Source

Patch Changes

• #​744 1707983 Thanks @​mattiamanzati! - Fix lazyPromiseInEffectSync false positives for Effect.sync thunks whose return type degrades to any. Promise detection now ignores any and unknown before falling back to assignability against the global Promise type.

• #​740 df50dfc Thanks @​jbmusso! - Fix effectRpcDefinition wiping the upstream go-to-definition result when the user clicks on a JSX <Namespace.Component /> tag name. The plugin's RpcClient → Rpc enrichment now skips ancestor nodes whose type cannot be resolved (such as JSX tag-name nodes) instead of returning undefined for the entire request.

---

Configuration

📅 Schedule: (in timezone UTC)

• Branch creation
  • "after 02:00 and before 06:00 every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
lupe-docs	Ready	Preview, Comment	Jul 26, 2026 6:07pm

[coderabbitai]

📝 Walkthrough

Walkthrough

This change updates the @effect/language-service devDependency version in package.json from 0.86.2 to 0.86.4. No other files or dependencies are modified.

Changes

Dependency Update

Layer / File(s)	Summary
Update devDependency version package.json	@effect/language-service version bumped from 0.86.2 to 0.86.4 in devDependencies.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is related to the main change: it indicates a dependency update in the Effect ecosystem.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/effect

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	effect@​3.21.4 ⏵ 3.22.0	-2		+1	+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm effect is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: apps/action/package.json → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report