chore(deps-dev): Bump no-defaults from 2.0.0 to 2.1.0 - #3139

Sourced from no-defaults's releases.

v2.1.0

What's Changed

• Leave one unfixable file alone rather than aborting the run by @​adamtheturtle in adamtheturtle/no-defaults#76
• Inherit the fields of a base that is a dataclass in the same file by @​adamtheturtle in adamtheturtle/no-defaults#77
• Refresh the performance figures for 2.0.0 by @​adamtheturtle in adamtheturtle/no-defaults#78
• Do not count a default in an unfixed file as removed by @​adamtheturtle in adamtheturtle/no-defaults#79
• Report call sites even when no default was removed by @​adamtheturtle in adamtheturtle/no-defaults#80
• Keep the defaults that follow one which cannot be removed by @​adamtheturtle in adamtheturtle/no-defaults#82
• Prepare the 2.1.0 release by @​adamtheturtle in adamtheturtle/no-defaults#83

Full Changelog: adamtheturtle/no-defaults@v2.0.0...v2.1.0

Sourced from no-defaults's changelog.

2.1.0 - 2026-08-07

Anyone on 2.0.0 who uses --fix on a project containing .pyi stubs should upgrade: see the first entry under ### Fixed.

Added

• --fix updates the construction sites of a dataclass whose base is a dataclass in the same file. The base's fields come first in the generated constructor, so Child() becomes Child(a=1, b=2) where a is the base's, and a subclass that removed nothing of its own still gets back the defaults its base lost. It stays narrow: one base only, because dataclasses walks the reverse MRO to order several; the base must be named directly and its own constructor fully known; and a name two classes share resolves to neither. Anything else keeps the existing warning.

Changed

• A file whose fix would not have parsed is left alone by itself, rather than aborting the whole run with exit status 2 and writing nothing anywhere. One file this linter has a bug on no longer blocks fixing an entire project. The file is named in a warning, counted as remaining rather than fixed, and the run exits 1 with an accurate summary.

Fixed

• A default that cannot be removed now keeps the defaults after it. Since 2.0.0 made = ... in a stub unfixable, a signature mixing it with an ordinary default was rewritten into def f(x: int = ..., y: int), which Python rejects — on the pinned Typeshed checkout that hit 175 files, and 2.0.0 aborted the whole run over it, fixing nothing anywhere. The dataclass form was worse: a: int = ... followed by a fixed b: int is valid syntax, so it was written out and raised TypeError: non-default argument 'b' follows default argument 'a' at import. Keyword-only parameters and fields are exempt, since order does not constrain them.

Documentation

• The ## Performance section quotes measured 2.0.0 figures rather than 1.0.0 ones, gives full and concise side by side, and drops a caveat about full-output memory that the fixes to its quadratic behaviour made obsolete.

• 1d2ff2e Prepare the 2.1.0 release (#83)
• f3e194c Keep the defaults that follow one which cannot be removed (#82)
• e022b2e Report call sites even when no default was removed (#80)
• d933a43 Do not count a default in an unfixed file as removed (#79)
• ad172a4 Refresh the performance figures for 2.0.0 (#78)
• 9c4641a Inherit the fields of a base that is a dataclass in the same file (#77)
• 43a5f70 Leave one unfixable file alone rather than aborting the run (#76)
• See full diff in compare view

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)