Repository navigation
chore: release 0.5.1 - #99
Merged
Merged
Conversation
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
pyproject.toml: version 0.5.1, withuv.lockrelocked to match. The tagv0.5.1goes on this PR's merge commit.Since v0.5.0:
combobulator combineon the glob path refuses VTTs a failed or interrupted run left, and a run recorded complete clears any chunk checkpoint (fix(combine): refuse VTTs a run did not finish #79).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, thenscripts/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
Docs match how it works now
No secrets or private information