Skip to content

fix(deps): update all dependencies - #499

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all
Open

fix(deps): update all dependencies#499
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all

Conversation

@renovate

@renovate renovate Bot commented Sep 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
abravalheri/validate-pyproject repository minor 0.26 → v0.27 age confidence
allure-framework/allure-action action minor v0.9.0 → v0.12.0 age confidence
allure-pytest (source) project.dependencies patch ==2.16.0 → ==2.16.2 age confidence
astral-sh/ruff-pre-commit repository minor v0.16.4 → v0.17.3 age confidence
astral-sh/setup-uv action minor v10.0.1 → v10.3.2 age confidence
deprecated (changelog) project.dependencies major ==1.3.1 → ==3.0.0 age confidence
mysql-connector-python (changelog) project.dependencies minor ==26.7.0 → ==26.10.0 age confidence
pre-commit dependency-groups minor ==4.6.2 → ==4.7.0 age confidence
pytest (changelog) project.dependencies minor ==9.1.1 → ==9.2.0 age confidence
pytest-check project.dependencies major ==2.9.1 → ==3.0.3 age confidence
pytest-rerunfailures project.dependencies minor ==16.6 → ==16.7 age confidence
python uses-with minor 3.14 → 3.15 age confidence
python-dotenv project.dependencies patch ==1.2.3 → ==1.2.4 age confidence
python-jsonschema/check-jsonschema repository minor 0.38.0 → 0.39.0 age confidence
ruff (source, changelog) dependency-groups minor ==0.16.4 → ==0.17.3 age confidence
selenium project.dependencies minor ==4.47.0 → ==4.51.0 age confidence
tenacity (changelog) project.dependencies minor ==9.1.4 → ==9.2.1 age confidence

Note: The pre-commit manager in Renovate is not supported by the pre-commit maintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.

Release Notes

abravalheri/validate-pyproject

v0.27

Compare Source

What's Changed

New Contributors

Full Changelog: abravalheri/validate-pyproject@0.26...v0.26

allure-framework/allure-action

v0.12.0

Compare Source

What's Changed

⬆️ Dependency Updates

Full Changelog: allure-framework/allure-action@v0.11.3...v0.12.0

v0.11.3

Compare Source

What's Changed

👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.11.2...v0.11.3

v0.11.2

Compare Source

What's Changed

👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.11.1...v0.11.2

v0.11.1

Compare Source

What's Changed

⬆️ Dependency Updates
👻 Internal changes

New Contributors

Full Changelog: allure-framework/allure-action@v0.11.0...v0.11.1

v0.11.0

Compare Source

What's Changed

🔬 Improvements
⬆️ Dependency Updates
👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.10.3...v0.11.0

v0.10.3

Compare Source

What's Changed

👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.10.2...v0.10.3

v0.10.2

Compare Source

What's Changed

👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.10.1...v0.10.2

v0.10.1

Compare Source

What's Changed

🔬 Improvements
⬆️ Dependency Updates
👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.10.0...v0.10.1

v0.10.0

Compare Source

What's Changed

🔬 Improvements
⬆️ Dependency Updates
👻 Internal changes

Full Changelog: allure-framework/allure-action@v0.9.0...v0.10.0

allure-framework/allure-python (allure-pytest)

v2.16.2

Compare Source

🐞 Bug Fixes

👀 Links

Commits since 2.16.1

v2.16.1

Compare Source

👀 Links

Commits since 2.16.0

astral-sh/ruff-pre-commit

v0.17.3

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.17.3

v0.17.2

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.17.2

v0.17.1

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.17.1

v0.17.0

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.17.0

v0.16.10

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.10

v0.16.9

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.9

v0.16.8

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.8

v0.16.7

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.7

v0.16.6

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.6

v0.16.5

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.5

astral-sh/setup-uv

v10.3.2: 🌈 update known checksums for 0.13.5

Compare Source

Changes
🧰 Maintenance
📚 Documentation

v10.3.1: 🌈 preserve cache error class names in save-cache bundle

Compare Source

Changes

This release includes a fix so that multiple concurrent workflows trying to upload the same cache no longer warn

##[warning]Failed to save: Unable to reserve cache with key ..., another job may be creating this cache.

🐛 Bug fixes

🧰 Maintenance

📚 Documentation

⬆️ Dependency updates

v10.3.0: 🌈 Add Python architecture selection

Compare Source

Changes

