Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 18, 2026

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-client from 7.6.0 to 11.5.0

Release notes

Sourced from aleph-alpha-client's releases.

v11.5.0

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v11.4.0...v11.5.0

v11.4.0

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v11.2.0...v11.4.0

v11.2.0

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v11.1.0...v11.2.0

v11.1.0

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v11.0.0...v11.1.0

v11.0.0

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v10.6.2...v11.0.0

v10.6.2

What's Changed

Full Changelog: Aleph-Alpha/aleph-alpha-client@v10.6.1...v10.6.2

v10.6.1

What's Changed

... (truncated)

Changelog

Sourced from aleph-alpha-client's changelog.

11.5.0

  • Add reranking support

11.4.0

  • Tool calling for chat tasks where the model supports it

11.3.0

  • Drop support for python3.9

11.2.0

  • Add support for pydantic objects for structured output response format
  • Add additional fields for OpenAI compatibility wrt structured output

11.1.0

  • Fix API for response_format

11.0.0

  • enable encoding_format parameter for /embeddings endpoints
  • allow input for /embeddings to be of other types as well
  • fix typo: EmbeddingV2ReponseData -> EmbeddingV2ResponseData

10.6.2

  • Fix typing and attribute exports

10.6.1

  • Fix imports for OpenAI compatible embeddings

10.6.0

  • Add support for OpenAI compatible /embeddings endpoint.

10.5.1

  • Enable using TextMessage objects in multi-turn chats

10.5.0

  • Remove default values for top_p, top_k and temperature as not supported by all models

10.4.0

  • Add support for multimodal prompts (images only)

... (truncated)

Commits

Updates pytest-sugar from 1.0.0 to 1.1.1

Release notes

Sourced from pytest-sugar's releases.

pytest-sugar 1.1.1

Adjust signature of SugarTerminalReporter to avoid conflicts with other pytest plugins (#297 by @​TolstochenkoDaniil)

pytest-sugar 1.1.0

Add Playwright trace file detection and display support for failed tests (#296 by @​kiebak3r)

This enhancement automatically detects and displays Playwright trace.zip files with viewing commands when tests fail, making debugging easier for Playwright users. Playwright trace.zip

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.1 - 2025-08-23 ^^^^^^^^^^^^^^^^^^

Adjust signature of SugarTerminalReporter to avoid conflicts with other pytest plugins

Contributed by Daniil via [PR #297](Teemu/pytest-sugar#297)

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. Playwright trace.zip

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
  • 8133503 Release pytest-sugar 1.1.1
  • 6798042 Fix conflict with other Pytest plugins (#297)
  • 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
  • Additional commits viewable in compare view

Updates ruff from 0.14.11 to 0.14.13

Release notes

Sourced from ruff's releases.

0.14.13

Release Notes

Released on 2026-01-15.

This is a follow-up release to 0.14.12. Because of an issue publishing the WASM packages, there is no GitHub release or Git tag for 0.14.12, although the package was published to PyPI. The contents of the 0.14.13 release are identical to 0.14.12.

0.14.12

Preview features

  • [flake8-blind-except] Allow more logging methods (BLE001) (#22057)
  • [ruff] Respect lint.pydocstyle.property-decorators in RUF066 (#22515)

Bug fixes

  • Fix configuration path in --show-settings (#22478)
  • Respect fmt: skip for multiple statements on the same logical line (#22119)

Rule changes

  • [pydocstyle] Update Rust crate imperative to v1.0.7 (D401) (#22519)
  • [isort] Insert imports in alphabetical order (I002) (#22493)

Documentation

  • Add llms.txt support for documentation (#22463)
  • Use prek in documentation and CI (#22505)
  • [flake8-pytest-style] Add check parameter example to PT017 docs (#22546)
  • [ruff] Make example error out-of-the-box (RUF103) (#22558)
  • [ruff] document RUF100 trailing comment fix behavior (#22479)

Other changes

  • wasm: Require explicit logging initialization (#22587)

Contributors

... (truncated)

Changelog

Sourced from ruff's changelog.

0.14.13

Released on 2026-01-15.

This is a follow-up release to 0.14.12. Because of an issue publishing the WASM packages, there is no GitHub release or Git tag for 0.14.12, although the package was published to PyPI. The contents of the 0.14.13 release are identical to 0.14.12.

0.14.12

Released on 2026-01-15.

Preview features

  • [flake8-blind-except] Allow more logging methods (BLE001) (#22057)
  • [ruff] Respect lint.pydocstyle.property-decorators in RUF066 (#22515)

Bug fixes

  • Fix configuration path in --show-settings (#22478)
  • Respect fmt: skip for multiple statements on the same logical line (#22119)

Rule changes

  • [pydocstyle] Update Rust crate imperative to v1.0.7 (D401) (#22519)
  • [isort] Insert imports in alphabetical order (I002) (#22493)

Documentation

  • Add llms.txt support for documentation (#22463)
  • Use prek in documentation and CI (#22505)
  • [flake8-pytest-style] Add check parameter example to PT017 docs (#22546)
  • [ruff] Make example error out-of-the-box (RUF103) (#22558)
  • [ruff] document RUF100 trailing comment fix behavior (#22479)

Other changes

  • wasm: Require explicit logging initialization (#22587)

Contributors

... (truncated)

Commits
  • b4b8299 [ty] Make NamedTuple(...) and namedtuple(...) calls stricter (#22601)
  • fd9f87d Bump 0.14.13 (#22604)
  • 048f02f [ty] Remove redundant re-exports that share the same top-most module
  • a72af10 [ty] Add ModuleName::top
  • 2f34836 [ty] Add test capturing redundant re-exports from pandas
  • db9eee7 [ty] Attach origin module on to re-exported symbols
  • 2cbd68a [ty] Move fully qualified name into auto-import implementation
  • 2a09467 Add trailing slashes to npm publish paths (#22603)
  • eca58ca [ty] Override __file__ to str when applicable on imported modules (#22333)
  • aa9f1b2 Further improvements to typing conformance script (#22596)
  • Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.8 to 1.3.0

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 1.3.0

1.3.0 - 2025-11-10

Removed

  • Support for Python 3.9 (#1278)

Added

  • Support for pytest 9 (#1279)

Notes for Downstream Packagers

  • Tested Python versions include free threaded Python 3.14t (#1274)
  • Tests are run in the same pytest process, instead of spawning a subprocess with pytest.Pytester.runpytest_subprocess. This prevents the test suite from accidentally using a system installation of pytest-asyncio, which could result in test errors. (#1275)

pytest-asyncio 1.2.0

1.2.0 - 2025-09-12

Added

  • --asyncio-debug CLI option and asyncio_debug configuration option to enable asyncio debug mode for the default event loop. (#980)
  • A pytest.UsageError for invalid configuration values of asyncio_default_fixture_loop_scope and asyncio_default_test_loop_scope. (#1189)
  • Compatibility with the Pyright type checker (#731)

Fixed

  • RuntimeError: There is no current event loop in thread 'MainThread' when any test unsets the event loop (such as when using asyncio.run and asyncio.Runner). (#1177)
  • Deprecation warning when decorating an asynchronous fixture with @pytest.fixture in [strict]{.title-ref} mode. The warning message now refers to the correct package. (#1198)

Notes for Downstream Packagers

  • Bump the minimum required version of tox to v4.28. This change is only relevant if you use the tox.ini file provided by pytest-asyncio to run tests.
  • Extend dependency on typing-extensions>=4.12 from Python<3.10 to Python<3.13.

pytest-asyncio 1.1.1

v1.1.1 - 2025-09-12

Notes for Downstream Packagers

- Addresses a build problem with setuptoos-scm >= 9 caused by invalid setuptools-scm configuration in pytest-asyncio. (#1192)

pytest-asyncio 1.1.0

Added

  • Propagation of ContextVars from async fixtures to other fixtures and tests on Python 3.10 and older (#127)
  • Cancellation of tasks when the loop_scope ends (#200)
  • Warning when the current event loop is closed by a test

Fixed

... (truncated)

Commits
  • 2e9695f docs: Compile changelog for v1.3.0
  • dd0e9ba docs: Reference correct issue in news fragment.
  • 4c31abe Build(deps): Bump nh3 from 0.3.1 to 0.3.2
  • 13e9477 Link to migration guides from changelog
  • 4d2cf3c tests: handle Python 3.14 DefaultEventLoopPolicy deprecation warnings
  • ee3549b test: Remove obsolete test for the event_loop fixture.
  • 7a67c82 tests: Fix failing test by preventing warning conversion to error.
  • a17b689 test: add pytest config to isolated test directories
  • 18afc9d fix(tests): replace runpytest_subprocess with runpytest
  • cdc6bd1 Add support for pytest 9 and drop Python 3.9 support
  • 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-alephalpha package.

  • Dependency Updates:
    • Update aleph_alpha_client from 7.6.0 to 11.5.0.
    • Update pytest-sugar from 1.0.0 to 1.1.1.
    • Update ruff from 0.14.11 to 0.14.13.
    • Update pytest-asyncio from 0.23.8 to 1.3.0.

This description was created by Ellipsis for 0b8f5a2. You can customize this summary. It will automatically update as commits are pushed.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Jan 18, 2026
@coderabbitai
Copy link

coderabbitai bot commented Jan 18, 2026

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.

  • 🔍 Trigger a full review

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@ellipsis-dev ellipsis-dev bot left a 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 25 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-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% <= threshold 50% 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% <= threshold 50% 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% <= threshold 50% The comment is discussing a dependency version change, specifically for pytest-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 Ellipsis by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.

@dependabot dependabot bot force-pushed the dependabot/uv/packages/opentelemetry-instrumentation-alephalpha/gha-047d2a6234 branch 2 times, most recently from 195594f to bd05372 Compare January 26, 2026 16:30
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]>
@dependabot dependabot bot force-pushed the dependabot/uv/packages/opentelemetry-instrumentation-alephalpha/gha-047d2a6234 branch from bd05372 to b185e96 Compare January 28, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants