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

[dependabot]

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

Updates @unthrown/oxlint from 5.7.0 to 5.8.0

Release notes

Sourced from @​unthrown/oxlint's releases.

@​unthrown/oxlint@​5.8.0

Minor Changes

• 40f7a54: unthrown/prefer-pre-lifted: ban .toAsync() on a freshly constructed Ok(...) / Err(...).

  Ok(value).toAsync(); // → OkAsync(value)
  Err(error).toAsync(); // → ErrAsync(error)
  Ok().toAsync(); // → OkAsync()
  Ok(undefined).toAsync(); // → OkAsync()

  The receiver is the whole test, which is what makes this rule safe where prefer-ensure was not. prefer-ensure had to decide whether an Ok(x) inside a callback carried the same x the callback was handed — an identity judgement across a scope, and the source of its false positives. Here the question is syntactic: a call to the imported Ok or Err, immediately followed by .toAsync(). So .toAsync() on a Result that already exists — a variable, a call's return, a ternary, fromNullable(...) — is the combinator doing its actual job and is never reported.

  Autofixable for the same reason: the pre-lifted name with the arguments untouched, Ok() and Ok(undefined) both collapsing to OkAsync(), and the specifier added to the existing unthrown import when the name is free.

  Opt-in, beside no-throw and no-get-or-throw — a spelling preference, not a thesis about correctness. It is a rule rather than a convention because that is the profile only a linter holds: btravstack/btravstack documented this convention, asserted one violation, and a sweep found thirty-three. It type-checks, tests stay green, and it is invisible in review.

  The fix never adds a value specifier to an import type { … }, and treats a type-only OkAsync binding as taken rather than as already imported — both would produce code that does not compile. A shadowed undefined parameter is resolved through scope, so only the global collapses to OkAsync().

  This repository now enables it too, and the autofix cleaned 21 sites across packages/boxed, packages/effect and four examples.

  Closes #260.

Changelog

Sourced from @​unthrown/oxlint's changelog.

5.8.0

Minor Changes

• 40f7a54: unthrown/prefer-pre-lifted: ban .toAsync() on a freshly constructed Ok(...) / Err(...).

  Ok(value).toAsync(); // → OkAsync(value)
  Err(error).toAsync(); // → ErrAsync(error)
  Ok().toAsync(); // → OkAsync()
  Ok(undefined).toAsync(); // → OkAsync()

  The receiver is the whole test, which is what makes this rule safe where prefer-ensure was not. prefer-ensure had to decide whether an Ok(x) inside a callback carried the same x the callback was handed — an identity judgement across a scope, and the source of its false positives. Here the question is syntactic: a call to the imported Ok or Err, immediately followed by .toAsync(). So .toAsync() on a Result that already exists — a variable, a call's return, a ternary, fromNullable(...) — is the combinator doing its actual job and is never reported.

  Autofixable for the same reason: the pre-lifted name with the arguments untouched, Ok() and Ok(undefined) both collapsing to OkAsync(), and the specifier added to the existing unthrown import when the name is free.

  Opt-in, beside no-throw and no-get-or-throw — a spelling preference, not a thesis about correctness. It is a rule rather than a convention because that is the profile only a linter holds: btravstack/btravstack documented this convention, asserted one violation, and a sweep found thirty-three. It type-checks, tests stay green, and it is invisible in review.

  The fix never adds a value specifier to an import type { … }, and treats a type-only OkAsync binding as taken rather than as already imported — both would produce code that does not compile. A shadowed undefined parameter is resolved through scope, so only the global collapses to OkAsync().

  This repository now enables it too, and the autofix cleaned 21 sites across packages/boxed, packages/effect and four examples.

  Closes #260.

Commits

• b6521de chore: release packages (#272)
• 40f7a54 feat(oxlint): prefer-pre-lifted — no .toAsync() on a fresh Ok/Err (#273)
• See full diff in compare view

Updates unthrown from 5.7.0 to 5.8.0

Changelog

Sourced from unthrown's changelog.

5.8.0

Commits

• b6521de chore: release packages (#272)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions