Skip to content

fix(deps): drop the macOS litellm<1.92 carve-out now that litellm ships macOS wheels - #4838

Merged
nicoloboschi merged 2 commits into
vectorize-io:mainfrom
vadimcomanescu:fix/macos-litellm-floor
Oct 6, 2026
Merged

nicoloboschi merged 2 commits into
vectorize-io:mainfrom
vadimcomanescu:fix/macos-litellm-floor

Conversation

@vadimcomanescu

@vadimcomanescu vadimcomanescu commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

On macOS with Python 3.14, hindsight-api-slim installs but fails uv pip check:

The package `litellm` requires Python >=3.10, <3.14, but `3.14.6` is installed

The darwin carve-out pins litellm to the 1.91.x line, and every 1.91.x release declares Requires-Python <3.14. uv installs it anyway (it ignores that upper bound), so the failure shows up only in tools that validate the environment, such as uv pip check.

The carve-out's reason no longer holds: litellm has published macOS wheels (arm64 and x86_64) since 2026-08-09, and every release from 1.95.1 on carries them (1.94.0, 1.94.1 and 1.95.0 do not, hence the floor). This replaces both litellm lines with litellm>=1.95.1 in hindsight-api-slim and in hindsight-integrations/litellm, and regenerates both locks with uv lock. The locks gain boto3 1.43.x, pydantic-settings and their dependencies because litellm 1.102.1 requires them (boto3>=1.43.1, pydantic-settings>=2.14.1).

Checked on an Apple Silicon Mac (macOS 26.6.2), Python 3.14.6, uv 0.11.21, each in a fresh venv:

  • hindsight-api-slim==0.10.1: installs litellm 1.91.5; uv pip check fails as above.
  • This branch: installs litellm 1.102.1; uv pip check reports "All installed packages are compatible".

vadimcomanescu and others added 2 commits October 6, 2026 10:43
- api-slim comment: 1.95.1 ships per-version cp wheels, not abi3; reword
  the history of the removed darwin pin
- litellm integration comment: reflow and record the removed darwin pin
- test-hermes-compat.sh: drop the 'Linux only' note about litellm<1.92,
  which no longer applies
- rebased onto main and regenerated both uv.lock files
@nicoloboschi
nicoloboschi force-pushed the fix/macos-litellm-floor branch from 701f77d to 0961828 Compare October 6, 2026 08:48
@nicoloboschi
nicoloboschi merged commit a466355 into vectorize-io:main Oct 6, 2026
218 of 220 checks passed
allyblockcast Bot added a commit to Blockcast/hindsight that referenced this pull request Oct 18, 2026
…26.9.21 (BLO-47316) (#33)

Hermes main moved the hindsight provider out of its tree and gated every core
dependency on Python 3.14, so #32 pinned the gate to v2026.9.21. Upstream
(vectorize-io/hindsight) already redesigned the gate for exactly this and it
passes against Hermes main (e.g. run job 117087267621, hermes-agent@848fc0ad,
2026-10-16). Port it rather than re-derive it:

- scripts/test-hermes-compat.sh from vectorize-io main (vectorize-io#4575, vectorize-io#4769, vectorize-io#4838):
  3.14 venv, default ref main, installs THIS checkout's
  hindsight-integrations/hermes as an external plugin, runs
  `hermes plugins validate`, asserts the loaded provider is ours, asserts the
  four Hindsight distributions are the locally built wheels, and drives the
  MemoryProvider contract (step 7; skipped with an explicit message when no
  LLM key is present).
- hindsight-embed _http_probe fix from vectorize-io#4575: 0.10.0's probe cleared the
  caller's event loop, breaking local_embedded between two client calls.
- test.yml job changes from vectorize-io#4575 (integrations-hermes trigger, 60m timeout,
  LLM key env).

No PM-runtime redesign is needed: the plugin is loaded from
$HERMES_HOME/plugins inside a venv where Hermes and this checkout's wheels
were co-resolved, which is the compatibility property the gate exists for.

Signed-off-by: PlatformSREEngineer <platformsreengineer@paperclip.blockcast.net>
Co-authored-by: PlatformSREEngineer <platformsreengineer@paperclip.blockcast.net>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@nicoloboschi nicoloboschi mentioned this pull request Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants