Skip to content

chore: bump smallestai minimum to >=4.4.6 across examples#48

Merged
maharshi-smallest merged 1 commit into
mainfrom
chore/bump-smallestai-to-4.4.6
May 20, 2026
Merged

chore: bump smallestai minimum to >=4.4.6 across examples#48
maharshi-smallest merged 1 commit into
mainfrom
chore/bump-smallestai-to-4.4.6

Conversation

@maharshi-smallest

Copy link
Copy Markdown
Contributor

Summary

Bump every smallestai>=4.4.4 pin to >=4.4.6 across the root requirements.txt and all 14 per-example requirements.txt files.

Why

The Python SDK shipped two back-to-back changes:

  • 4.4.5 — breaking rename of SmallestAI(token=…)SmallestAI(api_key=…) and $SMALLEST_AI_TOKEN$SMALLEST_API_KEY, aligning the auto-generated client with the helpers, the dashboard UI, and every .env.sample in this cookbook (see fern-demo/smallest-ai-python-sdk#60).
  • 4.4.6 — follow-up that fixes the wire-test fixture and refreshes the auto-generated README.md / reference.md after the rename (see fern-demo/smallest-ai-python-sdk#61).

Pinning to >=4.4.6 means anyone running pip install -r requirements.txt on a cookbook example lands on the version where the rename is fully consistent — kwarg, env var, tests, README, and reference doc all agree.

What changed

  • requirements.txt (root, common deps)
  • voice-agents/{agent_with_tools,analytics,appointment_scheduler,background_agent,bank_csr,call_control,campaigns,form_filler,getting_started,inbound_ivr,interrupt_control,knowledge_base_rag,language_switching,observability}/requirements.txt

All 15 files now read smallestai>=4.4.6.

Test plan

  • grep -rn "smallestai>=4.4.4" . returns nothing
  • grep -rn "smallestai>=4.4.5" . returns nothing
  • Every affected requirements.txt now reads smallestai>=4.4.6
  • PyPI shows 4.4.6 available (lands when fern-demo/smallest-ai-python-sdk#61 merges)

🤖 Generated with Claude Code

4.4.5 introduced a breaking rename in the Python SDK:
  SmallestAI(token=…)  →  SmallestAI(api_key=…)
  $SMALLEST_AI_TOKEN   →  $SMALLEST_API_KEY

4.4.6 is the follow-up that fixes the wire-test fixture and the
auto-generated README/reference docs after the rename. Pinning to
>=4.4.6 means the cookbook landing experience (pip install + read the
README + run examples) is fully coherent.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@vercel

vercel Bot commented May 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
smallest-showcase Ready Ready Preview, Comment May 20, 2026 9:14am

Request Review

@maharshi-smallest maharshi-smallest merged commit 44822b8 into main May 20, 2026
2 checks passed
@entelligence-ai-pr-reviews

Copy link
Copy Markdown

EntelligenceAI PR Summary

This PR updates the smallestai dependency minimum version from >=4.4.4 to >=4.4.6 across all 15 requirements files in the repository.

  • Affects the root requirements.txt and all 14 voice-agent module requirements files
  • Ensures patch releases 4.4.5 and 4.4.6 are pulled in as the minimum baseline
  • No code logic changes; dependency version constraint update only

Confidence Score: 5/5 - Safe to Merge

Safe to merge — this PR makes a straightforward dependency version bump across all 15 requirements.txt files, updating the smallestai minimum constraint from >=4.4.4 to >=4.4.6 to ensure patch releases 4.4.5 and 4.4.6 are included as the minimum baseline. No code logic, application behavior, or API surface is altered; this is a purely mechanical version constraint update. All 15 changed files were reviewed and no issues were identified, making this a clean, low-risk maintenance change.

Key Findings:

  • All 15 requirements files consistently updated from >=4.4.4 to >=4.4.6, ensuring no file was missed and no inconsistent version constraint exists across root and voice-agent modules.
  • No logic, runtime, or behavioral changes are introduced — this is a dependency floor bump only, which carries minimal risk compared to upper-bound pinning or major/minor version changes.
  • The bump from 4.4.4 to 4.4.6 spans only two patch releases, significantly limiting the risk of breaking changes being introduced as the new minimum baseline.
  • Zero review comments generated and zero pre-existing unresolved issues, with full 15/15 file coverage confirming a clean automated review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant