chore(deps-dev): bump the gha group across 1 directory with 4 updates

[dependabot]

Bumps the gha group with 4 updates in the /packages/opentelemetry-instrumentation-chromadb directory: flake8, pytest, pytest-sugar and chromadb.

Updates flake8 from 7.0.0 to 7.3.0

Commits

• c48217e Release 7.3.0
• f9e0f33 Merge pull request #1986 from PyCQA/document-f542
• 6bcdb62 document F542
• 70a15b8 Merge pull request #1985 from PyCQA/upgrade-deps
• 4941a3e upgrade pyflakes / pycodestyle
• 23e4005 Merge pull request #1983 from PyCQA/py314
• 019424b add support for t-strings
• 6b6f3d5 Merge pull request #1980 from PyCQA/asottile-patch-1
• 8dfa669 add rtd sphinx config
• ce34111 Merge pull request #1976 from PyCQA/document-f824
• Additional commits viewable in compare view

Updates pytest from 8.2.2 to 8.4.1

Release notes

Sourced from pytest's releases.

8.4.1

pytest 8.4.1 (2025-06-17)

Bug fixes

• #13461: Corrected _pytest.terminal.TerminalReporter.isatty to support being called as a method. Before it was just a boolean which could break correct code when using -o log_cli=true).

• #13477: Reintroduced pytest.PytestReturnNotNoneWarning{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.

  This warning is raised when a test functions returns a value other than None, which is often a mistake made by beginners.

  See return-not-none{.interpreted-text role="ref"} for more information.

• #13497: Fixed compatibility with Twisted 25+.

Improved documentation

• #13492: Fixed outdated warning about faulthandler not working on Windows.

8.4.0

pytest 8.4.0 (2025-06-02)

Removals and backward incompatible breaking changes

• #11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.

• #12346: Tests will now fail, instead of raising a warning, if they return any value other than None.

• #12874: We dropped support for Python 3.8 following its end of life (2024-10-07).

• #12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.

  See the docs <yield tests deprecated>{.interpreted-text role="ref"} for more information.

Deprecations (removal in next major release)

• #10839: Requesting an asynchronous fixture without a [pytest_fixture_setup]{.title-ref} hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or autouse=True. For guidance on how to work around this warning see sync-test-async-fixture{.interpreted-text role="ref"}.

New features

• #11538: Added pytest.RaisesGroup{.interpreted-text role="class"} as an equivalent to pytest.raises{.interpreted-text role="func"} for expecting ExceptionGroup{.interpreted-text role="exc"}. Also adds pytest.RaisesExc{.interpreted-text role="class"} which is now the logic behind pytest.raises{.interpreted-text role="func"} and used as parameter to pytest.RaisesGroup{.interpreted-text role="class"}. RaisesGroup includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulating except* <except_star>{.interpreted-text role="ref"}. See assert-matching-exception-groups{.interpreted-text role="ref"} and docstrings for more information.

• #12081: Added capteesys{.interpreted-text role="fixture"} to capture AND pass output to next handler set by --capture=.

• #12504: pytest.mark.xfail{.interpreted-text role="func"} now accepts pytest.RaisesGroup{.interpreted-text role="class"} for the raises parameter when you expect an exception group. You can also pass a pytest.RaisesExc{.interpreted-text role="class"} if you e.g. want to make use of the check parameter.

• #12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.

... (truncated)

Commits

• 8d99211 Prepare release version 8.4.1
• 5dc5880 docs: update pytest.ini addopts example to use separate -p entries (#13529) (...
• d0c7ed0 Reintroduce PytestReturnNotNoneWarning (#13495) (#13527)
• a1b3a78 Fix compatibility with Twisted 25 (#13502) (#13531)
• 4c161ab pytester: avoid unraisableexception gc collects in inline runs to speed up te...
• a86ee09 Fix typo in parametrize.rst (#13514) (#13516)
• 1a0581b Remove outdated warning about faulthandler_timeout on Windows (#13492) (#13493)
• 4e631a7 Merge pull request #13486 from hosmir/fixtypo (#13487)
• b49745e fix: support TerminalReporter.isatty being called (#13462) (#13483)
• cc5ceed RELEASING: remove pytest mailing list (#13472) (#13473)
• Additional commits viewable in compare view

Updates pytest-sugar from 1.0.0 to 1.1.0

Release notes

Sourced from pytest-sugar's releases.

pytest-sugar 1.1.0

Add Playwright trace file detection and display support for failed tests. This enhancement automatically detects and displays Playwright trace.zip files with viewing commands when tests fail, making debugging easier for Playwright users.

New command-line options:

• --sugar-trace-dir: Configure the directory name for Playwright trace files (default: test-results)
• --sugar-no-trace: Disable Playwright trace file detection and display

Changelog

Sourced from pytest-sugar's changelog.

1.1.0 - 2025-08-16 ^^^^^^^^^^^^^^^^^^

Add Playwright trace file detection and display support for failed tests. This enhancement automatically detects and displays Playwright trace.zip files with viewing commands when tests fail, making debugging easier for Playwright users.

New command-line options:

• --sugar-trace-dir: Configure the directory name for Playwright trace files (default: test-results)
• --sugar-no-trace: Disable Playwright trace file detection and display

Contributed by kie via [PR #296](Teemu/pytest-sugar#296)

Commits

• 43bbdd0 Release pytest-sugar 1.1.0
• 855d661 Feature - Playwright Support for Trace Zip Mapping (#296)
• 2a5862a Merge pull request #293 from cgoldberg/add-py313
• ca26d98 Add support for Python 3.13
• 69989eb Clarify license as BSD 3-Clause License
• 3c86a5c Merge pull request #289 from deronnax/remove-packaging-dep
• c123be0 remove 'packaging' package
• efafd9c Merge pull request #282 from penguinpee/main
• 536c1a8 Fix license string
• See full diff in compare view

Updates chromadb from 0.5.4 to 1.0.17

Release notes

Sourced from chromadb's releases.

1.0.17

Version: 1.0.17 Git ref: refs/tags/1.0.17 Build Date: 2025-08-14T22:52 PIP Package: chroma-1.0.17.tar.gz Github Container Registry Image: :1.0.17 DockerHub Image: :1.0.17

What's Changed

• [ENH]: add metrics for span & metric exporters by @​codetheweb in chroma-core/chroma#5223
• [ENH]: add metric for # of aborted tasks in dispatcher by @​codetheweb in chroma-core/chroma#5224
• [ENH]: make take_result_channel() return an option by @​codetheweb in chroma-core/chroma#5230
• [ENH] Wire up the should_trace_error for soft-deleted collections. by @​rescrv in chroma-core/chroma#5228
• Revert "[DOC] Made light/dark mode for Chroma logo" by @​kylediaz in chroma-core/chroma#5233
• [ENH] Create update_tenant API by @​drewkim in chroma-core/chroma#5214
• [BUG] Remove id field from GetCollectionByResourceNameRequest by @​drewkim in chroma-core/chroma#5235
• [ENH]: REVERT: add metrics for span & metric exporters by @​codetheweb in chroma-core/chroma#5236
• [CHORE] Cut the two most spammy spans from RLS by @​rescrv in chroma-core/chroma#5234
• [DOC] remove duplicate code block on Morph docs by @​philipithomas in chroma-core/chroma#5240
• [DOC] add docs for collection forking by @​philipithomas in chroma-core/chroma#5229
• [ENH]: Reduce peak memory usage of compactor by @​sanketkedia in chroma-core/chroma#5231
• [BLD] Make Slack notifications consistent by @​eculver in chroma-core/chroma#5238
• [ENH] Allow scorecarding of fork collection by collection or tenant. by @​rescrv in chroma-core/chroma#5247
• [ENH]: Add index on collections with created_at as sortkey by @​tanujnay112 in chroma-core/chroma#5208
• [ENH] Add flag on Dockerfile to use AVX512 instructions by @​jairad26 in chroma-core/chroma#5194
• [ENH] Do not trace this error if not should_trace_error by @​rescrv in chroma-core/chroma#5249
• Add WordPress (AI Engine Pro) to Chroma integrations by @​jordymeow in chroma-core/chroma#5242
• [ENH]: Make number of concurrent block flushes configurable by @​sanketkedia in chroma-core/chroma#5252
• [ENH] Upload spans by @​HammadB in chroma-core/chroma#5253
• [ENH]: Reduce recall threshold in test_add to 95 by @​sanketkedia in chroma-core/chroma#5254
• [RELEASE] CLI 1.1.6, Python 1.0.17, JS 3.0.12 by @​itaismith in chroma-core/chroma#5255

New Contributors

• @​jordymeow made their first contribution in chroma-core/chroma#5242

Full Changelog: chroma-core/chroma@1.0.16...1.0.17

1.0.16

Version: 1.0.16 Git ref: refs/tags/1.0.16 Build Date: 2025-08-08T00:26 PIP Package: chroma-1.0.16.tar.gz Github Container Registry Image: :1.0.16 DockerHub Image: :1.0.16

What's Changed

• [ENH]: add cache mount & tolerations to garbage collector template in Helm chart by @​codetheweb in chroma-core/chroma#5016
• [DOC] Fix docs typo by @​itaismith in chroma-core/chroma#5018
• [CLN] Change GenericQuotaError from 429 to 422 by @​drewkim in chroma-core/chroma#5022
• [CHORE] Fix type error in batch_utils by @​jairad26 in chroma-core/chroma#5024

... (truncated)

Commits

• 955fd8e [RELEASE] CLI 1.1.6, Python 1.0.17, JS 3.0.12 (#5255)
• ff5e0a5 [ENH]: Reduce recall threshold in test_add to 95 (#5254)
• a08f976 [ENH] Upload spans (#5253)
• 12b313a [ENH]: Make number of concurrent block flushes configurable (#5252)
• c2fa412 Add WordPress (AI Engine Pro) to Chroma integrations (#5242)
• 4018509 [ENH] Do not trace this error if not should_trace_error (#5249)
• a2f8573 [ENH] Add flag on Dockerfile to use AVX512 instructions (#5194)
• 9a54b8b [ENH]: Add index on collections with created_at as sortkey (#5208)
• cbb510c [ENH] Allow scorecarding of fork collection by collection or tenant. (#5247)
• 99549ff [BLD] Make Slack notifications consistent (#5238)
• Additional commits viewable in compare view

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 development dependencies in pyproject.toml for opentelemetry-instrumentation-chromadb, including flake8, pytest, pytest-sugar, and chromadb.

• Dependencies Updated:
  • flake8 updated from 7.0.0 to 7.3.0.
  • pytest updated from 8.2.2 to 8.4.1.
  • pytest-sugar updated from 1.0.0 to 1.1.0.
  • chromadb updated from 0.5.4 to 1.0.17.
• File Affected:
  • pyproject.toml in packages/opentelemetry-instrumentation-chromadb directory.

^{This description was created by for f5a9e88. 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.

[coderabbitai]

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to f5a9e88 in 42 seconds. Click for details.

• Reviewed 23 lines of code in 1 files
• Skipped 1 files when reviewing.
• Skipped posting 3 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-chromadb/pyproject.toml:34

• Draft comment:
  Updated flake8 version to 7.3.0. Verify that any new lint rules or changes in behavior are compatible with our codebase.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify compatibility with the codebase after a dependency update, which is against the rules. It doesn't provide a specific suggestion or point out a specific issue.

2. packages/opentelemetry-instrumentation-chromadb/pyproject.toml:36

• Draft comment:
  Bump pytest-sugar to 1.1.0; new version adds support (e.g., Playwright trace file detection) that could enhance test diagnostics.
• 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 bump and its potential benefits. It does not suggest any action or raise any concerns about the change.

3. packages/opentelemetry-instrumentation-chromadb/pyproject.toml:39

• Draft comment:
  Changed chromadb dependency from '^0.5.0' to '>=0.5,<1.1' to allow use of the new 1.0.17 release while constraining the upper bound. Confirm that this range aligns with intended compatibility.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to confirm their intention regarding the dependency version range. It is not making a specific code suggestion or pointing out a specific issue with the code. It violates the rule against asking the author to confirm their intention or ensure compatibility.

Workflow ID: wflow_5tKqDSxoZQROl6pN

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

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.