Update Poetry dependencies - #331
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/poetry-dependencies
branch
from
September 3, 2026 01:04
96390f3 to
dd26916
Compare
|
renovate
Bot
force-pushed
the
renovate/poetry-dependencies
branch
from
September 11, 2026 10:53
dd26916 to
1ba3a40
Compare
renovate
Bot
force-pushed
the
renovate/poetry-dependencies
branch
from
September 18, 2026 22:51
1ba3a40 to
f6bfd00
Compare
renovate
Bot
force-pushed
the
renovate/poetry-dependencies
branch
from
September 20, 2026 23:55
f6bfd00 to
49fc1bc
Compare
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.





This PR contains the following updates:
7.15.4→7.16.11.8.21→1.8.220.26.2→0.26.32.33.0.20260712→2.33.0.20260906Release Notes
coveragepy/coveragepy (coverage)
v7.16.1Compare Source
Fix: when the body of an irrefutable
case(likecase _:) is entirelyexcluded, the
caseline is now excluded too, just as an excludedelse:body removes theelse:line. Previously thecaseline wasleft behind and reported as missing. Closes
issue 1563_ withpull 2269_.Fix: using :meth:
.CoverageData.updatetwice on an in-memory database wouldfail, as described in
issue 2279_. This is now fixed... _issue 1563: #1563
.. _pull 2269: #2269
.. _issue 2279: #2279
.. _changes_7-16-0:
v7.16.0Compare Source
When combining files, now path separator slashes will automatically be
converted to the local file system style. This makes it less necessary to
define
[paths]configuration to combine data across operating systems.Fixes
issue 2266_.The :meth:
.Coverage.switch_contextmethod now returns the previous context.Fix: previously, a
[paths]pattern would be replaced everywhere in a filepath when it was only meant to be replaced once, in the leading portion of
the path. This is now fixed, in
pull 2268_.Fixes to validation of options and configuration settings:
Negative precision settings now always cause useful error messages (
pull 2261_).An invalid regex in the
--contextsoption (or the[report] contextssetting) reported a confusing "Couldn't use data file ...:user-defined function raised exception" error. Now it raises a proper
configuration error naming the bad regex, like other regex settings do
(
pull 2262_).Non-string values in TOML configuration settings now produce a helpful
error message instead of a traceback. This affects list settings whose
elements aren't strings (like
omit,exclude_lines, or a[paths]entry), file settings like
data_file, and any wrong-typed value in the[paths]section (pull 2263_).coverage runrefuses run-affecting command-line options like--branchalongside--concurrency=multiprocessing, since they can'treach the subprocesses. The check only recognized
multiprocessingasthe entire option value, so
--concurrency=multiprocessing,threadslipped through and failed later with "Can't combine statement coverage
data with branch data". Each named concurrency library is now properly
considered (
pull 2270_).Fix:
coverage annotate -d DIRraised anAssertionErrorif anymeasured file had an extension other than
.py, such as a.pywfile onWindows. The original extension is now restored on the annotated copy (
pull 2265_)... _pull 2261: #2261
.. _pull 2262: #2262
.. _pull 2263: #2263
.. _pull 2265: #2265
.. _issue 2266: #2266
.. _pull 2268: #2268
.. _pull 2270: #2270
.. _changes_7-15-4:
microsoft/debugpy (debugpy)
v1.8.22: debugpy v1.8.22Compare Source
Fixes
Enhancements
Infrastructure work
Thanks to @pdepetro, @rchiodo, @nshepperd, @aperez, @karandhaodiyal28-hash, @danfiedler-msft, and @finnagin for the commits.
Full Changelog: microsoft/debugpy@v1.8.21...v1.8.22
getsentry/responses (responses)
v0.26.3Compare Source
keep_headersargument to_recorder.recordandRecorder.dump_to_fileto preserve named headers (for exampleDate)that are otherwise stripped as verbose defaults, so a signed response can be
recorded and later verified. Matching is case-insensitive. See #763
CallListso static type checkers inferCallvalues when iterating, indexing, or filtering recorded calls. See #722query_string_matcher(and the query matching auto-applied to aregistered URL's own query string) discarding blank-valued query params
(
b=), which caused requests with an extra or missing blank param tomatch incorrectly. See #804
fragment_identifier_matchertreating opaque fragments (those without=, e.g./users/5) as always equal, so a required fragment matched adifferent one or none at all. See #806
Configuration
📅 Schedule: (in timezone CET)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.