Bump maximum admissible version of aio-pika

[haudren-woven]

Description

aio-pika version 10.0.1 was released on July 9th. However, the current auto-instrumentaiton checks for version < 10.0.0. After verifying that the auto-instrumentation works fine with 10.0.1, this commit proposes to bump the maximum admissible version to 11.0.0.

I am not entirely sure how unit tests are ran, so I did not add any, but

Fixes # NO-ISSUE

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Ran a test with latest aio-pika and this instrumentation, ensured that traces were being published

Does This PR Require a Core Repo Change?

• Yes. - Link to PR:
• No.

Checklist:

See contributing.md for styleguide, changelog guidelines, and more.

• Followed the style guidelines of this project
• Changelogs have been updated
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: haudren-woven / name: Hervé Audren (051390a, bd4b7f8)

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-09-02 20:51 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.

[haudren-woven]

/dashboard route:reviewers

[opentelemetry-pr-dashboard]

@haudren-woven, this pull request was routed to reviewers.

[emdneto]

Can you run tox -e generate-workflows and update the CI to include the new tox environment? Thanks!

I'm fine with this change, but I believe would be better to test only the oldest/latest supported versions, simmilar to https://github.com/open-telemetry/opentelemetry-python-contrib/blob/c89544601e28422a74daa19e279a99c2cf002d83/instrumentation/opentelemetry-instrumentation-fastapi/test-requirements.latest.txt

[haudren-woven]

@emdneto : Sorry for the late reply. I have addressed your change: I created a requirements.in, which can get the latest aio-pika and be used for future updates using uv pip compile. I haven't touched the existing test environments. Furthermore, note that the latest aio-pika is not compatible with python <3.11, so I've enabled the latest test only for Python 3.12+. Thanks 🙇