upgraded pipecat to 0.0.103

[rootflo-hardik]

• also allowed pre release of sarvam 0.1.26a2

Summary by CodeRabbit

• Chores
  • Updated pipecat-ai dependency to version 0.0.103 for improved stability and compatibility.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pipecat-ai dependency version in the call processing module's pyproject.toml was updated from 0.0.102 to 0.0.103. This is a patch-level version bump with all associated feature extras maintained.

Changes

Cohort / File(s)	Summary
Dependency Update wavefront/server/apps/call_processing/pyproject.toml	Bumped pipecat-ai package version from 0.0.102 to 0.0.103, preserving all feature extras (websocket, cartesia, google, silero, deepgram, groq, runner, azure, local-smart-turn-v3, sarvam).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A version bump, so small, so neat,
pipecat-ai hops to the beat,
From one-oh-two to one-oh-three,
Dependencies dance merrily! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'upgraded pipecat to 0.0.103' clearly and concisely summarizes the main change in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix_upgrade_pipecat_to_0_0_103

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

wavefront/server/apps/call_processing/pyproject.toml (1)

24-24: Transitive dependency on a pre-release sarvam package (0.1.26a2) in production.

The PR description states that this upgrade "allows the pre-release of sarvam version 0.1.26a2." This means the sarvam extra inside pipecat-ai==0.0.103 now resolves to a pre-release (a2) build of the Sarvam SDK. Pre-release packages carry no stability guarantees and are generally unsuitable for production workloads. If the sarvam integration is actively used, monitor for regressions and plan a follow-up pin once a stable 0.1.26 is available.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@wavefront/server/apps/call_processing/pyproject.toml` at line 24, The
pipecat-ai extra list in pyproject.toml currently pulls a pre-release sarvam
(0.1.26a2) via "pipecat-ai[...sarvam...]==0.0.103"; update the dependency
resolution to avoid pre-releases by either removing the sarvam extra from the
pipecat-ai extras or explicitly pining sarvam to a stable version (e.g.,
sarvam==0.1.26 when available) or adding a non-prerelease constraint (e.g.,
exclude alpha/beta/prerelease versions) so CI and production do not resolve to
0.1.26a2, and ensure package metadata (pyproject.toml) reflects that change.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6890d90 and 516fcfe.

⛔ Files ignored due to path filters (1)

• wavefront/server/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• wavefront/server/apps/call_processing/pyproject.toml

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@wavefront/server/apps/call_processing/pyproject.toml`:
- Line 24: The pipecat-ai extra list in pyproject.toml currently pulls a
pre-release sarvam (0.1.26a2) via "pipecat-ai[...sarvam...]==0.0.103"; update
the dependency resolution to avoid pre-releases by either removing the sarvam
extra from the pipecat-ai extras or explicitly pining sarvam to a stable version
(e.g., sarvam==0.1.26 when available) or adding a non-prerelease constraint
(e.g., exclude alpha/beta/prerelease versions) so CI and production do not
resolve to 0.1.26a2, and ensure package metadata (pyproject.toml) reflects that
change.