Skip to content

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 22, 2025

Bumps the gha group with 11 updates in the /packages/opentelemetry-instrumentation-llamaindex directory:

Package From To
flake8 7.0.0 7.3.0
vcrpy 6.0.2 7.0.0
pytest-recording 0.13.2 0.13.4
pytest-asyncio 0.23.8 1.1.0
chromadb 0.5.23 1.0.20
openai 1.99.9 1.101.0
llama-index-postprocessor-cohere-rerank 0.3.0 0.4.0
sqlalchemy 2.0.36 2.0.43
llama-index-llms-cohere 0.4.1 0.5.0
onnxruntime 1.19.2 1.20.1
llama-parse 0.5.20 0.6.62

Updates flake8 from 7.0.0 to 7.3.0

Commits

Updates vcrpy from 6.0.2 to 7.0.0

Release notes

Sourced from vcrpy's releases.

v7.0.0

What's Changed

- Drop support for python 3.8 (major version bump) - thanks @jairhenrique
- Various linting and test fixes - thanks @jairhenrique
- Bugfix for urllib2>=2.3.0 - missing version_string ([#888](https://github.com/kevin1024/vcrpy/issues/888))
- Bugfix for asyncio.run - thanks @alekeik1

New Contributors

Changelog

Sourced from vcrpy's changelog.

Changelog

For a full list of triaged issues, bugs and PRs and what release they are targeted for please see the following link.

ROADMAP MILESTONES <https://github.com/kevin1024/vcrpy/milestones>_

All help in providing PRs to close out bug issues is appreciated. Even if that is providing a repo that fully replicates issues. We have very generous contributors that have added these to bug issues which meant another contributor picked up the bug and closed it out.

  • 7.0.0

  • 6.0.2

  • 6.0.1

    • Bugfix with to Tornado cassette generator (thanks @​graingert)
  • 6.0.0

    • BREAKING: Fix issue with httpx support (thanks @​parkerhancock) in #784. NOTE: You may have to recreate some of your cassettes produced in previous releases due to the binary format being saved incorrectly in previous releases
    • BREAKING: Drop support for boto (vcrpy still supports boto3, but is dropping the deprecated boto support in this release. (thanks @​jairhenrique)
    • Fix compatibility issue with Python 3.12 (thanks @​hartwork)
    • Drop simplejson (fixes some compatibility issues) (thanks @​jairhenrique)
    • Run CI on Python 3.12 and PyPy 3.9-3.10 (thanks @​mgorny)
    • Various linting and docs improvements (thanks @​jairhenrique)
    • Tornado fixes (thanks @​graingert)
  • 5.1.0

  • 5.0.0

    • BREAKING CHANGE: Drop support for Python 3.7. 3.7 is EOL as of 6/27/23 Thanks @​jairhenrique
    • BREAKING CHANGE: Custom Cassette persisters no longer catch ValueError. If you have implemented a custom persister (has anyone implemented a custom persister? Let us know!) then you will need to throw a CassetteNotFoundError when unable to find a cassette. See #681 for discussion and reason for this change. Thanks @​amosjyng for the PR and the review from @​hartwork
  • 4.4.0

    • HUGE thanks to @​hartwork for all the work done on this release!
    • Bring vcr/unittest in to vcrpy as a full feature of vcr instead of a separate library. Big thanks to @​hartwork for doing this and to @​agriffis for originally creating the library
    • Make decompression robust towards already decompressed input (thanks @​hartwork)

... (truncated)

Commits
  • 3278619 Release v7.0.0
  • 3fb62e0 fix: correctly handle asyncio.run when loop exists
  • 8197865 build(deps): update sphinx requirement from <8 to <9
  • be651bd pre-commit: Autoupdate
  • a6698ed Fix aiohttp tests
  • 48d0a2e Fixed missing version_string attribute when used with urllib3>=2.3.0
  • 5b858b1 Fix lint
  • c8d99a9 Fix ruff configuration
  • ce27c63 Merge pull request #736 from kevin1024/drop-python38
  • ab8944d Drop python 3.8 support
  • Additional commits viewable in compare view

Updates pytest-recording from 0.13.2 to 0.13.4

Release notes

Sourced from pytest-recording's releases.

Release 0.13.4

Fixed

  • AttributeError on Windows. #174

Release 0.13.3

Fixed

  • Limit generated cassette names to prevent OSError. #172
Changelog

Sourced from pytest-recording's changelog.

0.13.4_ - 2025-04-24

  • AttributeError on Windows. [#174](https://github.com/kiwicom/pytest-recording/issues/174)_

0.13.3_ - 2025-04-24

  • Limit generated cassette names to prevent OSError. [#172](https://github.com/kiwicom/pytest-recording/issues/172)_
Commits
  • c2d2db7 chore: Release 0.13.4
  • cf919c9 test: Run tests on Windows
  • b8b45b7 fix: Use fallback for max filename length on Windows
  • 8a7e19f docs: Update README.rst
  • 3ad7910 chore: Release 0.13.3
  • 9a6e12c docs: Add a note for package maintainers
  • a70532b chore: Revert "test: Disable pretty plugin in pytest"
  • 6b84832 chore(deps): update codecov/codecov-action action to v5.4.2
  • 460a7f9 test: Add long_cassette_name test
  • 9822a50 fix: Check default_cassette to prevent it from being too long.
  • Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.8 to 1.1.0

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 1.1.0

Added

  • Propagation of ContextVars from async fixtures to other fixtures and tests on Python 3.10 and older (#127)
  • Cancellation of tasks when the loop_scope ends (#200)
  • Warning when the current event loop is closed by a test

Fixed

  • Error about missing loop when calling functions requiring a loop in the finally clause of a task (#878)
  • An error that could cause duplicate warnings to be issued

Notes for Downstream Packagers

pytest-asyncio 1.1.0a1

1.1.0a1 - 2025-06-30

Added

  • Propagation of ContextVars from async fixtures to other fixtures and tests on Python 3.10 and older (#127)
  • Cancellation of tasks when the loop_scope ends (#200)
  • Warning when the current event loop is closed by a test

Fixed

  • Error about missing loop when calling functions requiring a loop in the finally clause of a task (#878)
  • An error that could cause duplicate warnings to be issued

Notes for Downstream Packagers

pytest-asyncio 1.0.0

1.0.0 - 2025-05-26

Removed

  • The deprecated event_loop fixture. (#1106)

Added

  • Prelimiary support for Python 3.14 (#1025)

Changed

... (truncated)

Commits
  • ce06c07 chore: Prepare release of v1.1.0.
  • d9a8dcc ci: Workaround missing Tag annotation during release.
  • d66e12f [pre-commit.ci] pre-commit autoupdate
  • 9e5e25f Build(deps): Bump certifi in /dependencies/docs
  • 0e63423 Build(deps): Bump hypothesis in /dependencies/default
  • bd4551c Build(deps): Bump ncipollo/release-action from 1.16.0 to 1.18.0
  • 8e20305 Build(deps): Bump hypothesis in /dependencies/default
  • b7a8ab5 Build(deps): Bump coverage from 7.9.1 to 7.9.2 in /dependencies/default
  • 8cc378d Build(deps): Bump typing-extensions in /dependencies/default
  • fb6bfbf [pre-commit.ci] pre-commit autoupdate
  • Additional commits viewable in compare view

Updates chromadb from 0.5.23 to 1.0.20

Release notes

Sourced from chromadb's releases.

1.0.20

Version: 1.0.20 Git ref: refs/tags/1.0.20 Build Date: 2025-08-18T17:04 PIP Package: chroma-1.0.20.tar.gz Github Container Registry Image: :1.0.20 DockerHub Image: :1.0.20

What's Changed

Full Changelog: chroma-core/chroma@1.0.19...1.0.20

1.0.18

Version: 1.0.18 Git ref: refs/tags/1.0.18 Build Date: 2025-08-18T08:09 PIP Package: chroma-1.0.18.tar.gz Github Container Registry Image: :1.0.18 DockerHub Image: :1.0.18

What's Changed

... (truncated)

Commits

Updates openai from 1.99.9 to 1.101.0

Release notes

Sourced from openai's releases.

v1.101.0

1.101.0 (2025-08-21)

Full Changelog: v1.100.3...v1.101.0

Features

  • api: Add connectors support for MCP tool (a47f962)
  • api: adding support for /v1/conversations to the API (e30bcbc)

Chores

v1.100.3

1.100.3 (2025-08-20)

Full Changelog: v1.100.2...v1.100.3

Chores

  • internal/ci: setup breaking change detection (ca2f936)

v1.100.2

1.100.2 (2025-08-19)

Full Changelog: v1.100.1...v1.100.2

Chores

  • api: accurately represent shape for verbosity on Chat Completions (c39d5fd)

v1.100.1

1.100.1 (2025-08-18)

Full Changelog: v1.100.0...v1.100.1

Bug Fixes

  • types: revert response text config deletion (ac4fb19)

v1.100.0

1.100.0 (2025-08-18)

Full Changelog: v1.99.9...v1.100.0

Features

  • api: add new text parameters, expiration options (e3dfa7c)
Changelog

Sourced from openai's changelog.

1.101.0 (2025-08-21)

Full Changelog: v1.100.3...v1.101.0

Features

  • api: Add connectors support for MCP tool (a47f962)
  • api: adding support for /v1/conversations to the API (e30bcbc)

Chores

1.100.3 (2025-08-20)

Full Changelog: v1.100.2...v1.100.3

Chores

  • internal/ci: setup breaking change detection (ca2f936)

1.100.2 (2025-08-19)

Full Changelog: v1.100.1...v1.100.2

Chores

  • api: accurately represent shape for verbosity on Chat Completions (c39d5fd)

1.100.1 (2025-08-18)

Full Changelog: v1.100.0...v1.100.1

Bug Fixes

  • types: revert response text config deletion (ac4fb19)

1.100.0 (2025-08-18)

Full Changelog: v1.99.9...v1.100.0

Features

  • api: add new text parameters, expiration options (e3dfa7c)
Commits
  • 4e28a42 release: 1.101.0 (#2577)
  • e328fb4 release: 1.100.3
  • 72e0ad6 chore(internal/ci): setup breaking change detection
  • 4ada66f release: 1.100.2
  • a94bd5b chore(api): accurately represent shape for verbosity on Chat Completions
  • f889071 release: 1.100.1
  • b3547d6 fix(types): revert response text config deletion
  • adb1af8 release: 1.100.0
  • 0843a11 feat(api): add new text parameters, expiration options
  • See full diff in compare view

Updates llama-index-postprocessor-cohere-rerank from 0.3.0 to 0.4.0

Updates sqlalchemy from 2.0.36 to 2.0.43

Release notes

Sourced from sqlalchemy's releases.

2.0.43

Released: August 11, 2025

orm

  • [orm] [bug] Fixed issue where using the post_update feature would apply incorrect "pre-fetched" values to the ORM objects after a multi-row UPDATE process completed. These "pre-fetched" values would come from any column that had an Column.onupdate callable or a version id generator used by orm.Mapper.version_id_generator; for a version id generator that delivered random identifiers like timestamps or UUIDs, this incorrect data would lead to a DELETE statement against those same rows to fail in the next step.

    References: #12748

  • [orm] [bug] Fixed issue where _orm.mapped_column.use_existing_column parameter in _orm.mapped_column() would not work when the _orm.mapped_column() is used inside of an Annotated type alias in polymorphic inheritance scenarios. The parameter is now properly recognized and processed during declarative mapping configuration.

    References: #12787

  • [orm] [bug] Improved the implementation of the _orm.selectin_polymorphic() inheritance loader strategy to properly render the IN expressions using chunks of 500 records each, in the same manner as that of the _orm.selectinload() relationship loader strategy. Previously, the IN expression would be arbitrarily large, leading to failures on databases that have limits on the size of IN expressions including Oracle Database.

    References: #12790

engine

  • [engine] [usecase] Added new parameter create_engine.skip_autocommit_rollback which provides for a per-dialect feature of preventing the DBAPI .rollback() from being called under any circumstances, if the connection is detected as being in "autocommit" mode. This improves upon a critical performance issue identified in MySQL dialects where the network overhead of the .rollback() call remains prohibitive even if autocommit mode is set.

    References: #12784

postgresql

... (truncated)

Commits

Updates llama-index-llms-cohere from 0.4.1 to 0.5.0

Updates onnxruntime from 1.19.2 to 1.20.1

Release notes

Sourced from onnxruntime's releases.

ONNX Runtime v1.20.1

What's new?

Python Quantization Tool

CPU EP

QNN EP

TensorRT EP

Packaging

Contributions

Big thank you to the release manager @​yf711, along with @​adrianlizarraga, @​HectorSVC, @​jywu-msft, and everyone else who helped to make this patch release process a smooth one!

ONNX Runtime v1.20.0

Release Manager: @​apsonawane

Announcements

  • All ONNX Runtime Training packages have been deprecated. ORT 1.19.2 was the last release for which onnxruntime-training (PyPI), onnxruntime-training-cpu (PyPI), Microsoft.ML.OnnxRuntime.Training (Nuget), onnxruntime-training-c (CocoaPods), onnxruntime-training-objc (CocoaPods), and onnxruntime-training-android (Maven Central) were published.
  • ONNX Runtime packages will stop supporting Python 3.8 and Python 3.9. This decision aligns with NumPy Python version support. To continue using ORT with Python 3.8 and Python 3.9, you can use ORT 1.19.2 and earlier.
  • ONNX Runtime 1.20 CUDA packages will include new dependencies that were not required in 1.19 packages. The following dependencies are new: libcudnn_adv.so.9, libcudnn_cnn.so.9, libcudnn_engines_precompiled.so.9, libcudnn_engines_runtime_compiled.so.9, libcudnn_graph.so.9, libcudnn_heuristic.so.9, libcudnn_ops.so.9, libnvrtc.so.12, and libz.so.1.

Build System & Packages

  • Python 3.13 support is included in PyPI packages.
  • ONNX 1.17 support will be delayed until a future release, but the ONNX version used by ONNX Runtime has been patched to include a shape inference change to the Einsum op.
  • DLLs in the Maven build are now digitally signed (fix for issue reported here).
  • (Experimental) vcpkg support added for the CPU EP. The DML EP does not yet support vcpkg, and other EPs have not been tested.

Core

  • MultiLoRA support.
  • Reduced memory utilization.
    • Fixed alignment that was causing mmap to fail for external weights.
    • Eliminated double allocations when deserializing external weights.
    • Added ability to serialize pre-packed weights so that they don’t cause an increase in memory utilization when the model is loaded.
  • Support bfloat16 and float8 data types in python I/O binding API.

Performance

  • INT4 quantized embedding support on CPU and CUDA EPs.

... (truncated)

Commits

Updates llama-parse from 0.5.20 to 0.6.62

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @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

Important

Update multiple dependencies in pyproject.toml for opentelemetry-instrumentation-llamaindex to newer versions.

  • Dependencies Updated:
    • flake8 updated to 7.3.0.
    • vcrpy updated to >=6.0.1,<8.0.0.
    • pytest-asyncio updated to >=0.23.7,<1.2.0.
    • chromadb updated to >=0.5.23,<1.1.0.
    • llama-index-postprocessor-cohere-rerank updated to >=0.3,<0.5.
    • llama-index-llms-cohere updated to >=0.4,<0.6.
    • onnxruntime updated to <1.21.0.
    • llama-parse updated to >=0.5.20,<0.7.0.

This description was created by Ellipsis for 7db7be0. You can customize this summary. It will automatically update as commits are pushed.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 22, 2025
Copy link

coderabbitai bot commented Aug 22, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Important

Looks good to me! 👍

Reviewed everything up to 7db7be0 in 1 minute and 47 seconds. Click for details.
  • Reviewed 41 lines of code in 1 files
  • Skipped 1 files when reviewing.
  • Skipped posting 8 draft comments. View those below.
  • Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:35
  • Draft comment:
    flake8 bumped from 7.0.0 to 7.3.0. Consider pinning a narrow range (e.g. >=7.3.0,<7.4.0) for patch updates if that’s preferred.
  • Reason this comment was not posted:
    Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% This is a dependency version suggestion. According to the rules, we should not comment on dependency changes or library versions. While the suggestion to use ranges is technically valid and matches the style used elsewhere in the file, the rules explicitly state not to comment on dependency-related matters. The author likely has a reason for choosing an exact pin vs a range. The comment does point out an inconsistency in versioning style compared to other dependencies in the file. Maybe this consistency is important for the project. Even if consistency is valuable, the rules are clear that we should not comment on dependency versions or assume we know better than the author about version constraints. The comment should be deleted as it violates the rule about not commenting on dependency changes and version numbers.
2. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:38
  • Draft comment:
    vcrpy version updated from '^6.0.1' to '>=6.0.1,<8.0.0', which locks out major releases while allowing minor/patch updates.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative about the version change of a dependency. It doesn't provide any actionable feedback or suggestions for the PR author.
3. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:40
  • Draft comment:
    pytest-asyncio now uses a range (>=0.23.7,<1.2.0), ensuring support up to v1.1.x. Verify the lower bound meets all required features.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is about a dependency version range, which is not something I should comment on according to the rules. It asks to verify the lower bound, which is similar to asking the author to ensure compatibility, which is not allowed.
4. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:41
  • Draft comment:
    chromadb version constraint updated to '>=0.5.23,<1.1.0', which allows current v1.0.x updates while preventing unwanted major upgrades.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining the version constraint update for a dependency. It does not provide a suggestion, ask for confirmation, or highlight a potential issue. It violates the rule against making purely informative comments.
5. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:45
  • Draft comment:
    llama-index-postprocessor-cohere-rerank updated to '>=0.3,<0.5', which accommodates 0.3.x and 0.4.x releases as intended.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, providing details about a dependency version update. It does not suggest any action or raise any concerns about the change.
6. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:52
  • Draft comment:
    llama-index-llms-cohere version constraint revised to '>=0.4,<0.6' to support the new 0.5.0 release, while guarding against major changes.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, providing details about a version constraint change. It does not suggest any action or raise any concerns about the change. According to the rules, purely informative comments should be removed.
7. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:55
  • Draft comment:
    onnxruntime upper bound increased to '<1.21.0' to include 1.20.x patches; this update appears correct.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it states that the update appears correct without providing any actionable feedback or suggestions. It does not ask for confirmation or suggest any changes.
8. packages/opentelemetry-instrumentation-llamaindex/pyproject.toml:56
  • Draft comment:
    llama-parse now uses a range '>=0.5.20,<0.7.0', covering updates up to version 0.6.x. This seems aligned with recent changes.
  • Reason this comment was not posted:
    Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, as it simply states the range of versions for a dependency and notes that it seems aligned with recent changes. It does not provide a suggestion, ask for confirmation of intent, or point out a potential issue.

Workflow ID: wflow_LDgPXzmqRhGNjIdT

You can customize Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@dependabot dependabot bot force-pushed the dependabot/pip/packages/opentelemetry-instrumentation-llamaindex/gha-eb9b5e477f branch 5 times, most recently from a28e0d1 to e29972b Compare August 29, 2025 18:42
@dependabot dependabot bot force-pushed the dependabot/pip/packages/opentelemetry-instrumentation-llamaindex/gha-eb9b5e477f branch 3 times, most recently from 729fd0f to 80055d5 Compare September 14, 2025 12:16
@dependabot dependabot bot force-pushed the dependabot/pip/packages/opentelemetry-instrumentation-llamaindex/gha-eb9b5e477f branch from 80055d5 to 607aa37 Compare September 17, 2025 08:14
Bumps the gha group with 11 updates in the /packages/opentelemetry-instrumentation-llamaindex directory:

| Package | From | To |
| --- | --- | --- |
| [flake8](https://github.com/pycqa/flake8) | `7.0.0` | `7.3.0` |
| [vcrpy](https://github.com/kevin1024/vcrpy) | `6.0.2` | `7.0.0` |
| [pytest-recording](https://github.com/kiwicom/pytest-recording) | `0.13.2` | `0.13.4` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `0.23.8` | `1.1.0` |
| [chromadb](https://github.com/chroma-core/chroma) | `0.5.23` | `1.0.20` |
| [openai](https://github.com/openai/openai-python) | `1.99.9` | `1.101.0` |
| llama-index-postprocessor-cohere-rerank | `0.3.0` | `0.4.0` |
| [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) | `2.0.36` | `2.0.43` |
| llama-index-llms-cohere | `0.4.1` | `0.5.0` |
| [onnxruntime](https://github.com/microsoft/onnxruntime) | `1.19.2` | `1.20.1` |
| llama-parse | `0.5.20` | `0.6.62` |



Updates `flake8` from 7.0.0 to 7.3.0
- [Commits](PyCQA/flake8@7.0.0...7.3.0)

Updates `vcrpy` from 6.0.2 to 7.0.0
- [Release notes](https://github.com/kevin1024/vcrpy/releases)
- [Changelog](https://github.com/kevin1024/vcrpy/blob/master/docs/changelog.rst)
- [Commits](kevin1024/vcrpy@v6.0.2...v7.0.0)

Updates `pytest-recording` from 0.13.2 to 0.13.4
- [Release notes](https://github.com/kiwicom/pytest-recording/releases)
- [Changelog](https://github.com/kiwicom/pytest-recording/blob/master/docs/changelog.rst)
- [Commits](kiwicom/pytest-recording@v0.13.2...v0.13.4)

Updates `pytest-asyncio` from 0.23.8 to 1.1.0
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v0.23.8...v1.1.0)

Updates `chromadb` from 0.5.23 to 1.0.20
- [Release notes](https://github.com/chroma-core/chroma/releases)
- [Changelog](https://github.com/chroma-core/chroma/blob/main/RELEASE_PROCESS.md)
- [Commits](chroma-core/chroma@0.5.23...1.0.20)

Updates `openai` from 1.99.9 to 1.101.0
- [Release notes](https://github.com/openai/openai-python/releases)
- [Changelog](https://github.com/openai/openai-python/blob/main/CHANGELOG.md)
- [Commits](openai/openai-python@v1.99.9...v1.101.0)

Updates `llama-index-postprocessor-cohere-rerank` from 0.3.0 to 0.4.0

Updates `sqlalchemy` from 2.0.36 to 2.0.43
- [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases)
- [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst)
- [Commits](https://github.com/sqlalchemy/sqlalchemy/commits)

Updates `llama-index-llms-cohere` from 0.4.1 to 0.5.0

Updates `onnxruntime` from 1.19.2 to 1.20.1
- [Release notes](https://github.com/microsoft/onnxruntime/releases)
- [Changelog](https://github.com/microsoft/onnxruntime/blob/main/docs/ReleaseManagement.md)
- [Commits](microsoft/onnxruntime@v1.19.2...v1.20.1)

Updates `llama-parse` from 0.5.20 to 0.6.62

---
updated-dependencies:
- dependency-name: flake8
  dependency-version: 7.3.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
- dependency-name: vcrpy
  dependency-version: 7.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: gha
- dependency-name: pytest-recording
  dependency-version: 0.13.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: gha
- dependency-name: pytest-asyncio
  dependency-version: 1.1.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: gha
- dependency-name: chromadb
  dependency-version: 1.0.20
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: gha
- dependency-name: openai
  dependency-version: 1.101.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
- dependency-name: llama-index-postprocessor-cohere-rerank
  dependency-version: 0.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
- dependency-name: sqlalchemy
  dependency-version: 2.0.43
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: gha
- dependency-name: llama-index-llms-cohere
  dependency-version: 0.5.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
- dependency-name: onnxruntime
  dependency-version: 1.20.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
- dependency-name: llama-parse
  dependency-version: 0.6.62
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: gha
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/pip/packages/opentelemetry-instrumentation-llamaindex/gha-eb9b5e477f branch from 607aa37 to 8946259 Compare September 22, 2025 02:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants