Update all dependencies #65

renovate · 2025-08-11T00:46:21Z

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	`v4` → `v6`
actions/download-artifact	action	major	`v4` → `v7`
actions/setup-python	action	major	`v5` → `v6`
actions/upload-artifact	action	major	`v4` → `v6`
coverage	dependencies	minor	`7.10.2` → `7.13.1`
kubernetes	dependencies	major	`33.1.0` → `34.1.0`
pylint (changelog)	dependencies	major	`^3.0.0` → `^4.0.0`
sphinxcontrib-apidoc	dependencies	minor	`^0.5.0` → `^0.6.0`

Release Notes

actions/checkout (actions/checkout)

`v6`

Compare Source

`v5`

Compare Source

actions/download-artifact (actions/download-artifact)

actions/setup-python (actions/setup-python)

`v6`

Compare Source

actions/upload-artifact (actions/upload-artifact)

`v6`

Compare Source

`v5`

Compare Source

coveragepy/coveragepy (coverage)

`v7.13.1`

Compare Source

Added: the JSON report now includes a "start_line" key for function and
class regions, indicating the first line of the region in the source. Closes
issue 2110_.
Added: The debug data command now takes file names as arguments on the
command line, so you can inspect specific data files without needing to set
the COVERAGE_FILE environment variable.
Fix: the JSON report used to report module docstrings as executed lines,
which no other report did, as described in issue 2105_. This is now fixed,
thanks to Jianrong Zhao.
Fix: coverage.py uses a more disciplined approach to detecting where
third-party code is installed, and avoids measuring it. This shouldn't change
any behavior. If you find that it does, please get in touch.
Performance: data files that will be combined now record their hash as part
of the file name. This lets us skip duplicate data more quickly, speeding the
combining step.
Docs: added a section explaining more about what is considered a missing
branch and how it is reported: :ref:branch_explain, as requested in issue 1597. Thanks to Ayisha Mohammed <pull 2092_>.
Tests: the test suite misunderstood what core was being tested if
COVERAGE_CORE wasn't set on 3.14+. This is now fixed, closing issue 2109_.

.. _issue 1597: #1597
.. _pull 2092: #2092
.. _issue 2105: #2105
.. _issue 2109: #2109
.. _issue 2110: #2110

.. _changes_7-13-0:

`v7.13.0`

Compare Source

Feature: coverage.py now supports :file:.coveragerc.toml configuration
files. These files use TOML syntax and take priority over
:file:pyproject.toml but lower priority than :file:.coveragerc files.
Closes issue 1643_ thanks to Olena Yefymenko <pull 1952_>_.
Fix: we now include a permanent .pth file which is installed with the code,
fixing issue 2084. In 7.12.1b1 this was done incorrectly: it didn't work
when using the source wheel (py3-none-any). This is now fixed. Thanks,
Henry Schreiner <pull 2100_>.
Deprecated: when coverage.py is installed, it creates three command entry
points: coverage, coverage3, and coverage-3.10 (if installed for
Python 3.10). The second and third of these are not needed and will
eventually be removed. They still work for now, but print a message about
their deprecation.

.. _issue 1643: #1643
.. _pull 1952: #1952
.. _pull 2100: #2100

.. _changes_7-12-1b1:

`v7.12.0`

Compare Source

The HTML report now shows separate coverage totals for statements and
branches, as well as the usual combined coverage percentage. Thanks to Ryuta
Otsuka for the discussion <issue 2081_>_ and the implementation <pull 2085_>_.
The JSON report now includes separate coverage totals for statements and
branches, thanks to Ryuta Otsuka <pull 2090_>_.
Fix: except* clauses were not handled properly under the "sysmon"
measurement core, causing KeyError exceptions as described in issue 2086_.
This is now fixed.
Fix: we now defend against aggressive mocking of open() that could cause
errors inside coverage.py. An example of a failure is in issue 2083_.
Fix: in unusual cases where a test suite intentionally exhausts the system's
file descriptors to test handling errors in open(), coverage.py would
fail when trying to open source files, as described in issue 2091_. This
is now fixed.
A small tweak to the HTML report: file paths now use thin spaces around
slashes to make them easier to read.

.. _issue 2081: #2081
.. _issue 2083: #2083
.. _pull 2085: #2085
.. _issue 2086: #2086
.. _pull 2090: #2090
.. _issue 2091: #2091

.. _changes_7-11-3:

`v7.11.3`

Compare Source

Fix: the 7.11.1 changes meant that conflicts between a requested measurement
core and other settings would raise an error. This was a breaking change from
previous behavior, as reported in issue 2076_ and issue 2078_.

The previous behavior has been restored: when the requested core conflicts
with other settings, another core is used instead, and a warning is issued.
For contributors: the repo has moved from Ned's nedbat GitHub account_ to
the coveragepy GitHub organization_. The default branch has changed from
master to main.

.. _issue 2076: #2076
.. _issue 2078: #2078
.. _nedbat GitHub account: https://github.com/nedbat
.. _coveragepy GitHub organization: https://github.com/coveragepy

.. _changes_7-11-2:

`v7.11.2`

Compare Source

Fix: using the "sysmon" measurement core in 7.11.1, if Python code was
claimed to come from a non-Python file, a NotPython exception could be
raised. This could happen for example with Jinja templates compiled to
Python, as reported in issue 2077_. This is now fixed.
Doc: corrected the first entry in the 7.11.1 changelog.

.. _issue 2077: #2077

.. _changes_7-11-1:

`v7.11.1`

Compare Source

Fix: some chanages to details of how the measurement core is chosen, and how
conflicting settings are handled. The "sysmon" core cannot be used with some
conurrency settings, with dynamic context, and in Python 3.12/3.13, with
branch measurement.
- If the core is not specified and defaults to "sysmon" (Python 3.14+), but
  other settings conflict with sysmon, then the "ctrace" core will be used
  instead with no warning. For concurrency conflicts, this used to produce an
  error, as described in issue 2064_.
- If the "sysmon" core is explicitly requested in your configuration, but
  other settings conflict, an error is now raised. This used to produce a
  warning.
Fix: some multi-line case clauses or for loops (and probably other
constructs) could cause incorrect claims of missing branches with the
sys.monitoring core, as described in issue 2070_. This is now fixed.
Fix: when running in pytest under coverage, a breakpoint() would stop in
the wrong frame, one level down from where it should, as described in issue 1420_. This was due to a coverage change in v6.4.1 that seemed to give a
slight performance improvement, but I couldn't reproduce the performance
gain, so it's been reverted, fixing the debugger problem.
A new debug option --debug=core shows which core is in use and why.
Split sqlite debugging information out of the sys :ref:coverage debug <cmd_debug> and :ref:cmd_run_debug options since it's bulky and not
very useful.
Updated the :ref:howitworks page to better describe the three different
measurement cores.

.. _issue 1420: #1420
.. _issue 2064: #2064
.. _issue 2070: #2070

.. _changes_7-11-0:

`v7.11.0`

Compare Source

Dropped support for Python 3.9, declared support for Python 3.15 alpha.

.. _changes_7-10-7:

`v7.10.7`

Compare Source

Performance: with branch coverage in large files, generating HTML, JSON, or
LCOV reports could take far too long due to some quadratic behavior when
creating the function and class index pages. This is now fixed, closing
issue 2048_. Thanks to Daniel Diniz for help diagnosing the problem.
Most warnings and a few errors now have links to a page in the docs
explaining the specific message. Closes issue 1921_.

.. _issue 1921: #1921
.. _issue 2048: #2048

.. _changes_7-10-6:

`v7.10.6`

Compare Source

Fix: source directories were not properly communicated to subprocesses
that ran in different directories, as reported in issue 1499_. This is now
fixed.
Performance: Alex Gaynor continues fine-tuning <pull 2038_>_ the speed of
combination, especially with many contexts.

.. _issue 1499: #1499
.. _pull 2038: #2038

.. _changes_7-10-5:

`v7.10.5`

Compare Source

Big speed improvements for coverage combine: it's now about twice as
fast! Huge thanks to Alex Gaynor for pull requests 2032 <pull 2032_>,
2033 <pull 2033_>, and 2034 <pull 2034_>_.

.. _pull 2032: #2032
.. _pull 2033: #2033
.. _pull 2034: #2034

.. _changes_7-10-4:

`v7.10.4`

Compare Source

Added patch = fork for times when the built-in forking support is
insufficient.
Fix: patch = execv also inherits the entire coverage configuration now.

.. _changes_7-10-3:

`v7.10.3`

Compare Source

Fixes for patch = subprocess:
- If subprocesses spawned yet more subprocesses simultaneously, some coverage
  could be missed. This is now fixed, closing issue 2024_.
- If subprocesses were created in other directories, their data files were
  stranded there and not combined into the totals, as described in issue 2025_. This is now fixed.
- On Windows (or maybe only some Windows?) the patch would fail with a
  ModuleNotFound error trying to import coverage. This is now fixed,
  closing issue 2022_.
- Originally only options set in the coverage configuration file would apply
  to subprocesses. Options set on the coverage run command line (such as
  --branch) wouldn't be communicated to the subprocesses. This could
  lead to combining failures, as described in issue 2021_. Now the entire
  configuration is used in subprocesses, regardless of its origin.
- Added debug=patch to help diagnose problems.
Fix: really close all SQLite databases, even in-memory ones. Closes issue 2017_.

.. _issue 2017: #2017
.. _issue 2021: #2021
.. _issue 2022: #2022
.. _issue 2024: #2024
.. _issue 2025: #2025

.. _changes_7-10-2:

kubernetes-client/python (kubernetes)

`v34.1.0`

Compare Source

Kubernetes API Version: v1.34.1

pylint-dev/pylint (pylint)

`v4.0.4`

Compare Source

What's new in Pylint 4.0.4?

Release date: 2025-11-30

False Positives Fixed

Fixed false positive for invalid-name where module-level constants were incorrectly classified as variables when a class-level attribute with the same name exists.

Closes #10719
Fix a false positive for invalid-name on an UPPER_CASED name inside an if branch that assigns an object.

Closes #10745

`v4.0.3`

Compare Source

What's new in Pylint 4.0.3?

Release date: 2025-11-13

False Positives Fixed

Add Enum dunder methods _generate_next_value_, _missing_, _numeric_repr_, _add_alias_, and _add_value_alias_ to the list passed to --good-dunder-names.

Closes #10435
Fixed false positive for invalid-name with typing.Annotated.

Closes #10696
Fix false positive for f-string-without-interpolation with template strings
when using format spec.

Closes #10702
Fix a false positive when an UPPER_CASED class attribute was raising an
invalid-name when typed with Final.

Closes #10711
Fix a false positive for unbalanced-tuple-unpacking when a tuple is assigned to a function call and the structure of the function's return value is ambiguous.

Closes #10721

Other Bug Fixes

Make 'ignore' option work as expected again.

Closes #10669
Fix crash for consider-using-assignment-expr when a variable annotation without assignment
is used as the if test expression.

Closes #10707
Fix crash for prefer-typing-namedtuple and consider-math-not-float when
a slice object is called.

Closes #10708

`v4.0.2`

Compare Source

False Positives Fixed

Fix false positive for invalid-name on a partially uninferable module-level constant.

Closes #10652
Fix a false positive for invalid-name on exclusive module-level assignments
composed of three or more branches. We won't raise disallowed-name on module-level names that can't be inferred
until a further refactor to remove this false negative is done.

Closes #10664
Fix false positive for invalid-name for TypedDict instances.

Closes #10672

`v4.0.1`

Compare Source

What's new in Pylint 4.0.1?

Release date: 2025-10-14

False Positives Fixed

Exclude __all__ and __future__.annotations from unused-variable.

Closes #10019
Fix false-positive for bare-name-capture-pattern if a case guard is used.

Closes #10647
Check enums created with the Enum() functional syntax to pass against the
--class-rgx for the invalid-name check, like other enums.

Closes #10660

`v4.0.0`

Compare Source

Pylint now supports Python 3.14.
Pylint's inference engine (astroid) is now much more precise,
understanding implicit booleanness and ternary expressions. (Thanks @zenlyj!)

Consider this example:

class Result:
    errors: dict | None = None

result = Result()
if result.errors:
    result.errors[field_key]

##### inference engine understands result.errors cannot be None
##### pylint no longer raises unsubscriptable-object

The required astroid version is now 4.0.0. See the astroid changelog for additional fixes, features, and performance improvements applicable to pylint.

Handling of invalid-name at the module level was patchy. Now,
module-level constants that are reassigned are treated as variables and checked
against --variable-rgx rather than --const-rgx. Module-level lists,
sets, and objects can pass against either regex.

Here, LIMIT is reassigned, so pylint only uses --variable-rgx:

LIMIT = 500  # [invalid-name]
if sometimes:
    LIMIT = 1  # [invalid-name]

If this is undesired, refactor using exclusive assignment so that it is
evident that this assignment happens only once:

if sometimes:
    LIMIT = 1
else:
    LIMIT = 500  # exclusive assignment: uses const regex, no warning

Lists, sets, and objects still pass against either const-rgx or variable-rgx
even if reassigned, but are no longer completely skipped:

MY_LIST = []
my_list = []
My_List = []  # [invalid-name]

Remember to adjust the regexes and allow lists to your liking.

Breaking Changes

invalid-name now distinguishes module-level constants that are assigned only once
from those that are reassigned and now applies --variable-rgx to the latter. Values
other than literals (lists, sets, objects) can pass against either the constant or
variable regexes (e.g. "LOGGER" or "logger" but not "LoGgEr").

Remember that --good-names or --good-names-rgxs can be provided to explicitly
allow good names.

Closes #3585
The unused pylintrc argument to PyLinter.__init__() is deprecated
and will be removed.

Refs #6052
Commented out code blocks such as # bar() # TODO: remove dead code will no longer emit fixme.

Refs #9255
pyreverse Run was changed to no longer call sys.exit() in its __init__.
You should now call Run(args).run() which will return the exit code instead.
Having a class that always raised a SystemExit exception was considered a bug.

Normal usage of pyreverse through the CLI will not be affected by this change.

Refs #9689
The suggestion-mode option was removed, as pylint now always emits user-friendly hints instead
of false-positive error messages. You should remove it from your conf if it's defined.

Refs #9962
The async.py checker module has been renamed to async_checker.py since async is a Python keyword
and cannot be imported directly. This allows for better testing and extensibility of the async checker functionality.

Refs #10071
The message-id of continue-in-finally was changed from E0116 to W0136. The warning is
now emitted for every Python version since it will raise a syntax warning in Python 3.14.
See PEP 765 - Disallow return/break/continue that exit a finally block.

Refs #10480
Removed support for nmp.NaN alias for numpy.NaN being recognized in ':ref:nan-comparison'. Use np or numpy instead.

Refs #10583
Version requirement for isort has been bumped to >=5.0.0.
The internal compatibility for older isort versions exposed via pylint.utils.IsortDriver has
been removed.

Refs #10637

New Features

comparison-of-constants now uses the unicode from the ast instead of reformatting from
the node's values preventing some bad formatting due to utf-8 limitation. The message now uses
" instead of ' to better work with what the python ast returns.

Refs #8736
Enhanced pyreverse to properly distinguish between UML relationship types (association, aggregation, composition) based on object ownership semantics. Type annotations without assignment are now treated as associations, parameter assignments as aggregations, and object instantiation as compositions.

Closes #9045
Closes #9267
The fixme check can now search through docstrings as well as comments, by using
check-fixme-in-docstring = true in the [tool.pylint.miscellaneous] section.

Closes #9255
The use-implicit-booleaness-not-x checks now distinguish between comparisons
used in boolean contexts and those that are not, enabling them to provide more accurate refactoring suggestions.

Closes #9353
The verbose option now outputs the filenames of the files that have been checked.
Previously, it only included the number of checked and skipped files.

Closes #9357
colorized reporter now colorizes messages/categories that have been configured as fail-on in red inverse.
This makes it easier to quickly find the errors that are causing pylint CI job failures.

Closes #9898
Enhanced support for @property decorator in pyreverse to correctly display return types of annotated properties when generating class diagrams.

Closes #10057
Add --max-depth option to pyreverse to control diagram complexity. A depth of 0 shows only top-level packages, 1 shows one level of subpackages, etc.
This helps manage visualization of large codebases by limiting the depth of displayed packages and classes.

Refs #10077
Handle deferred evaluation of annotations in Python 3.14.

Closes #10149
Enhanced pyreverse to properly detect aggregations for comprehensions (list, dict, set, generator).

Closes #10236
pyreverse: add support for colorized output when using output format mmd (MermaidJS) and html.

Closes #10242
pypy 3.11 is now officially supported.

Refs #10287
Add support for Python 3.14.

Refs #10467
Add naming styles for ParamSpec and TypeVarTuple that align with the TypeVar style.

Refs #10541

New Checks

Add match-statements checker and the following message:
bare-name-capture-pattern.
This will emit an error message when a name capture pattern is used in a match statement which would make the remaining patterns unreachable.
This code is a SyntaxError at runtime.

Closes #7128
Add new check async-context-manager-with-regular-with to detect async context managers used with regular with statements instead of async with.

Refs #10408
Add break-in-finally warning. Using break inside the finally clause
will raise a syntax warning in Python 3.14.
See PEP 765 - Disallow return/break/continue that exit a finally block <https://peps.python.org/pep-0765/>_.

Refs #10480
Add new checks for invalid uses of class patterns in :keyword:match.
- :ref:invalid-match-args-definition is emitted if :py:data:object.__match_args__ isn't a tuple of strings.
- :ref:too-many-positional-sub-patterns if there are more positional sub-patterns than specified in :py:data:object.__match_args__.
- :ref:multiple-class-sub-patterns if there are multiple sub-patterns for the same attribute.
Refs #10559
Add additional checks for suboptimal uses of class patterns in :keyword:match.
- :ref:match-class-bind-self is emitted if a name is bound to self instead of
  using an as pattern.
- :ref:match-class-positional-attributes is emitted if a class pattern has positional
  attributes when keywords could be used.
Refs #10587
Add a consider-math-not-float message. float("nan") and float("inf") are slower
than their counterpart math.inf and math.nan by a factor of 4 (notwithstanding
the initial import of math) and they are also not well typed when using mypy.
This check also catches typos in float calls as a side effect.

The :ref:pylint.extensions.code_style need to be activated for this check to work.

Refs #10621

False Positives Fixed

Fix a false positive for used-before-assignment when a variable defined under
an if and via a named expression (walrus operator) is used later when guarded
under the same if test.

Closes #10061
Fix :ref:no-name-in-module for members of concurrent.futures with Python 3.14.

Closes #10632

False Negatives Fixed

Fix false negative for used-before-assignment when a TYPE_CHECKING import is used as a type annotation prior to erroneous usage.

Refs #8893
Match cases are now counted as edges in the McCabe graph and will increase the complexity accordingly.

Refs #9667
Check module-level constants with type annotations for invalid-name.
Remember to adjust const-naming-style or const-rgx to your liking.

Closes #9770
Fix false negative where function-redefined (E0102) was not reported for functions with a leading underscore.

Closes #9894
We now raise a logging-too-few-args for format string with no
interpolation arguments at all (i.e. for something like logging.debug("Awaiting process %s")
or logging.debug("Awaiting process {pid}")). Previously we did not raise for such case.

Closes #9999
Fix false negative for used-before-assignment when a function is defined inside a TYPE_CHECKING guard block and used later.

Closes #10028
Fix a false negative for possibly-used-before-assignment when a variable is conditionally defined
and later assigned to a type-annotated variable.

Closes #10421
Fix false negative for deprecated-module when a __import__ method is used instead of import sentence.

Refs #10453
Count match cases for too-many-branches check.

Refs #10542
Fix false-negative where :ref:unused-import was not reported for names referenced in a preceding global statement.

Refs #10633

Other Bug Fixes

When displaying unicode with surrogates (or other potential UnicodeEncodeError),
pylint will now display a '?' character (using encode(encoding="utf-8", errors="replace"))
instead of crashing. The functional tests classes are also updated to handle this case.

Closes #8736
Fixed unidiomatic-typecheck only checking left-hand side.

Closes #10217
Fix a crash caused by malformed format strings when using .format with keyword arguments.

Closes #10282
Fix false positive inconsistent-return-statements when using quit() or exit() functions.

Closes #10508
Fix a crash in :ref:nested-min-max when using builtins.min or builtins.max
instead of min or max directly.

Closes #10626
Fixed a crash in :ref:unnecessary-dict-index-lookup when the index of an enumerated list
was deleted inside a for loop.

Closes #10627

Other Changes

Remove support for launching pylint with Python 3.9.
Code that supports Python 3.9 can still be linted with the --py-version=3.9 setting.

Refs #10405

Internal Changes

Modified test framework to allow for different test output for different Python versions.

Refs #10382

`v3.3.9`

Compare Source

What's new in Pylint 3.3.9?

Release date: 2025-10-05

False Positives Fixed

Fix used-before-assignment for PEP 695 type aliases and parameters.

Closes #9815
No longer flag undeprecated functions in importlib.resources as deprecated.

Closes #10593
Fix false positive inconsistent-return-statements when using quit() or exit() functions.

Closes #10508
Fix false positive undefined-variable (E0602) for for-loop variable shadowing patterns like for item in item: when the variable was previously defined.

Closes #10562

Other Bug Fixes

Fixed crash in 'unnecessary-list-index-lookup' when starting an enumeration using
minus the length of an iterable inside a dict comprehension when the len call was only
made in this dict comprehension, and not elsewhere. Also changed the approach,
to use inference in all cases but the simple ones, so we don't have to fix crashes
one by one for arbitrarily complex expressions in enumerate.

Closes #10510

`v3.3.8`

Compare Source

What's new in Pylint 3.3.8?

Release date: 2025-08-09

This patch release includes an exceptional fix for a false negative issue. For details, see: #10482 (comment)

False Positives Fixed

Fix false positives for possibly-used-before-assignment when variables are exhaustively
assigned within a match block.

Closes #9668
Fix false positive for missing-raises-doc and missing-yield-doc when the method length is less than docstring-min-length.

Refs #10104
Fix a false positive for unused-variable when multiple except handlers bind the same name under a try block.

Closes #10426

False Negatives Fixed

Fix false-negative for used-before-assignment with from __future__ import annotations in function definitions.

Refs #10482

Other Bug Fixes

Fix a bug in Pyreverse where aggregations and associations were included in diagrams regardless of the selected --filter-mode (such as PUB_ONLY, ALL, etc.).

Closes #10373
Fix double underscores erroneously rendering as bold in pyreverse's Mermaid output.

Closes #10402

sphinx-contrib/apidoc (sphinxcontrib-apidoc)

`v0.6.0`

Compare Source

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/all branch from b2ea717 to 1de70e5 Compare August 11, 2025 14:53

renovate bot force-pushed the renovate/all branch from 1de70e5 to a37722c Compare September 6, 2025 19:13

renovate bot force-pushed the renovate/all branch from a37722c to 5868cfe Compare September 29, 2025 22:10

renovate bot force-pushed the renovate/all branch 3 times, most recently from 496ca9c to 8eba457 Compare October 15, 2025 17:52

renovate bot force-pushed the renovate/all branch 2 times, most recently from 1ecf877 to 23fcabe Compare October 24, 2025 21:55

renovate bot force-pushed the renovate/all branch 4 times, most recently from f3242b5 to aaae1a3 Compare November 13, 2025 20:44

renovate bot force-pushed the renovate/all branch 2 times, most recently from 2f44e26 to 019c492 Compare November 20, 2025 17:56

renovate bot force-pushed the renovate/all branch from 019c492 to 88b3352 Compare November 30, 2025 18:40

renovate bot force-pushed the renovate/all branch 2 times, most recently from 390516c to 0d2d39f Compare December 12, 2025 21:34

Update all dependencies

cd36e0d

Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

renovate bot force-pushed the renovate/all branch from 0d2d39f to cd36e0d Compare December 28, 2025 17:05

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Update all dependencies #65

Update all dependencies #65

Uh oh!

renovate bot commented Aug 11, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Update all dependencies #65

Are you sure you want to change the base?

Update all dependencies #65

Uh oh!

Conversation

renovate bot commented Aug 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

What's new in Pylint 4.0.4?

False Positives Fixed

What's new in Pylint 4.0.3?

False Positives Fixed

Other Bug Fixes

False Positives Fixed

What's new in Pylint 4.0.1?

False Positives Fixed

Breaking Changes

New Features

New Checks

False Positives Fixed

False Negatives Fixed

Other Bug Fixes

Other Changes

Internal Changes

What's new in Pylint 3.3.9?

False Positives Fixed

Other Bug Fixes

What's new in Pylint 3.3.8?

False Positives Fixed

False Negatives Fixed

Other Bug Fixes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Aug 11, 2025 •

edited

Loading