do you have a migration for python agents v1.3 to ...
# ask-ai
a
do you have a migration for python agents v1.3 to v1.4?
t
Thanks for reaching out, Sebastián. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — you’re asking whether a migration guide exists for Python agents from v1.3 → v1.4. I looked into our resources: we don’t have a specific migration guide published for the 1.3 → 1.4 minor upgrade. What I can help with right now: • I can walk you through common upgrade steps that are safe for minor version moves (dependency update, running tests, checking changelog). • I can review relevant changelog entries or release notes for v1.4 with you and point out any breaking changes or behavioral changes you should test for. • If you share the parts of your integration you’re most worried about (for example: agent initialization, event handlers, transport/auth changes, or specific APIs you call), I can give targeted guidance and example code changes. If you want to start, please tell me: • Where you install the agent (PyPI package name or repo) and the exact package version strings you’re using now and target (e.g.,
livekit-agent==1.3.x
→
1.4.0
). • Any areas of your integration you’re concerned about (auth, reconnection, custom handlers, asyncio usage, etc.). • Whether you have a test/staging environment we should assume for rollout steps. I’ll use that info to produce a concise upgrade checklist and highlight any likely compatibility issues. Sources: How to Get Help from LiveKit
a
so you're saying is not breaking? i have a fork with small adaptation of livekit/agents that is on v1.3.2
t
Thanks — I hear you: you have a fork of livekit/agents at v1.3.2 with a few small adaptations and you want to know whether upgrading to v1.4 is breaking. I don’t have a published changelog or release notes here that cover 1.3.2 → 1.4, so I can’t confirm whether the minor bump is non‑breaking. What I can do is help you safely evaluate and plan the upgrade. Here’s a focused plan I recommend so we can determine impact quickly: 1. Quick repo checks (I can help run these if you share details) ◦ Check the v1.4 release notes or GitHub commits between the v1.3.2 tag and v1.4 tag for any breaking API or behavior changes. ◦ Search commits for keywords like “breaking”, “remove”, “rename”, “deprecated”, “signature”, and “major refactor”. 1. Targeted code areas to inspect in your fork ◦ Initialization and configuration paths (how the agent is constructed and configured). ◦ Public method signatures you override or call. ◦ Event/callback handler names and payload shapes. ◦ Transport, auth, and reconnection logic. ◦ Any asyncio / concurrency primitives you rely on. 1. Upgrade/test checklist a. Update a branch in your fork: bump dependency to
1.4.0
(or the exact 1.4.x you plan to use) in a feature branch. b. Run your unit and integration tests. Note failing tests and stack traces. c. Add quick runtime smoke tests in a staging environment—start an agent, connect, send/receive events, and exercise the adapted paths. d. If tests fail, capture the first failing stack trace and the failing code path to target fixes. e. If everything passes, run a limited rollout and monitor logs for warnings or deprecations. 1. How I can help right now (pick one) ◦ I can scan relevant commits/changelog for v1.4 if you point me to the repo or the release URL. ◦ You can paste the small adaptations you made (files or diffs). I’ll review them and highlight likely incompatibilities. ◦ If you share failing test output after a bump, I’ll help diagnose fixes. If you want to proceed, tell me which option you prefer: • Link to the livekit/agents repo or the v1.4 release page, or • Paste the diffs for your adaptations (or a short summary of the changes), or • Share test failures you see after attempting the bump. I’ll follow up with precise guidance based on what you provide. Sources: Building the all-in-one platform for voice AI agents | Models overview | LiveKit Documentation