Update dependency @effect/tsgo to v0.51.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@effect/tsgo (source)	0.46.1 → 0.51.1

---

Release Notes

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

v0.51.1

Compare Source

Patch Changes

• a5bd7f1: Update the TypeScript next tag to typescript@next, which ships typescript-go commit a1ef42b9ea7032fa60df127d42b4c86fd2a110ee, and update the TypeScript latest tag to typescript@latest.

v0.51.0

Compare Source

Minor Changes

• 9ca6ea2: Add related declaration locations to apiStabilityLeak diagnostics. For example, when a stable export exposes an experimental type, the diagnostic on the export now includes a child pointing to the experimental type's declaration, including declarations in other files.

Patch Changes

• caee22f: Fix apiStabilityLeak to ignore inherited bases whose public members are all optional and explicitly stability-tagged, including bases reached through augmentations and superclass factories. Direct properties and parameters typed as those bases remain checked. Exclude @internal properties and methods from the public surface throughout the leak check.

v0.50.0

Compare Source

Minor Changes

• 69c8ce5: Add the opt-in apiStabilityLeak diagnostic for Effect v4 package maintainers.
  It reports exports whose public types, parameters, or return values expose a
  less stable API: stable exports must not expose unstable or experimental types,
  and unstable exports must not expose experimental types. Untagged exports are
  treated as stable; experimental exports impose no restriction.

  For example, export interface StableApi { value: ExperimentalType } reports
  a leak when ExperimentalType has an @stability experimental tag. Public
  members, generic arguments, inferred types, and re-exports are checked without
  recursively instantiating types.

  The rule is off by default and excluded from the recommended, strict, and
  correctness presets. Enable the new maintainers preset to report it as a
  warning, or configure apiStabilityLeak directly. Declared stability lookups are
  shared with the existing unstable and experimental API usage diagnostics.

v0.49.0

Compare Source

Minor Changes

• 75e6ca5: Migrate compiler integrations to the current TypeScript path and configuration APIs, and refresh the TypeScript patch stack for the new upstream snapshot. Keep TypeScript 7.0.2 supported through adapters for the legacy typescript-go provider.

  For example, plugin option and diagnostic severity resolution now accept rooted source and config file paths directly, while the legacy shims adapt those calls to TypeScript 7.0.2. Preserve Effect options through upstream option cloning and comparison, and fix include patterns for files in filesystem roots.

  Keep the Nix compiler source pin, lock file, and vendor hash synchronized with the updated snapshot, and apply Git binary compiler patches during Nix builds. Preserve the original TypeScript 7.0.2 provider shim APIs for tsgolint, with modern API adapters confined to the canonical shim facade.

v0.48.1

Compare Source

Patch Changes

• c964cca: Fix unstableApiUsage and experimentalApiUsage naming overloaded (dual) exports by module, which prevented allowedUnstableApis / allowedExperimentalApis from allowing them per export.

  A dual export whose call signatures carry their own @stability tag — for example effect/http/HttpClientRequest#bodyText — was reported under the bare module name (effect/http/HttpClientRequest) because the selected call signature is not the module export. An allow-list entry for effect/http/HttpClientRequest#bodyText therefore never matched, and the only way to allow the use was a whole-module entry.

  The reported name now resolves to the export that owns the selected overload signature, matching the README's package/module#exportName form:

  import { HttpClientRequest } from "effect/http"
  
  export const request = HttpClientRequest.post("http://x").pipe(
    HttpClientRequest.setHeader("a", "b"),
    HttpClientRequest.bodyText("{}", "application/json")
  )

  With:

  "allowedUnstableApis": [
    "effect/http/HttpClientRequest#post",
    "effect/http/HttpClientRequest#setHeader",
    "effect/http/HttpClientRequest#bodyText"
  ]

  all three uses are allowed, and any unlisted dual export still warns under package/module#exportName.

v0.48.0

Compare Source

Minor Changes

• a954eb5: Add allowedUnstableApis and allowedExperimentalApis to selectively allow unstable or experimental declaration modules or exported APIs. For example, effect/http/HttpClient allows the entire module, while effect/http/HttpClient#get allows only its exported get API. Both options support per-file overrides, and both diagnostics display the declaration-based name.

Patch Changes

• 0900778: Build packaged TypeScript compilers without embedded standard libraries so editor go-to-definition opens real library files. Ship matching lib.*.d.ts files beside each versioned compiler and the latest lib/tsc alias, keeping diagnostics and get-exe-path working when running the packaged executable directly.

v0.47.2

Compare Source

Patch Changes

• 536f83a: Fix a panic in unstableApiUsage and experimentalApiUsage on the default of a dynamically imported export = or JSON module.
• bddb623: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 0681ef7fa3a2378ccf49645b6d5b7463bdca74bb, and update the TypeScript latest tag to typescript@latest.

v0.47.1

Compare Source

Patch Changes

• d4f19b3: Allow effect-tsgo patch to run without the deprecated --force flag.

v0.47.0

Compare Source

Minor Changes

• b67ef81: Update the Effect v4 integration to 4.0.0-rc.118 and use its public module paths. Namespace auto-imports for nested modules now resolve to paths such as effect/cli/Prompt.
• 66668e2: Add the experimentalApiUsage and unstableApiUsage diagnostics for APIs marked with @stability experimental or @stability unstable. Both rules warn by default. For example, a reference to an unstable API now reports that breaking changes may happen between versions.

Patch Changes

• 8067475: Fix getExePath rejecting the schema version shipped by platform packages.

  Discover installed Oxlint musl bindings without rejecting them before component selection, so TypeScript-only commands work when Oxlint is installed on Alpine Linux. Report unsupported Oxlint replacements during patch preparation instead, allowing --skip-missing and restoring original binaries with unpatch.

• 2e215ce: Update the TypeScript next tag to typescript@next, which ships typescript-go commit 4f5ddae224b9529a69b571f631fe3a2cb283162f, and update the TypeScript latest tag to typescript@latest. Refresh the Oxlint configuration schema from the selected package.

---

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.

[GraemeF]

Holding this one open. The bump itself is clean, but 0.47.0 can't install here.

0.47.0's `patch` command declares its deprecated `--force` flag without a default, so our `prepare` script's `effect-tsgo patch` fails with `Missing required flag: --force`. Upstream fixed this in Effect-TS/tsgo#777, released as 0.47.1.

With patching forced by hand, the full gate passes on 0.47.0, and the new `experimentalApiUsage` and `unstableApiUsage` rules report nothing in this codebase.

0.47.1 clears the 7-day release-age gate on 2026-10-07 at 04:35 UTC. Renovate should then move this PR on to it, and it can be evaluated again from there. Adding `--force` to `prepare` would get 0.47.0 in today, but only by shipping a deprecated flag that the next bump would have to take out again.