Repository navigation
docs: torchaudio 2.11.0 does not cap torch - #70
Merged
Merged
Conversation
… 2.11.1 and torch 2.15.0
thatsrue
added a commit
that referenced
this pull request
Nov 16, 2026
## What changed - `pyproject.toml`: version 0.5.1, with `uv.lock` relocked to match. The tag `v0.5.1` goes on this PR's merge commit. Since v0.5.0: - `combobulator combine` on the glob path refuses VTTs a failed or interrupted run left, and a run recorded complete clears any chunk checkpoint (#79). - Docs: torchaudio 2.11 does not cap torch; comments name the current pins (#70). ## Why The owner asked to release these and move runewright's pin to them. Batch runs pass combine the exact VTTs they produced, so the D&D pipeline's transcripts do not change; it is proven on a real transcription on the Mac's GPU before the pin moves. No issue: chore ## How you checked it - `uv sync --locked --extra dev`, then `scripts/check`: 0 (lock, pins, ruff, pyrefly, pytest with real Whisper and VAD inference, build). - [ ] A bug fix comes with a test that fails without it - [x] Docs match how it works now - [x] No secrets or private information
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
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.
What changed
The comments in
pyproject.tomlandAGENTS.mdsaid torch and torchaudio are an exact pair and that torchaudio 2.11.0 caps torch. They now say torchaudio 2.11 runs with torch 2.11 and later, and that the pinned 2.11.1 declarestorch>=2.11. Thepip checknote inAGENTS.mdnamestorch==2.15.0, the current pin. No pins change. Change class: docs and comments only, no behavior change.Why
PyTorch's torchaudio installation docs say 2.11 is built against PyTorch's stable ABI, so it supports torch 2.11 and all later versions (the compatibility matrix lists "2.11 and above"). v0.5.0 pins
torch==2.15.0next totorchaudio==2.11.1, a supported pair, and the old comments still described the pre-v0.5.0 pins.Closes #55
How you checked it
scripts/checkin a fresh uv venv: lock, pins, ruff, pyrefly, pytest including the slow tests, build all oktorch>=2.11;pip checkclean with torch 2.15.0 and mlx-whisper 0.4.3 (themacextra)