chore(deps): bump @unthrown/oxlint from 5.1.0 to 5.5.0

[dependabot]

Bumps @unthrown/oxlint from 5.1.0 to 5.5.0.

Release notes

Sourced from @​unthrown/oxlint's releases.

@​unthrown/oxlint@​5.5.0

Minor Changes

• 7a8a302: Restore the no-throw rule, removed in 5.4.0 (#227). It is unchanged and still opt-in — not part of the recommended preset, since it bans a core language statement.

  The 5.4.0 removal reasoned that an unconditional ThrowStatement report belongs in a no-restricted-syntax entry rather than a rule. oxlint does not implement no-restricted-syntax, so that migration path does not exist: a codebase that bans throw outright had no way left to enforce it. And because oxlint refuses to parse a config naming an unknown rule, the upgrade did not degrade to a warning — it failed the consumer's entire lint run, every non-unthrown rule included, on a minor.

  Nothing to do to adopt: a config that still names "unthrown/no-throw" resolves again, and existing oxlint-disable-next-line unthrown/no-throw comments point at a rule that exists once more.

  prefer-ensure stays removed. It flagged correct code that violates no thesis — a report-only refactor suggestion, with a known false positive, that was not paying for its AST analysis. Configs naming it should drop the entry.

@​unthrown/oxlint@​5.4.0

Minor Changes

• d892c07: Breaking, released as a minor. Remove the no-throw and prefer-ensure rules. The plugin now ships six rules: five in recommended, plus no-get-or-throw as the one opt-in. A config naming either removed rule fails to resolve it — see the migration note below. Configs that use the recommended preset alone are unaffected, since neither rule was in it.

  prefer-ensure flagged a shape that violates no thesis — a flatMap gating its own parameter is correct code with a better name available. Every other rule flags a spelling unthrown considers wrong, and a report-only refactor suggestion with a known false positive (a reassigned parameter) was not paying for 300 lines of AST analysis.

  no-throw reported every ThrowStatement unconditionally, with no binding to resolve and no shape to match — a no-restricted-syntax entry rather than a rule. The guidance it carried lives in the "Lint your codebase" guide and in no-get-or-throw's own message.

  Migrating: remove "unthrown/no-throw" and "unthrown/prefer-ensure" from your .oxlintrc.json. Neither was in the recommended preset, so configs using the preset alone need no change. To keep banning throw, reach for oxlint's own no-restricted-syntax.

  Also: the recommended preset is now a plain object literal instead of a defineConfig(...) call, which drops a runtime import of oxlint — a peer

... (truncated)

Changelog

Sourced from @​unthrown/oxlint's changelog.

5.5.0

Minor Changes

• 7a8a302: Restore the no-throw rule, removed in 5.4.0 (#227). It is unchanged and still opt-in — not part of the recommended preset, since it bans a core language statement.

  The 5.4.0 removal reasoned that an unconditional ThrowStatement report belongs in a no-restricted-syntax entry rather than a rule. oxlint does not implement no-restricted-syntax, so that migration path does not exist: a codebase that bans throw outright had no way left to enforce it. And because oxlint refuses to parse a config naming an unknown rule, the upgrade did not degrade to a warning — it failed the consumer's entire lint run, every non-unthrown rule included, on a minor.

  Nothing to do to adopt: a config that still names "unthrown/no-throw" resolves again, and existing oxlint-disable-next-line unthrown/no-throw comments point at a rule that exists once more.

  prefer-ensure stays removed. It flagged correct code that violates no thesis — a report-only refactor suggestion, with a known false positive, that was not paying for its AST analysis. Configs naming it should drop the entry.

5.4.0

Minor Changes

• d892c07: Breaking, released as a minor. Remove the no-throw and prefer-ensure rules. The plugin now ships six rules: five in recommended, plus no-get-or-throw as the one opt-in. A config naming either removed rule fails to resolve it — see the migration note below. Configs that use the recommended preset alone are unaffected, since neither rule was in it.

  prefer-ensure flagged a shape that violates no thesis — a flatMap gating its own parameter is correct code with a better name available. Every other rule flags a spelling unthrown considers wrong, and a report-only refactor suggestion with a known false positive (a reassigned parameter) was not paying for 300 lines of AST analysis.

  no-throw reported every ThrowStatement unconditionally, with no binding to resolve and no shape to match — a no-restricted-syntax entry rather than a rule. The guidance it carried lives in the "Lint your codebase" guide and in no-get-or-throw's own message.

  Migrating: remove "unthrown/no-throw" and "unthrown/prefer-ensure" from your .oxlintrc.json. Neither was in the recommended preset, so configs using the preset alone need no change. To keep banning throw, reach for oxlint's own no-restricted-syntax.

... (truncated)

Commits

• cbadb6c chore: release packages (#229)
• 7a8a302 fix(oxlint): restore no-throw, and document Prisma's modeled-code boundary (#...
• ec5d9d4 chore: release packages (#224)
• 655edbd docs: split per-package specs out of the root CLAUDE.md (#225)
• d892c07 refactor: cut over-engineering found by a repo-wide audit (#223)
• d98dbf8 chore: release packages (#220)
• de9486c feat(core): add fromExecutor, a callback-API boundary (#222)
• 56410c2 chore: release packages (#212)
• 0ebb060 feat(oxlint): add the AsyncResult import in prefer-async-result's fix (#215)
• 3eef964 feat(oxlint): add the no-get-or-throw rule (#211)
• Additional commits viewable 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)