Skip to content

chore(deps-dev): bump the development group across 1 directory with 4 updates - #29

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-67d701f4c6
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/development-67d701f4c6

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor

Bumps the development group with 4 updates in the / directory: @types/node, oxfmt, oxlint and tsdown.

Updates @types/node from 26.4.0 to 26.4.1

Commits

Updates oxfmt from 0.65.0 to 0.66.0

Commits

Updates oxlint from 1.80.0 to 1.81.0

Release notes

Sourced from oxlint's releases.

oxlint v1.81.0 & oxfmt v0.66.0

Table of Contents

Oxlint v1.81.0

🚀 Features

  • 60b945d linter/nextjs/no-typos: Implement suggestion (#26091) (Mikhail Baev)

🐛 Bug Fixes

  • 33ac4b0 linter/lsp: Prevent tsgolint from holding onto processes (#25570) (Adrian Schaedle)
  • baf4b1e linter/import/no-empty-named-blocks: Make empty value import removal a suggestion (#26155) (camc314)
  • 77cfaec linter/eslint/object-shorthand: Preserve __proto__ semantics (#26154) (camc314)
  • fa3c082 linter/unicorn/prefer-set-size: Ignore shadowed Set constructors (#26153) (camc314)
  • e412cf2 linter: Clamp invalid JS plugin locations (#26144) (camc314)
  • d86c113 linter: Normalize reversed JS plugin locations (#26138) (camc314)
  • 73c09b2 linter/eslint/no-use-before-define: Run on JS, JSX files (#26114) (camc314)
  • 03ef0f2 linter/unicorn/no-useless-spread: Treat typed arrays as a distinct value hint (#26067) (Aadharsh Pannirselvam)
  • bd15905 linter/react/no-unstable-nested-components: Check nested component object property names (#26101) (camc314)
  • 3910e2b linter/eslint/no-unassigned-vars: Skip Svelte and Vue files (#26042) (Hamody We)
  • 047f7ca linter/plugins: Fix interaction between JS plugins and Vue rules (#26080) (overlookmotel)
  • 8531b9b linter/plugins: Alter method for obtaining mutable Program when sending AST to JS plugins (#26077) (overlookmotel)
  • dc464ff linter/unicorn/prefer-math-min-max: Avoid unsafe autofix (#26060) (camc314)

📚 Documentation

  • 464ddd1 linter: Support a shared short description for jest/vitest rules (#26186) (connorshea)
  • 9db5ad3 linter: Add short description to vue/no-dupe-keys (#26183) (connorshea)
  • db66f58 linter: Correct export/import mismatch in bar and foo example (#25927) (billychannnnnn)
  • d5be037 linter/typescript/switch-exhaustiveness-check: Clarify default case comment pattern (#26100) (camc314)

Oxfmt v0.66.0

🚀 Features

  • 1fb37b6 formatter/css: Format declaration-shaped raw-prelude rules (postcss nested config blocks) (#26194) (leaysgur)

🐛 Bug Fixes

  • 9f81002 formatter: Re-add suppressed statement terminators per options.semi (#26220) (leaysgur)
  • 769ffd5 formatter: Print suppressed typecast parens (#26218) (leaysgur)
  • 5ff57f8 formatter/sort-imports: Handle custom side effect groups (#26217) (leaysgur)
  • 2f4d759 formatter: Do not skip cast comment lookup (#26216) (leaysgur)
  • 1213e12 formatter: Preserve comment for statement terminators and binary casts (#26213) (leaysgur)
  • 57e8e22 formatter_css: Space a folded sign after a call in Less operations (#26134) (leaysgur)
  • e4298fb formatter/jsdoc: Follow CommonMark for interrupting lists and guard wrapping from creating them (#26098) (leaysgur)
  • a1e21c2 formatter: Apply head body policy everywhere (#26074) (leaysgur)
  • 676b7e1 formatter: Keep comments in their for-head slot, before an empty-statement body and do-while (#26073) (leaysgur)

... (truncated)

Changelog

Sourced from oxlint's changelog.

[1.81.0] - 2026-08-31

📚 Documentation

  • d5be037 linter/typescript/switch-exhaustiveness-check: Clarify default case comment pattern (#26100) (camc314)

[1.79.0] - 2026-08-18

💥 BREAKING CHANGES

  • 8c4552d linter: [BREAKING] Split react/react-compiler into per-category rules (#25500) (Boshen)

🐛 Bug Fixes

  • 228e8e0 linter: Resolve inactive React compiler rules (#25830) (Boshen)
  • aa49d86 linter: Allow spread rule options in config types (#25675) (ch3rry)
  • 36f8451 linter/eslint/no-eval: Align indirect default with ESLint (#25656) (camc314)
  • beb724d linter/eslint/no-unused-vars: Report bare underscore parameters (#25663) (camc314)
  • 4004c10 linter/eslint/no-irregular-whitespace: Check comments by default (#25660) (camc314)
  • 285820e linter/no-large-snapshots: Precompile and document allowed snapshot matchers (#25611) (Mikhail Baev)
  • 4df5835 linter: Allow capitalized built-in calls (#25516) (Boshen)

[1.78.0] - 2026-08-10

🚀 Features

  • ccb8fe8 linter/jsdoc: Implement no-blank-blocks rule (#25207) (Mikhail Baev)
  • d4a897c linter/eslint: Implement one-var rule (#24470) (Cole Ellison)
  • 5ab9340 linter/jsx-a11y/anchor-has-content: Add options to match eslint (#24571) (Cole Ellison)

🐛 Bug Fixes

  • 9573937 linter/typescript: Validate ban-ts-comment description_format (#25320) (Mikhail Baev)

[1.77.0] - 2026-08-03

🐛 Bug Fixes

  • 5c0fa61 linter/eslint/no-warning-comments: Unify config structs and remove manual options docs (#25151) (Mikhail Baev)

📚 Documentation

  • 9dc7756 linter/typescript/no-unnecessary-condition: Clarify options (#25110) (camc314)

[1.76.0] - 2026-07-27

🚀 Features

  • 8d31dfa linter: Verify eslint/no-restricted-globals config schema (#24598) (vigneshwar)
  • 7069621 linter: Verify jest/vitest prefer-lowercase-title config schema (#24724) (Bartok)

... (truncated)

Commits
  • 0b4e2e6 release(apps): oxlint v1.81.0 && oxfmt v0.66.0 (#26199)
  • d5be037 docs(linter/typescript/switch-exhaustiveness-check): clarify default case com...
  • 63bc313 chore(npm): update funding URL (#26066)
  • See full diff in compare view

Updates tsdown from 0.22.14 to 0.23.0

Release notes

Sourced from tsdown's releases.

v0.23.0

   🧭 Migration Guide

Most users can upgrade directly. Before upgrading, run one final build with [email protected] and resolve all deprecation warnings.

  • config:
    • bundle: falseunbundle: true; bundle: true can be removed
    • outExtensionoutExtensions
    • publicDir / --public-dircopy / --copy
    • removeNodeProtocol: truenodeProtocol: 'strip'
    • injectStylecss.inject
  • deps:
    • inlineOnly / deps.onlyAllowBundledeps.onlyBundle
    • skipNodeModulesBundle: truedeps.neverBundle: true
    • resolveDepSubpath now defaults to false; set it to true to preserve the previous behavior
  • dts:
    • rolldown-plugin-dts was upgraded from 0.27.13 to 0.28.5
    • dts.oxc: truedts.generator: 'oxc'
    • dts.tsgo: truedts.generator: 'tsgo'; oxc and tsgo objects now only configure their respective generators
    • dts.volarPluginsdts.customLanguages; rename each language's create hook to createVolarPlugins
    • Custom languages, including vue, now throw when combined with an incompatible generator
    • dts.cjsReexport was removed; dual-format builds now generate CJS declarations in a separate pass
  • attw:
    • The default profile changed from strict to esm-only; set profile: 'strict' to preserve the previous checks
  • programmatic API:
    • build() now returns { bundles, watch }; replace const bundles = await build() with const { bundles } = await build()
  • requirements:
    • Node.js 25 is no longer supported; use ^22.18.0, ^24.11.0, or >=26.0.0
    • rolldown-plugin-dts now requires Rolldown 1.2.x
    • Legacy types and typesVersions fallbacks were removed; use TypeScript's bundler, node16, or nodenext module resolution

   🚨 Breaking Changes

   🚀 Features

... (truncated)

Commits

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

… updates

Bumps the development group with 4 updates in the / directory: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node), [oxfmt](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxfmt), [oxlint](https://github.com/oxc-project/oxc/tree/HEAD/npm/oxlint) and [tsdown](https://github.com/rolldown/tsdown).


Updates `@types/node` from 26.4.0 to 26.4.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `oxfmt` from 0.65.0 to 0.66.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxfmt/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxfmt_v0.66.0/npm/oxfmt)

Updates `oxlint` from 1.80.0 to 1.81.0
- [Release notes](https://github.com/oxc-project/oxc/releases)
- [Changelog](https://github.com/oxc-project/oxc/blob/main/npm/oxlint/CHANGELOG.md)
- [Commits](https://github.com/oxc-project/oxc/commits/oxlint_v1.81.0/npm/oxlint)

Updates `tsdown` from 0.22.14 to 0.23.0
- [Release notes](https://github.com/rolldown/tsdown/releases)
- [Commits](rolldown/tsdown@v0.22.14...v0.23.0)

---
updated-dependencies:
- dependency-name: "@types/node"
  dependency-version: 26.4.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: development
- dependency-name: oxfmt
  dependency-version: 0.66.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: oxlint
  dependency-version: 1.81.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
- dependency-name: tsdown
  dependency-version: 0.23.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner September 7, 2026 18:57
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@clawsweeper

clawsweeper Bot commented Sep 7, 2026

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updated@​types/​node@​26.4.0 ⏵ 26.4.11001008196100
Updatedoxfmt@​0.65.0 ⏵ 0.66.086 +11008896100
Updatedtsdown@​0.22.14 ⏵ 0.23.09810088 +198 +1100
Updatedoxlint@​1.80.0 ⏵ 1.81.09910091 +195 -1100

View full report

@clawsweeper clawsweeper Bot added P2 Normal priority bug or improvement with limited blast radius. merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action. labels Sep 7, 2026
@clawsweeper

clawsweeper Bot commented Sep 7, 2026

Copy link
Copy Markdown

Codex review: blocked before merge. Reviewed September 14, 2026, 3:01 PM ET / 19:01 UTC (Revision 7).

ClawSweeper review

What this changes

Updates Node.js types, formatting, linting, and package-building development dependencies and their lockfile resolutions.

Regression provenance

Possible regression — suspected (reviewed change). No predecessor PR is attributed.

Merge readiness

Blocked before merge - 3 items remain

The update remains distinct from main and useful, but the previously reported Node 25 development-install compatibility gap remains unresolved.

Priority: P2
Reviewed head: 989485307493c24ab358ba26ba24bf4b5fcc8d0a

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) The focused update has passing cross-platform checks but retains a concrete development-install compatibility gap.
Proof confidence 🌊 off-meta tidepool Not applicable: This Dependabot tooling PR is exempt from contributor runtime proof; CI exercises build and package-import validation, while the Node 25 migration remains a separate compatibility blocker.
Patch quality 🦐 gold shrimp (3/6) 1 actionable review finding remain.

Verification

Check Result Evidence
Real behavior Not applicable Not applicable: This Dependabot tooling PR is exempt from contributor runtime proof; CI exercises build and package-import validation, while the Node 25 migration remains a separate compatibility blocker.
Evidence reviewed 8 items Introduced compatibility change: The pinned delta upgrades tsdown to 0.23.0 and rolldown-plugin-dts to 0.28.5; both change their Node engine range from ^22.18.0 || >=24.11.0 to ^22.18.0 || ^24.11.0 || >=26.0.0, excluding Node 25.
Contributor setup contract: CONTRIBUTING.md directs contributors to repository-declared Node versions; package.json includes Node 25, while .npmrc sets engine-strict=true. The build script directly executes tsdown with declaration generation, establishing the relevant dependency contract.
Upstream migration requirements: The official v0.23.0 migration guide explicitly drops Node 25. Other listed removals do not match this repository’s simple ESM CLI build or bundler module resolution. Source: https://github.com/rolldown/tsdown/releases/tag/v0.23.0.
Findings 1 actionable finding [P1] Document the Node 25 development-install break
Security None None.

How this fits together

The development toolchain checks the router’s TypeScript source and produces its published JavaScript and type declarations. Contributors and CI install these tools through pnpm before building and validating the package.

flowchart LR
  A[Contributor Node version] --> B[pnpm engine checks]
  C[Locked development tools] --> B
  B --> D[Build and quality checks]
  E[Router source] --> D
  D --> F[JavaScript and declarations]
  F --> G[Package import validation]
Loading

Before merge

  • Document the Node 25 development-install break (P1) - Upgrading tsdown also selects rolldown-plugin-dts 0.28.5, and both now exclude Node 25. CONTRIBUTING.md:16 still directs contributors to the repository engine range, which includes Node 25; with .npmrc enabling engine-strict, fresh or updated development installations on that version fail. Document the development-only range and migration to supported Node, or retain compatible tooling, without narrowing the published router’s runtime engines. This previously reported finding remains unresolved.
  • Resolve merge risk (P1) - Existing contributors using Node 25 will encounter engine-strict installation failures after updating; the documented development setup does not explain the required Node migration.
  • Complete next step (P2) - Document the development-only Node range and Node 25 migration, then validate fresh and upgraded contributor setups while preserving published runtime engines.

Findings

  • [P1] Document the Node 25 development-install break — package.json:57
Agent review details

Security

None.

Review metrics

Metric Value Why it matters
Validation coverage 6 passing jobs: 2 Node versions × 3 operating systems The existing CI covers Node 22 and 24 but does not exercise the excluded Node 25 contributor setup.

Merge-risk options

Maintainer options:

  1. Document the development migration (recommended)
    Explain the supported development Node range and migration from Node 25, and validate fresh and upgraded contributor installations while retaining runtime compatibility.
  2. Retain the compatible builder
    Defer tsdown 0.23 and its declaration-tool upgrade while retaining the other development updates.
Copy recommended automerge instruction
@clawsweeper automerge

Special instructions:
Document the development-only Node range and Node 25 migration in CONTRIBUTING.md and add the repository-required compatibility changelog note; preserve package.json runtime engines and validate fresh and upgraded contributor setups.

Technical review

Best possible solution:

Keep the tooling update with explicit development Node requirements and a Node 25 migration note, preserving the published router’s runtime engine range.

Do we have a high-confidence way to reproduce the issue?

Yes, from source: installing this head’s development dependencies on Node 25 conflicts with two newly narrowed engine ranges under engine-strict. Installation was not executed in this read-only review.

Is this the best way to solve the issue?

The dependency update is reasonable, but incomplete as submitted: separate development requirements from runtime support and document the migration instead of narrowing consumer runtime engines.

Full review comments:

  • [P1] Document the Node 25 development-install break — package.json:57
    Upgrading tsdown also selects rolldown-plugin-dts 0.28.5, and both now exclude Node 25. CONTRIBUTING.md:16 still directs contributors to the repository engine range, which includes Node 25; with .npmrc enabling engine-strict, fresh or updated development installations on that version fail. Document the development-only range and migration to supported Node, or retain compatible tooling, without narrowing the published router’s runtime engines. This previously reported finding remains unresolved.
    Confidence: 0.98

Overall correctness: patch is incorrect
Overall confidence: 0.97

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against ea06377b0e80.

Labels

Label justifications:

  • P2: This is a bounded development-tooling update with a contributor-install compatibility issue.
  • merge-risk: 🚨 compatibility: The new build dependencies exclude Node 25 despite contributor instructions pointing to a repository engine range that includes it.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🦐 gold shrimp.
  • status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: This Dependabot tooling PR is exempt from contributor runtime proof; CI exercises build and package-import validation, while the Node 25 migration remains a separate compatibility blocker.

Evidence

Acceptance criteria:

  • [P1] pnpm install --frozen-lockfile.
  • [P1] pnpm run check.
  • [P1] git diff --check.
  • [P1] git diff --stat.

What I checked:

  • Introduced compatibility change: The pinned delta upgrades tsdown to 0.23.0 and rolldown-plugin-dts to 0.28.5; both change their Node engine range from ^22.18.0 || >=24.11.0 to ^22.18.0 || ^24.11.0 || >=26.0.0, excluding Node 25. (pnpm-lock.yaml:1116, 989485307493)
  • Contributor setup contract: CONTRIBUTING.md directs contributors to repository-declared Node versions; package.json includes Node 25, while .npmrc sets engine-strict=true. The build script directly executes tsdown with declaration generation, establishing the relevant dependency contract. (CONTRIBUTING.md:16, 989485307493)
  • Upstream migration requirements: The official v0.23.0 migration guide explicitly drops Node 25. Other listed removals do not match this repository’s simple ESM CLI build or bundler module resolution. Source: https://github.com/rolldown/tsdown/releases/tag/v0.23.0.
  • Review continuity and captured body: The previous completed review assessed the identical head and reported this same compatibility defect. The fetched full body matched captured SHA-256 80060a1bc3da60539ea22fbe40e38be4626ae557e9c95327098ce8ef220602a5; its omitted migration section acknowledges upstream Node 25 removal but supplies no repository-specific development migration. (989485307493)
  • Main and release necessity check: Current main still selects tsdown ^0.22.14 and oxfmt ^0.65.0. The v0.1.1 package also predates these upgrades. The repository PR listing establishes no merged replacement for this update. (package.json:57, ea06377b0e80)
  • Release package inspection: Read the v0.1.1 package manifest through GitHub after the local historical blob could not be retrieved; it selects tsdown ^0.22.14 and oxfmt ^0.60.0. (package.json:57, f5ce7c0d7c04)

Likely related people:

  • unknown: The claimed source-line change could not be verified from bounded local history. (role: source history unknown; confidence: low)

Rank-up moves

Optional improvements that raise the rating; they are not merge blockers.

  • Document development Node requirements and the Node 25 migration, then validate fresh and upgraded contributor setups without changing runtime engines.

Rating scale

Score Internal tier Crab rank Meaning
6/6 S 🦀 challenger crab Exceptional readiness
5/6 A 🦞 diamond lobster Very strong readiness
4/6 B 🐚 platinum hermit Good normal PR; ordinary maintainer review
3/6 C 🦐 gold shrimp Useful, but confidence is limited
2/6 D 🦪 silver shellfish Proof or implementation needs work
1/6 F 🧂 unranked krab Not merge-ready
N/A NA 🌊 off-meta tidepool Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (6 earlier review cycles)
  • reviewed 2026-09-07T18:59:54.450Z sha 9894853 :: blocked before merge. :: [P1] Document the Node 25 development-install break
  • reviewed 2026-09-08T18:58:56.708Z sha 9894853 :: blocked before merge. :: [P1] [P1] Document the Node 25 development-install break
  • reviewed 2026-09-09T06:59:13.543Z sha 9894853 :: blocked before merge. :: [P1] [P1] Document the Node 25 development-install break
  • reviewed 2026-09-09T18:58:57.322Z sha 9894853 :: blocked before merge. :: [P1] [P1] Document the Node 25 development-install break
  • reviewed 2026-09-10T18:57:48.715Z sha 9894853 :: blocked before merge. :: [P1] [P1] Document the Node 25 development-install break
  • reviewed 2026-09-11T18:59:10.709Z sha 9894853 :: blocked before merge. :: [P1] Document the Node 25 development-install break

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code merge-risk: 🚨 compatibility 🚨 Merging this PR could break existing users, config, migrations, defaults, or upgrades. P2 Normal priority bug or improvement with limited blast radius. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. status: ⏳ waiting on author ClawSweeper has contributor-facing work open and is waiting for author action.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants