-
Notifications
You must be signed in to change notification settings - Fork 872
chore(deps-dev): bump the gha group across 1 directory with 4 updates #3611
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?
chore(deps-dev): bump the gha group across 1 directory with 4 updates #3611
Conversation
|
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 0b8f5a2 in 1 minute and 49 seconds. Click for details.
- Reviewed
25lines 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:
Updated pytest-sugar from 1.0.0 to 1.1.1 as per release notes. Verify that this version remains compatible with our other pytest plugins. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is asking the PR author to verify compatibility of a dependency update, which is against the rules. It doesn't provide a specific suggestion or point out a specific issue with the code.
2. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:37
- Draft comment:
Expanded aleph_alpha_client version range from <8 to <12 to support major updates up to 11.x. Confirm that any breaking changes are handled. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is about a dependency version change, which is generally not something to comment on unless there's a specific issue or suggestion. The comment asks the author to confirm handling of breaking changes, which is against the rules.
3. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:39
- Draft comment:
Updated pytest-asyncio version range to allow versions up to but not including 1.4.0 (from <0.24.0). Ensure migration changes in pytest-asyncio 1.x are compatible. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%<= threshold50%The comment is discussing a dependency version change, specifically forpytest-asyncio. It suggests ensuring compatibility with migration changes in the new version range. However, it does not provide a specific suggestion or point out a specific issue with the code. It falls under the category of asking the author to ensure compatibility, which is not allowed.
4. packages/opentelemetry-instrumentation-alephalpha/pyproject.toml:41
- Draft comment:
Duplicate pytest-sugar entry in the test group mirrors the dev group update. Confirm that maintaining this duplicate is intentional. - 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 asking the PR author to "confirm" something, which directly violates the rule: "Do NOT ask the PR author to confirm their intention, to explain, to double-check things, to ensure the behavior is intended, to make sure their change is tested, or similar." The comment doesn't suggest a clear code change - it's just pointing out that there's a duplicate and asking for confirmation. Having the same dependency in both dev and test groups might be intentional (e.g., test group might be used independently of dev group). The comment doesn't provide strong evidence that this is a problem that needs fixing. Perhaps the duplicate is actually a mistake and should be removed from one of the groups. The comment might be trying to helpfully point out a potential issue with dependency management that could lead to maintenance problems. Even if the duplicate could be a mistake, the comment doesn't provide a clear actionable suggestion - it just asks for confirmation. If the tool thought this was definitely wrong, it should have suggested removing the duplicate from one group. The fact that it's asking for confirmation suggests uncertainty, and per the rules, we should delete comments that aren't clearly identifying an issue. This comment should be deleted because it asks the PR author to "confirm" something, which violates the explicit rule against asking authors to confirm intentions or double-check things. It doesn't provide a clear, actionable code change suggestion.
Workflow ID: wflow_43WPyKiJOdKUTHtl
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
195594f to
bd05372
Compare
Bumps the gha group with 4 updates in the /packages/opentelemetry-instrumentation-alephalpha directory: [aleph-alpha-client](https://github.com/Aleph-Alpha/aleph-alpha-client), [pytest-sugar](https://github.com/Teemu/pytest-sugar), [ruff](https://github.com/astral-sh/ruff) and [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio). Updates `aleph-alpha-client` from 7.6.0 to 11.5.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.5.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.13 - [Release notes](https://github.com/astral-sh/ruff/releases) - [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md) - [Commits](astral-sh/ruff@0.14.11...0.14.13) Updates `pytest-asyncio` from 0.23.8 to 1.3.0 - [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases) - [Commits](pytest-dev/pytest-asyncio@v0.23.8...v1.3.0) --- updated-dependencies: - dependency-name: aleph-alpha-client dependency-version: 11.5.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.13 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: gha - dependency-name: pytest-asyncio dependency-version: 1.3.0 dependency-type: direct:development update-type: version-update:semver-major dependency-group: gha ... Signed-off-by: dependabot[bot] <[email protected]>
bd05372 to
b185e96
Compare
Bumps the gha group with 4 updates in the /packages/opentelemetry-instrumentation-alephalpha directory: aleph-alpha-client, pytest-sugar, ruff and pytest-asyncio.
Updates
aleph-alpha-clientfrom 7.6.0 to 11.5.0Release notes
Sourced from aleph-alpha-client's releases.
... (truncated)
Changelog
Sourced from aleph-alpha-client's changelog.
... (truncated)
Commits
7918d0dtest: modify cassette base URL225701etest: fix image URL according to new docsaff0103test: change URL to contain /v132cc201feat: add reranking support2aeb791feat: Tool call response (#330)d96ff94Tool calling (#319)50d4186test: Use vcr in tests (#321)50f7923chore: Bump version and add changelog entry (#325)aa6b3bbtest: Adjust response_format for structured output (#324)ec32136chore: Bump version and add changelog entryUpdates
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.13Release notes
Sourced from ruff's releases.
... (truncated)
Changelog
Sourced from ruff's changelog.
... (truncated)
Commits
b4b8299[ty] MakeNamedTuple(...)andnamedtuple(...)calls stricter (#22601)fd9f87dBump 0.14.13 (#22604)048f02f[ty] Remove redundant re-exports that share the same top-most modulea72af10[ty] AddModuleName::top2f34836[ty] Add test capturing redundant re-exports from pandasdb9eee7[ty] Attach origin module on to re-exported symbols2cbd68a[ty] Move fully qualified name into auto-import implementation2a09467Add trailing slashes tonpm publishpaths (#22603)eca58ca[ty] Override__file__to str when applicable on imported modules (#22333)aa9f1b2Further improvements to typing conformance script (#22596)Updates
pytest-asynciofrom 0.23.8 to 1.3.0Release notes
Sourced from pytest-asyncio's releases.
... (truncated)
Commits
2e9695fdocs: Compile changelog for v1.3.0dd0e9badocs: Reference correct issue in news fragment.4c31abeBuild(deps): Bump nh3 from 0.3.1 to 0.3.213e9477Link to migration guides from changelog4d2cf3ctests: handle Python 3.14 DefaultEventLoopPolicy deprecation warningsee3549btest: Remove obsolete test for the event_loop fixture.7a67c82tests: Fix failing test by preventing warning conversion to error.a17b689test: add pytest config to isolated test directories18afc9dfix(tests): replace runpytest_subprocess with runpytestcdc6bd1Add support for pytest 9 and drop Python 3.9 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.5.0.pytest-sugarfrom1.0.0to1.1.1.rufffrom0.14.11to0.14.13.pytest-asynciofrom0.23.8to1.3.0.This description was created by
for 0b8f5a2. You can customize this summary. It will automatically update as commits are pushed.