chore: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

eslint-plugin-faultline@0.3.0

Minor Changes

• 7a010cc: Rule improvements and publish-readiness fixes.

  Rules:

  • throw-type-mismatch now inspects all overload signatures, not just the first — overloaded functions are fully checked for transitive error propagation.
  • throw-type-mismatch reports throw <identifier> when the surrounding function declares a TypedPromise error type and the thrown variable's type has no resolvable _tag.
  • uncovered-catch no longer misattributes throws inside async closures (e.g. setTimeout(async () => ...)) to the outer try's catch.
  • Published LIMITATIONS.md documenting patterns the rules can't detect, plus an 11-pattern torture-fixture corpus guarding the rules.

  Packaging:

  • Ship the previously-missing README.md (it was already listed in files).
  • Derive meta.version from package.json at build time so it can no longer drift from the published version (was hardcoded 0.1.0).
  • Run tests as part of prepublishOnly.

faultline@0.3.0

Minor Changes

• 7a010cc: Add boundary.try(error) — a non-throwing variant of a boundary that returns Result<To, System.BoundaryViolation> instead of throwing on an unmapped tag. Boundaries usually sit at a transport edge where an uncaught throw is costly; .try() lets you handle an unexpected (untyped/foreign) error tag as a value. Exposes the BoundaryViolationError type.

• 7a010cc: Redaction: support a ** globstar segment in redactPaths to redact a key at any depth (e.g. **.password). Redaction paths are matched against the serialized error structure and a non-matching path is a silent no-op (it fails open), so **.<key> is now the recommended form for sensitive keys — it can't silently miss a nested occurrence the way a brittle exact path can. Documented this behavior in the README and SECURITY.md.

  Also clarified (docs only, no behavior change): attemptAsync/TaskResult cancellation is cooperative — aborting short-circuits subsequent steps and stops the caller waiting, but does not preempt in-flight work unless your function threads the AbortSignal through. And defineBoundary throws System.BoundaryViolation (preserving the original as cause) when an unmapped error tag reaches it.

• 7a010cc: TaskResult cancellation, rejection safety, and API pruning.

  Breaking changes:

  • TaskResult.toPromise() removed. Use .run() instead — same signature.
  • TaskResult chain methods (.map, .andThen, .catchTag, etc.) now widen their error union to include System.Cancelled. Exhaustive match() over a TaskResult needs a 'System.Cancelled' handler or a _ branch.
  • TaskResult.fromPromise return type now widens to include System.Unexpected. Factory rejections are no longer unhandled — they are caught and wrapped as System.Unexpected with the original throw preserved as .cause.

  Added:

  • TaskResult chain steps check context.signal?.aborted between every step. Aborting the signal mid-pipeline short-circuits the remaining steps to System.Cancelled instead of running them to completion.

faultline-cli@0.2.0

Minor Changes

• 7a010cc: The CLI is now publishable to npm and runs on plain Node.js (>=18). The bin points at a built dist/index.js with a Node shebang (previously a raw .ts file with a bun shebang), typescript is declared as a runtime dependency, and the package ships a files allowlist, README, LICENSE, and full repository metadata.