GeezerVison is showing github.com — Bump the pip group with 5 updates by dependabot[bot] · Pull Request #482 · python/blurb_it
Conversation
Bumps the pip group with 5 updates:
Updates aiohttp from 3.14.4 to 3.14.5
Updates gidgethub from 5.4.0 to 6.0.0
Release notes
Sourced from gidgethub's releases.
6.0.0
What's Changed
New Contributors
Full Changelog: gidgethub/gidgethub@v5.3.0...v6.0.0
Changelog
Sourced from gidgethub's changelog.
6.0.0
-
Add managed GitHub App authentication to :class:gidgethub.abc.GitHubAPI
through new app_id and private_key constructor arguments. JWTs are
generated, cached, and refreshed automatically while explicit per-request
credentials continue to take precedence. This design was inspired by
Jonathan Sick's (@jonathansick) earlier implementation in
PR [#201](https://github.com/gidgethub/gidgethub/issues/201) <https://github.com/gidgethub/gidgethub/pull/201>_
(Issue [#199](https://github.com/gidgethub/gidgethub/issues/199) <https://github.com/gidgethub/gidgethub/issues/199>_). Generated
JWTs now backdate their issue time by 60 seconds to tolerate clock drift,
with their expiration measured from that backdated issue time so GitHub's
10 minute limit on the time between issue and expiration is respected.
-
Handle 422 responses whose errors entries are strings instead of objects,
raising :exc:gidgethub.ValidationError instead of :exc:TypeError
(Issue [#139](https://github.com/gidgethub/gidgethub/issues/139) <https://github.com/gidgethub/gidgethub/issues/139>_)
-
Add :meth:gidgethub.abc.GitHubAPI.manage_rate_limit as an overridable
hook, along with the :attr:gidgethub.abc.GitHubAPI.requests_in_flight
attribute, to let users implement their own rate-limit/backpressure
strategies
(Issue [#19](https://github.com/gidgethub/gidgethub/issues/19) <https://github.com/gidgethub/gidgethub/issues/19>_)
-
Add :meth:gidgethub.abc.GitHubAPI.handle_rate_limit_error as an
overridable hook, allowing requests that fail with an
:exc:~gidgethub.HTTPException to be retried (e.g. after a secondary
rate limit or abuse-detection response)
(Issue [#19](https://github.com/gidgethub/gidgethub/issues/19) <https://github.com/gidgethub/gidgethub/issues/19>_)
-
Add :attr:gidgethub.HTTPException.headers attribute
(PR [#227](https://github.com/gidgethub/gidgethub/issues/227) <https://github.com/gidgethub/gidgethub/pull/227>_)
-
Add a trailing / to url and remove any leading / in base_url for
:func:gidgethub.sansio.format_url
(PR [#234](https://github.com/gidgethub/gidgethub/issues/234) <https://github.com/gidgethub/gidgethub/pull/234>_)
-
Use httpx2 as a drop-in replacement for httpx backend.
The "httpx" extra was updated to use httpx2 and a new httpx2 extra
was also added.
-
Document that :meth:gidgethub.abc.GitHubAPI.graphql returns the value of
the "data" key from the JSON response
(Issue [#127](https://github.com/gidgethub/gidgethub/issues/127) <https://github.com/gidgethub/gidgethub/issues/127>_)
-
Add support for Python 3.14 and 3.15, and drop support for Python 3.8 and
3.9. The minimum supported Python version is now 3.10.
Commits
e3755a1 6.0.0 release (#254)2cb3a93 Add Python version support entry to Unreleased changelog8a818e7 Noxfile touch ups (#253)9fc0f84 Add managed GitHub App JWT authentication (#252)8e63d7d Handle 422 responses whose errors list contains strings (#250)ece9dd5 Document GitHub handling of misnamed GraphQL variables (#251)60c2c89 Document that graphql() returns the 'data' key value (#249)f2e9b7b Add proactive and reactive rate limiting API (#247)7e4c788 Preserve Router.register handler signatures with ParamSpec (#246)c026365 Raise minimum Python version to 3.10 (#248)- Additional commits viewable in compare view
Updates sentry-sdk from 2.70.0 to 2.73.0
Release notes
Sourced from sentry-sdk's releases.
2.73.0
New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
Deps
Other
2.72.0
New Features ✨
Asgi
Boto3
Wsgi
... (truncated)
Changelog
Sourced from sentry-sdk's changelog.
2.73.0
New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
Deps
Other
2.72.0
New Features ✨
Asgi
Boto3
Wsgi
... (truncated)
Commits
54160ae release: 2.73.025d265b fix: Exclude litellm==1.107.0 from extras (#8104)60116ac fix(celery): Don't round down beat schedule intervals (#7842)68bc4dd fix(arq): Don't monitor cron jobs with unsupported schedules (#8098)1c249d8 feat(huey): Add an option to monitor Huey periodic tasks (#8052)4e19592 feat(rq): Add an option to monitor rq-scheduler jobs (#8053)f8b08b3 meta: Update AGENTS.md (#8077)cfce72f chore(deps): bump uv from 0.13.0 to 0.13.4 (#8095)a9553c4 feat(arq): Add an option to monitor arq cron jobs (#8051)641517a fix(attributes): Handle special float values correctly (#8067)- Additional commits viewable in compare view
Updates coverage from 7.16.1 to 7.17.0
Release notes
Sourced from coverage's releases.
7.17.0
Version 7.17.0 — 2026-10-22
- Dropped support for Python 3.10.
- Binary wheels are now provided for iOS and Android. This allows the use of the optimized C tracer on mobile platforms.
- Fix: three or more levels of nested
with statements could make a with line look like a branch with an exit that can never happen. Using the sys.monitoring core, these phantom branches were reported as partial. Other cores hid the problem but still counted the phantom branches in the total. Closes issue 1987.
- Fix: a comment or string that merely mentioned
if True: or while True: could mark its line as a branch that is known to be partial, so a branch that never ran was reported as taken. These built-in patterns now only match at the start of the statement. Closes issue 2314.
- Fix: region detection missed functions defined in unusual places, such as
else and except clauses. This is now fixed.
- Fix: recent versions of the lcov tool complain if the same function name appears more than once in a report. Python can have multiple same-named functions in a few ways, for example, getters/setters or conditionally defined functions. These are now disambiguated by adding a
@<line number> suffix to the function name. Fixes issue 2335.
- Fix: The “Can’t combine statement coverage data with branch data” error now names the two data files it couldn’t combine. The error description in the docs now lists common causes and how to find the process that wrote the file.
- Fix: at coverage totals close to 0 or 100, the XML report could get incorrect
line-rate values like 8.333e-05 or 1. This is now fixed, closing issue 2293 and issue 2294.
- Fix: a parallel data file saved more than once kept the hash of its first save in its file name. Combining could then skip it as a duplicate of another file that had the same data at that point, and delete it, losing the data recorded after the first save. Each save now updates the hash. This had been a problem since 7.13.1. Fixes issue 2338.
- Fixes for obscure but legal file names:
- File names (and plugin names) can contain control characters, which are legal in POSIX paths but unsafe in reports: in XML 1.0 they make the document non-well-formed, and in a terminal they act as escape sequences (colors, title/clipboard sequences, cursor moves that forge output). Now the XML report, the text and Markdown summary reports, and
coverage debug data replace non-printable characters in names. Printable names are unchanged.
- A file pattern (from
include, omit, or a [paths] alias) containing a newline sent the glob-to-regex translation into an infinite loop, hanging the process. Newlines in patterns are now handled like any other character.
- Fixes in the implementation of the C tracer:
- If a plugin’s
dynamic_source_filename method raised an exception, lines in that function could be recorded as belonging to a different file. Also fixed some minor memory leaks in the C tracer.
- The refcount of
None was mismanaged during function calls, including comprehensions. This was unlikely to cause an actual problem, but is now fixed. Thanks, Andrew Dalke.
- The C tracer held borrowed references to dictionary values, which was unsafe on free-threaded Python. Now it takes its own references.
- An internal error while recording a new file could be reported as a confusing
SystemError instead of the actual exception.
- Performance: the text summary report (
coverage report) held on to every file’s parsed source until it finished, so its memory use grew with the size of the project: ten times or more what 7.14 used on large projects. Now it keeps only what it needs to print. Fixes issue 2277.
- Performance: HTML reports should be about 5% faster to produce.
- Kept the political banner in the README. Closes issue 2344.
➡️ PyPI page: coverage 7.17.0.
:arrow_right: To install: python3 -m pip install coverage==7.17.0
7.16.2
Version 7.16.2 — 2026-09-27
- Fix: on Python 3.14 and later, a
for loop completing immediately before a function return could mistakenly report an uncovered branch. This is now fixed, closing issue 2168.
- Fix: on Python 3.14 and later, the
else clause of a try whose body is a with statement could incorrectly be reported as covered when the with raised. This is now fixed, closing issue 2289.
- Fix: with
dynamic_context = test_function, test methods written as @staticmethod or @classmethod were not given a context of their own. Now they are, on Python 3.11 and later. Closes issue 1923.
➡️ PyPI page: coverage 7.16.2.
:arrow_right: To install: python3 -m pip install coverage==7.16.2
Changelog
Sourced from coverage's changelog.
Version 7.17.0 — 2026-10-22
-
Dropped support for Python 3.10.
-
Binary wheels are now provided for iOS and Android. This allows the use of
the optimized C tracer on mobile platforms.
-
Fix: three or more levels of nested with statements could make a with
line look like a branch with an exit that can never happen. Using the
sys.monitoring core, these phantom branches were reported as partial. Other
cores hid the problem but still counted the phantom branches in the total.
Closes issue 1987_.
-
Fix: a comment or string that merely mentioned if True: or
while True: could mark its line as a branch that is known to be partial,
so a branch that never ran was reported as taken. These built-in patterns
now only match at the start of the statement. Closes issue 2314_.
-
Fix: region detection missed functions defined in unusual places, such as
else and except clauses. This is now fixed.
-
Fix: recent versions of the lcov tool complain if the same function name
appears more than once in a report. Python can have multiple same-named
functions in a few ways, for example, getters/setters or conditionally
defined functions. These are now disambiguated by adding a @<line number>
suffix to the function name. Fixes issue 2335.
-
Fix: The "Can't combine statement coverage data with branch data" error now
names the two data files it couldn't combine. The :ref:error description <error_cant_combine> in the docs now lists common causes and how to find the
process that wrote the file.
-
Fix: at coverage totals close to 0 or 100, the XML report could get incorrect
line-rate values like 8.333e-05 or 1. This is now fixed, closing
issue 2293_ and issue 2294_.
-
Fix: a parallel data file saved more than once kept the hash of its first
save in its file name. Combining could then skip it as a duplicate of another
file that had the same data at that point, and delete it, losing the data
recorded after the first save. Each save now updates the hash. This had been
a problem since 7.13.1. Fixes issue 2338_.
-
Fixes for obscure but legal file names:
- File names (and plugin names) can contain control characters, which are
legal in POSIX paths but unsafe in reports: in XML 1.0 they make the
document non-well-formed, and in a terminal they act as escape sequences
(colors, title/clipboard sequences, cursor moves that forge output). Now
the XML report, the text and Markdown summary reports, and ``coverage debug
... (truncated)
Commits
393ac71 docs: prep for 7.17.014257d3 test: check that 100% files haven't lost coveragedb056ac docs: keep the ukraine banner #23446033660 fix: update the data file hash when a parallel data file is saved again (#2339)99024b5 fix: clamp rate in XML report to prevent false 1.0/0.0 rounding and scientifi...ff62a02 refactor: remove unused caching branches24d0b67 fix: KeyError for a with statement at the end of a finally clause (#2336)934f5b8 chore: upgrade pip==26.2.2 certifi==2026.10.19f95c980 fix: triply nested with statements don't cause false branch misses #19876aaa858 docs: more changelog gardening- Additional commits viewable in compare view
Updates pytest-mock from 3.15.1 to 3.17.0
Release notes
Sourced from pytest-mock's releases.
v3.17.0
2026-10-17
- #641: Failures of mock assertions such as
assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.
- #642: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call:
assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.
- #643:
assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.
v3.16.1
2026-10-17
- #617: Fixed
assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).
- #621: Fixed
mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.
- #621:
mocker.stop() now undoes the most recent patch first when the same object is used in several patches.
- #623: Fixed misleading introspection in
assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.
- #624: Clear
spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.
- #627: Document
async_stub await assertions and the distinction between call and await tracking.
- #629: Fixed
mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.
- #630:
mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.
- #633: Fixed spies on
classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.
v3.16.0
2026-09-27
- #604: Fixed
duplicate_iterators=True for async functions spied with mocker.spy.
- #611: Fixed async mock assertion introspection to use awaited arguments instead of the latest call's arguments.
- #606:
mocker.resetall(return_value=True, side_effect=True) now also applies to non-callable mocks, such as those returned by mocker.create_autospec(SomeClass, instance=True). Previously both arguments were silently ignored for them.
- #547: Added
SpyType for annotating mocker.spy results.
- Dropped support for EOL Python 3.9.
- #147: Removed handling of
RuntimeError: stop called on unstarted patcher, which can no longer occur in the supported Python versions.
- Added support for Python 3.15.
Changelog
Sourced from pytest-mock's changelog.
3.17.0
2026-10-17
[#641](https://github.com/pytest-dev/pytest-mock/issues/641) <https://github.com/pytest-dev/pytest-mock/pull/641>_: Failures of mock assertions such as assert_called_with are again reported only once, instead of two or three times with the original error from the mock module chained before them.[#642](https://github.com/pytest-dev/pytest-mock/issues/642) <https://github.com/pytest-dev/pytest-mock/pull/642>_: Mock assertion failures no longer show misleading introspection when they are not about the arguments of the last call: assert_called, assert_called_once, assert_not_called, assert_any_call, their await counterparts, and assert_called_once_with/assert_awaited_once_with when the mock was not called (awaited) exactly once. The introspection also no longer reports arguments passed by position versus by keyword as different for autospecced mocks, and no longer shows empty Args:/Kwargs: sections when assertion rewriting is not available.[#643](https://github.com/pytest-dev/pytest-mock/issues/643) <https://github.com/pytest-dev/pytest-mock/pull/643>_: assert_has_calls and assert_has_awaits failures no longer show pytest introspection, which compared the expected and actual calls position by position and so reported differences between unrelated calls. The mock's own message, listing the expected and actual calls, is still shown.
3.16.1
2026-10-17
[#617](https://github.com/pytest-dev/pytest-mock/issues/617) <https://github.com/pytest-dev/pytest-mock/pull/617>_: Fixed assert_has_calls raising ValueError instead of AssertionError (or showing misleading introspection) when the expected calls are plain tuples rather than call(...) objects, such as (args, kwargs) entries of another mock's call_args_list, (args,), (kwargs,), (name, args) or (name, kwargs).[#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: Fixed mocker.stop() sometimes stopping the wrong mock, for example with mocks from mocker.create_autospec.[#621](https://github.com/pytest-dev/pytest-mock/issues/621) <https://github.com/pytest-dev/pytest-mock/pull/621>_: mocker.stop() now undoes the most recent patch first when the same object is used in several patches.[#623](https://github.com/pytest-dev/pytest-mock/issues/623) <https://github.com/pytest-dev/pytest-mock/pull/623>_: Fixed misleading introspection in assert_has_awaits failures, and assert_has_calls/assert_has_awaits raising IndexError instead of AssertionError when calls is passed by keyword.[#624](https://github.com/pytest-dev/pytest-mock/issues/624) <https://github.com/pytest-dev/pytest-mock/pull/624>_: Clear spy_return_iter after a spied synchronous or asynchronous function raises, matching spy_return.[#627](https://github.com/pytest-dev/pytest-mock/issues/627) <https://github.com/pytest-dev/pytest-mock/pull/627>_: Document async_stub await assertions and the distinction between call and await tracking.[#629](https://github.com/pytest-dev/pytest-mock/issues/629) <https://github.com/pytest-dev/pytest-mock/pull/629>_: Fixed mocker.resetall() skipping the mocks patched with mocker.patch.multiple(), both the ones it creates and the ones passed explicitly.[#630](https://github.com/pytest-dev/pytest-mock/issues/630) <https://github.com/pytest-dev/pytest-mock/pull/630>_: mocker.resetall() now also resets spy_return and spy_exception of spies, like it already did for spy_return_list and spy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.[#633](https://github.com/pytest-dev/pytest-mock/issues/633) <https://github.com/pytest-dev/pytest-mock/pull/633>_: Fixed spies on classmethod, staticmethod, builtins and classes returning a MagicMock instead of calling the spied code after mocker.resetall(side_effect=True). Resetting a spy's side_effect now goes back to calling the spied code, also clearing any side_effect set on the spy.
3.16.0
2026-09-27
[#604](https://github.com/pytest-dev/pytest-mock/issues/604) <https://github.com/pytest-dev/pytest-mock/pull/604>_: Fixed duplicate_iterators=True for async functions spied with mocker.spy.[#611](https://github.com/pytest-dev/pytest-mock/issues/611) <https://github.com/pytest-dev/pytest-mock/pull/611>_: Fixed async mock assertion introspection to use awaited arguments instead of the latest call's arguments.[#606](https://github.com/pytest-dev/pytest-mock/issues/606) <https://github.com/pytest-dev/pytest-mock/pull/606>_: mocker.resetall(return_value=True, side_effect=True) now also applies to non-callable mocks, such as those returned by mocker.create_autospec(SomeClass, instance=True). Previously both arguments were silently ignored for them.[#547](https://github.com/pytest-dev/pytest-mock/issues/547) <https://github.com/pytest-dev/pytest-mock/issues/547>_: Added SpyType for annotating mocker.spy results.- Dropped support for EOL Python 3.9.
[#147](https://github.com/pytest-dev/pytest-mock/issues/147) <https://github.com/pytest-dev/pytest-mock/issues/147>_: Removed handling of RuntimeError: stop called on unstarted patcher, which can no longer occur in the supported Python versions.- Added support for Python 3.15.
Commits
5c2f207 Release 3.17.09625271 Bump the minor version for releases that change existing behavior34b87ae Drop introspection from assert_has_calls and assert_has_awaits (#643)866520f Only show introspection for failures about the call arguments (#642)5ab41c1 Do not chain the original mock error to wrapped assertion failures (#641)1916b14 Merge pull request #635 from nicoddemus/docs-contributing-resetall212fcd9 Document resetall, the changelog format and running tests with tox9374b2c Merge pull request #634 from pytest-dev/release-3.16.1fab730d Release 3.16.1d26d41b Merge pull request #627 from xiehuanyi/docs/async-stub-awaits-20261012-r2- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase will rebase this PR@dependabot recreate will recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
---
updated-dependencies:
- dependency-name: aiohttp
dependency-version: 3.14.5
dependency-type: direct:production
update-type: version-update:semver-patch
dependency-group: pip
- dependency-name: gidgethub
dependency-version: 6.0.0
dependency-type: direct:production
update-type: version-update:semver-major
dependency-group: pip
- dependency-name: sentry-sdk
dependency-version: 2.73.0
dependency-type: direct:production
update-type: version-update:semver-minor
dependency-group: pip
- dependency-name: coverage
dependency-version: 7.17.0
dependency-type: direct:development
update-type: version-update:semver-minor
dependency-group: pip
- dependency-name: pytest-mock
dependency-version: 3.17.0
dependency-type: direct:development
update-type: version-update:semver-minor
dependency-group: pip
...
Signed-off-by: dependabot[bot] <[email protected]>
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Labels
dependencies
Pull requests that update a dependency file
python
Pull requests that update Python code
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|