chore(deps): bump the unthrown group across 1 directory with 2 updates

[dependabot]

Bumps the unthrown group with 2 updates in the / directory: @unthrown/oxlint and unthrown.

Updates @unthrown/oxlint from 5.8.0 to 5.9.0

Release notes

Sourced from @​unthrown/oxlint's releases.

@​unthrown/oxlint@​5.9.0

Patch Changes

• 352c204: no-unhandled-result and no-async-result-race now recognise the accumulating aggregates. Both rules resolve producers by name, so a dropped validateAll(...) statement went unreported and the sibling-race no-async-result-race exists for was invisible on validateAllAsync. The four free functions and their Result.* / AsyncResult.* facade members are now in the producer sets.

Changelog

Sourced from @​unthrown/oxlint's changelog.

5.9.0

Patch Changes

• 352c204: no-unhandled-result and no-async-result-race now recognise the accumulating aggregates. Both rules resolve producers by name, so a dropped validateAll(...) statement went unreported and the sibling-race no-async-result-race exists for was invisible on validateAllAsync. The four free functions and their Result.* / AsyncResult.* facade members are now in the producer sets.

Commits

• dee7cfb chore: release packages (#277)
• 352c204 feat: add validateAll, validateAllFromDict and their async counterparts (#274)
• See full diff in compare view

Updates unthrown from 5.8.0 to 5.9.0

Release notes

Sourced from unthrown's releases.

unthrown@5.9.0

Minor Changes

• 352c204: validateAll / validateAllFromDict and their async counterparts (validateAllAsync / validateAllFromDictAsync): the accumulating siblings of all / allFromDict, which report only the first Err.

  const checked = validateAllFromDict(
    {
      stock: checkStock(order),
      credit: checkCreditLimit(customer),
      address: checkAddress(order),
    },
    (entries) => new OrderRejected({ violations: entries }),
  );
  // stock and address failed → Err(OrderRejected) naming both, not just the first

  The success channel is all's, unchanged: a fixed tuple keeps its positional types, a dynamic array collapses to Result<T[], E2>, and a record answers a record. Only the error channel differs.

  merge is mandatory, and that is the point. neverthrow's combineWithAllErrors answers Result<T[], E[]>; here you supply (errors) => E2. An E[] is a shape, not a domain failure — Thesis #1 says E holds anticipated failures a caller can match on and act upon, and an array pushes "what does it mean that several rules failed?" to every consuming site, forever. Naming an E2 answers it once, where the errors were collected.

  merge receives a non-empty list, so it is total — it never runs on an all-Ok batch. The record form hands it [key, error] entries correlated per key ({ a: Result<A, E1>; b: Result<B, E2> } yields ["a", E1] | ["b", E2]), so a switch on the key narrows the error and an impossible pairing does not typecheck — which is what keeps two checks sharing one error type distinguishable.

  Every existing aggregate rule still holds. A Defect dominates and discards the accumulated errors — a batch carrying an unmodeled failure produced violations computed alongside broken code, so merge is never called; an out-of-contract non-Result element is still a TypeError-caused Defect; a throw inside merge becomes a Defect; the async pair resolves concurrently (order preserved) and its internal promise never rejects. merge must be synchronous (NotThenable) — an async one would land an unqualified Promise in E, the boundary rule from Thesis #3.

  This narrows, rather than reverses, the "no error accumulation" decision. For schema-shaped input — a request body, a form — @unthrown/standard-schema's fromSchema is still the tool: a validator already hands you every issue as the modeled error, and validateAll there duplicates a job it does better. What the

... (truncated)

Changelog

Sourced from unthrown's changelog.

5.9.0

Minor Changes

• 352c204: validateAll / validateAllFromDict and their async counterparts (validateAllAsync / validateAllFromDictAsync): the accumulating siblings of all / allFromDict, which report only the first Err.

  const checked = validateAllFromDict(
    {
      stock: checkStock(order),
      credit: checkCreditLimit(customer),
      address: checkAddress(order),
    },
    (entries) => new OrderRejected({ violations: entries }),
  );
  // stock and address failed → Err(OrderRejected) naming both, not just the first

  The success channel is all's, unchanged: a fixed tuple keeps its positional types, a dynamic array collapses to Result<T[], E2>, and a record answers a record. Only the error channel differs.

  merge is mandatory, and that is the point. neverthrow's combineWithAllErrors answers Result<T[], E[]>; here you supply (errors) => E2. An E[] is a shape, not a domain failure — Thesis #1 says E holds anticipated failures a caller can match on and act upon, and an array pushes "what does it mean that several rules failed?" to every consuming site, forever. Naming an E2 answers it once, where the errors were collected.

  merge receives a non-empty list, so it is total — it never runs on an all-Ok batch. The record form hands it [key, error] entries correlated per key ({ a: Result<A, E1>; b: Result<B, E2> } yields ["a", E1] | ["b", E2]), so a switch on the key narrows the error and an impossible pairing does not typecheck — which is what keeps two checks sharing one error type distinguishable.

  Every existing aggregate rule still holds. A Defect dominates and discards the accumulated errors — a batch carrying an unmodeled failure produced violations computed alongside broken code, so merge is never called; an out-of-contract non-Result element is still a TypeError-caused Defect; a throw inside merge becomes a Defect; the async pair resolves concurrently (order preserved) and its internal promise never rejects. merge must be synchronous (NotThenable) — an async one would land an unqualified Promise in E, the boundary rule from Thesis #3.

  This narrows, rather than reverses, the "no error accumulation" decision. For schema-shaped input — a request body, a form — @unthrown/standard-schema's fromSchema is still the tool: a validator already hands you every issue as the

... (truncated)

Commits

• dee7cfb chore: release packages (#277)
• 352c204 feat: add validateAll, validateAllFromDict and their async counterparts (#274)
• See full diff in compare view

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: ed46d75b-72f3-44d8-8444-2a9639891c88

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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.}

[btravers]

@dependabot rebase