chore(deps): update dependency @effect/tsgo to v0.37.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@effect/tsgo (source)	0.36.1 → 0.37.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

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

v0.37.0

Compare Source

Minor Changes

• afb17ac: Support both the legacy microsoft/typescript-go compiler and the migrated
  microsoft/TypeScript/tsc compiler behind the canonical TypeScript shim
  namespace.

Patch Changes

• a3af171: Build the Nix package from the migrated TypeScript monorepo source and update the pinned compiler revision correctly.
• eba879b: Suppress the unnecessaryPipeChain diagnostic when merging chained pipe calls would exceed the available overload arity.
• 83b8e2a: Update the TypeScript next tag to typescript@next, which ships typescript-go commit e9e477458d7b975ed5e43117fb85f6bc87363a6a, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

v0.36.5

Compare Source

Patch Changes

• 9ddab5d: Report unsupported target package versions with the current @effect/tsgo version and the supported alternatives.
• 922903b: Document the target package versions supported by each published release.
• ca311a5: Exclude type-only heritage nodes from execution flow graphs across supported TypeScript versions.
• 7c54018: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 34ffe2a2531a226da0046d213899ae0b721229b0, and update the TypeScript latest tag to typescript@latest.

v0.36.4

Compare Source

Patch Changes

• 7a616ec: Allow declaration emit with noEmitOnError when all diagnostics are ignored Effect diagnostics.

v0.36.3

Compare Source

Patch Changes

• 73f7f28: Refresh patched binaries when an updated @effect/tsgo package provides a different replacement artifact.
• 9190801: Update Effect v4 dependencies and embedded test fixtures to 4.0.0-beta.107.

v0.36.2

Compare Source

Patch Changes

• 8362acc: Extend the walker-rule prefilter to call expressions.

  A call expression's type is its resolved signature's return type, and both the signature and that return type are already cached from the main check phase. NodeCouldBeStrictEffect now consults them for call nodes and skips the expensive flow-analysis re-check when the declared return type conclusively cannot be a strict Effect. Signature-less calls, optional chains, and every inconclusive return type stay conservative, and promiseInEffectSuccess no longer computes a location type for calls only to discard it. Emitted diagnostics are unchanged; on a large Effect monorepo build this removes a further ~4.6% of wall time on top of the reference-node prefilter, bringing the total Effect diagnostics overhead versus a pristine tsgo build of the same commit down to ~17%.

• 9020153: Skip diagnostic rules below the minimum visible severity before executing them.

  In tsc CLI mode without includeSuggestionsInTsc, suggestion- and message-severity diagnostics are dropped from the output after rules run. The rule runner now receives the minimum severity the caller can surface and skips such rules up front, avoiding their type-checker queries entirely. A rule below the threshold still runs when any directive in the file references it (for example // @effect-diagnostics ruleName:error or a wildcard), since directives can raise its severity and must be tracked for unusedDirective reporting. Emitted diagnostics are unchanged; on a large Effect monorepo build this removes roughly 1–2s of check time.

• 257af25: Skip flow-analysis type queries for references that conclusively cannot be an Effect.

  The effectInFailure and promiseInEffectSuccess rules walk every node of a file and query its flow type just to test whether it is a strict Effect type. The new TypeParser.NodeCouldBeStrictEffect prefilter inspects the referenced symbol's declared type first — flow narrowing can only refine the declared type, so a declared type that conclusively contains no possibly-Effect constituent (primitives, plain objects with a different type name, unions thereof) can never produce a strict Effect flow type, and the expensive query is skipped. The predicate is conservative: any/unknown, type parameters, conditionals, symbol-less types, and deep unions always fall through to the full query. Emitted diagnostics are unchanged; on a large Effect monorepo build this removes ~10% of build wall time (~2.7s of ~26.8s).

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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