This release adds the python-arch input to select a Python architecture independently of the Python version. With uv 0.13.0 or later, set python-arch: x86_64 to use x64 Python on Windows ARM64 runners.

It also includes embedded checksums for uv releases through 0.13.0.

🚀 Enhancements

🧰 Maintenance

⬆️ Dependency updates

v10.2.0: 🌈 Disable automatic cache saves for merge queues

Compare Source

Changes

This release contains the known-checksum of the most recent uv releases and also disabled the uploading(saving) of the cache when in a merge queue since theses caches would almost never be used.

🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates

v10.1.0: 🌈 New output python-runtime-idand respect NO_PROXY

Compare Source

Changes

This release adds more bheind the scene security improvements and also 2 small improvements.

NO_PROXY

This action now respects no_proxy/NO_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 (comment) for details on why this can be useful.

🐛 Bug fixes
🚀 Enhancements
🧰 Maintenance
📚 Documentation
⬆️ Dependency updates
laurent-laporte-pro/deprecated (deprecated)

v3.0.0

Compare Source

Major release: Python 3.12+ modernization

[!WARNING]
This release drops the support of Python 2.7 and of Python 3 versions older than 3.12.
Use Deprecated 1.3.x on these versions: pip keeps resolving to 1.3.x on Python < 3.12.

[!IMPORTANT]
Upgrading from 1.x — the public API (@deprecated, @deprecated_params,
deprecated.sphinx, ClassicAdapter) is unchanged, but check the following points:

  • wrapt >= 1.16 is required (was >= 1.10);
  • deprecated.__date__ and deprecated.classic.string_types are removed;
  • from deprecated import * only exports deprecated and deprecated_params;
  • stacked @deprecated_params decorators emit one warning per deprecated parameter;
  • the warnings of deprecated subclasses now refer to the user code: tests which assert
    the file name or the line number of a warning may need to be updated.

[!NOTE]
There is no 2.x release: the major version 3 was chosen to match Python 3.

Changed
  • Require Python >= 3.12 and wrapt >= 1.16 (first wrapt release supporting Python 3.12).
    See PR #​102.
  • Migrate the packaging from setuptools (setup.py/setup.cfg/MANIFEST.in) to
    pyproject.toml with the Hatchling build backend; the version is read from
    src/deprecated/__init__.py.
  • Adopt the src layout: the package moves to src/deprecated
    (the tests stay in tests and the documentation in docs).
  • Manage the project with uv (uv.lock) and Hatch: tox is dropped and replaced
    by the hatch test matrix.
  • Modernize the Makefile (uv/Hatch based targets, run make help).
  • Replace bump2version by hatch version <major|minor|patch>: the version is only defined
    in src/deprecated/__init__.py, and the git tag is created by GitHub when the release
    is published.
  • Update the Fedora RPM spec file to the %pyproject_* macros.
Removed
  • Remove the inspect2 dependency (it was only used on Python 2). See PR #​102.
  • Remove the Python 2 compatibility constructs (u"" literals, coding cookies,
    class Foo(object), super(Class, self), OrderedDict...). See PR #​102.
  • Remove the undocumented deprecated.classic.string_types compatibility tuple.
    A bytes positional reason is still accepted by @deprecated, as before. See PR #​102.
  • Remove the deprecated.__date__ attribute (the release dates are in the changelog).
    See PR #​102.
Added
  • Add the deprecated.google module: the @deprecated, @versionadded and @versionchanged
    decorators insert a Deprecated:, Version added: or Version changed: section
    in Google style
    docstrings (see the "Google" decorators
    page). See PR #​105.
  • Add the deprecated.numpy module: the @deprecated, @versionadded and @versionchanged
    decorators insert a Deprecated, Version added or Version changed section
    in NumPy style
    docstrings (see the "NumPy" decorators
    page). See PR #​106.
  • Add the ClassicAdapter.warn() method used to emit the deprecation warning
    (can be overridden by custom adapters). See PR #​102.
  • Add Python 3.12 type annotations to the public API and ship the py.typed marker (PEP 561):
    the decorators preserve the signature of the decorated functions and classes. See PR #​102.
  • Add __all__ to the deprecated package: from deprecated import * only exports
    deprecated and deprecated_params. See PR #​102.
