Skip to content

fix(deps): update all non-major dependencies - #391

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

fix(deps): update all non-major dependencies#391
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Oct 17, 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
astral-sh/setup-uv action patch v10.3.0 → v10.3.3 age confidence
charliermarsh/ruff-pre-commit repository patch v0.17.0 → v0.17.5 age confidence
httpx2 (changelog) project.dependencies minor >=2.13.1 → >=2.16.0 age confidence
loguru (changelog) dependency-groups minor >=0.7.3 → >=0.8.0 age confidence
peter-evans/create-pull-request action patch v8.1.1 → v8.1.3 age confidence
pre-commit dependency-groups minor >=4.6.2 → >=4.7.0 age confidence
pytest (changelog) dependency-groups minor >=9.1.1 → >=9.2.0 age confidence
pytest-asyncio (changelog) dependency-groups minor >=1.4.0 → >=1.5.0 age confidence
ruff (source, changelog) dependency-groups patch >=0.17.0 → >=0.17.5 age confidence
tisfeng/issues-translate-action action minor v2.9.2 → v2.10.0 age confidence
vcrpy dependency-groups minor >=8.3.0 → >=8.5.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

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
charliermarsh/ruff-pre-commit

v0.17.5

Compare Source

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

v0.17.4

Compare Source

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

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

pydantic/httpx2 (httpx2)

v2.16.0

Compare Source

Highlights
🍪 Faster requests with large cookie jars

Building the Cookie header no longer scans every cookie in the jar. The client reuses its jar instead of copying it on every request and redirect (#​1284), only looks up the domains that can match the request host, and skips the expired cookie sweep until a cookie is due (#​1285). With 1,000 cookies across 500 domains, building the Cookie header is about 18 times faster.

Cookies from different domains are now sent from the least to the most specific domain, for example .example.org before sub.example.org, instead of in the order the domains were added. Cookies with longer paths still come first.

httpx2
Changed
  • Look up only the cookie domains that match the request host, and skip the expired cookie sweep until a cookie is due. With 1,000 cookies across 500 domains, building the Cookie header is about 18 times faster. Cookies from different domains are now sent from the least to the most specific domain (#​1285).
Fixed
  • Reuse the client cookie jar instead of copying it on every request and redirect. A custom policy set with client.cookies.jar.set_policy() now applies to outgoing requests (#​1284).
httpcore2

No changes since 2.15.1. Version bumped to stay in lockstep with httpx2.

Full Changelog: pydantic/httpx2@v2.15.1...v2.16.0

v2.15.1

Compare Source

Highlights
🔒 Flat CPU usage for long-lived clients on Linux

On Linux, the default SSL context is now configured once instead of on every handshake (#​1253). With OpenSSL older than 3.4, each handshake added a duplicate certificate lookup path, so CPU usage per request grew over the lifetime of a reused client. Certificate verification is unchanged, and Windows and macOS still use truststore.

httpx2
Fixed
  • Configure the default SSL context once on Linux, instead of on every handshake. With OpenSSL older than 3.4, CPU usage grew over the lifetime of a reused client (#​1253).
httpcore2
Fixed
  • Configure the default SSL context once on Linux, instead of on every handshake. With OpenSSL older than 3.4, CPU usage grew over the lifetime of a reused client (#​1253).

Full Changelog: pydantic/httpx2@v2.15.0...v2.15.1

v2.15.0

Compare Source

Highlights
🐍 Python 3.11+ required

httpx2 and httpcore2 no longer support Python 3.10 (#​1274). There are no other changes in this release.

httpx2
Removed
  • Drop support for Python 3.10 (#​1274).
httpcore2
Removed
  • Drop support for Python 3.10 (#​1274).

Full Changelog: pydantic/httpx2@v2.14.0...v2.15.0

v2.14.0

Compare Source

Highlights

🌐 CIDR ranges in NO_PROXY

NO_PROXY and mounts now match IP CIDR ranges like 192.168.0.0/16 and [fe80::]/10, so any address in the range bypasses the proxy (#​1165). Bracketed IPv6 addresses like [::1]:8080 are accepted, and unparseable NO_PROXY entries are ignored instead of failing client creation (#​1267).

🔐 FIPS-enforced Python support

httpx2 now imports on FIPS-enforced Python builds without hashlib.md5. DigestAuth raises ProtocolError only when the server asks for an unavailable algorithm (#​1130).

🔌 Sturdier connections and WebSocket shutdown

HTTP/2 reads no longer block when a server lowers SETTINGS_MAX_CONCURRENT_STREAMS mid-flight (#​1217), and writing after a peer closes TLS without close_notify raises WriteError (#​1263). Sync WebSocket sessions no longer hang on exit with a full event queue (#​1123), and ASGI WebSocket reads after app shutdown no longer leak anyio exceptions (#​1233).

httpx2

Added
  • Match IP CIDR ranges, like 192.168.0.0/16 and [fe80::]/10, in NO_PROXY and mounts. Requests to any address in the range now bypass the proxy; previously only the network address itself did (#​1165).
  • Accept bracketed IPv6 addresses, like [::1] and [::1]:8080, in NO_PROXY (#​1267).
Changed
  • Raise InvalidURL for a mounts key with an IP host followed by anything other than a valid CIDR prefix, like all://10.0.0.0/33 (#​1165).
Fixed
  • Ignore NO_PROXY entries that cannot be parsed, instead of raising InvalidURL when the client is created (#​1267).
  • Import httpx2 on FIPS-enforced Python builds without hashlib.md5. DigestAuth raises ProtocolError when the server asks for an unavailable algorithm (#​1130).
  • Handle reads after an ASGI WebSocket app shuts down, instead of leaking anyio exceptions (#​1233).
  • Stop the sync WebSocket session from hanging on exit when its event queue is full (#​1123).

httpcore2

Fixed
  • Keep CONNECT and absolute-form proxy targets when the request sets the target extension (#​1262).
  • Stop blocking reads when an HTTP/2 server lowers SETTINGS_MAX_CONCURRENT_STREAMS while requests are in flight (#​1217).
  • Raise WriteError instead of anyio.EndOfStream when writing after the peer closes a TLS connection without close_notify (#​1263).

Full Changelog: pydantic/httpx2@v2.13.1...v2.14.0

Delgan/loguru (loguru)

v0.8.0

Compare Source

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

  • Change the default log format to include the timezone offset since it produces less ambiguous logs (#&#8203;856 <https://github.com/Delgan/loguru/pull/856>, thanks @tim-x-y-z <https://github.com/tim-x-y-z>).
  • Add new logger.reinstall() method to automatically set up the logger in spawned child processes (#&#8203;818 <https://github.com/Delgan/loguru/issues/818>, thanks @monchin <https://github.com/monchin>).
  • Add support for template strings used as log messages (#&#8203;1397 <https://github.com/Delgan/loguru/issues/1397>, thanks @TurtleOrangina <https://github.com/TurtleOrangina>).
  • Add record["template"] that includes the raw, unformatted message (#&#8203;1349 <https://github.com/Delgan/loguru/issues/1349>, thanks @sentrivana <https://github.com/sentrivana>).
  • Fix incorrect microsecond value when formatting the log timestamp using {time:x} (#&#8203;1440 <https://github.com/Delgan/loguru/issues/1440>_).
  • Fix parsing of 12-hour rotation times without seconds (#&#8203;1474 <https://github.com/Delgan/loguru/issues/1474>, thanks @c-tonneslan <https://github.com/c-tonneslan>).
  • Fix a "<weekday> at <time>" rotation firing its first rotation on the creation day instead of the requested weekday when the time of day was later than the creation time (#&#8203;1484 <https://github.com/Delgan/loguru/pull/1484>, thanks @gaoflow <https://github.com/gaoflow>).
  • Fix hex color short code expansion (#&#8203;1426 <https://github.com/Delgan/loguru/issues/1426>, thanks @turkoid <https://github.com/turkoid>).
  • Fix possible regular expression denial of service (ReDoS) when parsing color markups in strings containing long sequences of backslashes (#&#8203;1537 <https://github.com/Delgan/loguru/issues/1537>_).
  • Fix possible internal error when dealing with (rare) frame objects missing a f_lineno value (#&#8203;1435 <https://github.com/Delgan/loguru/issues/1435>_).
  • Fix a regression preventing formatting of record["time"] when using zoneinfo.ZoneInfo timezones (#&#8203;1260 <https://github.com/Delgan/loguru/pull/1260>, thanks @bijlpieter <https://github.com/bijlpieter>).
  • Fix possible ValueError raised on Windows when system clock was set far ahead in the future (#&#8203;1291 <https://github.com/Delgan/loguru/issues/1291>_).
  • Fix externally raised Exception possibly causing invalid state generating repeated RuntimeError of avoided deadlock (#&#8203;1335 <https://github.com/Delgan/loguru/issues/1335>_).
  • Fix incorrect formatting of negative timezone offsets with sub-minute components (#&#8203;1500 <https://github.com/Delgan/loguru/issues/1500>_).
  • Fix incorrect formatting of negative timestamps (#&#8203;1501 <https://github.com/Delgan/loguru/issues/1501>_).
  • Fix incorrect thread and process identifiers of standard logging Handler records when using enqueue=True (#&#8203;1527 <https://github.com/Delgan/loguru/issues/1527>_).
  • Fix catch=True being ignored for exceptions raised during sink termination, such as file retention or compression triggered by logger.remove() (#&#8203;1532 <https://github.com/Delgan/loguru/issues/1532>_).
  • Fix logger.parse() decoding log files with the locale encoding instead of UTF-8 when given a path, which failed on non-ASCII logs written using the file sink default encoding on Windows (#&#8203;1540 <https://github.com/Delgan/loguru/pull/1540>_).
  • Fix formatting of truncated ExceptionGroup errors, which used a plural for a single remaining exception and could miss the closing ruler (#&#8203;1541 <https://github.com/Delgan/loguru/pull/1541>, thanks @JeremyL691 <https://github.com/JeremyL691>).
  • Respect the .level attribute of standard logging Handler used as sink, which was previously ignored (#&#8203;1409 <https://github.com/Delgan/loguru/issues/1409>_).
  • Allow the rotation argument of file sinks to accept a list of rotation conditions, any of which can trigger the rotation (#&#8203;1174 <https://github.com/Delgan/loguru/issues/1174>, thanks @CollinHeist <https://github.com/CollinHeist>).
  • Honor the NO_COLOR environment variable which disables color output by default if colorize is not provided (#&#8203;1178 <https://github.com/Delgan/loguru/issues/1178>_).
  • Honor the FORCE_COLOR environment variable which enables color output by default if colorize is not provided (#&#8203;1305 <https://github.com/Delgan/loguru/issues/1305>, thanks @nhurden <https://github.com/nhurden>).
  • Add requirement for TERM environment variable not to be "dumb" to enable colorization (#&#8203;1287 <https://github.com/Delgan/loguru/pull/1287>, thanks @snosov1 <https://github.com/snosov1>).
  • Make logger.catch() usable as an asynchronous context manager (#&#8203;1084 <https://github.com/Delgan/loguru/issues/1084>_).
  • Make logger.catch() compatible with asynchronous generators (#&#8203;1302 <https://github.com/Delgan/loguru/issues/1302>_).
  • Improve feedback for invalid format keys in logger format strings (#&#8203;1450 <https://github.com/Delgan/loguru/issues/1450>, thanks @Krishnachaitanyakc <https://github.com/Krishnachaitanyakc>).
peter-evans/create-pull-request

v8.1.3: Create Pull Request v8.1.3

Compare Source

What's Changed

Full Changelog: peter-evans/create-pull-request@v8.1.2...v8.1.3

v8.1.2: Create Pull Request v8.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: peter-evans/create-pull-request@v8.1.1...v8.1.2

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_count, log_level, log_cli_level, log_file_level,log_auto_indent and faulthandler_timeout configuration options now accept native integer (and, for log_auto_indent, boolean) values in TOML configuration files, while still accepting strings for backward compatibility.
    log_file_mode now reports invalid values as a usage error.

  • #​15254: tmp_path and TempPathFactory.mktemp <pytest.TempPathFactory.mktemp> no longer list the whole base temporary directory on every call, which made sessions with many temporary directories quadratically slow. Numbers are now handed out from a per-prefix counter, skipping names that already exist.

  • #​4569: Node.add_marker <_pytest.nodes.Node.add_marker> now stores a ~pytest.Mark in node.keywords, matching what marks applied during collection store. Previously it stored a ~pytest.MarkDecorator.

  • #​9436: Avoided formatting tracebacks for tests marked with xfail(run=False).

Bug fixes

  • #​10128: Configured warning filters now apply to warnings emitted by pytest_configure hooks.

  • #​10210: pytest.approx now raises a TypeError for any nested container, not
    only for one of the same type as its parent. Previously approx([{"k": 1}])
    and approx({"k": [1]}) were accepted and then compared unequal to every
    value, silently ignoring the tolerance, while approx([[1]]) correctly
    reported that nesting is unsupported.

  • #​10644: monkeypatch.setattr() no longer leaves a new entry in the instance __dict__ when it patches an attribute that the instance inherits from its class.

    Previously undo() assigned the inherited value onto the instance, which shadowed the class attribute -- permanently freezing the result for descriptors that resolve dynamically.

  • #​1139: Fixed tracebacks showing ??? instead of source lines for code compiled with a filename relative to a directory other than the current working directory -- e.g. compiled Cython modules, when running pytest from a subdirectory of the project root.
    The source lookup now falls back to searching sys.path for such filenames, as the standard traceback module does.

  • #​11502: The rootdir is no longer derived from a configuration file that is not a regular file, such as --config-file=/dev/null.

  • #​11783: Plugins installed in editable mode (660) are marked for assertion rewriting again.

    Such installs do not record the package's Python files in the distribution metadata, so pytest found nothing to rewrite and assertions inside the plugin lost their introspection. The plugin's entry point is now used to locate the package in that case.

  • #​11933: pytest.warns no longer re-emits unmatched warnings with module="warnings", which caused module-based warning filters to be applied to the wrong warnings. Since warnings.WarningMessage does not record the module a warning was emitted with, re-emitted warnings now use the standard warnings.warn_explicit default of deriving the module from the warning's filename.

  • #​12175: ExceptionInfo.exconly(tryshort=True) <pytest.ExceptionInfo.exconly> now strips the AssertionError: prefix of failed assert statements for ~pytest.ExceptionInfo objects created by pytest.raises, and failures inside unittest.TestCase.subTest report the same short crash line as regular tests.

  • #​12223: The message attribute of <failure> and <error> elements in --junitxml reports is now shortened to whole lines within 500 characters. When something is dropped, it ends with a note pointing to the element text, which still holds the full report. Previously, very verbose assertion output (e.g. with -vv) produced attributes tens of thousands of characters long, which some XML parsers fail on.

  • #​12307: Fixed truncation of long collections (lists, dicts, sets, etc.) in the "message" part of failed assertions (as in assert condition, msg) when using -vv: the message now uses the same unlimited repr as the rest of the assertion output, instead of eliding collection elements with ....

  • #​12824: Custom command-line options now fail with a clear error when their implicit
    destination conflicts with an existing option, avoiding silent overrides of
    built-in

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

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Only on Sunday and Saturday (* * * * 0,6)
  • 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.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Oct 17, 2026
@renovate

renovate Bot commented Oct 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: uv.lock
Downloading cpython-3.10.22-linux-x86_64-gnu (download) (28.0MiB)
 Downloaded cpython-3.10.22-linux-x86_64-gnu (download)
Using CPython 3.10.22
error: No solution found when resolving dependencies for split (markers: python_full_version == '3.10.*' and platform_python_implementation != 'PyPy')
  cause: Because the requested Python version (>=3.10) does not satisfy Python>=3.11 and your project depends on httpx2[http2]>=2.16.0, we can conclude that your project's requirements are unsatisfiable.
         And because your project requires picimagesearch[socks], we can conclude that your project's requirements are unsatisfiable.

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from cf9dc6e to 18cd435 Compare October 18, 2026 16:39
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Oct 18, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 62f4116 to 631c143 Compare October 25, 2026 21:25
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 314994a to 12954bf Compare November 2, 2026 19:29
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from ab2039e to 0472ca8 Compare November 12, 2026 19:08
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 0472ca8 to 31e3649 Compare November 13, 2026 16:58
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 31e3649 to 4e79b9b Compare November 13, 2026 23:11

This branch has not been deployed

No deployments
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

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants