Update dependency agno to >=2.6.7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
agno	>=2.6.6 → >=2.6.7

---

Release Notes

agno-agi/agno (agno)

v2.6.7

Compare Source

Changelog

New Features:

• Gemini Interactions: Added a new GeminiInteractions model class that makes use of Googles new stateful interactions API
• AgentOS: Added an opt-in per-user data isolation layer for AgentOS authenticated endpoints.

Improvements:

• Knowledge Readers: Added allowed_hosts parameter to URL-fetching readers to restrict outbound fetches.

Bug Fixes:

• Qdrant: Fixed to remove duplicate sparse encoder call in Qdrant async_insert.
• Traces: Fixed the parent trace's session_id / agent_id / team_id from being overwritten by a child agent's spans when both share a trace_id. Most visible when a Team uses a post-hook (e.g. @hook(run_in_background=True).
• Workflow: Fixed workflow’s HITL continue path to use corresponding async function acleanup_run if running in an async context.

What's Changed

• fix: remove duplicate sparse encoder call in Qdrant async_insert by @​sannya-singal in #​7893
• fix: traces update db level by @​kausmeows in #​7796
• cookbook: update notion mcp example to current server by @​ashpreetbedi in #​7921
• feat: per-user data isolation across AgentOS endpoints by @​SamJupe in #​7606
• fix: Calling acleanup_run instead of cleanup_run by @​abhi10691 in #​7916
• [fix] fix duplicated word in docker container network_mode comment by @​otjdiepluong in #​7913
• fix: add allowed_hosts SSRF guard to knowledge readers by @​sannya-singal in #​7892
• fix: use SESSION_ID_REQUIRED constant in continue-run routes by @​ysolanky in #​7936
• feat: add GeminiInteractions model for Google's Interactions API by @​ysolanky in #​7926
• chore: Release v2.6.7 by @​kausmeows in #​7931

New Contributors

• @​otjdiepluong made their first contribution in #​7913

Full Changelog: agno-agi/agno@v2.6.6...v2.6.7

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[semanticdiff-com]

Review changes with  

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-15 20:24 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (71a5033) and #1859 together #1860
• 🚫 Left the queue — 2026-05-15 20:30 UTC · at 9a593cd8e5e908877be1d8b2eeebc864cb06f67e

This pull request spent 5 minutes 51 seconds in the queue, including 5 minutes 30 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Test Image / API Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-22 01:51 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (9c03706) and #1859 together #1936
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-22 01:59 UTC · at b1608922aa1ba46e0d54b64235df3700a3d783c3

This pull request spent 8 minutes 32 seconds in the queue, including 7 minutes 55 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Test Image / API Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-22 02:36 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (80b9271) and #1859 together #1941
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-22 02:39 UTC · at 509cd0f21fee6a92c3aa4dd500020b3f383ab770

This pull request spent 2 minutes 56 seconds in the queue, with no time running CI.

Waiting for

• check-success = Test Image / API Test
• any of: [🛡 GitHub repository ruleset rule main]
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-22 13:59 UTC · Rule: Python Dependency Updates
• ✅ Checks started · on draft merge queue: embarking main (b6e0665) and #1859 together #1947
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-22 14:10 UTC · at 9cf2ccf19cba9f7a294c1755aa4c8376d9f571f5

This pull request spent 10 minutes 50 seconds in the queue, including 9 minutes 55 seconds running CI.

Waiting for

• check-success = Test Image / API Test

All conditions

• check-success = Test Image / API Test
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ Test Image / API Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[mergify]

Hey @renovate[bot], your pull request has been dequeued due to the following reason: CHECKS_FAILED. Sorry about that, but you can requeue the PR by using @mergifyio requeue if you think this was a mistake.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud