Repository navigation
Release v3.0.0 - #73
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.
Bumps
VERSIONand__version__to 3.0.0 and moves the Unreleased CHANGELOG entries under[3.0.0] - 2026-09-28.Why a major release:
load_videoreturns uint8,magnify_motionsreturns float32 with new keyword arguments, and scripts need a__main__guard whenjobs> 1.--gpuin the GPU image's entrypoint.These are listed as BREAKING in the CHANGELOG and in the README's new "Breaking Changes → v3.0.0" section. The README intro now summarises v3.0.0.
After merge: tag the merge commit
v3.0.0(annotated) and push the tag. Docker images pick up the newVERSIONlabel on their next build.