Bump the python-dependencies group across 1 directory with 44 updates

[dependabot]

Updates the requirements on click, robotframework, flit-core, astroid, build, certifi, charset-normalizer, check-manifest, coverage, dill, docutils, exceptiongroup, idna, importlib-metadata, iniconfig, isort, jaraco-context, jaraco-functools, keyring, markdown-it-py, more-itertools, mypy, mypy-extensions, nh3, packaging, pkginfo, platformdirs, pluggy, pygments, pylint, pyproject-hooks, pytest, pytest-cov, pytest-spec, readme-renderer, requests, rich, ruff, tomli, tomlkit, twine, typing-extensions, urllib3 and zipp to permit the latest version.
Updates click from 8.1.8 to 8.5.0

Release notes

Sourced from click's releases.

8.5.0

This is the Click 8.5.0 feature release. A feature release may include new features, remove previously deprecated code, add new deprecation, or introduce potentially breaking changes.

We encourage everyone to upgrade. You can read more about our Version Support Policy on our website.

PyPI: https://pypi.org/project/click/8.5.0/ Changes: https://click.palletsprojects.com/page/changes/#version-8-5-0 Milestone https://github.com/pallets/click/milestone/33

• Add built-in shell completion support for PowerShell (Windows PowerShell 5.1+ and pwsh 7+) alongside the existing bash, zsh, and fish completers. Use _FOO_BAR_COMPLETE=powershell_source foo-bar to generate the completion script. #2672 #3637
• Supported versions of Windows enable ANSI terminal styles by default. Colorama is no longer a dependency and is not used. #2986 #3505
• {class}Argument accepts a help parameter, and help output includes a Positional arguments section when argument help is available. #2983 #3473
• confirm() and prompt() strip ANSI color and style codes from the prompt when the output stream does not support them, matching echo(). This stripping was lost in 8.4.0 when #2969 began writing the prompt with input() directly. #3572 #3653
• {class}Path with allow_dash=True no longer triggers a BytesWarning, an error under python -bb, when checking a value against the - convention. #2877 #3642
• Add {func}custom_version_option, a --version option whose output is produced by a callback, covering cases {func}version_option intentionally does not. The feature set of {func}version_option is now frozen; see [discussion #3527](`@version_option` future direction pallets/click#3527). #3581
• style() and secho() no longer silently drop the 256-color index 0 (black) passed as fg or bg, and now validate color arguments. Invalid colors raise a ValueError instead of a TypeError. #3677
• The automatic help option stores its value under the reserved name _click_default_help instead of help, so a parameter named help no longer breaks parsing. The new name is visible in {meth}Command.to_info_dict output. Parameters that overwrite each other's value trigger a warning: an argument sharing its name with another parameter, or any parameter claiming the reserved name. Options may still share a name to compete for the same value (feature switches). #2819 #3678
• unstyle and the ANSI handling behind help-text wrapping now strip the full CSI escape-sequence grammar. #3681
• Streamline Option flag handling: the flag-kind, type, lazy-default and validation steps in Option.__init__ move into focused helpers, and flag_value and default keep their unset sentinel at construction (resolved lazily on read) so is UNSET reliably tells a user-supplied value from an auto-derived one. Runtime behavior is unchanged, but {meth}Parameter.to_info_dict now resolves default=True on a feature switch to its flag_value, matching what the function receives at call

... (truncated)

Changelog

Sourced from click's changelog.

Version 8.5.0

Released 2026-08-24

• Add built-in shell completion support for PowerShell (Windows PowerShell 5.1+ and pwsh 7+) alongside the existing bash, zsh, and fish completers. Use _FOO_BAR_COMPLETE=powershell_source foo-bar to generate the completion script. {issue}2672 {pr}3637
• Supported versions of Windows enable ANSI terminal styles by default. Colorama is no longer a dependency and is not used. {issue}2986 {pr}3505
• {class}Argument accepts a help parameter, and help output includes a Positional arguments section when argument help is available. {issue}2983 {pr}3473
• confirm() and prompt() strip ANSI color and style codes from the prompt when the output stream does not support them, matching echo(). This stripping was lost in 8.4.0 when {pr}2969 began writing the prompt with input() directly. {issue}3572 {pr}3653
• Fix test failures when using pytest >= 9.1. {pr}3656
• {class}Path with allow_dash=True no longer triggers a BytesWarning, an error under python -bb, when checking a value against the - convention. {issue}2877 {pr}3642
• Add {func}custom_version_option, a --version option whose output is produced by a callback, covering cases {func}version_option intentionally does not. The feature set of {func}version_option is now frozen; see [discussion #3527](`@version_option` future direction pallets/click#3527). {pr}3581
• style() and secho() no longer silently drop the 256-color index 0 (black) passed as fg or bg, and now validate color arguments. Invalid colors raise a ValueError instead of a TypeError. {pr}3677
• The automatic help option stores its value under the reserved name _click_default_help instead of help, so a parameter named help no longer breaks parsing. The new name is visible in {meth}Command.to_info_dict output. Parameters that overwrite each other's value trigger a warning: an argument sharing its name with another parameter, or any parameter claiming the reserved name. Options may still share a name to compete for the same value (feature switches). {issue}2819 {pr}3678
• unstyle and the ANSI handling behind help-text wrapping now strip the full CSI escape-sequence grammar. {pr}3681
• Streamline Option flag handling: the flag-kind, type, lazy-default and validation steps in Option.__init__ move into focused helpers, and flag_value and default keep their unset sentinel at construction (resolved lazily on read) so is UNSET reliably tells a user-supplied value from an auto-derived one. Runtime behavior is unchanged, but {meth}Parameter.to_info_dict now resolves default=True on a feature switch to its flag_value, matching what the function receives at call time. {pr}3641
• {func}get_binary_stream and {func}get_text_stream are deprecated and will be removed in Click 9.0. {issue}3481 {pr}3695
• The following click.utils names were never intentionally public and are now private (_-prefixed). The old names remain available with a DeprecationWarning until Click 9.0: LazyFile, KeepOpenFile,

... (truncated)

Commits

• 8b19813 Release version 8.5.0
• 2c8cd3a Add FAQ entry about UnicodeEncodeError on Windows (#3778)
• 131c86a Add FAQ entry about UnicodeEncodeError on Windows
• e1fd594 Add support of pathlib.Path to edit (#3781)
• a1d8785 Add support of pathlib.Path to edit
• 2103e15 Forward all user's parameters set in PAGER and improve flag detection (#3777)
• a6256bf Forwards all user's parameters set in PAGER
• 61b69e9 Resolve the pager command once, in _pager_contextmanager (#3776)
• 9835b0f Resolve the pager command once, in _pager_contextmanager
• f36d58b Refactor pager stream handling (#3767)
• Additional commits viewable in compare view

Updates robotframework from 6.1 to 7.5

Release notes

Sourced from robotframework's releases.

Robot Framework 7.5 is a new feature release with major enhancements to the library documentation tool Libdoc, support for test/task metadata, enhanced console logging configuration and several other enhancements and bug fixes.

For more details, see the full release notes.

Robot Framework 7.5 release candidate 1

Robot Framework 7.5 is a new feature release with major enhancements to the library documentation tool Libdoc, support for test/task metadata, enhanced console logging configuration and several other enhancements and bug fixes. This release candidate contains all planned features and fixes.

For more details, see the full release notes.

Robot Framework 7.5 beta 1

Robot Framework 7.5 is a new feature release with major enhancements to the library documentation tool Libdoc, enhanced console logging configuration, several other enhancements and various bug fixes. This beta release contains most of the planned features, but some new functionality will still be added before the final release targeted for end of July, 2026.

For more details, see the full release notes.

Robot Framework 7.4.2

Robot Framework 7.4.2 is the last planned bug fix release in the Robot Framework 7.4.x series. It contains some bug fixes as well as documentation enhancements. The most important change is the deprecation of the built-in Testdoc tool in favor of the external Testdoc tool.

For more details, see the full release notes.

Robot Framework 7.4.1

Robot Framework 7.4.1 is the first bug fix release in the Robot Framework 7.4.x series. It fixes all reported regressions in Robot Framework 7.4.

For more details, see the full release notes.

Robot Framework 7.4

Robot Framework 7.4 is a feature release with support for secret variables, typed standard library keywords, enhancements to working with bytes and various other features and fixes.

Robot Framework 7.4 was released on Friday December 12, 2025. For more information, see the full release notes.

Robot Framework 7.4 release candidate 2

Robot Framework 7.4 is a feature release with support for secret variables, typed standard library keywords, enhancements to working with bytes and various other features and fixes.

Robot Framework 7.4 release candidate 2 was released on Tuesday December 9, 2025. For more information, see the full release notes.

Robot Framework 7.4 release candidate 1

Robot Framework 7.4 is a feature release with support for secret variables, typed standard library keywords, enhancements to working with bytes and various other features and fixes.

Robot Framework 7.4 release candidate 1 was released on Tuesday December 2, 2025. For more information, see the full release notes.

Robot Framework 7.4 beta 2

Robot Framework 7.4 is a feature release with support for secret variables and various other enhancements and bug fixes. This beta release contains the majority of the planned features and it is especially targeted for users interested to test the aforementioned secret variables.

Robot Framework 7.4 beta 2 was released on Saturday November 8, 2025. For more information, see the full release notes.

Robot Framework 7.4 beta 1

Robot Framework 7.4 is a feature release with support for secret variables and various other enhancements and bug fixes. This beta release contains the majority of the planned features and it is especially targeted for users interested to test the aforementioned secret variables.

Robot Framework 7.4 beta 1 was released on Tuesday October 7, 2025. For more information see the full release notes.

Robot Framework 7.3.2

... (truncated)

Commits

• bef418c Fix link target
• 1a747d8 Updated version to 7.5
• 364f9ff Release notes tuning
• c2ecb05 Release notes for 7.5
• 4e9544f Formatting
• 9134357 Fix test after update docs of library these tests use
• 0181dea Note that Telnet is deprecated.
• ad6a86f Bump browserslist (#5785)
• 59da4b2 Final updates to OperatingSystem docs.
• d294ba4 Enhance OperatingSystem docs (#5782)
• Additional commits viewable in compare view

Updates flit-core to 4.1.0

Changelog

Sourced from flit-core's changelog.

Release history

Version 4.1

• License expressions with named exceptions, the WITH syntax, are accepted (:ghpull:809).
• flit init allows dotted module names, for a component of a namespace package (:ghissue:822).
• Fix line endings in .cmd script wrappers on Windows (:ghpull:824).

Version 4.0.3

• Fix built wheels being created with overly restrictive 0600 permissions instead of the normal, world-readable 0644 (:ghpull:806).

Version 4.0.2

• Fix invalid metadata files with Import-Name (:ghissue:813).

Version 4.0.1

No changes, but a new tag to trigger an upload to PyPI now that twine will accept it.

Version 4.0

This version contains breaking changes, but most projects which are already using the [project] table for metadata shouldn't be affected, and can simply change the flit_core <4 constraint to <5.

• The [tool.flit.metadata] table is no longer used for project metadata (:ghpull:771). Use the newer :ref:[project] table <pyproject_toml_project> instead (or if that is not possible, build with flit_core <4).
• :ref:build_cmd and :ref:publish_cmd no longer include files in the sdist based on what is committed in git or Mercurial (:ghpull:772). These commands now build packages more like Flit does when called as a backend by e.g. python -m build. Specify :ref:sdist include & exclude patterns <pyproject_toml_sdist> instead (Flit can help to generate these), or pass the --use-vcs option to get the old behaviour back.
• flit_core now requires Python 3.8 or above (:ghpull:738)
• The --setup-py option to generate sdists containing a setup.py file is no longer available (:ghpull:776).
• Making typing stubs packages with a -stubs suffix will now work (:ghpull:742).

... (truncated)

Commits

• 75b1c90 Merge pull request #826 from pypa/prepare-4.1
• b5ad0d7 Add release note about PR #824
• 9fb48c1 Bump version: 4.0.2 → 4.1.0
• a4ea331 Prepare release notes for 4.1
• 337c499 Merge pull request #824 from r3wretrhy/fix-win-cmd-crlf
• 04cfa08 Merge pull request #825 from hxperl/docs-dynamic-fields
• 33be607 doc: list all four fields accepted in project.dynamic
• d538cb4 install: keep explicit CRLF in Windows .cmd wrappers
• 3c92604 Merge pull request #809 from yangfan-yf-yf/fix/spdx-with-exceptions
• 33a7a39 Clarify SPDX WITH version requirement and error message
• Additional commits viewable in compare view

Updates astroid from 3.3.7 to 4.3.1

Release notes

Sourced from astroid's releases.

4.3.1

What's New in astroid 4.3.1?

Release date: 2026-08-17

• Fix inference of the attributes of a namedtuple created with rename=True. The renamed fields were applied to _fields and to the class body, but the instance kept the field names as written, so an instance of namedtuple("Tuple", "abc def", rename=True) was inferred as having a def attribute instead of _1, and duplicate field names collapsed into a single attribute instead of being renamed.

  Closes #242

v4.3.0

What's New in astroid 4.3.0?

Release date: 2026-08-07

Version 4.2.0 was skipped: a v4.2.0 tag was created by mistake during an aborted release attempt, so the changes from the 4.2.0 betas are released as 4.3.0.

• Fix a crash on a functional namedtuple whose field name changes under NFKC normalization, such as namedtuple("mu", ["µ"]). Python normalizes identifiers, so the parsed class stores the field under "μ" while the brain looked it up as written, raising KeyError on a definition that namedtuple itself accepts.

  Closes pylint-dev/pylint#8746

• Fix inference of a method's first argument (self or cls) when the method's return value is stored on an unrelated object. This avoids inferring cls as the caller's class when indexing a tuple returned by a classmethod such as A.c()[0].

  Closes pylint-dev/pylint#11101

• super() with no argument now resolves against the class of the object the method was called on, instead of the class the method is written in. One consequence is that a typing.Self return value survives a chain of super() calls.

  Closes #2852 Closes pylint-dev/pylint#10807

• typing.overload stubs no longer shadow the implementation when a special method is looked up in the MRO.

  Closes #2448

... (truncated)

Changelog

Sourced from astroid's changelog.

What's New in astroid 4.3.1?

Release date: 2026-08-17

• Fix inference of the attributes of a namedtuple created with rename=True. The renamed fields were applied to _fields and to the class body, but the instance kept the field names as written, so an instance of namedtuple("Tuple", "abc def", rename=True) was inferred as having a def attribute instead of _1, and duplicate field names collapsed into a single attribute instead of being renamed.

  Closes #242

What's New in astroid 4.3.0?

Release date: 2026-08-07

Version 4.2.0 was skipped: a v4.2.0 tag was created by mistake during an aborted release attempt, so the changes from the 4.2.0 betas are released as 4.3.0.

• Fix a crash on a functional namedtuple whose field name changes under NFKC normalization, such as namedtuple("mu", ["µ"]). Python normalizes identifiers, so the parsed class stores the field under "μ" while the brain looked it up as written, raising KeyError on a definition that namedtuple itself accepts.

  Closes pylint-dev/pylint#8746

• Fix inference of a method's first argument (self or cls) when the method's return value is stored on an unrelated object. This avoids inferring cls as the caller's class when indexing a tuple returned by a classmethod such as A.c()[0].

  Closes pylint-dev/pylint#11101

• super() with no argument now resolves against the class of the object the method was called on, instead of the class the method is written in. One consequence is that a typing.Self return value survives a chain of super() calls.

  Closes #2852 Closes pylint-dev/pylint#10807

• typing.overload stubs no longer shadow the implementation when a special method is looked up in the MRO.

  Closes #2448

• Fix a crash when the field names of a functional Enum or namedtuple

... (truncated)

Commits

• 4ea15d4 Bump astroid to 4.3.1, update changelog (#3225)
• 38edf0e [Backport maintenance/4.3.x] Give a renamed namedtuple's instance the renamed...
• a52596a Bump astroid to 4.3.0, update changelog
• 3dfb6ca Rename the 4.2.0 changelog section to 4.3.0
• 941430e Ignore typing.overload stubs in dunder lookup (#3150)
• 1e71c7d Fix crash on a namedtuple field name that changes under NFKC normalization (#...
• 3316637 Fix crash on a dataclass base that annotates init (#3206)
• 8577346 Infer the value of a data descriptor as unknown
• 8666418 Fix crash in has_known_bases() for a non-class metaclass
• 5952c15 Fix crash on non-name assignment targets in typing.NamedTuple body
• Additional commits viewable in compare view

Updates build from 1.2.2.post1 to 1.6.1

Release notes

Sourced from build's releases.

1.6.1

What's Changed

• chore[v1]: prepare for v1.6.1 by @​henryiii in pypa/build#1181

Full Changelog: pypa/build@1.6.0...1.6.1

1.6.0

What's Changed

• Replace prettier with mdformat and yamlfmt by @​gaborbernat in pypa/build#1133
• Let yamlfmt format the workflows by @​gaborbernat in pypa/build#1134
• 🐛 fix(release): semver auto bump, changelog reflow, and roll back 1.5.1 by @​gaborbernat in pypa/build#1132
• fix: hash verification in --dependency-constraints-txt could be silently skipped by @​manfred-kaiser in pypa/build#1140
• 🐛 fix(ci): bump build-and-inspect-python-package to v3.0.1 by @​gaborbernat in pypa/build#1147
• 🐛 fix(ci): pin coverage core to ctrace so test contexts record by @​gaborbernat in pypa/build#1148
• chore: run mypy on more parts of the code by @​henryiii in pypa/build#1151
• chore: turn up strictness on mypy by @​henryiii in pypa/build#1153
• chore: faster mypy, fix merge error by @​henryiii in pypa/build#1156
• 🐛 fix(ci): rerun integration tests on transient network errors by @​gaborbernat in pypa/build#1150
• chore: clean up unused casts in tests by @​henryiii in pypa/build#1154
• refactor(typing): apply review feedback from #1093 by @​henryiii in pypa/build#1155
• chore: Generator is more accurate than Iterator by @​henryiii in pypa/build#1152
• tests: mark test_main_sdist_input_end_to_end with pytest.mark.network by @​frenzymadness in pypa/build#1144
• Revert "⚠️ feat(util): deprecate project_wheel_metadata" by @​henryiii in pypa/build#1158
• tests: download integration sources once per run by @​henryiii in pypa/build#1157
• Use stdlib importlib.metadata for typing by @​layday in pypa/build#1162
• Drop redundant exc_info parameter from backend exception wrapper by @​layday in pypa/build#1161
• Drop a few PyPy-specific test skips by @​layday in pypa/build#1164
• 🔧 chore: batch dependency updates weekly on Tuesday by @​gaborbernat in pypa/build#1165
• 👷 ci: use app token for releases by @​gaborbernat in pypa/build#1169

New Contributors

• @​manfred-kaiser made their first contribution in pypa/build#1140
• @​frenzymadness made their first contribution in pypa/build#1144

Full Changelog: pypa/build@1.5.1...1.6.0

1.5.1

What's Changed

• ✨ feat(cli): accept sdist tarball as srcdir argument by @​gaborbernat in pypa/build#1057
• chore: drop 3.9 branches for version_info checks by @​henryiii in pypa/build#1059
• tests: skip test_uv_install_strips_pythonpath with missing uv by @​mtelka in pypa/build#1063
• chore: remove myself from codeowners by @​FFY00 in pypa/build#1066
• refactor: safe_extractall to use pathlib.Path by @​henryiii in pypa/build#1060

... (truncated)

Changelog

Sourced from build's changelog.

#################### 1.6.1 (2026-09-10) ####################

---

Bugfixes

---

• Avoid trying to detect symlinks on Windows, regression in 1.6.0 - by :user:henryiii (:issue:1175) (:issue:1175)

---

Documentation

---

• Fix doubled backslashes in the Windows pip config path (%APPDATA%\pip\pip.ini) in the docs - by :user:aroh3006 (:issue:1149)

---

Miscellaneous

---

• :issue:1168, :issue:1170, :issue:1178

#################### 1.6.0 (2026-08-27) ####################

---

Features

---

• Add --report=PATH to write a machine-readable JSON report of built artifacts; --metadata now also accepts .whl files - by :user:gaborbernat (:issue:198)
• The srcdir argument now accepts .tar.gz source distributions, extracting and building from them - by :user:gaborbernat (:issue:311)
• The "Unmet dependencies" error from --no-isolation builds now shows the wanted version, found version, and interpreter - by :user:gaborbernat (:issue:504)
• Add --sdist-extract-dir to extract the intermediate sdist into a persistent directory, enabling compiler cache reuse across rebuilds - by :user:gaborbernat (:issue:614)
• Add --env-dir to place the isolated build environment at a fixed path, enabling compiler cache reuse across builds
  • by :user:gaborbernat (:issue:655)
• Print a summary of resolved dependency versions (name==version) after installing them in isolated builds - by :user:gaborbernat (:issue:959)
• On build failure, print a tip pointing to --env-dir and --sdist-extract-dir for debugging and link to the "Debug a failed build" how-to - reported by :user:dimpase, implemented by :user:gaborbernat (:issue:966)

---

Bugfixes

---

... (truncated)

Commits

• 89cccef chore: prepare for 1.6.1
• a6f707a ci: support releases from v* branches (#1178)
• 7785161 docs: fix doubled backslashes in Windows pip config path (#1149)
• 244b250 fix: always use copies for the isolated venv on Windows (#1176)
• c93ca6f build(deps): bump re-actors/alls-green from 1.2.2 to 1.3.0 in the github-acti...
• e02ffd3 pre-commit: bump repositories (#1173)
• aad39a8 docs: fix changelog page heading levels and sidebar (#1171)
• 5c3fd46 docs: use PyPI ref directly (#1172)
• 1c5bd6c 🐛 fix(release): format generated changelog (#1170)
• 7f0cc7e 🔧 build(type): replace mypy with pyrefly (#1168)
• Additional commits viewable in compare view

Updates certifi from 2024.12.14 to 2026.7.22

Commits

• f4bc676 2026.07.22 (#428)
• 4c91f9c Bump actions/setup-python from 6.3.0 to 7.0.0 (#427)
• 01a66c5 Bump actions/checkout from 7.0.0 to 7.0.1 (#426)
• eb355f4 Bump pypa/gh-action-pypi-publish from 1.14.0 to 1.14.1 (#425)
• 474e6fc Include tests in the source distribution (#424)
• a31ef39 Bump actions/setup-python from 6.2.0 to 6.3.0 (#420)
• 98eb2c7 Bump actions/checkout from 6.0.3 to 7.0.0 (#419)
• d0ac52f 2026.06.17 (#418)
• d46de62 Bump actions/checkout from 6.0.2 to 6.0.3 (#417)
• 6c183ec fix: update Requests docs link to canonical URL (#415)
• Additional commits viewable in compare view

Updates charset-normalizer from 3.4.0 to 3.5.1

Release notes

Sourced from charset-normalizer's releases.

Version 3.5.1

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

Version 3.5.0

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

Version 3.4.9

3.4.9 (2026-07-07)

Fixed

• Regression in our fallback path leading to a decode error. (#771) We've yanked 3.4.8 as a result of that bug.

Version 3.4.8

3.4.8 (2026-07-06)

Fixed

... (truncated)

Changelog

Sourced from charset-normalizer's changelog.

3.5.1 (2026-08-15)

Changed

• Raised upper bound of setuptools to v84 (#794)
• Cache performance access optimization for our CharInfo struct (prebuilt only).

Fixed

• No longer decoding large content when the noise detector output give a high entropy. Only impacted large content input >1M bytes.

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

3.4.9 (2026-07-07)

Fixed

• Regression in our fallback path leading to a decode error. (#771) We've yanked 3.4.8 as a result of that bug.

3.4.8 (2026-07-06)

Fixed

• Wall import time due to cascade codec imports for our multibyte first sort of iana supported codecs (#742)
• Unnecessary json import at runtime (#753)
• Inverse capitalization not seen by noise detector (#731)

... (truncated)

Commits

• e239bdc Merge pull request #795 from jawah/release-3.5.1
• 648ad77 docs: update faq
• fab2749 docs: write changelog for 3.5.1
• 7d32774 chore: bump version to 3.5.1
• 9a69f60 docs: update data/info
• 5dcc6dd perf: charinfo cache access optimization in cython
• ea3b447 fix: do not validate-decode large payload when md says it's noise
• a05917f chore: allow setuptools 84 builds (#794)
• 3325d87 Merge pull request #792 from jawah/update-cibuildwheel-action
• 77203b1 chore: reformat noxfile.py
• Additional commits viewable in compare view

Updates check-manifest from 0.50 to 0.51

Changelog

Sourced from check-manifest's changelog.

0.51 (2025-10-15)

• Add Python 3.14 support.
• Drop Python 3.7 support.

Commits

• 61edb75 Preparing release 0.51
• 396b822 Merge pull request #173 from mgedmin/py314
• 93159b9 Python script to update branch protection rules
• 6a97f2e Revert "Why not go for broke? Let's try breezy"
• 0ccbcda Why not go for broke? Let's try breezy
• 950a047 Giving up
• 3f69fa0 Let's also detect TTYs please
• a59a82d Print more debug info
• 4848c16 Move OS-level installs back to top
• 304f15e Sort VCSes alphabetically
• Additional commits viewable in compare view

Updates coverage from 7.6.9 to 7.16.1

Release notes

Sourced from coverage's releases.

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.

➡️  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

• When combining files, now path separator slashes will automatically be converted to the local file system style. This makes it less necessary to define [paths] configuration to combine data across operating systems. Fixes issue 2266.
• The Coverage.switch_context() method now returns the previous context.
• Fix: previously, a [paths] pattern would be replaced everywhere in a file path when it was only meant to be replaced once, in the leading portion of the path. This is now fixed, in pull 2268.
• Fixes to validation of options and configuration settings:
  • Negative precision settings now always cause useful error messages (pull 2261).
  • An invalid regex in the --contexts option (or the [report] contexts setting) reported a confusing “Couldn’t use data file …: user-defined function raised exception” error. Now it raises a proper configuration error naming the bad regex, like other regex settings do (pull 2262).
  • Non-string values in TOML configuration settings now produce a h...

    Description has been truncated