chore(deps): update samples-migrations - #606
Open
renovate-bot wants to merge 1 commit into
Open
Conversation
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
May 27, 2026 22:59
112a392 to
5ad5fbe
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
May 28, 2026 00:50
5ad5fbe to
529a0e0
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
May 29, 2026 11:00
529a0e0 to
fe28804
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 8, 2026 16:45
fe28804 to
225f058
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 8, 2026 23:04
225f058 to
2c6be01
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 9, 2026 22:19
2c6be01 to
18653ac
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 10, 2026 23:28
18653ac to
e772e86
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 11, 2026 07:01
e772e86 to
9b46a2e
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 11, 2026 11:13
9b46a2e to
64a466e
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 12, 2026 20:34
64a466e to
ef241dd
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 13, 2026 22:31
ef241dd to
26bcb44
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
June 17, 2026 22:42
26bcb44 to
5ffd83d
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 8, 2026 20:43
76d3d36 to
94f1a43
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 10, 2026 04:34
94f1a43 to
ff0c81f
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 17, 2026 11:41
ff0c81f to
1bb06b6
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 21, 2026 07:53
1bb06b6 to
8b4350c
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 23, 2026 23:36
8b4350c to
d862cae
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 28, 2026 17:40
d862cae to
eafde2b
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
July 30, 2026 16:50
eafde2b to
96d7b22
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 4, 2026 15:04
96d7b22 to
dc5af15
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 10, 2026 13:15
dc5af15 to
5c9322c
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 10, 2026 19:50
5c9322c to
c9a84c7
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 12, 2026 00:56
c9a84c7 to
cc3e8dd
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 13, 2026 17:46
cc3e8dd to
60afde6
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 16, 2026 11:52
60afde6 to
01f3912
Compare
|
/gcbrun |
renovate-bot
force-pushed
the
renovate/samples-migrations
branch
from
August 20, 2026 05:06
01f3912 to
bb2707b
Compare
|
/gcbrun |
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:
==1.3.3→==1.6.0==0.14.0→==0.15.0==0.3.3→==0.4.0==0.0.6→==0.0.8==2.6.9→==2.6.17==9.0.3→==9.1.1==1.3.0→==1.4.0==1.17.0→==1.19.0==4.20.3→==4.23.0Release Notes
googleapis/langchain-google-alloydb-pg-python (langchain-google-alloydb-pg)
v0.15.0Compare Source
Features
Bug Fixes
milvus-io/pymilvus (pymilvus)
v2.6.17: PyMilvus v2.6.17 Release NotesCompare Source
What's Changed
Protocol and compatibility
milvus-protowith Milvus v2.6.20 and regenerate Python protobuf bindings, including support for the inclusiveDumpMessagesstart option (#3687).Bug fixes
auto_idprimary-key DataFrame column during insert (source #3673; 2.6 #3677).target_sizeincompact()to be a positive integer (source #3642; 2.6 #3643; fixes #3169).Build and release tooling
vcs-versioning<2semantics (source #3633; 2.6 #3635).Full Changelog: milvus-io/pymilvus@v2.6.16...v2.6.17
v2.6.16: PyMilvus v2.6.16 Release NotesCompare Source
What's Changed
Features and enhancements
dump_messagessupport for data salvage (source #3573; 2.6 #3574).Bug fixes
CONNECT_FAILED(source #3589; 2.6 #3591).Type handling and client internals
Documentation and tests
Full Changelog: milvus-io/pymilvus@v2.6.15...v2.6.16
v2.6.15: PyMilvus v2.6.15 Release NotesCompare Source
What's Changed
get_replicate_info()toMilvusClientandAsyncMilvusClientfor reading replication checkpoint state. #3509 by @bigsheeper, backported in #3515.TypeCapabilitycontract for shared type-specific operation bindings. #3531, backported in #3532.uv. #3512 by @zhuwenxing, backported in #3530.Full Changelog: milvus-io/pymilvus@v2.6.14...v2.6.15
v2.6.14: PyMilvus v2.6.14 Release NotesCompare Source
What's Changed
Full Changelog: milvus-io/pymilvus@v2.6.13...v2.6.14
v2.6.13: PyMilvus v2.6.13 Release NotesCompare Source
What's Changed
Full Changelog: milvus-io/pymilvus@v2.6.12...v2.6.13
v2.6.12: PyMilvus v2.6.12 Release NotesCompare Source
What's Changed
Bug Fixes
Improvements
CI
Full Changelog: milvus-io/pymilvus@v2.6.11...v2.6.12
v2.6.11: PyMilvus v2.6.11 Release NotesCompare Source
What's Changed
Bug Fixes
@pymilvus-bot
Features & Enhancements
Improvements
raise ex from extry/except blocks (#3341, #3351)Full Changelog: milvus-io/pymilvus@v2.6.10...v2.6.11
v2.6.10: PyMilvus v2.6.10 Release NotesCompare Source
What's Changed
New Features
Bug Fixes
Enhancements
Testing & CI
Full Changelog: milvus-io/pymilvus@v2.6.9...v2.6.10
pytest-dev/pytest (pytest)
v9.1.1Compare Source
pytest 9.1.1 (2026-06-19)
Bug fixes
pytest.RaisesGroupwhich would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.list-itemtyping errors from mypy in@pytest.mark.parametrize <pytest.mark.parametrize ref>argvaluesparameter.conftest.pyfiles located in<invocation dir>/test*were no longer loaded as initial conftests when invoked without arguments.This could cause certain hooks (like
pytest_addoption) in these files to not fire.v9.1.0Compare Source
pytest 9.1.0 (2026-06-13)
Removals and backward incompatible breaking changes
#14533: When using
--doctest-modules, autouse fixtures withmodule,packageorsessionscope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.If this is undesirable, move the fixture definition to a
conftest.pyfile if possible.Technical explanation for those interested:
When using --doctest-modules, pytest possibly collects Python modules twice, once as
pytest.Moduleand once as aDoctestModule(depending on the configuration).Due to improvements in pytest's fixture implementation, if e.g. the
DoctestModulecollects a fixture, it is now visible to it only, and not to theModule.This means that both need to register the fixtures independently.
Deprecations (removal in next major release)
#10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without
@classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use@classmethoddecorator instead -- byyastcher.See
10819and14011.#12882: Calling
request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.See
dynamic-fixture-request-during-teardownfor details.#13409: Using non-
~collections.abc.Collectioniterables (such as generators, iterators, or custom iterable objects) for theargvaluesparameter in@pytest.mark.parametrize <pytest.mark.parametrize ref>andmetafunc.parametrize <pytest.Metafunc.parametrize>is now deprecated.These iterables get exhausted after the first iteration,
leading to tests getting unexpectedly skipped in cases such as running
pytest.main()multiple times,using class-level parametrize decorators,
or collecting tests multiple times.
See
parametrize-iteratorsfor details and suggestions.#13946: The private
config.inicfgattribute is now deprecated.Use
config.getini() <pytest.Config.getini>to access configuration values instead.See
config-inicfgfor more details.#14004: Passing
baseidto~pytest.FixtureDefornodeidstrings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.Use the
nodeparameter instead for fixture scoping. This enables more robust node-basedmatching instead of string prefix matching.
If you've used
nodeid=None, passnode=sessioninstead.This will be removed in pytest 10.
#14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10.
See
hook-markersfor more details.#14434: The
--pastebinoption is now deprecated.The same functionality is now available in an external plugin,
pytest-pastebin.See
pastebin-deprecatedfor more details.#14513: The private
FixtureDef.has_locationattribute is now deprecated and will be removed in pytest 10.See
fixturedef-has-location-deprecatedfor details.#1764:
pytest.console_mainis now deprecated and will be removed in pytest 10.It was never intended for programmatic use; use
pytest.maininstead.New features
#12376: Added
pytest.register_fixture()to register fixtures using an imperative interface.This is an advanced function intended for use by plugins.
Normally, fixtures should be registered declaratively using the
@pytest.fixture <pytest.fixture>decorator.Pytest looks for these fixture definitions during the collection phase and registers them automatically.
For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.
#14023: Added --report-chars long CLI option.
#14371: Added
--max-warningscommand-line option andmax_warningsconfiguration option to fail the test run when the number of warnings exceeds a given threshold -- bymiketheman.#6757: Added the
assertion_text_diff_styleconfiguration option, allowingstring equality failures to be rendered as separate
Left:andRight:blocks instead of
ndiffoutput.#8395: Added support for
~datetime.datetimeand~datetime.timedeltacomparisons withpytest.approx. An explicitabsorreltolerance as a~datetime.timedeltais required and relative tolerance is not supported for datetime comparisons -- byhamza-mobeen.Improvements in existing functionality
#11225:
pytest.warnsnow shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but thematchpattern did not match.#11295: Improved output of
--fixtures-per-testby excluding internal-implementation fixtures generated by@pytest.mark.parametrizeand similar.#13241:
pytest.raises,pytest.warnsandpytest.deprecated_callnow usesParamSpecfor the type hint to the (old and not recommended) callable overload, instead ofAny. This allows type checkers to raise errors when passing incorrect function parameters.funccan now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.#13862: Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr.
#14026: Added test coverage for compiled regex patterns in
pytest.raisesmatch parameter.#14137: pytest.ScopeName is now public to allow using it in function signatures.
#14342: Marked
yield_fixtureas deprecated to type checkers using thedeprecateddecorator. Note ithas originally been deprecated <yield-fixture-deprecated>in pytest 6.2 already.#14373: Added type annotations for
pytest.approx.#14430: When using
--setup-show, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.#14441: Reduced the default number of
gc.collect()passes in theunraisableexceptionplugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via__del__. This can noticeably speed up test suites that trigger many pytester runs.#14461: Improved assertion failure explanations for equality comparisons between mapping objects that are not
dictinstances.#14513: The order in which fixture definitions overriding each other are resolved is now determined first by their visibility in the collection tree rather than by the order in which they are registered.
A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.
#14524: Add official Python 3.15 support.
#1764: Improved argparse program name to show
pytest,python -m pytest, orpytest.main()based on how pytest was invoked, making help and error messages clearer.#8265: Emit a
PytestCollectionWarningwhen a module-level__getattr__returnsNoneforpytestmarkinstead of raisingAttributeError.Previously this caused a cryptic
TypeError: got None instead of Markerror.Now pytest issues a helpful warning and continues collecting the module normally.
Bug fixes
#13192: Fixed | (pipe) not being treated as a regex meta-character that needs escaping in
pytest.raises(match=...) <pytest.raises>.#13484: Fixed
-Woption values being duplicated inConfig.known_args_namespace.#13626: Fixed function-scoped fixture values being kept alive after a test was interrupted by
KeyboardInterruptor early exit,allowing them to potentially be released more promptly.
#13784: Fixed
capteesysproducing doubled output when used with--capture=no(-s).#13817: Fixed a secondary AttributeError masking the original error when an option argument fails to initialize.
#13884: Fixed rare internal IndexError caused by builtins.compile being overridden in client code.
#13885: Fixed autouse fixtures defined inside a
unittest.TestCaseclass running even when the class is decorated withunittest.skiporunittest.skipIf-- regression since pytest 8.1.0.#13917:
unittest.SkipTestis no longer considered an interactive exception, i.e.pytest_exception_interactis no longer called for it.#13963: Fixed subtests running with
pytest-xdistwhen their contexts contain objects that are not JSON-serializable.Fixes pytest-dev/pytest-xdist#1273.
#14004: Fixed conftest.py fixture scoping when
testpathspoints outside of therootdir <rootdir>.Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
when using a relative
testpathslike../tests/sdk.Conftest fixtures are now parsed during
Directory <pytest.Directory>collection, using theDirectorynode for proper scoping.#14050: Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.
#14080: fix missing type annotations on
Pytester.makepyfileandPytester.maketxtfilemethods.#14114: An exception from
pytest_fixture_post_finalizerno longer prevents fixtures from being torn down, causing additional errors in the following tests.#14161: Fixed
monkeypatch.setattr() <pytest.MonkeyPatch.setattr>leaving a stale entry on the undo stack when the underlyingsetattr()call fails (e.g. on immutable targets), causing anAttributeErrorcrash during teardown.#14214: Fixed
-vhint inpytest.raisesmatch diff not working because assertion verbosity was not propagated.#14234: Allow
pytest.HIDDEN_PARAM <hidden-param>in@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>typing.#14248: Fixed direct parametrization causing the static fixture closure (as reflected in
request.fixturenames <pytest.FixtureRequest.fixturenames>) to omit fixtures that are requested transitively from overridden fixtures.#14263: Unraisable exceptions from finalizers are now collected during
pytest_unconfigure, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an activeerrorfilter could be removed before the exception surfaced and a late resource leak would pass silently. A-W errorfilter, or any filter matchingpytest.PytestUnraisableExceptionWarning, now promotes these exceptions to failures regardless of plugin cleanup order.#14377: Fixed crash in Config.get_terminal_writer when an assertion fails with the
terminalreporterplugin disabled.#14381: Fixed
-V(short form of--version) to properly display the current version.#14389: Improved
pytest.raises(..., match=...) <pytest.raises>failures to suppress the mismatched exception as a cause of the resultingAssertionError.#14392: Fixed a bug in
pytest.raises(match=...) <pytest.raises>"fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.#14442: Fixed a regression in pytest 9.0 where
--strict-markersand--strict-configspecified throughaddoptswere silently ignored.Note that when targeting pytest >= 9.0, it's nicer to use
strict_markersandstrict_config, orstrict mode <strict mode>.#14456: Fixed
pytest.approxnot recognizing types with__array_interface__as numpy-like arrays.#14474: Fixed a regression where
-kand-mexpressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise aSyntaxErrorabout escaping.#14483: Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by
EternalRights#14492: Fixed
Code.getargs()incorrectly including local variable names in the returned argument tuple for functions with*argsand/or**kwargs. The method was usingco_flagsbitmask values (4and8) directly as counts instead of converting them to1viabool(), and was not accounting forco_kwonlyargcountwhenvar=True.#3697: Logging capture now works for non-propagating loggers.
Previously only logs which reached the root logger were captured.
This includes
caplogand the "Captured log calls" test reporting.#3850: Fixed JUnit XML report: the
testsattribute of the<testsuite>element now always matches the number of<testcase>elements in the file. In some cases (test passes but fails during teardown) thetestsattribute would report an incorrect number of testcases in the XML file.#5848:
pytest_fixture_post_finalizeris no longer called extra times for the same fixture teardown in some cases.#719: Fixed
@pytest.mark.parametrize <pytest.mark.parametrize ref>not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g.,"arg,").The trailing comma form now correctly behaves like the tuple form
("arg",), treating argvalues as a list of tuples to unpack.Improved documentation
@pytest.hookimpl(specname=...)only works for function names starting withpytest_.requestfixture provides indirect parametrization values viarequest.param.conftest.pyfiles are not available to other plugins during theirpytest_addoption()execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implementpytest_addoption()to add their own command-line options.ini options refsection of the API Reference now specified the type and default value of every configuration option.pytestconfig.cacheaccess pattern when thecacheproviderplugin is disabled.newhooks.pyfile inpytest-xdistat tagv3.8.0instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.Miscellaneous internal changes
pytest-dev/pytest-asyncio (pytest-asyncio)
v1.4.0: pytest-asyncio v1.4.0Compare Source
1.4.0 - 2026-05-26
Deprecated
pytest_asyncio_loop_factorieshook instead. (#1419)Added
Added the
pytest_asyncio_loop_factorieshook to parametrize asyncio tests with custom event loop factories.The hook returns a mapping of factory names to loop factories, and
pytest.mark.asyncio(loop_factories=[...])selects a subset of configured factories per test. When a single factory is configured, test names are unchanged.Synchronous
@pytest_asyncio.fixturefunctions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., viaasyncio.run()orasyncio.set_event_loop(None)). (#1164)Changed
asyncio_default_fixture_loop_scopeis unset (#1298)asyncio.AbstractEventLoopPolicyfor type checking to avoid raisinga DeprecationWarning. (#1394)
Configuration
📅 Schedule: (UTC)
🚦 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.