docs: sound endpoints accept sources up to 8 minutes (sonilo 0.15.2) - #38
Merged
Merged
Conversation
Lightsage docs evalsWaiting for the staging docs URL before running evals. Lightsage will start the selected PR evals automatically when GitHub reports a successful docs deployment for this PR. This usually happens within 15 minutes. Commit: |
The API raised video-to-sound and video-to-video-sound from 180 to 480 sec (api-dashboard PR #328, deployed 2026-09-04). The limit is enforced server-side and nothing here gates on it, but the README stated 180 — and a caller who believes that trims a video the API would have taken. Docs-only content, but PyPI renders the README on the project page, so the corrected cap only reaches readers through a release. sonilo-cli is untouched: its README does not state this cap, and its `sonilo>=0.15.0,<0.16` pin already covers 0.15.4, so no widening is needed. text-to-sfx's own 1-180 sec `duration` is a different parameter and is unchanged; the `<= 180` strings left in tests/test_errors.py are sample API validation payloads for that field, not this cap. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SFP9xPKwk2S1Qjmk5krx6h
spencer-zqian
force-pushed
the
feat/video-sfx-sound-8min
branch
from
September 4, 2026 23:18
f70415f to
33b5c82
Compare
spencer-zqian
added a commit
that referenced
this pull request
Sep 4, 2026
`#38` bumped `pyproject.toml` to 0.15.4 but left `src/sonilo/_version.py` on 0.15.3. `__version__` ships as the `x-sonilo-client-version` header, so a 0.15.4 release would have had every client on it identify itself as 0.15.3. Nothing caught it: the existing version tests compare the header to `__version__`, which stays self-consistent however stale it is, and no test compared either to pyproject. The release commits have always bumped both by hand (a41a37c, 2c78bd8), which works right up until someone bumps only one. Adds the missing comparison so the next one-sided bump fails in CI instead of on PyPI. sonilo-cli is unaffected — its own version and its `sonilo>=0.15.0,<0.16` pin both still hold. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SFP9xPKwk2S1Qjmk5krx6h
spencer-zqian
added a commit
that referenced
this pull request
Sep 4, 2026
`#38` bumped `pyproject.toml` to 0.15.4 but left `src/sonilo/_version.py` on 0.15.3. `__version__` ships as the `x-sonilo-client-version` header, so a 0.15.4 release would have had every client on it identify itself as 0.15.3. Nothing caught it: the existing version tests compare the header to `__version__`, which stays self-consistent however stale it is, and no test compared either to pyproject. The release commits have always bumped both by hand (a41a37c, 2c78bd8), which works right up until someone bumps only one. Adds the missing comparison so the next one-sided bump fails in CI instead of on PyPI. sonilo-cli is unaffected — its own version and its `sonilo>=0.15.0,<0.16` pin both still hold. Claude-Session: https://claude.ai/code/session_01SFP9xPKwk2S1Qjmk5krx6h Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The API raised
video-to-soundandvideo-to-video-soundfrom 180 to 480 sec (api-dashboard PR #328, deployed 2026-09-04).The limit is enforced server-side and nothing here gates on it — but the README stated 180, and a caller who believes that trims a video the API would have taken. Same shape as
3dc1341.Docs-only content, but PyPI renders the README on the project page, so the corrected cap only reaches readers through a release →
sonilo0.15.1 → 0.15.2.sonilo-cliis untouched: its README does not state this cap, and itssonilo>=0.15.0,<0.16pin already covers 0.15.2, so no widening is needed this round.Checked and deliberately left alone:
text-to-sfx's own 1–180 secdurationis a different parameter, and the<= 180strings intests/test_errors.pyare sample API validation payloads for that field, not this cap. No client-side duration gate exists in this SDK.289 passed.🤖 Generated with Claude Code
https://claude.ai/code/session_01SFP9xPKwk2S1Qjmk5krx6h