Martin NucandClaude Opus 5.5
151d741a71
Home Assistant 2026.10 pins openai==3.10.0 in its package constraints, so the manifest's exact openai==2.45.0 can no longer be installed and setup fails: Setup failed for custom integration 'openai_compatible': Requirements for openai_compatible not found: ['openai==2.45.0']. The requirement is now a floor. Each Home Assistant release then installs the openai it pins: 2.45.0 on 2026.9, 3.10.0 on 2026.10. The vendored code needs no change for 3.x. The only breaking change in openai 3.0 is HTTPX2 as the default client, and passing Home Assistant's legacy httpx client is still supported at runtime, which is how core's own integration handles it. Every openai import in the integration resolves on 3.10.0, and the suite passes against it on the 2026.10.0 test harness (170 passed). requirements_test.txt now pins 3.10.0 so CI tests what current Home Assistant ships. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0123XQr8dh5RnFLnECHPVNrd
16 lines
653 B
Plaintext
16 lines
653 B
Plaintext
# Requires Python 3.14+ (Home Assistant 2026.9 floor). Not installable on Python 3.13.
|
|
pytest-homeassistant-custom-component>=0.13.317
|
|
# Core 2026.10's pin; the manifest only sets a floor.
|
|
openai==3.10.0
|
|
|
|
# The manifest declares dependencies: ["conversation"], and the ported tests exercise
|
|
# stt/tts too; a full HA install resolves each core component's own `requirements` at
|
|
# runtime, but bare pytest does not, so they're pinned here to match core tag 2026.9.2's
|
|
# homeassistant/components/{conversation,tts}/manifest.json.
|
|
hassil==3.12.0
|
|
gazetteer-matcher==1.1.0
|
|
home-assistant-intents==2026.8.28
|
|
mutagen==1.48.1
|
|
PyTurboJPEG==1.8.3
|
|
ha-ffmpeg==3.2.2
|