Bump the python-packages group with 9 updates

Merged
DE
11d ago
+381-268

Bumps the python-packages group with 9 updates:

PackageFromTo
coverage7.14.37.17.0
more-itertools11.1.011.2.1
pbr7.0.37.1.3
pluggy1.6.01.7.0
ruff0.15.190.17.2
mypy2.1.02.4.0
types-pyyaml6.0.12.202605186.0.12.20260906
mkdocstrings-python2.0.52.0.10
pymdown-extensions11.0.112.3

Updates coverage from 7.14.3 to 7.17.0

Release notes

Sourced from coverage's releases.

7.17.0

Version 7.17.0 — 2026-10-22

  • Dropped support for Python 3.10.
  • Binary wheels are now provided for iOS and Android. This allows the use of the optimized C tracer on mobile platforms.
  • Fix: three or more levels of nested with statements could make a with line look like a branch with an exit that can never happen. Using the sys.monitoring core, these phantom branches were reported as partial. Other cores hid the problem but still counted the phantom branches in the total. Closes issue 1987.
  • Fix: a comment or string that merely mentioned if True: or while True: could mark its line as a branch that is known to be partial, so a branch that never ran was reported as taken. These built-in patterns now only match at the start of the statement. Closes issue 2314.
  • Fix: region detection missed functions defined in unusual places, such as else and except clauses. This is now fixed.
  • Fix: recent versions of the lcov tool complain if the same function name appears more than once in a report. Python can have multiple same-named functions in a few ways, for example, getters/setters or conditionally defined functions. These are now disambiguated by adding a @<line number> suffix to the function name. Fixes issue 2335.
  • Fix: The “Can’t combine statement coverage data with branch data” error now names the two data files it couldn’t combine. The error description in the docs now lists common causes and how to find the process that wrote the file.
  • Fix: at coverage totals close to 0 or 100, the XML report could get incorrect line-rate values like 8.333e-05 or 1. This is now fixed, closing issue 2293 and issue 2294.
  • Fix: a parallel data file saved more than once kept the hash of its first save in its file name. Combining could then skip it as a duplicate of another file that had the same data at that point, and delete it, losing the data recorded after the first save. Each save now updates the hash. This had been a problem since 7.13.1. Fixes issue 2338.
  • Fixes for obscure but legal file names:
    • File names (and plugin names) can contain control characters, which are legal in POSIX paths but unsafe in reports: in XML 1.0 they make the document non-well-formed, and in a terminal they act as escape sequences (colors, title/clipboard sequences, cursor moves that forge output). Now the XML report, the text and Markdown summary reports, and coverage debug data replace non-printable characters in names. Printable names are unchanged.
    • A file pattern (from include, omit, or a [paths] alias) containing a newline sent the glob-to-regex translation into an infinite loop, hanging the process. Newlines in patterns are now handled like any other character.
  • Fixes in the implementation of the C tracer:
    • If a plugin’s dynamic_source_filename method raised an exception, lines in that function could be recorded as belonging to a different file. Also fixed some minor memory leaks in the C tracer.
    • The refcount of None was mismanaged during function calls, including comprehensions. This was unlikely to cause an actual problem, but is now fixed. Thanks, Andrew Dalke.
    • The C tracer held borrowed references to dictionary values, which was unsafe on free-threaded Python. Now it takes its own references.
    • An internal error while recording a new file could be reported as a confusing SystemError instead of the actual exception.
  • Performance: the text summary report (coverage report) held on to every file’s parsed source until it finished, so its memory use grew with the size of the project: ten times or more what 7.14 used on large projects. Now it keeps only what it needs to print. Fixes issue 2277.
  • Performance: HTML reports should be about 5% faster to produce.
  • Kept the political banner in the README. Closes issue 2344.

:arrow_right:  PyPI page: coverage 7.17.0. :arrow_right:  To install: python3 -m pip install coverage==7.17.0

7.16.2

Version 7.16.2 — 2026-09-27

  • Fix: on Python 3.14 and later, a for loop completing immediately before a function return could mistakenly report an uncovered branch. This is now fixed, closing issue 2168.
  • Fix: on Python 3.14 and later, the else clause of a try whose body is a with statement could incorrectly be reported as covered when the with raised. This is now fixed, closing issue 2289.
  • Fix: with dynamic_context = test_function, test methods written as @staticmethod or @classmethod were not given a context of their own. Now they are, on Python 3.11 and later. Closes issue 1923.

:arrow_right:  PyPI page: coverage 7.16.2. :arrow_right:  To install: python3 -m pip install coverage==7.16.2

7.16.1

Version 7.16.1 — 2026-09-13

  • Fix: when the body of an irrefutable case (like case _:) is entirely excluded, the case line is now excluded too, just as an excluded else: body removes the else: line. Previously the case line was left behind and reported as missing. Closes issue 1563 with pull 2269.
  • Fix: using CoverageData.update() twice on an in-memory database would fail, as described in issue 2279. This is now fixed.
  • Fix: the Total row in the footer of the HTML report’s index page was recomputed in JavaScript with rounding that could disagree with the total the server rendered in the heading, including showing 100% when coverage was not complete. The footer now clamps values the way the rest of the report does, and when nothing is filtered out it is shown exactly as the server rendered it, so the two can’t disagree. That also keeps rows the report omits (--skip-covered drops fully covered files) in the total. Fixes issue 2256.

:arrow_right:  PyPI page: coverage 7.16.1. :arrow_right:  To install: python3 -m pip install coverage==7.16.1

7.16.0

Version 7.16.0 — 2026-08-28

... (truncated)

Changelog

Sourced from coverage's changelog.

Version 7.17.0 — 2026-10-22

  • Dropped support for Python 3.10.

  • Binary wheels are now provided for iOS and Android. This allows the use of the optimized C tracer on mobile platforms.

  • Fix: three or more levels of nested with statements could make a with line look like a branch with an exit that can never happen. Using the sys.monitoring core, these phantom branches were reported as partial. Other cores hid the problem but still counted the phantom branches in the total. Closes issue 1987_.

  • Fix: a comment or string that merely mentioned if True: or while True: could mark its line as a branch that is known to be partial, so a branch that never ran was reported as taken. These built-in patterns now only match at the start of the statement. Closes issue 2314_.

  • Fix: region detection missed functions defined in unusual places, such as else and except clauses. This is now fixed.

  • Fix: recent versions of the lcov tool complain if the same function name appears more than once in a report. Python can have multiple same-named functions in a few ways, for example, getters/setters or conditionally defined functions. These are now disambiguated by adding a @<line number> suffix to the function name. Fixes issue 2335.

  • Fix: The "Can't combine statement coverage data with branch data" error now names the two data files it couldn't combine. The :ref:error description <error_cant_combine> in the docs now lists common causes and how to find the process that wrote the file.

  • Fix: at coverage totals close to 0 or 100, the XML report could get incorrect line-rate values like 8.333e-05 or 1. This is now fixed, closing issue 2293_ and issue 2294_.

  • Fix: a parallel data file saved more than once kept the hash of its first save in its file name. Combining could then skip it as a duplicate of another file that had the same data at that point, and delete it, losing the data recorded after the first save. Each save now updates the hash. This had been a problem since 7.13.1. Fixes issue 2338_.

  • Fixes for obscure but legal file names:

    • File names (and plugin names) can contain control characters, which are legal in POSIX paths but unsafe in reports: in XML 1.0 they make the document non-well-formed, and in a terminal they act as escape sequences (colors, title/clipboard sequences, cursor moves that forge output). Now the XML report, the text and Markdown summary reports, and ``coverage debug

... (truncated)

Commits
  • 393ac71 docs: prep for 7.17.0
  • 14257d3 test: check that 100% files haven't lost coverage
  • db056ac docs: keep the ukraine banner #2344
  • 6033660 fix: update the data file hash when a parallel data file is saved again (#2339)
  • 99024b5 fix: clamp rate in XML report to prevent false 1.0/0.0 rounding and scientifi...
  • ff62a02 refactor: remove unused caching branches
  • 24d0b67 fix: KeyError for a with statement at the end of a finally clause (#2336)
  • 934f5b8 chore: upgrade pip==26.2.2 certifi==2026.10.19
  • f95c980 fix: triply nested with statements don't cause false branch misses #1987
  • 6aaa858 docs: more changelog gardening
  • Additional commits viewable in compare view

Updates more-itertools from 11.1.0 to 11.2.1

Release notes

Sourced from more-itertools's releases.

Version 11.2.1

This release includes #1331, a packaging-related change. No module code changed.

Version 11.2.0

Highlights:

  • New random_ordered_range function
  • New subfactorial function
  • Python 3.10 is no longer officially supported
  • Python 3.15 is now officially supported

See the release notes for details.

Commits
  • 4aeb433 Merge pull request #1331 from more-itertools/flit-4-sdist
  • da864da Version 11.2.1: Include additional files in sdist
  • 737c261 Merge pull request #1314 from more-itertools/version-11.2.0
  • 909b703 Bump version to 11.2.0
  • 6ad55cb Swap 310 for 315 in tox
  • 787bcb5 Drop typing_extensions for more.pyi
  • 68a52e0 Update versions.rst
  • be6ecc0 Changelog tweaks
  • 45c65a3 Even more WIP release notes for 11.2.0
  • 56a469c More WIP release ntoes 11.2.0
  • Additional commits viewable in compare view

Updates pbr from 7.0.3 to 7.1.3

Updates pluggy from 1.6.0 to 1.7.0

Changelog

Sourced from pluggy's changelog.

pluggy 1.7.0 (2026-10-14)

Deprecations and Removals

  • [#632](https://github.com/pytest-dev/pluggy/issues/632) <https://github.com/pytest-dev/pluggy/issues/632>_: Hookspec methods defined without self as the first parameter now emit a :class:DeprecationWarning. Add self as the first parameter or use @staticmethod.

Features

  • [#170](https://github.com/pytest-dev/pluggy/issues/170) <https://github.com/pytest-dev/pluggy/issues/170>_: Hookspecs can now declare default values for arguments, using the usual def myhook(myarg="default") syntax. This is mainly a backward compatibility feature, to allow a hookspec to add new parameters to an existing hook without breaking existing callers. See :ref:hookspec_arg_default for details.

  • [#729](https://github.com/pytest-dev/pluggy/issues/729) <https://github.com/pytest-dev/pluggy/issues/729>_: Tracing now adds detail where str() is ambiguous: empty strings and strings containing whitespace are quoted, and enums and paths show their repr().

    A value spanning several lines is now displayed as a block instead of running into the surrounding trace.

Bug Fixes

  • [#629](https://github.com/pytest-dev/pluggy/issues/629) <https://github.com/pytest-dev/pluggy/issues/629>_: Fix hooks failing to register on Python 3.14+ when type annotations use forward references.

  • [#315](https://github.com/pytest-dev/pluggy/issues/315) <https://github.com/pytest-dev/pluggy/issues/315>_: Source archives created by git archive (including GitHub's "Source code" downloads) now carry version information, so building pluggy from them no longer fails with a missing version.

  • [#442](https://github.com/pytest-dev/pluggy/issues/442) <https://github.com/pytest-dev/pluggy/issues/442>_: With the addition of default values for hookspec arguments, we also changed the precedence of default values for hookimpl arguments. Previously, if a hookimpl function declared a default for an argument, it was always used, even if the hook call passed an explicit value. Now the precedence is changed to: hook call passed value > hookspec default value > hookimpl default value. See :ref:hookimpl_arg_defaults.

  • [#701](https://github.com/pytest-dev/pluggy/issues/701) <https://github.com/pytest-dev/pluggy/issues/701>_: Hookimpls and hookspecs are now discovered via :func:inspect.getattr_static, so properties, cached_property and other descriptors are no longer executed while scanning a plugin. Hooks declared through such a descriptor are not supported.

    As a side effect, @hookimpl/@hookspec applied above @classmethod or @staticmethod is now picked up; previously the marker sat on the wrapper where getattr() never saw it. Callables stored directly on a plugin instance -- in its __dict__ or in a __slots__ slot -- keep being called exactly as getattr() returned them, i.e. without an implicit self.

... (truncated)

Commits
  • 4c7f636 Preparing release 1.7.0
  • 21c7e16 Merge pull request #787 from pytest-dev/rm-outdated-doc
  • 628959b docs: remove outdated hookimpl default args paragraph
  • 2edab5e Merge pull request #752 from bluetech/register-none-allow
  • 6995073 Merge pull request #776 from RonnyPfannschmidt/fix/uv-lock-pytest-downgrade
  • 50c1ac9 [pre-commit.ci] pre-commit autoupdate (#781)
  • 6a7e84e Add changelog fragment for #776
  • d22cfb5 Drop tox from the dev dependency group
  • 74cbfa2 Relock pytest and tox that dependabot downgraded
  • 87f130a Merge pull request #755 from harbinresearcher/codex/entrypoint-plugin-presence
  • Additional commits viewable in compare view

Updates ruff from 0.15.19 to 0.17.2

Release notes

Sourced from ruff's releases.

0.17.2

Release Notes

Released on 2026-10-22.

Preview features

  • [complexity] Add unnecessary-regular-expression-compile (#25533)

Bug fixes

  • Avoid syntax errors for type variables with starred constraints (UP040, UP046, UP047, RUF053) (#28362)
  • [pydocstyle] Treat backslash-escaped *args and **kwargs as documented (D417) (#29536)
  • [pylint] Avoid false positive on starred elements (PLE0643) (#29483)
  • [pylint] Mark fixes unsafe when deleting comments (PLR5501, PLW0120) (#29414)
  • [pyupgrade] Mark fix unsafe when deleting comments (UP035) (#29413)

Performance

  • Avoid intermediate names in lint name resolution (#29506)
  • Prefilter bidirectional Unicode checks by UTF-8 leading bytes (#29561)
  • Share postfix parsing and reduce expression copies (#29480)

Configuration

  • [pylint] Add a configurable allowlist for magic-value-comparison (PLR2004) (#18961)

Documentation

  • Clarify documentation and correct stale guidance (#29374)
  • [pyupgrade] Remove mentions of variance related to fix safety (UP040, UP047) (#29592)

Contributors

Install ruff 0.17.2

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.17.2/ruff-installer.sh | sh
</tr></table>

... (truncated)

Changelog

Sourced from ruff's changelog.

0.17.2

Released on 2026-10-22.

Preview features

  • [complexity] Add unnecessary-regular-expression-compile (#25533)

Bug fixes

  • Avoid syntax errors for type variables with starred constraints (UP040, UP046, UP047, RUF053) (#28362)
  • [pydocstyle] Treat backslash-escaped *args and **kwargs as documented (D417) (#29536)
  • [pylint] Avoid false positive on starred elements (PLE0643) (#29483)
  • [pylint] Mark fixes unsafe when deleting comments (PLR5501, PLW0120) (#29414)
  • [pyupgrade] Mark fix unsafe when deleting comments (UP035) (#29413)

Performance

  • Avoid intermediate names in lint name resolution (#29506)
  • Prefilter bidirectional Unicode checks by UTF-8 leading bytes (#29561)
  • Share postfix parsing and reduce expression copies (#29480)

Configuration

  • [pylint] Add a configurable allowlist for magic-value-comparison (PLR2004) (#18961)

Documentation

  • Clarify documentation and correct stale guidance (#29374)
  • [pyupgrade] Remove mentions of variance related to fix safety (UP040, UP047) (#29592)

Contributors

0.17.1

Released on 2026-10-15.

Preview features

  • [pycodestyle] Don't treat None, True, or False as keywords (E271-E274) (#29322)

... (truncated)

Commits
  • 30516b4 Bump version to 0.17.2 (#29637)
  • 59a9e85 [ty] Generalize nested types in inferred return types (#29488)
  • 0d562aa [ty] Check inherited attribute conflicts (#28559)
  • 48dcdd0 [ty] Restrict range implications from gradual equivalence (#29577)
  • 734d75a [ty] Check for unsatisfiable bodies before existentially quantifying (#29504)
  • b0f9526 [ty] Preserve checks for recursive descriptor setter types (#29148)
  • 32869b4 Avoid creating deployments for automation jobs (#29626)
  • ec891ba Link the commit in pull request report footers (#29621)
  • 8958748 [ty] Publish ecosystem reports from GitHub Actions (#29609)
  • 01f5394 [ty] Publish typing conformance reports from GitHub Actions (#29608)
  • Additional commits viewable in compare view

Updates mypy from 2.1.0 to 2.4.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next Release

Mypy 2.4

We've just uploaded mypy 2.4.0 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Python 3.15 Support

Mypy 2.4 supports running on Python 3.15 and type checking most Python 3.15 features. This includes the new builtin sentinel type for sentinel values (PEP 661), which mypy now supports (see below for details). Lazy imports (PEP 810) and unpacking in comprehensions (PEP 798) are also supported. Closed TypedDicts (PEP 728) have been supported since mypy 2.2, but the extra_items TypedDict argument, also introduced in PEP 728, is still unsupported. Support for extra_items will be added in a future mypy release.

Native Parser Enabled by Default

Mypy now uses the new native parser by default. It's based on the Ruff parser, and it's significantly faster than the legacy parser, which uses the stdlib ast module. The native parser also has other benefits:

  • You can target newer Python versions and use recent Python syntax even when running mypy on an older Python version. For example, you can use --python-version 3.15 when running mypy on Python 3.14.
  • Stub files can use syntax that is newer than the target Python version. For example, stubs can use the PEP 695 generic class syntax (class Box[T]: ...) when running on or targeting Python 3.10.
  • Parallel type checking requires the native parser.

The legacy parser is still available through --no-native-parser, or native_parser = False in the config file (native_parser = false under [tool.mypy] in pyproject.toml). We are planning to remove the legacy parser in early 2027. If you run into a problem with the native parser, please report it on the issue tracker.

Unlike the legacy parser, the native parser doesn't support type comments for variables defined by for and with statements. These type comments are silently ignored, and the types of the variables are

... (truncated)

Commits

Updates types-pyyaml from 6.0.12.20260518 to 6.0.12.20260906

Commits

Updates mkdocstrings-python from 2.0.5 to 2.0.10

Release notes

Sourced from mkdocstrings-python's releases.

2.0.10

2.0.10 - 2026-10-19

Compare with 2.0.9

Build

  • Drop support for Python 3.10 (aad7fc6 by Timothée Mazzucotelli).

Bug Fixes

  • Prefix code anchor/span IDs in signatures to avoid collisions (35cde4c by Timothée Mazzucotelli). Issue-200

2.0.9

2.0.9 - 2026-09-22

Compare with 2.0.8

Bug Fixes

  • Improve inventory object types (incorrectly called roles in mkdocstrings) (d754326 by Timothée Mazzucotelli). Issue-339, PR-340
  • Expand relative cross-references against the object the docstring was written on (a9a4ca3 by Dev M). Issue-341, PR-342

Performance Improvements

  • Small performance improvement when getting aliases and formatting/highlighting signatures (2263163 by Timothée Mazzucotelli).

2.0.8

2.0.8 - 2026-08-31

Compare with 2.0.7

Performance Improvements

  • Make template existence test (for locale templates) faster (c0424f2 by Timothée Mazzucotelli).

2.0.7

2.0.7 - 2026-08-17

Compare with 2.0.6

Bug Fixes

2.0.6

2.0.6 - 2026-08-16

Compare with 2.0.5

... (truncated)

Changelog

Sourced from mkdocstrings-python's changelog.

2.0.10 - 2026-10-19

Compare with 2.0.9

Build

  • Drop support for Python 3.10 (aad7fc6 by Timothée Mazzucotelli).

Bug Fixes

  • Prefix code anchor/span IDs in signatures to avoid collisions (35cde4c by Timothée Mazzucotelli). Issue-200

2.0.9 - 2026-09-22

Compare with 2.0.8

Bug Fixes

  • Improve inventory object types (incorrectly called roles in mkdocstrings) (d754326 by Timothée Mazzucotelli). Issue-339, PR-340
  • Expand relative cross-references against the object the docstring was written on (a9a4ca3 by Dev M). Issue-341, PR-342

Performance Improvements

  • Small performance improvement when getting aliases and formatting/highlighting signatures (2263163 by Timothée Mazzucotelli).

2.0.8 - 2026-08-31

Compare with 2.0.7

Performance Improvements

  • Make template existence test (for locale templates) faster (c0424f2 by Timothée Mazzucotelli).

2.0.7 - 2026-08-17

Compare with 2.0.6

Bug Fixes

2.0.6 - 2026-08-16

Compare with 2.0.5

Bug Fixes

  • Don't pass unsupported options to Griffe parsers (4b38b6b by Timothée Mazzucotelli). Issue-337
  • Increase stash key length from 1 to 2 (6ff2749 by Jonas Haag). PR-336
Commits
  • f561c84 chore: Prepare release 2.0.10
  • aad7fc6 build: Drop support for Python 3.10
  • 35cde4c fix: Prefix code anchor/span IDs in signatures to avoid collisions
  • c888dc2 chore: Prepare release 2.0.9
  • 2263163 perf: Small performance improvement when getting aliases and formatting/highl...
  • d754326 fix: Improve inventory object types (incorrectly called roles in mkdocstrings)
  • a9a4ca3 fix: Expand relative cross-references against the object the docstring was wr...
  • 8125b0d chore: Prepare release 2.0.8
  • 5054240 chore: Be a bit more minijinja compatible
  • c0424f2 perf: Make template existence test (for locale templates) faster
  • Additional commits viewable in compare view

Updates pymdown-extensions from 11.0.1 to 12.3

Release notes

Sourced from pymdown-extensions's releases.

12.3

  • NEW: BetterEm: Expose a way to disable CommonMark punctuation rules in BetterEm if desired via a new punctuation option.

12.2

  • NEW: Add official support for Python 3.15.
  • NEW: Tilde, Caret: For backwards compatibility, disable CommonMark punctuation rules by default. If subscript or superscript is disabled in the respective extension, CommonMark rules will be honored again. A new punctuation rule has been added to force CommonMark rules. When done, people will need to be aware of punctuation when subscript or superscript is enabled and escape any that violates CommonMark rules.
  • NEW: Highlight: Highlight now allows in the auto_title_map specifying the title as a simple string or a dictionary containing the title and the title mode: either text or html, with text being the default. This allows a title to be specified and treated as HTML when the mode is html.
  • NEW: SuperFences: Add new title_mode option for Pygments fenced blocks that allows a user to specify a title to be treated as HTML via title_mode="html".

12.1

  • NEW: SuperFences: Add optional reset function that can be specified for custom fences.
  • FIX: Tilde, Caret: Fix performance for long invalid delimiters.

12.0.1

  • FIX: BetterEm: fix a case with new logic.

12.0

  • BREAK: BetterEm: Complete rewrite. There may be some subtle differences between legacy behavior and new CommonMark behavior.

    • * and _ emphasis are handled at the same time to provide more natural nesting.
    • More performant.
    • CommonMark compliant.

  • BREAK: Tilde, Caret, Mark: Rewritten and now built upon the latest BetterEm logic.

    • When used with BetterEm, Tilde, Caret, and Mark will be added to the same delimiter processor under the hood and will be parsed at the same time as emphasis, allowing for better nesting logic.
    • More performant. Performance issues reported by (@​lexdotdev).
    • Tilde, Caret, Mark: Allow deletion, insertions, and marking mid-word by default. Set smart_delete, smart_insert, or smart_mark, respectively, to enable previous behavior, which prevented mid-word deletion.
    • Tilde, Caret: Add new option no_space to control whether the Pandoc style requirement of "no unescaped spaces" is enabled for subscript and superscript, respectively. no_space is enabled by default.

  • NEW: Details, Blocks.Details, Blocks.Admonitions: Allow and handle headers specially in titles.

  • NEW: Quotes: Allow and handle headers specially in callout titles.

  • NEW: BracketSpan: New extension that allows for the creation of spans using a Pandoc style bracket notation.

  • NEW: Arithmatex: Remove deprecated inline_mathjax_preview_format, inline_mathjax_format, and

... (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