Skip to content

Integrations: warn when a hand-wired framework isn't the version Tracekit is tested with #400

Closed

Description

@LoopGlitch26

tracekit.instrument() warns when a framework it wires is outside its tested range ("… is wired but untested; Tracekit is tested with …", tracekit/autowire.py line 417, from the ranges in FRAMEWORKS). The integrations you build by hand get no such warning: Microsoft Agent Framework, Google ADK, Haystack, LlamaIndex and Strands Agents. For Agent Framework this is a docs/limits.md row ("tested with Agent Framework 1.22 only … another version gets no warning") and a line in docs/integrations/microsoft-agent-framework.md. A framework minor that moved a hook or changed a callback's arguments then fails in ways that are hard to trace back to the version.

The tested minors are already written down: agent-framework-core>=1.22,<1.23, google-adk>=2.12,<2.13, haystack-ai>=3.4,<3.5, llama-index-core>=0.14.25,<0.15 (the dev extra in pyproject.toml) and strands-agents>=1.61,<1.62 (docs/integrations/strands.md). _version() and _release() in autowire.py already read and compare an installed version.

Task:

  • Warn once per process, when the integration is built (Tracekit(run) in tracekit/integrations/agent_framework.py, google_adk.py, haystack.py, llama_index.py, strands.py), if the installed distribution is outside its tested range, with the same wording as instrument()'s warning. Reuse _version()/_release() rather than copying them; one small helper the five call is enough.
  • Never raise: an unreadable or missing version means no warning.
  • Tests in the five existing test files (tests/test_agent_framework.py, tests/test_google_adk.py, tests/test_haystack.py, tests/test_llama_index.py, tests/test_strands.py), or one shared test of the helper plus one per integration that patches the version: inside the range no warning, outside it one warning.
  • Remove "another version gets no warning" from the Agent Framework row in docs/limits.md and from its integration page.

Done when: building Tracekit(run) with a framework version outside its range warns once, inside the range it doesn't, and make test passes.

Comment here to claim it. Commits need a DCO sign-off (git commit -s).

Activity

  1. AnnasMazhar commented on Oct 28, 2026

    @AnnasMazhar
    Contributor

    Claiming this. Working on it in #474: a shared version check (tracekit/integrations/version_check.py) that the five hand-wired integrations call when they are built, warning once per process when the installed framework is outside the tested range, reusing _version()/_release() and instrument()'s wording. WIP on the fork: https://github.com/AnnasMazhar/Tracekit/tree/fix/400-warn-untested-framework-versions

  2. LoopGlitch26 commented on Oct 28, 2026

    @LoopGlitch26
    MemberAuthor

    Thanks for taking this. The shared check reusing _version()/_release() and instrument()'s wording is the right shape. We'll review #474 once its CI has run.

  3. added a commit that references this issue on Oct 29, 2026
    17e1d1f
  4. added a commit that references this issue on Oct 30, 2026
    5ff0920
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions