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

[dependabot]

Bumps the gha group with 2 updates in the /packages/opentelemetry-semantic-conventions-ai directory: ruff and pytest-sugar.

Updates ruff from 0.14.11 to 0.14.12

Changelog

Sourced from ruff's changelog.

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

• @​terror
• @​harupy
• @​Jkhall81
• @​dhruvmanila
• @​lubaskinc0de
• @​zanieb
• @​MeGaGiGaGon
• @​charliermarsh
• @​renovate
• @​dylwil3
• @​MichaReiser
• @​11happy

Commits

• See full diff in compare view

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.

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.

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

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 ruff to 0.14.12 and pytest-sugar to 1.1.1 in opentelemetry-semantic-conventions-ai.

• Dependency Updates:
  • Update ruff from 0.14.11 to 0.14.12 in pyproject.toml and uv.lock.
  • Update pytest-sugar from 1.0.0 to 1.1.1 in pyproject.toml and uv.lock.

^{This description was created by for 88b8360. 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.

• 🔍 Trigger a full review

---

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

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 88b8360 in 1 minute and 34 seconds. Click for details.

• Reviewed 406 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 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-semantic-conventions-ai/pyproject.toml:23

• Draft comment:
  Dependency update: the dev dependency for pytest-sugar has been bumped from 1.0.0 to 1.1.1. Please make sure the new version’s behavior (e.g. any changes in reporting or CLI options) is fully compatible with our test suite.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is about a dependency update, specifically for pytest-sugar. It asks the PR author to ensure compatibility with the test suite, which violates the rule against asking the author to ensure behavior is intended or tested. Therefore, this comment should be removed.

2. packages/opentelemetry-semantic-conventions-ai/uv.lock:220

• Draft comment:
  Lock file update: The uv.lock now shows an increased revision (from 1 to 3) and updated metadata (upload-time, hash values, and URLs) for dependencies such as ruff (now 0.14.12) and pytest-sugar (1.1.1). Confirm that this re-resolution was intentional and does not alter dependency resolution beyond the version bumps.
• 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 confirm their intention regarding the lock file update and dependency resolution. This violates the rule against asking the author to confirm their intention or ensure behavior is intended. The comment does not provide a specific code suggestion or ask for a specific test to be written.

Workflow ID: wflow_u6XyiD5FK5cHki60

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