Fixed
  • Deprecated functions and methods can now be pickled (by reference, like regular functions),
    so they can be used with multiprocessing and the spawn start method (the default one on
    Windows and macOS), for instance as a Process target or with Pool.map().
    Previously, pickling failed with NotImplementedError: object proxy must define __reduce_ex__()
    (#​16). See PR #​108 and PR #​111
    (a function decorated with @deprecated above @staticmethod could not be pickled).
  • When a deprecated class inherits from a deprecated class, all the deprecation warnings now refer
    to the user code (previously, the warning of the parent class referred to classic.py).
    The warnings are emitted with skip_file_prefixes (Python 3.12+): the frames of this library
    and of wrapt are skipped, whatever the wrapt implementation (C extension or pure Python).
    See PR #​102.
  • Stacked @deprecated_params decorators now emit only one warning for each deprecated
    parameter: the message (and category) of the outermost decorator wins, as documented
    in the tutorial. The warnings refer to the caller. See PR #​102.
Documentation
  • Convert the documentation from reStructuredText to Markdown (MyST), built with Sphinx 9.1
    and MyST-Parser 5.1. The API page remains in reStructuredText (autodoc), and the docstrings
    are still written in reStructuredText. See PR #​103.
  • Convert the root files to plain Markdown, readable on GitHub: CHANGELOG.md,
    CONTRIBUTING.md and LICENSE.md.
  • Declare the documentation dependencies in the docs dependency group of pyproject.toml
    (docs/requirements.txt is removed); ReadTheDocs installs them with uv.
  • Check the documentation build in the CI (make docs-check: warnings are errors).
  • Rewrite the white paper: state of the art of deprecation in Python (warning categories and
    stack level, PEP 702 and the type checkers, the CPython policy, practices of major Open Source
    projects, best practices), and how to combine warnings.deprecated with this library.
    See PR #​104.
  • Remove the ebook, LaTeX, manual page and Texinfo configuration of the documentation (HTML only),
    with the files used by the ebook (cover, title page and blurb).
  • Rework the README: a short presentation, the warning emitted, the options of @deprecated,
    @deprecated_params, and how the library complements warnings.deprecated (PEP 702).
    The "Authors" section now tells who started the library and who maintains it.
  • New logo (a "best before: next major" price tag), shown in the README and on the home page
    of the documentation; it replaces the rusty tools image. See PR #​109.
  • Switch the documentation to the Furo theme, with light, dark
    and automatic (system preference) modes, and the red of the logo as accent color.
    The code is highlighted with the Lovelace (light) and Gruvbox dark (dark) Pygments styles,
    tuned for contrast (WCAG AA). See PR #​110.
  • Add make docs-live to preview the documentation while editing it: the pages are rebuilt
    and the browser is reloaded on each change (sphinx-autobuild, docs-live dependency group).
    See PR #​110.
  • Present the Google and NumPy docstring decorators in the documentation. See PR #​107.
  • Document the release process (docs/source/release.md).
  • Fix the outputs quoted in the tutorial and in the Sphinx page, stale references and typos
    of the documentation and of the docstrings. See PR #​111.
Other
  • Run the CI with uv and Hatch on Python 3.12, 3.13 and 3.14 (Linux, macOS and Windows),
    plus the wrapt compatibility matrix (wrapt 1.16, 1.17 and 2.x on every supported Python)
    and the pure Python implementation of wrapt. See PR #​102 and PR #​111.
  • Add the hatch check code (Ruff lint), hatch check fmt (Ruff format)
    and hatch check types (mypy, strict mode) quality checks. See PR #​102.
  • Add non-regression tests for the behaviours which differ between Python 2 and Python 3,
    and make the test_sphinx_metaclass tests test the Sphinx decorator. See PR #​102.
  • Bump the GitHub Actions versions. See PR #​99.
  • Run CodeQL on the develop and master branches, and add Dependabot version updates
    (GitHub Actions and uv.lock). See PR #​111.
  • Publish the coverage to Coveralls (README badge), and fail the tests below 95% of coverage.
    See PR #​111.
  • Add AGENTS.md and CLAUDE.md: guidance for AI coding agents.
mysql/mysql-connector-python (mysql-connector-python)

v26.10.0

Compare Source

=======

  • WL#17362: Upgrade third-party dependencies
  • BUG#40010859: Correct parameter serialization for selected character sets
  • BUG#39923843: Test certificates have expired
  • BUG#39912002: Upgrade zstandard to latest version (0.25.0)
pre-commit/pre-commit (pre-commit)

v4.7.0

Compare Source

==================

Fixes
pytest-dev/pytest (pytest)

v9.2.0

Compare Source

pytest 9.2.0 (2026-10-27)

Removals and backward incompatible breaking changes

  • #​14716: -c now raises a usage error for a path that does not exist, is a directory, or is in a format pytest has no loader for. Such paths were previously either ignored or reported as an unhandled FileNotFoundError.

  • #​8593: The indirect, ids and scope arguments of Metafunc.parametrize() <pytest.Metafunc.parametrize> -- and therefore of @pytest.mark.parametrize <pytest.mark.parametrize ref> -- are now keyword-only.

    Passing them positionally was a common source of confusing errors, e.g. parametrize("arg1", "arg2", [(1, 2)]) made the argvalues land in indirect and failed with indirect fixture '(1, 2)' doesn't exist; such mistakes now fail with an understandable TypeError. The type annotations have always declared these arguments as keyword-only.

  • #​993: Plugin import failures at startup are now reported and classified instead of escaping as a raw traceback with the accidental exit code 1:

    • a plugin that cannot be found -- via -p, pytest_plugins or PYTEST_PLUGINS -- exits with pytest.ExitCode USAGE_ERROR (4), like a conftest.py that fails to import;
    • a plugin that is found but raises while importing -- including a broken pytest11 entry point or a missing plugin dependency -- exits with pytest.ExitCode INTERNAL_ERROR (3), with the traceback preserved.

    pytest.main now returns these codes instead of raising ImportError. Also fixed an IndexError from pytest's own internals when the plugin raised an exception with no arguments.

Deprecations (removal in next major release)

  • #​14742: The private _pytest.python.CallSpec2 name has been renamed to CallSpec.
    The old CallSpec2 alias remains available for now and will be removed in pytest 10 or 11.

  • #​14755: Schedule yield_fixture decorator for removal in pytest 10 or 11.

  • #​14774: Similarly to the deprecation of class-scoped fixtures defined as instance methods in pytest 9.1,
    all higher-scoped fixtures (module, package, and session) defined
    as instance methods are now deprecated.

    They suffer from the same issue the original deprecation only fixed for
    class-scoped fixtures, see 10819 and 14011.

  • #​14808: Passing a non-string value to a string-typed ini option now emits a pytest.PytestRemovedIn10Warning. This affects [tool.pytest.ini_options] in pyproject.toml. In pytest 10 this will raise a TypeError, matching the behavior of the corresponding TOML config path.

  • #​7323: Passing bytes to TerminalReporter.write_line() is now deprecated, pass a str instead.

New features

  • #​14743: Full diff: now contains a legend explaining the + & - symbols in diff output.
  • #​2781: When strict_markers is enabled, marker names used in -m expressions are now validated against registered markers.
  • #​6881: Added the parametrize_long_str_id_strategy configuration option to control how long str/bytes parameter values are handled in auto-generated test IDs. Explicit IDs set via ids=[...] or pytest.param(..., id=...) are not affected. Available strategies: short (default, values over 100 chars fall back to argname+index), sha256 (SHA-256 hex digest), legacy (keep full value), and disallow (error requesting explicit IDs).

Improvements in existing functionality

  • #​10745: A RecursionError whose recursion origin cannot be located now shows only the
    first and last 10 stack frames, matching what pytest already did when locating
    the origin failed outright. Previously the full traceback -- often around a
    thousand near-identical frames -- was rendered, which was both slow and
    unreadable. Pass --full-trace to see every frame.

  • #​10745: The line numbers of a module's statements are now computed once per traceback
    instead of once per traceback entry, which noticeably speeds up rendering
    failures raised from large test modules.

  • #​11418: The cached rewritten modules in __pycache__ are now invalidated by a hash of
    the source instead of its modification time, using the checked-hash pyc format
    from 552.

    Timestamps make the cache useless wherever source files get fresh modification
    times, most notably in CI: a checkout gives every file a new mtime, so a
    restored cache is discarded in full and every test module is rewritten again.
    Hashing the source costs roughly 15 microseconds per file and makes the cache
    survive that.

    Existing timestamp based caches are ignored and rewritten once.

  • #​12624: The pytest_plugins variable and the PYTEST_PLUGINS environment variable now also accept entry point names of installed plugins (e.g. xdist), in addition to importable module names, matching the behavior of the -p command-line option.

    As part of this change, plugins specified by entry point name through these mechanisms are now also listed in the plugins: line of the terminal header (12615).

    Based on the original implementation by Marcel Telka in 12616.

  • #​12697: Warnings emitted while importing plugins through -p, PYTEST_PLUGINS, or entry point autoloading are now captured, filtered, and reported like other warnings.

  • #​12860: Assertion diffs for dict.items() and dict.keys() comparisons (>=, <=, >, <, ==) now show which items are missing, the same way set comparisons do.

  • #​13354: Node.get_closest_marker <_pytest.nodes.Node.get_closest_marker> now also accepts a ~pytest.MarkDecorator as its default, for example item.get_closest_marker("foo", pytest.mark.foo(1)), and returns the wrapped ~pytest.Mark.

    Previously the only way to build a default was to instantiate ~pytest.Mark directly, which is private and warns.

  • #​13369: Improved the error from pytest.RunResult.assert_outcomes when a plugin changes or removes pytest's standard terminal summary, and documented how to isolate output-changing plugins.

  • #​13431: Exposed pytest.ParameterSet as the type of the return value of pytest.param().
    This can be used in type annotations and isinstance checks.

  • #​13564: Issue a warning when fixtures are wrapped with a decorator that prevents
    correct discovery, including @classmethod above @pytest.fixture and
    @staticmethod above @pytest.fixture. Put @pytest.fixture above
    those decorators on test classes.

  • #​14164: Exposed pytest.Approx as the type of the return value of pytest.approx().
    This can be used in type annotations and isinstance checks.

  • #​14463: Assertion diffs for mappings now match up keys the way the compared mappings match them themselves.

    Key comparison goes through the mappings' key views instead of plain sets of their keys, so a mapping
    with its own notion of key equivalence, such as case-insensitive header mappings, no longer
    reports its common keys as missing on either side.

  • #​14523: Large assertion comparison diffs are now built lazily and capped to the
    truncation budget, so a huge diff is no longer formatted in full just to
    be truncated. As a consequence, the truncation footer no longer
    reports the exact number of hidden lines.

  • #​14687: The default fd-level output capturing (--capture=fd) now skips reading the capture buffer for tests which produce no output, reducing per-test overhead in large test suites.

  • #​14724: --no-summary now only applies directly to pytest's own summary.

    The flag no longer skips the pytest_terminal_summary hook, so third-party
    plugins (for example coverage) can still write their terminal summaries.

  • #​14751: parser.addini <pytest.Parser.addini> now also accepts type expressions for its type argument, in addition to the existing string tags: the plain Python types str, bool, int, float, a Literal of strings, and unions of these (for example int | str or int | Literal["auto"]).

  • #​14754: pytest.approx() now rejects infinite relative tolerances for datetime.timedelta values with a clear ValueError instead of raising OverflowError.

  • #​14791: The junit_family, junit_logging, junit_duration_report, console_output_style, empty_parameter_set_mark, assertion_text_diff_style and tmp_path_retention_policy configuration options are now registered with the set of values they accept: an invalid value now fails with a clean usage error instead of being silently ignored or crashing later, and pytest --help lists the accepted values.

    config.getini <pytest.Config.getini> now raises pytest.UsageError instead of TypeError or ValueError when the value read from the configuration file does not match the registered type, so a bad value is always reported as a short usage error message instead of an internal error traceback. Asking for an option name that was never registered still raises ValueError.

  • #​15006: pytest.approx now emits pytest.PytestApproxDecimalToleranceWarning when a rel or abs tolerance is given as a float that cannot be represented exactly for a ~decimal.Decimal comparison, since such a tolerance is widened to the float's exact binary value.

  • #​14675, #​14953, #​15153, #​15132: The truncation_limit_lines, truncation_limit_chars, max_warnings, verbosity_assertions, verbosity_test_cases, verbosity_subtests, `tmp_path_retention_co

[!IMPORTANT]
✂ PR body was truncated to here.

@github-actions

github-actions Bot commented Sep 1, 2026 •
edited
Loading

Copy link
Copy Markdown

Allure Report Summary

     Scope Duration Stats New Flaky Retry
     All tests 7ms Passed tests⁠ 1 1 0 0

Reports: Awesome

@coderabbitai

coderabbitai Bot commented Sep 10, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 52da4266-54aa-4d32-a8f0-aea82fce8518

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch had an error being deployed

1 failed deployment
github-pages — 1bcc0199 Deployed Oct 27, 2026 by renovate[bot] via deploy_pages #68
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@elias-shoursoh elias-shoursoh Awaiting requested review from elias-shoursoh
@nirtal85 nirtal85 Awaiting requested review from nirtal85

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants