-
Notifications
You must be signed in to change notification settings - Fork 868
chore(deps-dev): bump the gha group in /packages/opentelemetry-instrumentation-alephalpha with 5 updates #3585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Bumps the gha group in /packages/opentelemetry-instrumentation-alephalpha with 5 updates: | Package | From | To | | --- | --- | --- | | [aleph-alpha-client](https://github.com/Aleph-Alpha/aleph-alpha-client) | `7.6.0` | `11.2.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 `aleph-alpha-client` from 7.6.0 to 11.2.0 - [Release notes](https://github.com/Aleph-Alpha/aleph-alpha-client/releases) - [Changelog](https://github.com/Aleph-Alpha/aleph-alpha-client/blob/main/Changelog.md) - [Commits](Aleph-Alpha/aleph-alpha-client@v7.6.0...v11.2.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 `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: aleph-alpha-client dependency-version: 11.2.0 dependency-type: direct:development update-type: version-update:semver-major 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: 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] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
There was a problem hiding this 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 77524ef in 2 minutes and 24 seconds. Click for details.
- Reviewed
28lines 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-alephalpha/pyproject.toml:32
- Draft comment:
pytest-sugar is bumped from 1.0.0 to 1.1.1 here. This update is consistent across dev and test groups. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative, as it only states that a dependency version has been updated and is consistent across groups. It does not provide any actionable feedback or suggestions.
2. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:37
- Draft comment:
The aleph_alpha_client range is now '>=7.1.0,<12' (was <8) to allow versions up to 11.x. Consider if the lower bound should be raised to enforce the new client API (e.g. >=11.2.0) if backward compatibility isn’t needed. - 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 about a dependency version change, which the rules explicitly say to ignore ("Do NOT comment on dependency changes, library versions that you don't recognize, or anything else related to dependencies"). Additionally, the comment is speculative - it says "Consider if..." which is asking the author to think about something rather than pointing out a definite problem. The comment doesn't have strong evidence that the current version range is wrong; it's just suggesting the author might want to narrow it. This violates the rule about not making speculative comments. The comment could be seen as helpful guidance about API compatibility concerns, and it's technically about a code change in the diff. Perhaps dependency changes that affect API compatibility are important enough to warrant comments despite the general rule about ignoring dependency changes. While API compatibility could be important, the rules explicitly state to not comment on dependency changes. Moreover, the comment is speculative ("Consider if...") and doesn't provide strong evidence that there's actually a problem. The author presumably widened the range intentionally to support versions 7-11, and without evidence that this causes issues, we shouldn't second-guess that decision. This comment should be deleted because it violates the rule against commenting on dependency changes and is speculative rather than pointing out a definite issue. The author likely widened the version range intentionally, and there's no strong evidence this is incorrect.
3. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:39
- Draft comment:
pytest-asyncio’s range now allows versions up to <1.3.0. Since the bump is to 1.2.0, you might consider updating the lower bound from 0.23.7 to 1.2.0 if the new version is 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 makes an assumption that isn't supported by the diff. The diff only shows the upper bound being relaxed from <0.24.0 to <1.3.0. There's no indication that the project is actually using or requiring pytest-asyncio 1.2.0. The lower bound of 0.23.7 is unchanged, which suggests the code still works with that older version. Changing the lower bound to 1.2.0 would be a breaking change that forces users to upgrade, which should only be done if there's a specific requirement for features in 1.2.0. The comment is speculative ("you might consider") and makes an unfounded assumption about what version is being "bumped to". This violates the rule against speculative comments. Perhaps there's context outside this file (like a lock file or actual usage) that shows pytest-asyncio 1.2.0 is being used. The comment might be based on information not visible in this diff. Even if there's external context, the rule states I should only consider what's in the diff and not require additional context. The diff only shows a relaxation of the upper bound constraint, not a requirement for a newer version. Without clear evidence in the diff that 1.2.0 is required, this is a speculative suggestion. This comment should be deleted. It makes a speculative suggestion based on an assumption not supported by the diff. The change only relaxes the upper bound constraint, and there's no evidence that the lower bound needs to be updated. This is a "you might consider" type comment that isn't actionable based on the actual changes.
4. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:43
- Draft comment:
vcrpy’s range update to '<8' (was <7) accommodates v7.0.0 as expected. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%This comment is purely informative, providing information about a dependency version update. It does not suggest any action or raise any concerns about the change.
Workflow ID: wflow_hHaRNePMBVFX3733
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
Bumps the gha group in /packages/opentelemetry-instrumentation-alephalpha with 5 updates:
7.6.011.2.01.0.01.1.10.14.110.14.120.23.81.2.06.0.27.0.0Updates
aleph-alpha-clientfrom 7.6.0 to 11.2.0Release notes
Sourced from aleph-alpha-client's releases.
... (truncated)
Changelog
Sourced from aleph-alpha-client's changelog.
... (truncated)
Commits
50f7923chore: Bump version and add changelog entry (#325)aa6b3bbtest: Adjust response_format for structured output (#324)ec32136chore: Bump version and add changelog entry17c2962feat: adjust json schema for structured outputb3b2089chore: bump version and add changelog entryff9644fchore: bump version and add changelog entryc9c69bdfix: fix spellingc63452erefactor: do not pass optional values in case of being None9002a6dtest: use slitghly different pharia-1 embedding modelbb7cf79feat: support more params and types for embeddingsUpdates
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
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-alephalphapackage.aleph-alpha-clientfrom7.6.0to11.2.0.pytest-sugarfrom1.0.0to1.1.1.rufffrom0.14.11to0.14.12.pytest-asynciofrom0.23.8to1.2.0.vcrpyfrom6.0.2to7.0.0.This description was created by
for 77524ef. You can customize this summary. It will automatically update as commits are pushed.