Repository navigation
Prepare Sharp Frames v0.4.0 - #2
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
Why
The processing and selection pipelines had accumulated inconsistencies between preview and execution, incomplete failure reporting, fragile subprocess cleanup, and limited coverage of platform-specific behavior. This release makes those paths deterministic and testable while improving the frame-selection experience.
User impact
Users get more consistent sharp-frame selection across image resolutions, clearer failure reporting, safer output handling, and a timeline that can display and navigate the complete analyzed frame set. Windows users also gain explicit CI coverage and platform-aware FFmpeg handling.
Validation
venv/bin/python -m pytest -q— 327 passedvenv/bin/python -m build --wheel --outdir /tmp/sharp-frames-release-wheelgit diff --checkRelease checklist
develop, then promote the release commit tomasterv0.4.0from the finalmasterrelease commitRELEASE_NOTES.mdsharp-frames==0.4.0to the package index, if applicable