Skip to content

fix(deps): update all dependencies - #499

Merged
nirtal85 merged 5 commits into
mainfrom
renovate/all
Nov 4, 2026
Merged

fix(deps): update all dependencies#499
nirtal85 merged 5 commits into
mainfrom
renovate/all

Conversation

@renovate

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

Copy link
Copy Markdown
Contributor

Compatibility fix and validation

Fixed the dependency resolver failure without dropping Python 3.11 support: Deprecated 1.3.1 is selected on Python 3.11 and Deprecated 3.0.1 on Python 3.12+. Regenerated uv.lock and integrated the independently verified virtualenv, urllib3, and setuptools updates from main.

Validated locked installation on Python 3.11 and 3.12, Ruff lint/format, 30-test collection, and the existing Selenium sanity test against a local data URL. The same sanity test passed on both Python versions. Application CI is being checked on the final head before merging.

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
assertpy project.dependencies major ==1.1 → ==2.35.0 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.3 age confidence
compilerla/conventional-pre-commit repository minor v4.4.0 → v4.5.0 age confidence
deprecated (changelog) project.dependencies major ==1.3.1 → ==3.0.1 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.52.0 age confidence
tenacity (changelog) project.dependencies minor ==9.1.4 → ==9.2.1 age confidence
visual-regression-tracker project.dependencies major ==4.9.0 → ==5.1.0 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

assertpy/assertpy (assertpy)

v2.35.0: 2.35.0

Compare Source

assertpy 2.35.0 is the typed rewrite published until now as assertpy2, released under the original name: the first assertpy release since 1.1 in 2020
A major release. On 1.1 your imports stay the same, but some results, extensions and messages change

Thanks to Justin Shacklette for handing over the name, and to everyone who contributed to 1.x

TL;DR

You use What to do
assertpy 1.1, upgrading Read Upgrading from assertpy 1.x, remove types-assertpy, run your tests
assertpy 1.1, staying Pin assertpy<2. The 1.x source is on the v1.x branch
assertpy2 Switch the dependency and imports to assertpy. assertpy2 2.35.0 keeps old imports working meanwhile

Coming from assertpy 1.1

The same assert_that(...) chain, plus:

A major release, so some things change:

assert_that(float("nan")).is_greater_than(1)

Before (1.1)

passed

Now

AssertionFailure: Expected <nan> to be greater than <1>, but was not.
  • Some results change, in either direction: NaN in comparisons, bool in is_close_to(), and more
  • add_extension() refuses a taken name without override=True
  • Failures raise AssertionFailure, a subclass of AssertionError
  • Many messages are reworded: tests matching message text may need updating
  • Python 3.10+. Older interpreters keep getting 1.1
  • When upgrading, remove types-assertpy: it describes 1.1 and hides the 2.x types

Guide: Upgrading from assertpy 1.x

Coming from assertpy2

- assertpy2[json]
+ assertpy[json]
- from assertpy2 import assert_that
+ from assertpy import assert_that

Old flags, settings and environment variables still work, with a warning:

$ pytest --assertpy2-snapshot-update
FutureWarning: --assertpy2-snapshot-update is the assertpy2 name of --assertpy-snapshot-update. It keeps working until assertpy 3.0, use --assertpy-snapshot-update instead.
  • New names drop the 2: --assertpy-snapshot-update, assertpy_diff, ASSERTPY_SNAPSHOT_CI. Old ones go in 3.0
  • Under warnings-as-errors the warning stops the run: rename, or filter ignore:.*is the assertpy2 name of:FutureWarning
  • # assertpy2: allow-dangling is still read
  • No synonym for the loggers and the plugin name: update them by the table below

Guide: Coming from assertpy2

Behaviour changes

assertpy2 assertpy
assert_warn() default logger assertpy2 assertpy
log_passes() logger assertpy2.passes assertpy.passes
pytest plugin name -p no:assertpy2 -p no:assertpy
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.3: 🌈 Use Astral mirror for version manifests with GitHub fallback

Compare Source

Changes

This release contains something that should have been included a very long time ago. Sorry for sleeping on that.

This action now retrieves the release manifest that contains the available versions, their download links and checksums from the Astral mirror, rather than trying GitHub first. This should present much more stable.
(Known checksums are still checked, so the security impact does not change)

Also a big thank you to @​soujasK for a set of bugfixes 👏

🐛 Bug fixes
🧰 Maintenance
📚 Documentation

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
compilerla/conventional-pre-commit

v4.5.0

Compare Source

What's Changed

New Contributors

Full Changelog: compilerla/conventional-pre-commit@v4.4.0...v4.5.0

laurent-laporte-pro/deprecated (deprecated)

v3.0.1

Compare Source

Patch release: preserve the constructor signatures of deprecated classes

Fixed
  • Preserve constructor signatures on deprecated classes, including in Sphinx autodoc,
    instead of displaying the warning wrapper's generic arguments (#​86).
    See PR #​115 (Mirochill).
Other
  • Bump the dev-dependencies group (Dependabot). See PR #​114.
  • Add the social preview image of the repository and document its release steps. See PR #​113.

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 acc

[!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

     Environment Duration Stats New Flaky Retry
     All tests 5ms Passed tests⁠ 1 1 0 0

@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: dd45e6c4-4809-4669-ba8b-c766ccc72307

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

@renovate

renovate Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

This branch was successfully deployed

1 active deployment
github-pages — ccc0e58b Deployed Nov 4, 2026 by nirtal85 via deploy_pages #79
View deployment
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

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@nirtal85