chore(deps): bump knip from 6.11.0 to 6.12.2 - #228
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) from 6.11.0 to 6.12.2. - [Release notes](https://github.com/webpro-nl/knip/releases) - [Commits](https://github.com/webpro-nl/knip/commits/knip@6.12.2/packages/knip) --- updated-dependencies: - dependency-name: knip dependency-version: 6.12.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
Author
|
Looks like knip is up-to-date now, so this is no longer needed. |
btravers
pushed a commit
that referenced
this pull request
Aug 12, 2026
Retargets this PR from 5.4.0 to 5.5.0, which restores `unthrown/no-throw` (btravstack/unthrown#227 → #228). The rule is back unchanged and still opt-in, so naming it explicitly is all that is needed — and the repo's 93 `oxlint-disable-next-line unthrown/no-throw` comments point at a live rule again. Net config change against main is now much smaller than the 5.4.0 version of this branch: - `unthrown/no-throw` — kept, along with the spec-file override. No longer removed. - `unthrown/prefer-ensure` — dropped. Still gone in 5.5.0 (it flagged correct code and had a known false positive); zero usages here, so nothing to do. - `unthrown/no-unused-matcher` — newly enabled. It has shipped since 5.1.0 and simply was not turned on; it catches a `…Cases` callback that ignores the injected matcher, which silently recovers the wrong case or turns a modeled error into a defect. Passes clean. Core library API is unchanged across 5.1.0 → 5.5.0 apart from `fromExecutor` (added 5.4.0), which has no call site here. Verified: build 10/10, typecheck 12/12, oxlint clean, 555 unit tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
btravers
pushed a commit
that referenced
this pull request
Aug 12, 2026
Retargets this PR from 5.4.0 to 5.5.0, which restores `unthrown/no-throw` (btravstack/unthrown#227 → #228). The rule is back unchanged and still opt-in, so naming it explicitly is all that is needed — and the repo's 93 `oxlint-disable-next-line unthrown/no-throw` comments point at a live rule again. Net config change against main is now much smaller than the 5.4.0 version of this branch: - `unthrown/no-throw` — kept, along with the spec-file override. No longer removed. - `unthrown/prefer-ensure` — dropped. Still gone in 5.5.0 (it flagged correct code and had a known false positive); zero usages here, so nothing to do. - `unthrown/no-unused-matcher` — newly enabled. It has shipped since 5.1.0 and simply was not turned on; it catches a `…Cases` callback that ignores the injected matcher, which silently recovers the wrong case or turns a modeled error into a defect. Passes clean. Core library API is unchanged across 5.1.0 → 5.5.0 apart from `fromExecutor` (added 5.4.0), which has no call site here. Verified: build 10/10, typecheck 12/12, oxlint clean, 555 unit tests. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps knip from 6.11.0 to 6.12.2.
Release notes
Sourced from knip's releases.
Commits
cfb9ac4Release knip@6.12.2616739dfix(serverless-framework): skip functions without handler (close #1735)f37c5dafix(webpack): reference TS loaders for.ts/.ctsconfig (close #1732)d54074dFix symbol reporter file paths with --directory (#1733)b255195Release knip@6.12.14dcd756Fix inferred declaration export references (#1728)370236dFix Vercel config detection (#1726)0fe8dc3Bump jiti to ^2.7.0 (#1729)de33a2cfix: type-only imports in monorepos (#1715)44829feRelease knip@6.12.0Dependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)