Skip to content

chore(deps): update samples-migrations#606

Open
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/samples-migrations
Open

chore(deps): update samples-migrations#606
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/samples-migrations

Conversation

@renovate-bot

@renovate-bot renovate-bot commented May 27, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
langchain-core (changelog) ==1.3.3==1.4.8 age confidence
langchain-google-alloydb-pg (changelog) ==0.14.0==0.15.0 age confidence
langchain-weaviate ==0.0.6==0.0.7 age confidence
pymilvus ==2.6.9==2.6.16 age confidence
pytest (changelog) ==9.0.3==9.1.1 age confidence
pytest-asyncio (changelog) ==1.3.0==1.4.0 age confidence
qdrant-client ==1.17.0==1.18.0 age confidence
weaviate-client ==4.20.3==4.22.0 age confidence

Release Notes

googleapis/langchain-google-alloydb-pg-python (langchain-google-alloydb-pg)

v0.15.0

Compare Source

Features
Bug Fixes
  • Avoid mutable default argument for metadata_columns (#​588) (c270aba)
milvus-io/pymilvus (pymilvus)

v2.6.16: PyMilvus v2.6.16 Release Notes

Compare Source

What's Changed

Features and enhancements
Bug fixes
  • Harden sync and async connection recovery by protecting reconnect channel swaps and validating channel reclamation (sources #​3542, #​3564, and #​3579; 2.6 #​3566, #​3571, and #​3582).
  • Preserve connection timeout settings during recovery (source #​3610; 2.6 #​3614).
  • Map only connection-setup RPC failures to CONNECT_FAILED (source #​3589; 2.6 #​3591).
  • Reject boolean values in sparse vector validation and improve the related error message (source #​3624; 2.6 #​3625).
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 Notes

Compare Source

What's Changed

  • Add get_replicate_info() to MilvusClient and AsyncMilvusClient for reading replication checkpoint state. #​3509 by @​bigsheeper, backported in #​3515.
  • Move Search logical-type handling to the shared type registry. #​3482, backported in #​3498.
  • Add the internal TypeCapability contract for shared type-specific operation bindings. #​3531, backported in #​3532.
  • Use the logical type registry in batch insert and upsert paths. #​3517, backported in #​3540.
  • Migrate development, CI, TestPyPI, and release workflows to uv. #​3512 by @​zhuwenxing, backported in #​3530.
  • Use the package-local Hatchling version source for SCM-derived versions. #​3528 by @​zhuwenxing, backported in #​3535.

Full Changelog: milvus-io/pymilvus@v2.6.14...v2.6.15

v2.6.14: PyMilvus v2.6.14 Release Notes

Compare Source

What's Changed

Full Changelog: milvus-io/pymilvus@v2.6.13...v2.6.14

v2.6.13: PyMilvus v2.6.13 Release Notes

Compare Source

What's Changed

Full Changelog: milvus-io/pymilvus@v2.6.12...v2.6.13

v2.6.12: PyMilvus v2.6.12 Release Notes

Compare 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 Notes

Compare Source

What's Changed

Bug Fixes
Features & Enhancements
Improvements
  • refactor: extract _get_dim helper to deduplicate dimension lookup (#​3344, #​3350)
  • refactor: remove redundant raise ex from ex try/except blocks (#​3341, #​3351)
  • refactor: consolidate duplicate common_pb2 import in prepare.py (#​3346, #​3354)
  • test: improve unit test coverage from 83.98% to 90% (#​3313, #​3320)
  • chore: remove obsolete release_event and nightly_ci workflows (#​3358)

Full Changelog: milvus-io/pymilvus@v2.6.10...v2.6.11

v2.6.10: PyMilvus v2.6.10 Release Notes

Compare Source

What's Changed

New Features
  • feat: add global cluster client support (#​3264)
  • feat: add ConnectionManager to replace connections singleton for MilvusClient (#​3307)
Bug Fixes
  • fix: is_legal_ids() to accept negative int64 primary keys (#​3281)
  • fix: avoid calling len() on scipy sparse matrix in entity_to_field_data (#​3294)
  • fix: retry on REPLICATE_VIOLATION for global cluster region switch (#​3298)
  • fix: support non-float vectors in struct array in search (#​3299)
  • fix: enforce timeout for async operations when server is unreachable (#​3304)
  • fix: add debounce to prevent concurrent topology refresh in global client (#​3309)
Enhancements
  • enhance: general performance improvements across MilvusClient path (#​3280)
  • enhance: remote bulk writer support virtual_style_endpoint (#​3302)
  • enhance: update the milvus-proto commit (#​3310)
Testing & CI
  • enhance: requires 90% patch unit test coverage for new PRs (#​3297)
  • enhance: increase ORM unit test coverage to 90%+ per file (#​3312)

Full Changelog: milvus-io/pymilvus@v2.6.9...v2.6.10

pytest-dev/pytest (pytest)

v9.1.1

Compare Source

pytest 9.1.1 (2026-06-19)

Bug fixes

  • #​14220: Fixed a logic bug in pytest.RaisesGroup which would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.
  • #​14591: Fixed a regression in pytest 9.1.0 which caused overriding a parametrized fixture with an indirect @​pytest.mark.parametrize to fail with "duplicate parametrization of '<fixture name>'".
  • #​14606: Fixed list-item typing errors from mypy in @pytest.mark.parametrize <pytest.mark.parametrize ref> argvalues parameter.
  • #​14608: Fixed a regression in pytest 9.1.0 where conftest.py files 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.0

Compare Source

pytest 9.1.0 (2026-06-13)
Removals and backward incompatible breaking changes
  • #​14533: When using --doctest-modules, autouse fixtures with module, package or session scope 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.py file if possible.

    Technical explanation for those interested:
    When using --doctest-modules, pytest possibly collects Python modules twice, once as pytest.Module and once as a DoctestModule (depending on the configuration).
    Due to improvements in pytest's fixture implementation, if e.g. the DoctestModule collects a fixture, it is now visible to it only, and not to the Module.
    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 @classmethod decorator instead -- by yastcher.

    See 10819 and 14011.

  • #​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-teardown for details.

  • #​13409: Using non-~collections.abc.Collection iterables (such as generators, iterators, or custom iterable objects) for the argvalues parameter in @pytest.mark.parametrize <pytest.mark.parametrize ref> and metafunc.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-iterators for details and suggestions.

  • #​13946: The private config.inicfg attribute is now deprecated.
    Use config.getini() <pytest.Config.getini> to access configuration values instead.

    See config-inicfg for more details.

  • #​14004: Passing baseid to ~pytest.FixtureDef or nodeid strings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.

    Use the node parameter instead for fixture scoping. This enables more robust node-based
    matching instead of string prefix matching.
    If you've used nodeid=None, pass node=session instead.

    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-markers for more details.

  • #​14434: The --pastebin option is now deprecated.
    The same functionality is now available in an external plugin, pytest-pastebin.
    See pastebin-deprecated for more details.

  • #​14513: The private FixtureDef.has_location attribute is now deprecated and will be removed in pytest 10.
    See fixturedef-has-location-deprecated for details.

  • #​1764: pytest.console_main is now deprecated and will be removed in pytest 10.
    It was never intended for programmatic use; use pytest.main instead.

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-warnings command-line option and max_warnings configuration option to fail the test run when the number of warnings exceeds a given threshold -- by miketheman.

  • #​6757: Added the assertion_text_diff_style configuration option, allowing
    string equality failures to be rendered as separate Left: and Right:
    blocks instead of ndiff output.

  • #​8395: Added support for ~datetime.datetime and ~datetime.timedelta comparisons with pytest.approx. An explicit abs or rel tolerance as a ~datetime.timedelta is required and relative tolerance is not supported for datetime comparisons -- by hamza-mobeen.

Improvements in existing functionality
  • #​11225: pytest.warns now shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but the match pattern did not match.

  • #​11295: Improved output of --fixtures-per-test by excluding internal-implementation fixtures generated by @pytest.mark.parametrize and similar.

  • #​13241: pytest.raises, pytest.warns and pytest.deprecated_call now uses ParamSpec for the type hint to the (old and not recommended) callable overload, instead of Any. This allows type checkers to raise errors when passing incorrect function parameters.
    func can 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.raises match parameter.

  • #​14137: pytest.ScopeName is now public to allow using it in function signatures.

  • #​14342: Marked yield_fixture as deprecated to type checkers using the deprecated decorator. Note it
    has 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 the unraisableexception plugin 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 dict instances.

  • #​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, or pytest.main() based on how pytest was invoked, making help and error messages clearer.

  • #​8265: Emit a PytestCollectionWarning when a module-level __getattr__ returns None for pytestmark instead of raising AttributeError.

    Previously this caused a cryptic TypeError: got None instead of Mark error.
    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 -W option values being duplicated in Config.known_args_namespace.

  • #​13626: Fixed function-scoped fixture values being kept alive after a test was interrupted by KeyboardInterrupt or early exit,
    allowing them to potentially be released more promptly.

  • #​13784: Fixed capteesys producing 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.TestCase class running even when the class is decorated with unittest.skip or unittest.skipIf -- regression since pytest 8.1.0.

  • #​13917: unittest.SkipTest is no longer considered an interactive exception, i.e. pytest_exception_interact is no longer called for it.

  • #​13963: Fixed subtests running with pytest-xdist when their contexts contain objects that are not JSON-serializable.

    Fixes pytest-dev/pytest-xdist#1273.

  • #​14004: Fixed conftest.py fixture scoping when testpaths points outside of the rootdir <rootdir>.

    Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
    when using a relative testpaths like ../tests/sdk.

    Conftest fixtures are now parsed during Directory <pytest.Directory> collection, using the Directory node 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.makepyfile and Pytester.maketxtfile methods.

  • #​14114: An exception from pytest_fixture_post_finalizer no 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 underlying setattr() call fails (e.g. on immutable targets), causing an AttributeError crash during teardown.

  • #​14214: Fixed -v hint in pytest.raises match 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 active error filter could be removed before the exception surfaced and a late resource leak would pass silently. A -W error filter, or any filter matching pytest.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 terminalreporter plugin 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 resulting AssertionError.

  • #​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-markers and --strict-config specified through addopts were silently ignored.

    Note that when targeting pytest >= 9.0, it's nicer to use strict_markers and strict_config, or strict mode <strict mode>.

  • #​14456: Fixed pytest.approx not recognizing types with __array_interface__ as numpy-like arrays.

  • #​14474: Fixed a regression where -k and -m expressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise a SyntaxError about 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 *args and/or **kwargs. The method was using co_flags bitmask values (4 and 8) directly as counts instead of converting them to 1 via bool(), and was not accounting for co_kwonlyargcount when var=True.

  • #​3697: Logging capture now works for non-propagating loggers.
    Previously only logs which reached the root logger were captured.
    This includes caplog and the "Captured log calls" test reporting.

  • #​3850: Fixed JUnit XML report: the tests attribute of the <testsuite> element now always matches the number of <testcase> elements in the file. In some cases (test passes but fails during teardown) the tests attribute would report an incorrect number of testcases in the XML file.

  • #​5848: pytest_fixture_post_finalizer is 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
  • #​11022: Document safer alternatives and scope guidance for monkeypatching standard library functions.
  • #​11307: Document that @pytest.hookimpl(specname=...) only works for function names starting with pytest_.
  • #​13038: Document that doctests do not support parametrized fixtures, including parametrized autouse fixtures.
  • #​13155: Clarified how the request fixture provides indirect parametrization values via request.param.
  • #​13304: Clarified in the documentation that hook implementations defined in conftest.py files are not available to other plugins during their pytest_addoption() execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implement pytest_addoption() to add their own command-line options.
  • #​13902: Clarified how subtest progress markers are shown in the documentation.
  • #​14012: The ini options ref section of the API Reference now specified the type and default value of every configuration option.
  • #​14148: Documented a safe pytestconfig.cache access pattern when the
    cacheprovider plugin is disabled.
  • #​14303: The documentation is now built with Sphinx >= 9.
  • #​14465: Updated the hooks how-to page to link the newhooks.py file in pytest-xdist at tag v3.8.0 instead 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
  • #​14582: Improved the recursion traceback test to exercise all requested traceback styles.
pytest-dev/pytest-asyncio (pytest-asyncio)

v1.4.0: pytest-asyncio v1.4.0

Compare Source

1.4.0 - 2026-05-26

Deprecated

  • Overriding the event_loop_policy fixture is deprecated. Use the pytest_asyncio_loop_factories hook instead. (#​1419)

Added

  • Added the pytest_asyncio_loop_factories hook 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.fixture functions now see the correct event loop when custom loop factories are configured, even when test code disrupts the current event loop (e.g., via asyncio.run() or asyncio.set_event_loop(None)). (#​1164)

Changed

  • Improved the readability of the warning message that is displayed when asyncio_default_fixture_loop_scope is unset (#​1298)
  • Only import asyncio.AbstractEventLoopPolicy for type checking to avoid raising
    a DeprecationWarning. (#​1394)
  • Updated minimum supported pytest version to v8.4.0. (#​1397)

Fixed

  • Fixed a ResourceWarning: unclosed event loop warning that could occur when a synchronous test called asyncio.run() or otherwise unset the current event loop after pytest-asyncio had run an async test or fixture. (#​724)

Notes for Downstream Packagers

  • Added dependency on sphinx-tabs >= 3.5 to organize documentation examples into tabs. (#​1395)
qdrant/qdrant-client (qdrant-client)

v1.18.0

Compare Source

Change Log

Features 🌊

Fixes 🧑‍🔧

  • #​1191 - fix local mode inconsistency of values count with the server in case of iterables other than list by @​joein
  • #​1190 - fix local mode geo filter edge cases by @​joein

Deprecations ⏲️

Thanks to everyone who contributed to the current release!
@​jnMetaCode @​Anush008 @​joein

v1.17.1

Compare Source

Change Log

Features 🌊

Fixes 🔧

  • #​1169 - do not modify date filters in local mode by @​jnMetaCode
  • #​1168 - run server version check in a thread to avoid blocking async client b

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners May 27, 2026 17:36
@product-auto-label product-auto-label Bot added the api: alloydb Issues related to the googleapis/langchain-google-alloydb-pg-python API. label May 27, 2026
@product-auto-label product-auto-label Bot added the samples Issues that are directly related to samples. label May 27, 2026
@dpebot

dpebot commented May 27, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 112a392 to 5ad5fbe Compare May 27, 2026 22:59
@dpebot

dpebot commented May 27, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 5ad5fbe to 529a0e0 Compare May 28, 2026 00:50
@dpebot

dpebot commented May 28, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 529a0e0 to fe28804 Compare May 29, 2026 11:00
@dpebot

dpebot commented May 29, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from fe28804 to 225f058 Compare June 8, 2026 16:45
@dpebot

dpebot commented Jun 8, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 225f058 to 2c6be01 Compare June 8, 2026 23:04
@dpebot

dpebot commented Jun 8, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 2c6be01 to 18653ac Compare June 9, 2026 22:19
@dpebot

dpebot commented Jun 9, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 18653ac to e772e86 Compare June 10, 2026 23:28
@dpebot

dpebot commented Jun 10, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from e772e86 to 9b46a2e Compare June 11, 2026 07:01
@dpebot

dpebot commented Jun 11, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 9b46a2e to 64a466e Compare June 11, 2026 11:13
@dpebot

dpebot commented Jun 11, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 64a466e to ef241dd Compare June 12, 2026 20:34
@dpebot

dpebot commented Jun 12, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from ef241dd to 26bcb44 Compare June 13, 2026 22:31
@dpebot

dpebot commented Jun 13, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 26bcb44 to 5ffd83d Compare June 17, 2026 22:42
@dpebot

dpebot commented Jun 17, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 5ffd83d to 04404c6 Compare June 18, 2026 18:32
@dpebot

dpebot commented Jun 18, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 04404c6 to ce2e6cc Compare June 19, 2026 01:42
@dpebot

dpebot commented Jun 19, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from ce2e6cc to 8679a71 Compare June 19, 2026 14:54
@dpebot

dpebot commented Jun 19, 2026

Copy link
Copy Markdown

/gcbrun

@renovate-bot renovate-bot force-pushed the renovate/samples-migrations branch from 8679a71 to 76d3d36 Compare June 25, 2026 02:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: alloydb Issues related to the googleapis/langchain-google-alloydb-pg-python API. samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants