chore(deps-dev): bump the gha group across 1 directory with 6 updates #3582
Conversation
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
Bumps the gha group with 5 updates in the /packages/opentelemetry-instrumentation-mistralai directory: | Package | From | To | | --- | --- | --- | | [mistralai](https://github.com/mistralai/client-python) | `1.9.11` | `1.10.0` | | [pytest-sugar](https://github.com/Teemu/pytest-sugar) | `1.0.0` | `1.1.1` | | [ruff](https://github.com/astral-sh/ruff) | `0.14.11` | `0.14.12` | | [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `0.23.8` | `1.2.0` | | [vcrpy](https://github.com/kevin1024/vcrpy) | `6.0.2` | `7.0.0` | Updates `mistralai` from 1.9.11 to 1.10.0 - [Release notes](https://github.com/mistralai/client-python/releases) - [Changelog](https://github.com/mistralai/client-python/blob/main/RELEASES.md) - [Commits](mistralai/client-python@v1.9.11...v1.10.0) Updates `pytest-sugar` from 1.0.0 to 1.1.1 - [Release notes](https://github.com/Teemu/pytest-sugar/releases) - [Changelog](https://github.com/Teemu/pytest-sugar/blob/main/CHANGES.rst) - [Commits](Teemu/pytest-sugar@v1.0.0...v1.1.1) Updates `ruff` from 0.14.11 to 0.14.12 - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](https://github.com/astral-sh/ruff/commits) Updates `opentelemetry-sdk` from 1.39.1 to 1.38.0 - [Release notes](https://github.com/open-telemetry/opentelemetry-python/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-python/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-python@v1.39.1...v1.38.0) Updates `pytest-asyncio` from 0.23.8 to 1.2.0 - [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases) - [Commits](pytest-dev/pytest-asyncio@v0.23.8...v1.2.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) --- updated-dependencies: - dependency-name: mistralai dependency-version: 1.10.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: gha - dependency-name: pytest-sugar dependency-version: 1.1.1 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: gha - dependency-name: ruff dependency-version: 0.14.12 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: gha - dependency-name: opentelemetry-sdk dependency-version: 1.38.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: gha - dependency-name: pytest-asyncio dependency-version: 1.2.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: gha - dependency-name: vcrpy dependency-version: 7.0.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: gha ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
![ellipsis-dev[bot]](https://avatars.githubusercontent.com/in/64358?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to 04342e1 in 2 minutes and 25 seconds. Click for details.
- Reviewed
27lines of code in1files - Skipped
1files when reviewing. - Skipped posting
4draft 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-mistralai/pyproject.toml:31
- Draft comment:
Updated pytest-sugar to 1.1.1. Confirm that the new signature and behavior (per release notes) are compatible with the test suite. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is asking the PR author to confirm compatibility with the test suite after a dependency update. It violates the rule against asking the author to confirm or ensure behavior is intended or tested.
2. packages/opentelemetry-instrumentation-mistralai/pyproject.toml:38
- Draft comment:
The pytest-asyncio range has been widened to <1.3.0 but the lower bound is still 0.23.7. Since the update targets pytest-asyncio 1.2.0, consider changing the lower bound to '>=1.2.0' to enforce the new major version. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 15% vs. threshold = 50% The comment makes a speculative assumption that "the update targets pytest-asyncio 1.2.0" without any evidence. The diff only shows that the upper bound was widened from <0.24.0 to <1.3.0. This could be intentional to allow a wider range of versions (0.23.7 through 1.2.x), not necessarily to enforce version 1.2.0. The comment is asking the author to change their intention based on an assumption about what they meant to do. This violates the rule about not asking the author to confirm their intention or making speculative comments. The author may have intentionally kept the lower bound at 0.23.7 to maintain backward compatibility. The comment could be correct if the PR author actually intended to target pytest-asyncio 1.2.0 specifically and made a mistake. Without seeing the PR description or commit message, I can't be certain this is wrong advice. Even if the author intended to target 1.2.0, the comment is speculative ("Since the update targets pytest-asyncio 1.2.0") without evidence. The rules explicitly state not to make speculative comments or ask authors to confirm their intention. The widened range could be intentional for backward compatibility, and there's no strong evidence this is a mistake. This comment should be deleted. It makes an unfounded assumption about the PR author's intentions ("the update targets pytest-asyncio 1.2.0") and suggests changing the lower bound without strong evidence that the current range is incorrect. The widened upper bound could be intentional to allow flexibility.
3. packages/opentelemetry-instrumentation-mistralai/pyproject.toml:40
- Draft comment:
pytest-sugar is also pinned to 1.1.1 in the test group. Ensure this consistency is intentional and that both dev and test environments use the same version. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
4. packages/opentelemetry-instrumentation-mistralai/pyproject.toml:42
- Draft comment:
vcrpy's range now allows any version <8 while the upgrade target is 7.0.0. Consider updating the lower bound to '>=7.0.0' if the new features or fixes in v7 are required. - 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% The comment is speculative - it says "Consider updating... if the new features or fixes in v7 are required." This is a conditional suggestion without evidence that v7 features are actually required. The PR author intentionally kept the lower bound at 6.0.1, which indicates backward compatibility is desired. The comment violates the rule about speculative comments ("If X, then Y is an issue" - only comment if it's definitely an issue). There's no strong evidence that the lower bound needs to be changed. The comment is asking the author to consider something without clear justification. Perhaps the automated tool has knowledge that v7 introduces important features or fixes that this package should use. Maybe there's a security issue in v6 that makes keeping the lower bound problematic. Even if there were security issues or important features in v7, the comment doesn't mention them - it's purely speculative with "if the new features or fixes in v7 are required." Without concrete evidence of a problem with v6, this is just a suggestion to narrow compatibility for no stated reason. This comment should be deleted. It's speculative ("if... are required"), provides no evidence that v7 is actually needed, and the PR author's choice to keep the lower bound at 6.0.1 appears intentional to maintain backward compatibility.
Workflow ID: wflow_TPYm91ls8dhp9XaU
You can customize 
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.
Bumps the gha group with 5 updates in the /packages/opentelemetry-instrumentation-mistralai directory:
1.9.111.10.01.0.01.1.10.14.110.14.120.23.81.2.06.0.27.0.0Updates
mistralaifrom 1.9.11 to 1.10.0Release notes
Sourced from mistralai's releases.
... (truncated)
Changelog
Sourced from mistralai's changelog.
... (truncated)
Commits
9370820Generate version v1.10.0 #29713d22ba## SDK Changes Detected:d4144a0Merge pull request #296 from mistralai/alex/fix_running_example_scripte4d3ea3update workflow token8b8d97dfix: example script not failing correctly747341eAdd OTel Tracing (#280)c6c1f78Pins GH actions (#291)7e9f550[CI] Add retries to avoid failing because of flakey network issues (#281)Updates
pytest-sugarfrom 1.0.0 to 1.1.1Release notes
Sourced from pytest-sugar's releases.
Changelog
Sourced from pytest-sugar's changelog.
Commits
8133503Release pytest-sugar 1.1.16798042Fix conflict with other Pytest plugins (#297)43bbdd0Release pytest-sugar 1.1.0855d661Feature - Playwright Support for Trace Zip Mapping (#296)2a5862aMerge pull request #293 from cgoldberg/add-py313ca26d98Add support for Python 3.1369989ebClarify license as BSD 3-Clause License3c86a5cMerge pull request #289 from deronnax/remove-packaging-depc123be0remove 'packaging' packageefafd9cMerge pull request #282 from penguinpee/mainUpdates
rufffrom 0.14.11 to 0.14.12Changelog
Sourced from ruff's changelog.
Commits
Updates
opentelemetry-sdkfrom 1.39.1 to 1.38.0Changelog
Sourced from opentelemetry-sdk's changelog.
... (truncated)
Commits
1f68134Prepare release 1.38.0/0.59b0 (#4777)e75b0abUpdate version to 1.38.0.dev/0.59b0.dev (#4744)359f436opentelemetry-sdk: fix formatting (#4746)712ed5dOTEL attribute count limit not respected, causing columns dropped (#4677)dd93fa7infra: ignore pushes on otelbot branches (#4742)22d1fd1Fix API LogRecord serialization (#4741)d6c0441Add credentials environment variables to letChannelCredentialsand `Sessio...c71c4a4Cacheimportlib_metadata.entry_points(#4735)64de448Permit to override default OTLP HTTP exporter headers (#4634)0d9e1b4semantic-conventions: bump to 1.37.0 (#4731)Updates
pytest-asynciofrom 0.23.8 to 1.2.0Release notes
Sourced from pytest-asyncio's releases.
... (truncated)
Commits
0d3988fci: Create GitHub release before publishing to PyPI.07c5a0bdocs: Include orphaned news fragment in changelog.be24582chore: Prepare release of v1.2.0.7aeb296docs: Streamline news fragments7b8311cci: Fixes a bug that prevented SSH signature from being stripped from release...9d4c2bddocs: Add changelog entry for Pyright compatibility.94f6106test: Added tests which assert that the event loop is reinstated if unset by ...df61991[pre-commit.ci] pre-commit autoupdatef1f7941Build(deps): Bump pytest from 8.4.1 to 8.4.2c77d3d3Build(deps): Bump twine from 6.1.0 to 6.2.0Updates
vcrpyfrom 6.0.2 to 7.0.0Release notes
Sourced from vcrpy's releases.
Changelog
Sourced from vcrpy's changelog.
... (truncated)
Commits
3278619Release v7.0.03fb62e0fix: correctly handle asyncio.run when loop exists8197865build(deps): update sphinx requirement from <8 to <9be651bdpre-commit: Autoupdatea6698edFix aiohttp tests48d0a2eFixed missingversion_stringattribute when used with urllib3>=2.3.05b858b1Fix lintc8d99a9Fix ruff configurationce27c63Merge pull request #736 from kevin1024/drop-python38ab8944dDrop python 3.8 supportDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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 conditionsImportant
Update development dependencies in
pyproject.tomlforopentelemetry-instrumentation-mistralai.pytest-sugarfrom 1.0.0 to 1.1.1 inpyproject.toml.pytest-asynciofrom 0.23.8 to 1.2.0 inpyproject.toml.vcrpyfrom 6.0.2 to 7.0.0 inpyproject.toml.This description was created by
for 04342e1. You can customize this summary. It will automatically update as commits are pushed.