Repository navigation
chore(deps): update python packages - #217
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
Contributor
Author
|
Contributor
renovate
Bot
force-pushed
the
users/renovate/python
branch
6 times, most recently
from
September 3, 2026 23:59
e9d0562 to
f65d963
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
5 times, most recently
from
September 11, 2026 13:53
b093591 to
2f85780
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
6 times, most recently
from
September 20, 2026 13:41
b313a15 to
6eb7e8d
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
2 times, most recently
from
September 30, 2026 00:27
014d6b2 to
a8ceb40
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
7 times, most recently
from
October 7, 2026 01:28
cebd681 to
6e513e3
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
15 times, most recently
from
October 25, 2026 22:09
694d993 to
ca359e7
Compare
renovate
Bot
force-pushed
the
users/renovate/python
branch
14 times, most recently
from
October 30, 2026 01:08
b0e3446 to
9281f03
Compare
This branch has not been deployed
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
1.8.21→1.8.221.83.0→1.84.02.3.0→2.4.01.1.0→1.2.01.2.0→1.3.00.5.1→0.5.21.5.0→1.6.02.5.1→2.5.47.35.1→7.36.21.1.411→1.1.4143.15.1→3.17.03.8.0→3.8.11.60.0→1.66.01.83.0.20260730→1.84.0.202610217.34.1.20260518→7.35.1.20260906Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
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
grpc/grpc (grpcio)
v1.84.0Compare Source
This is release 1.84.0 (gimbal) of gRPC Core.
For gRPC documentation, see grpc.io. For previous releases, see Releases.
This release contains refinements, improvements, and bug fixes, with highlights listed below.
Core
C#
Python
UsageErrorexception from registered method. (#43086)Ruby
v1.83.2Compare Source
This is release 1.83.2 (garden) of gRPC Core.
For gRPC documentation, see grpc.io. For previous releases, see Releases.
This release contains refinements, improvements, and bug fixes, with highlights listed below.
Core
C#
Python
cygrpcshared object. (#42325)v1.83.1Compare Source
This is release gRPC Core 1.83.1 (garden).
For gRPC documentation, see grpc.io. For previous releases, see Releases.
This release contains refinements, improvements, and bug fixes.
python/mypy (mypy)
v2.4.0Compare Source
v2.3.1Compare Source
default_factoryfor inherited dataclass (Daniël van Noord, PR 21785)ni/python-styleguide (ni-python-styleguide)
v0.5.2Compare Source
Changed
ni/nidaqmx-python (nidaqmx)
v1.6.0Compare Source
Merged Pull Requests
Resolved Issues
Major Changes
Known Issues
numpy/numpy (numpy)
v2.5.4: (Oct 10, 2026)Compare Source
NumPy 2.5.4 Release Notes
Released on 2026-10-10.
NumPy 2.5.4 is a patch release that fixes bugs discovered after the 2.5.3
release. Highlights are:
This release supports Python versions 3.12-3.15.
Improvements
numpy.linalg.svdandnumpy.linalg.lstsqnow raise for inputs containinginfinities instead of returning garbage results.
Fixed hangs in
numpy.linalg.svdandnumpy.linalg.lstsqfor certain inputscontaining infinities for recent versions of some LAPACK implementations.
numpy.linalg.condnow handles non-finite inputs more consistently.(gh-32593)
StringDType hashing with NaN sentinels
StringDTypeinstances with equivalent floating-point NaN sentinels nowhave equal hashes. Previously, distinct NaN objects could produce equal
dtype instances with different hashes, causing dictionary lookups and set
deduplication to fail.
(gh-32563)
Changes
MaskedArrayresets a fill_value that cannot be represented in a new dtypeA fill_value copied from a source array is now reset to the default fill_value
for the new dtype when it cannot be represented in that dtype. Previously the
copied value could be stale: ufuncs that change dtype left the result holding a
fill_value typed for the old dtype, which raised a
TypeErroronly whensomething later validated it (such as
.view()), and a floating pointfill_value that overflows an integer dtype was kept as an out-of-range value
together with a
RuntimeWarning. Both now fall back to the default,including when a masked array is passed to
MaskedArraywith a differentdtype. A fill_value given explicitly by the user is still validated andraises as before. This can now raise a
ComplexWarningif the fill_value iscomplex and the new dtype is real.
(gh-32508)
(gh-32562)
Contributors
A total of 9 people contributed to this release. People with a "+" by their
names contributed a patch for the first time.
Pull requests merged
A total of 17 pull requests were merged for this release.
v2.5.3: (Sep 6, 2026)Compare Source
NumPy 2.5.3 Release Notes
The NumPy 2.5.3 is a patch release that fixes bugs discovered after the 2.5.2
release. Apart from the usual bug and maintenance work, there are a number of
StringDType related fixes for problems discovered during the ongoing string
work in the main branch.
This release supports Python versions 3.12-3.15
Changes
Casting a fixed-width byte string array (
np.bytes_) toStringDTypenow raises
TypeErrorwhen the bytes are not valid UTF-8. Previously theinvalid bytes were stored as-is and later caused undefined behavior in
string operations.
(gh-32296)
MaskedArray._fill_valuewould become stale when ufuncs that change dtypeleft the result holding a fill_value typed for the old dtype. The mismatch
was silent until something later called
_check_fill_value, such as.view(), and then aTypeErrorwould be raised. Now, when the copiedfill_value is no longer valid for the new dtype, fall back to the
default fill_value for that dtype instead of propagating the stale value.
This may raise a
ComplexWarningif the fill_value is complex and thenew dtype is real.
(gh-32423)
Contributors
A total of 9 people contributed to this release. People with a "+" by their
names contributed a patch for the first time.
Pull requests merged
A total of 27 pull requests were merged for this release.
np.random.{get,set}_bit_generatorimplicit re-exports...PyObject_functions instead of rawPyArray_ ones(#32331)v2.5.2: (Aug 9, 2026)Compare Source
NumPy 2.5.2 Release Notes
The NumPy 2.5.2 is a patch release that fixes bugs discovered after the 2.5.1
release. The big news is that it includes wheels for the newly released
Python 3.15.0rc1.
This release supports Python versions 3.12-3.15
C API changes
PyArray_StringDTypeObjectis opaque under the abi3t stable ABIThe
PyArray_StringDTypeObjectwas accidentally exposed in NumPy2.5 when targeting the free-threading-compatible stable ABI
(
Py_TARGET_ABI3T).PyArray_StringDTypeObjectis now an opaquestruct: extensions compiled that way cannot access its fields, since
the struct layout depends on the size of the object header. Any code
that accessed
PyArray_StringDTypeObjectfields in an abi3t buildwould have crashed, so we are making this API change in a bugfix
release.
The
NpyStringallocator API remains usable by passing thedescriptor object pointer, e.g.
NpyString_acquire_allocator((PyArray_StringDTypeObject *)descr).(gh-31771)
Contributors
A total of 16 people contributed to this release. People with a "+" by their
names contributed a patch for the first time.
Pull requests merged
A total of 28 pull requests were merged for this release.
StringDTypecoerce flag in binary ufunc promotion...5adb334→fa944ef) (#31908)np.fromitercorruption when reusing aStringDType...simd_sequence_from_iterable(#32038)iscloseshape-typing fix for 2d array-likes (#32205)RobertCraigie/pyright-python (pyright)
v1.1.414Compare Source
v1.1.413Compare Source
v1.1.412Compare Source
pytest-dev/pytest-mock (pytest-mock)
v3.17.0Compare Source
2026-10-17
#​641 <https://github.com/pytest-dev/pytest-mock/pull/641>_: Failures of mock assertions such asassert_called_withare again reported only once, instead of two or three times with the original error from themockmodule chained before them.#​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, theirawaitcounterparts, andassert_called_once_with/assert_awaited_once_withwhen 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 emptyArgs:/Kwargs:sections when assertion rewriting is not available.#​643 <https://github.com/pytest-dev/pytest-mock/pull/643>_:assert_has_callsandassert_has_awaitsfailures 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.1Compare Source
2026-10-17
#​617 <https://github.com/pytest-dev/pytest-mock/pull/617>_: Fixedassert_has_callsraisingValueErrorinstead ofAssertionError(or showing misleading introspection) when the expected calls are plain tuples rather thancall(...)objects, such as(args, kwargs)entries of another mock'scall_args_list,(args,),(kwargs,),(name, args)or(name, kwargs).#​621 <https://github.com/pytest-dev/pytest-mock/pull/621>_: Fixedmocker.stop()sometimes stopping the wrong mock, for example with mocks frommocker.create_autospec.#​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/pull/623>_: Fixed misleading introspection inassert_has_awaitsfailures, andassert_has_calls/assert_has_awaitsraisingIndexErrorinstead ofAssertionErrorwhencallsis passed by keyword.#​624 <https://github.com/pytest-dev/pytest-mock/pull/624>_: Clearspy_return_iterafter a spied synchronous or asynchronous function raises, matchingspy_return.#​627 <https://github.com/pytest-dev/pytest-mock/pull/627>_: Documentasync_stubawait assertions and the distinction between call and await tracking.#​629 <https://github.com/pytest-dev/pytest-mock/pull/629>_: Fixedmocker.resetall()skipping the mocks patched withmocker.patch.multiple(), both the ones it creates and the ones passed explicitly.#​630 <https://github.com/pytest-dev/pytest-mock/pull/630>_:mocker.resetall()now also resetsspy_returnandspy_exceptionof spies, like it already did forspy_return_listandspy_return_iter, and no longer overwrites attributes with these names on mocks that are not spies.#​633 <https://github.com/pytest-dev/pytest-mock/pull/633>_: Fixed spies onclassmethod,staticmethod, builtins and classes returning aMagicMockinstead of calling the spied code aftermocker.resetall(side_effect=True). Resetting a spy'sside_effectnow goes back to calling the spied code, also clearing anyside_effectset on the spy.v3.16.0Compare Source
2026-09-27
#​604 <https://github.com/pytest-dev/pytest-mock/pull/604>_: Fixedduplicate_iterators=Truefor async functions spied withmocker.spy.#​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/pull/606>_:mocker.resetall(return_value=True, side_effect=True)now also applies to non-callable mocks, such as those returned bymocker.create_autospec(SomeClass, instance=True). Previously both arguments were silently ignored for them.#​547 <https://github.com/pytest-dev/pytest-mock/issues/547>_: AddedSpyTypefor annotatingmocker.spyresults.#​147 <https://github.com/pytest-dev/pytest-mock/issues/147>_: Removed handling ofRuntimeError: stop called on unstarted patcher, which can no longer occur in the supported Python versions.readthedocs/sphinx-autoapi (sphinx-autoapi)
v3.8.1Compare Source
Bugfixes
^^^^^^^^
Improved Documentation
^^^^^^^^^^^^^^^^^^^^^^
autoapisummarydirective. (#377)Misc
^^^^
streamlit/streamlit (streamlit)
v1.66.0Compare Source
What's Changed
New Features 🎉
on_change="ignore"mode to st.color_picker by @lukasmasuch in #17209on_change="ignore"mode to st.camera_input by @lukasmasuch in #17246on_change="ignore"mode to st.feedback by @lukasmasuch in #17281on_change="ignore"mode to st.pills by @lukasmasuch in #17307on_change="ignore"mode to st.audio_input by @lukasmasuch in #17328on_change="ignore"mode to st.data_editor by @lukasmasuch in #17347on_change="ignore"mode to st.pagination by @lukasmasuch in #17397on_change="ignore"to st.segmented_control by @lukasmasuch in #17452Bug Fixes 🐛
Other Changes
Configuration
📅 Schedule: (in timezone US/Central)
* * * * 0)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.