Skip to content

fix(deps): update all dependencies #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update all dependencies #211

renovate wants to merge 1 commit into from
+84 −84

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2025 •
edited
Loading

ℹ️ 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 v0.24.1 → v0.25 age confidence
actions/checkout action major v5 → v6 age confidence
actions/download-artifact action major v5 → v7 age confidence
actions/upload-artifact action major v5 → v6 age confidence
allure-framework/allure-action action patch v0.6.2 → v0.6.4 age confidence
allure-pytest (source) project.dependencies patch ==2.15.0 → ==2.15.3 age confidence
astral-sh/ruff-pre-commit repository patch v0.14.1 → v0.14.14 age confidence
axe-playwright-python project.dependencies patch ==0.1.5 → ==0.1.7 age confidence
kentaro-m/auto-assign-action action patch v2.0.0 → v2.0.1 age confidence
macisamuele/language-formatters-pre-commit-hooks repository minor v2.15.0 → v2.16.0 age confidence
mcr.microsoft.com/playwright container minor v1.55.0 → v1.58.1 age confidence
playwright (changelog) project.dependencies minor ==1.55.0 → ==1.58.0 age confidence
pre-commit dependency-groups minor ==4.3.0 → ==4.5.1 age confidence
pytest (changelog) project.dependencies major ==8.4.2 → ==9.0.2 age confidence
pytest-playwright project.dependencies patch ==0.7.1 → ==0.7.2 age confidence
pytest-split (source) project.dependencies minor ==0.10.0 → ==0.11.0 age confidence
python uses-with minor 3.13 → 3.14 age confidence
python-jsonschema/check-jsonschema repository minor 0.34.1 → 0.36.1 age confidence
ruff (source, changelog) dependency-groups patch ==0.14.1 → ==0.14.14 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 (abravalheri/validate-pyproject)

v0.25

Compare Source

What's Changed

Other Changes

New Contributors

Full Changelog: abravalheri/validate-pyproject@v0.24.1...v0.25

actions/checkout (actions/checkout)

v6

Compare Source

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

v7

Compare Source

v6

Compare Source

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

v6

Compare Source

allure-framework/allure-action (allure-framework/allure-action)

v0.6.4

Compare Source

What's Changed

Full Changelog: allure-framework/allure-action@v0...v0.6.4

v0.6.3

Compare Source

What's Changed

Full Changelog: allure-framework/allure-action@v0...v0.6.3

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

v2.15.3

Compare Source

👀 Links

Commits since 2.15.2

v2.15.2

Compare Source

  • Set testCaseId for all test results produced by allure_robotframework (via #​884) - @​delatrie

👀 Links

Commits since 2.15.1

v2.15.1

Compare Source

👀 Links

Commits since 2.15.0

astral-sh/ruff-pre-commit (astral-sh/ruff-pre-commit)

v0.14.14

Compare Source

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

v0.14.13

Compare Source

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

v0.14.12

Compare Source

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

v0.14.11

Compare Source

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

v0.14.10

Compare Source

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

v0.14.9

Compare Source

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

v0.14.8

Compare Source

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

v0.14.7

Compare Source

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

v0.14.6

Compare Source

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

v0.14.5

Compare Source

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

v0.14.4

Compare Source

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

v0.14.3

Compare Source

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

v0.14.2

Compare Source

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

pamelafox/axe-playwright-python (axe-playwright-python)

v0.1.7

  • Fixed issue with passing custom options to Axe.run() method, which caused options to be ignored.
  • Added support for Python 3.14.

v0.1.6

  • Upgraded axe-core JS version to v4.11.0. You may see the number of violations change as a result, as new axe-core versions sometimes add new rules and update existing ones.
kentaro-m/auto-assign-action (kentaro-m/auto-assign-action)

v2.0.1

Compare Source

What's Changed

Full Changelog: kentaro-m/auto-assign-action@v2.0.0...v2.0.1

macisamuele/language-formatters-pre-commit-hooks (macisamuele/language-formatters-pre-commit-hooks)

v2.16.0

Compare Source

Microsoft/playwright-python (playwright)

v1.58.0

Compare Source

Trace Viewer Improvements

  • New 'system' theme option follows your OS dark/light mode preference
  • Search functionality (Cmd/Ctrl+F) is now available in code editors
  • Network details panel has been reorganized for better usability
  • JSON responses are now automatically formatted for readability

Thanks to @​cpAdm for contributing these improvements!

Miscellaneous

browser_type.connect_over_cdp() now accepts an is_local option. When set to True, it tells Playwright that it runs on the same host as the CDP server, enabling file system optimizations.

Breaking Changes ⚠️

  • Removed _react and _vue selectors. See locators guide for alternatives.
  • Removed :light selector engine suffix. Use standard CSS selectors instead.
  • Option devtools from browser_type.launch() has been removed. Use args=['--auto-open-devtools-for-tabs'] instead.
  • Removed macOS 13 support for WebKit. We recommend to upgrade your macOS version, or keep using an older Playwright version.

Browser Versions

  • Chromium 145.0.7632.6
  • Mozilla Firefox 146.0.1
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 144
  • Microsoft Edge 144

v1.57.0

Compare Source

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

new and old logo

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Breaking Change

After 3 years of being deprecated, we removed page.accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

  • worker.on("console") event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. worker.expect_event() can be used to wait for it.
  • locator.description() returns locator description previously set with locator.describe().
  • New option steps in locator.click() and locator.drag_to() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.
  • Network requests issued by Service Workers are now reported and can be routed through the BrowserContext, only in Chromium. You can opt out using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK environment variable.
  • Console messages from Service Workers are dispatched through worker.on("console"). You can opt out of this using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE environment variable.

Browser Versions

  • Chromium 143.0.7499.4
  • Mozilla Firefox 144.0.2
  • WebKit 26.0

v1.56.0

Compare Source

New APIs

Breaking Changes

Miscellaneous

  • Aria snapshots render and compare input placeholder

Browser Versions

  • Chromium 141.0.7390.37
  • Mozilla Firefox 142.0.1
  • WebKit 26.0
pre-commit/pre-commit (pre-commit)

v4.5.1

Compare Source

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

Fixes
  • Fix language: python with repo: local without additional_dependencies.

v4.5.0

Compare Source

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

Features

v4.4.0

Compare Source

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

Features
Fixes
pytest-dev/pytest (pytest)

v9.0.2

Compare Source

pytest 9.0.2 (2025-12-06)

Bug fixes

  • #​13896: The terminal progress feature added in pytest 9.0.0 has been disabled by default, except on Windows, due to compatibility issues with some terminal emulators.

    You may enable it again by passing -p terminalprogress. We may enable it by default again once compatibility improves in the future.

    Additionally, when the environment variable TERM is dumb, the escape codes are no longer emitted, even if the plugin is enabled.

  • #​13904: Fixed the TOML type of the tmp_path_retention_count settings in the API reference from number to string.

  • #​13946: The private config.inicfg attribute was changed in a breaking manner in pytest 9.0.0.
    Due to its usage in the ecosystem, it is now restored to working order using a compatibility shim.
    It will be deprecated in pytest 9.1 and removed in pytest 10.

  • #​13965: Fixed quadratic-time behavior when handling unittest subtests in Python 3.10.

Improved documentation

  • #​4492: The API Reference now contains cross-reference-able documentation of pytest's command-line flags <command-line-flags>.

v9.0.1

Compare Source

pytest 9.0.1 (2025-11-12)

Bug fixes

  • #​13895: Restore support for skipping tests via raise unittest.SkipTest.
  • #​13896: The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality.
  • #​13904: Fixed the TOML type of the verbosity settings in the API reference from number to string.
  • #​13910: Fixed UserWarning: Do not expect file_or_dir on some earlier Python 3.12 and 3.13 point versions.

Packaging updates and notes for downstreams

  • #​13933: The tox configuration has been adjusted to make sure the desired
    version string can be passed into its package_env through
    the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
    variable as a part of the release process -- by webknjaz.

Contributor-facing changes

  • #​13891, #​13942: The CI/CD part of the release automation is now capable of
    creating GitHub Releases without having a Git checkout on
    disk -- by bluetech and webknjaz.
  • #​13933: The tox configuration has been adjusted to make sure the desired
    version string can be passed into its package_env through
    the SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST environment
    variable as a part of the release process -- by webknjaz.

v9.0.0

Compare Source

pytest 9.0.0 (2025-11-05)

New features

  • #​1367: Support for subtests has been added.

    subtests <subtests> are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.

    Example:

    def contains_docstring(p: Path) -> bool:
    """Return True if the given Python file contains a top-level docstring."""
    ...

def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
    for path in Path.cwd().glob("*.py"):
        with subtests.test(path=str(path)):
            assert contains_docstring(path)

    Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.

    In addition, unittest.TestCase.subTest is now also supported.

    This feature was originally implemented as a separate plugin in pytest-subtests, but since then has been merged into the core.

    [!NOTE]
    This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

  • #​13743: Added support for native TOML configuration files.

    While pytest, since version 6, supports configuration in pyproject.toml files under [tool.pytest.ini_options],
    it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
    Now, pytest supports the native TOML data model.

    In pyproject.toml, the native TOML configuration is under the [tool.pytest] table.

    # pyproject.toml
[tool.pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The [tool.pytest.ini_options] table remains supported, but both tables cannot be used at the same time.

    If you prefer to use a separate configuration file, or don't use pyproject.toml, you can use pytest.toml or .pytest.toml:

    # pytest.toml or .pytest.toml
[pytest]
minversion = "9.0"
addopts = ["-ra", "-q"]
testpaths = [
    "tests",
    "integration",
]

    The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface.

    See config file formats for full details.

  • #​13823: Added a "strict mode" enabled by the strict configuration option.

    When set to true, the strict option currently enables

    • strict_config
    • strict_markers
    • strict_parametrization_ids
    • strict_xfail

    The individual strictness options can be explicitly set to override the global strict setting.

    The previously-deprecated --strict command-line flag now enables strict mode.

    If pytest adds new strictness options in the future, they will also be enabled in strict mode.
    Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
    or if you want to proactively adopt new strictness options as they are added.

    See strict mode for more details.

  • #​13737: Added the strict_parametrization_ids configuration option.

    When set, pytest emits an error if it detects non-unique parameter set IDs,
    rather than automatically making the IDs unique by adding 0, 1, ... to them.
    This can be particularly useful for catching unintended duplicates.

  • #​13072: Added support for displaying test session progress in the terminal tab using the OSC 9;4; ANSI sequence.
    When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty,
    you'll see the progress in the terminal tab or window,
    allowing you to monitor pytest's progress at a glance.

    This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows:

    • On a user level, using -p no:terminalprogress on the command line or via an environment variable PYTEST_ADDOPTS='-p no:terminalprogress'.
    • On a project configuration level, using addopts = "-p no:terminalprogress".

  • #​478: Support PEP420 (implicit namespace packages) as --pyargs target when consider_namespace_packages is true in the config.

    Previously, this option only impacted package imports, now it also impacts tests discovery.

  • #​13678: Added a new faulthandler_exit_on_timeout configuration option set to "false" by default to let faulthandler interrupt the pytest process after a timeout in case of deadlock.

    Previously, a faulthandler timeout would only dump the traceback of all threads to stderr, but would not interrupt the pytest process.

    -- by ogrisel.

  • #​13829: Added support for configuration option aliases via the aliases parameter in Parser.addini() <pytest.Parser.addini>.

    Plugins can now register alternative names for configuration options,
    allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options.
    The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file.

Improvements in existing functionality

  • #​13330: Having pytest configuration spread over more than one file (for example having both a pytest.ini file and pyproject.toml with a [tool.pytest.ini_options] table) will now print a warning to make it clearer to the user that only one of them is actually used.

    -- by sgaist

  • #​13574: The single argument --version no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version.

    Passing --version twice (e.g., pytest --version --version) retains the original behavior, showing both the pytest version and plugin information.

    [!NOTE]
    Since --version is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as PYTEST_ADDOPTS or addopts.

  • #​13823: Added strict_xfail as an alias to the xfail_strict option,
    strict_config as an alias to the --strict-config flag,
    and strict_markers as an alias to the --strict-markers flag.
    This makes all strictness options consistently have configuration options with the prefix strict_.

  • #​13700: --junitxml no longer prints the generated xml file summary at the end of the pytest session when --quiet is given.

  • #​13732: Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem.

  • #​13859: Clarify the error message for pytest.raises() when a regex match fails.

  • #​13861: Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be <expected>, but got <actual>". Now, it is "Expected <expected>, but got <actual>".

Removals and backward incompatible breaking changes

  • #​12083: Fixed a bug where an invocation such as pytest a/ a/b would cause only tests from a/b to run, and not other tests under a/.

    The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled:

    1. pytest a/b a/ or pytest a/ a/b are equivalent to pytest a; if an argument overlaps another arguments, only the prefix remains.
    2. pytest x.py x.py is equivalent to pytest x.py; previously such an invocation was taken as an explicit request to run the tests from the file twice.

    If you rely on these behaviors, consider using --keep-duplicates <duplicate-paths>, which retains its existing behavior (including the bug).

  • #​13719: Support for Python 3.9 is dropped following its end of life.

  • #​13766: Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables $CI or $BUILD_NUMBER was defined;
    now, CI mode is only activated if at least one of those variables is defined and set to a non-empty value.

  • #​13779: PytestRemovedIn9Warning deprecation warnings are now errors by default.

    Following our plan to remove deprecated features with as little disruption as
    possible, all warnings of type PytestRemovedIn9Warning now generate errors
    instead of warning messages by default.

    The affected features will be effectively removed in pytest 9.1, so please consult the
    deprecations section in the docs for directions on how to update existing code.

    In the pytest 9.0.X series, it is possible to change the errors back into warnings as a
    stopgap measure by adding this to your pytest.ini file:

    [pytest]
filterwarnings =
    ignore::pytest.PytestRemovedIn9Warning

    But this will stop working when pytest 9.1 is released.

    If you have concerns about the removal of a specific feature, please add a
    comment to 13779.

Deprecations (removal in next major release)

  • #​13807: monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend> now issues a deprecation warning when the prepended path contains legacy namespace packages (those using pkg_resources.declare_namespace()).
    Users should migrate to native namespace packages (420).
    See monkeypatch-fixup-namespace-packages for details.

Bug fixes

  • #​13445: Made the type annotations of pytest.skip and friends more spec-complaint to have them work across more type checkers.

  • #​13537: Fixed a bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.

  • #​13598: Fixed possible collection confusion on Windows when short paths and symlinks are involved.

  • [#​13716]

Configuration

📅 Schedule: Branch creation - "monthly" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

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

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

@coderabbitai
Copy link

coderabbitai bot commented Nov 1, 2025 •
edited
Loading

Important

Review skipped

Bot user detected.

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

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

  • 🔍 Trigger a full review

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

@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from ca584fe to 685c10c Compare November 13, 2025 22:04
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from c0f0175 to 0ddf549 Compare November 25, 2025 13:57
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 0d6f5d2 to 66f4155 Compare December 4, 2025 18:52
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 6faaac5 to 930fd8b Compare December 12, 2025 20:52
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from b5f6bc2 to 66d9d76 Compare December 18, 2025 20:27
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 73b2035 to 7b90029 Compare January 12, 2026 13:36
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from ad95cdd to 706581d Compare January 18, 2026 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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