chore(deps-dev): bump uv from 0.5.20 to 0.8.6 in /packages/opentelemetry-instrumentation-crewai

[dependabot]

Bumps uv from 0.5.20 to 0.8.6.

Release notes

Sourced from uv's releases.

0.8.6

Release Notes

This release contains hardening measures to address differentials in behavior between uv and Python's built-in ZIP parsers (CVE-2025-54368).

Prior to this release, attackers could construct ZIP files that would be extracted differently by pip, uv, and other tools. As a result, ZIPs could be constructed that would be considered harmless by (e.g.) scanners, but contain a malicious payload when extracted by uv. As of v0.8.6, uv now applies additional checks to reject such ZIPs.

Thanks to a triage effort with the Python Security Response Team and PyPI maintainers, we were able to determine that these differentials were not exploited via PyPI during the time they were present. The PyPI team has also implemented similar checks and now guards against these parsing differentials on upload.

Although the practical risk of exploitation is low, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this advisory a CVE identifier and have given it a "moderate" severity suggestion.

These changes have been validated against the top 15,000 PyPI packages; however, it's plausible that a non-malicious ZIP could be falsely rejected with this additional hardening. As an escape hatch, users who do encounter breaking changes can enable UV_INSECURE_NO_ZIP_VALIDATION to restore the previous behavior. If you encounter such a rejection, please file an issue in uv and to the upstream package.

For additional information, please refer to the following blog posts:

• Astral: uv security advisory: ZIP payload obfuscation
• PyPI: Preventing ZIP parser confusion attacks on Python package installers

Security

• Harden ZIP streaming to reject repeated entries and other malformed ZIP files (#15136)

Python

• Add CPython 3.13.6

Configuration

• Add support for per-project build-time environment variables (#15095)

Bug fixes

• Avoid invalid simplification with conflict markers (#15041)
• Respect UV_HTTP_RETRIES in uv publish (#15106)
• Support UV_NO_EDITABLE where --no-editable is supported (#15107)
• Upgrade cargo-dist to add UV_INSTALLER_URL to PowerShell installer (#15114)
• Upgrade h2 again to avoid too_many_internal_resets errors (#15111)
• Consider pythonw when copying entry points in uv run (#15134)

Documentation

• Ensure symlink warning is shown (#15126)

Install uv 0.8.6

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/uv/releases/download/0.8.6/uv-installer.sh | sh

... (truncated)

Changelog

Sourced from uv's changelog.

0.8.6

This release contains hardening measures to address differentials in behavior between uv and Python's built-in ZIP parser (CVE-2025-54368).

Prior to this release, attackers could construct ZIP files that would be extracted differently by pip, uv, and other tools. As a result, ZIPs could be constructed that would be considered harmless by (e.g.) scanners, but contain a malicious payload when extracted by uv. As of v0.8.6, uv now applies additional checks to reject such ZIPs.

Thanks to a triage effort with the Python Security Response Team and PyPI maintainers, we were able to determine that these differentials were not exploited via PyPI during the time they were present. The PyPI team has also implemented similar checks and now guards against these parsing differentials on upload.

Although the practical risk of exploitation is low, we take the hypothetical risk of parser differentials very seriously. Out of an abundance of caution, we have assigned this advisory a CVE identifier and have given it a "moderate" severity suggestion.

These changes have been validated against the top 15,000 PyPI packages; however, it's plausible that a non-malicious ZIP could be falsely rejected with this additional hardening. As an escape hatch, users who do encounter breaking changes can enable UV_INSECURE_NO_ZIP_VALIDATION to restore the previous behavior. If you encounter such a rejection, please file an issue in uv and to the upstream package.

For additional information, please refer to the following blog posts:

• Astral: uv security advisory: ZIP payload obfuscation
• PyPI: Preventing ZIP parser confusion attacks on Python package installers

Security

• Harden ZIP streaming to reject repeated entries and other malformed ZIP files (#15136)

Python

• Add CPython 3.13.6

Configuration

• Add support for per-project build-time environment variables (#15095)

Bug fixes

• Avoid invalid simplification with conflict markers (#15041)
• Respect UV_HTTP_RETRIES in uv publish (#15106)
• Support UV_NO_EDITABLE where --no-editable is supported (#15107)
• Upgrade cargo-dist to add UV_INSTALLER_URL to PowerShell installer (#15114)
• Upgrade h2 again to avoid too_many_internal_resets errors (#15111)
• Consider pythonw when copying entry points in uv run (#15134)

Documentation

• Ensure symlink warning is shown (#15126)

0.8.5

Enhancements

• Enable uv run with a GitHub Gist (#15058)
• Improve HTTP response caching log messages (#15067)
• Show wheel tag hints in install plan (#15066)
• Support installing additional executables in uv tool install (#14014)

... (truncated)

Commits

• 329a6b4 Bump version to v0.8.6 (#15137)
• abc68fc Consider pythonw when copying entrypoints in uv run (#15134)
• 7f1eaf4 Harden ZIP streaming to reject repeated entries and other malformed ZIP files...
• 038bf56 Sync latest Python releases (#15135)
• 84d57f2 Ensure symlink warning is shown (#15126)
• 9c634d9 Upgrade h2 again (#15111)
• 278295e Add test cases for find_uv_bin (#15110)
• aec90f0 Fix warnings when running tests with a subset of features (#15120)
• 3c1844c Add support for per-project build-time environment variables (#15095)
• fb51838 chore(ci): address linting findings in sync-python-releases.yml (#15117)
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[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.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[ellipsis-dev]

Skipped PR review on d492199 because no changed files had a supported extension. If you think this was in error, please contact us and we'll fix it right away.