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

[dependabot]

Bumps the gha group with 6 updates in the /packages/opentelemetry-instrumentation-cohere directory:

Package	From	To
flake8	7.0.0	7.3.0
pytest	8.2.2	8.4.1
pytest-sugar	1.0.0	1.1.0
cohere	5.6.1	5.17.0
vcrpy	6.0.1	7.0.0
pytest-recording	0.13.2	0.13.4

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 cohere from 5.6.1 to 5.17.0

Updates vcrpy from 6.0.1 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

• @​exslim made their first contribution in kevin1024/vcrpy#889
• @​alekseik1 made their first contribution in kevin1024/vcrpy#886

v6.0.2

• Ensure body is consumed only once (#846) - thanks @​sathieu
• Permit urllib3 2.x for non-PyPy Python >=3.10
• Fix typos in test commands - thanks @​chuckwondo
• Several test and workflow improvements - thanks @​hartwork and @​graingert

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

  • 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)
  • Bugfix for asyncio.run - thanks @​alekeik1

• 6.0.2

  • Ensure body is consumed only once (#846) - thanks @​sathieu
  • Permit urllib3 2.x for non-PyPy Python >=3.10
  • Fix typos in test commands - thanks @​chuckwondo
  • Several test and workflow improvements - thanks @​hartwork and @​graingert

• 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

  • Use ruff for linting (instead of current flake8/isort/pyflakes) - thanks @​jairhenrique
  • Enable rule B (flake8-bugbear) on ruff - thanks @​jairhenrique
  • Configure read the docs V2 - thanks @​jairhenrique
  • Fix typo in docs - thanks @​quasimik
  • Make json.loads of Python >=3.6 decode bytes by itself - thanks @​hartwork
  • Fix body matcher for chunked requests (fixes #734) - thanks @​hartwork
  • Fix query param filter for aiohttp (fixes #517) - thanks @​hartwork and @​salomvary
  • Remove unnecessary dependency on six. - thanks @​charettes
  • build(deps): update sphinx requirement from <7 to <8 - thanks @​jairhenrique
  • Add action to validate docs - thanks @​jairhenrique
  • Add editorconfig file - thanks @​jairhenrique
  • Drop iscoroutinefunction fallback function for unsupported python thanks @​jairhenrique

• 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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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-cohere package, including flake8, pytest-sugar, vcrpy, and pytest-recording.

• Dependencies Updated:
  • flake8 updated from 7.0.0 to 7.3.0.
  • pytest remains at 8.2.2.
  • pytest-sugar updated from 1.0.0 to 1.1.0.
  • vcrpy updated from 6.0.1 to 7.0.0.
  • pytest-recording updated from 0.13.2 to 0.13.4.
• Files Affected:
  • Updates made in pyproject.toml for opentelemetry-instrumentation-cohere package.

^{This description was created by for 45b315d. You can customize this summary. It will automatically update as commits are pushed.}

[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 45b315d in 1 minute and 34 seconds. Click for details.

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

• Draft comment:
  flake8 updated from 7.0.0 to 7.3.0. This bump includes bug fixes and improvements. Ensure that your linting configuration remains compatible.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and discusses a dependency change. It doesn't provide a specific code suggestion or ask for a specific test to be written. It also asks the author to ensure compatibility, which is against the rules.

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

• Draft comment:
  pytest-sugar updated from 1.0.0 to 1.1.0 in the dev dependencies. This version adds Playwright trace detection support; verify that test outputs remain as expected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update and asks the author to verify test outputs, which violates the rules. It doesn't provide a specific code suggestion or ask for a specific test to be written.

3. packages/opentelemetry-instrumentation-cohere/pyproject.toml:41

• Draft comment:
  Consistent update: pytest-sugar is bumped to 1.1.0 in the test dependencies. Good for uniformity across groups.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative and does not provide any actionable feedback or suggestions. It simply states that a dependency version has been updated, which is not within the scope of useful comments according to the rules.

4. packages/opentelemetry-instrumentation-cohere/pyproject.toml:42

• Draft comment:
  vcrpy version constraint updated from '^6.0.1' to '>=6.0.1,<8.0.0'. This widens the allowed range to include v7.x releases. Consider whether a stricter lower bound (e.g. '^7.0.0') is preferable if v7 is the target.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 0% vs. threshold = 50% According to the rules, we should NOT comment on dependency changes or library versions. The rules explicitly state "Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies." This is exactly what this comment is about - suggesting a different version constraint for a dependency. The comment might be technically correct about version constraints, and could prevent potential compatibility issues. While the comment might be technically valid, the rules are very clear about not commenting on dependency changes. We must trust that the author has chosen appropriate version constraints. The comment should be deleted as it violates the explicit rule about not commenting on dependency changes.

Workflow ID: wflow_zoLWJj649FwUy8kU

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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.