You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Integrations: test Pydantic AI, Google ADK, Haystack and Strands on their current releases #863
Three framework integrations are tested on a minor well behind the current release, so a new user who installs the latest gets an untested version (and instrument() warns that it is untested since #856):
One PR per framework, so they can land independently. Comment below with the one you're taking.
For each:
Move the dev-extras pin (or the docs pin, for Strands) to the latest minor, and the "tested with" line in docs/integrations/<framework>.md.
Run its contract and integration tests on the new minor (tests/test_contract_<framework>.py and tests/test_<framework>*.py; find them with git grep -l <framework> tests/). Fix what breaks in tracekit/integrations/<framework>.py, with a test that fails on the old code for anything that changed.
If the framework changed something the integration depends on (a hook, a callback, a private attribute), say what in the PR and add a docs/limits.md row if a call can now run ungated.
Run it once like a user: a small agent on the new minor with a real dev signer (tracekit installed from your branch), one allowed call and one held call, and paste what tracekit view shows.
Commits signed off (DCO).
The nightly adapter-contracts job runs these against @latest; a green run there on your branch's change is a good sign but not enough on its own.
Activity