Release v0.7.1#560
Merged
Merged
Conversation
Breakthrough
force-pushed
the
releases/0.7.1
branch
from
July 22, 2026 01:33
bb33ade to
f8b05b2
Compare
Breakthrough
marked this pull request as ready for review
July 22, 2026 03:02
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.
Release checklist for v0.7.1 (from RELEASE-PLAN.md). Boxes reflect current progress; this PR merges
releases/0.7.1back intomainas the final step after the release is verified and published.1. Version Identifiers, Branch Prep
releases/0.7.1offmain; fast-forward it tomainas release work lands.__version__inscenedetect/__init__.py(0.7.1)docs/LATEST_VERSION(0.7.1, matches the branch suffix sogenerate-docs.ymlupdatesdocs/latest)-devsuffix2. Documentation, Website, Changelog
sphinx-buildcompletes clean).docs/api/migration_guide.rstreviewed - 0.7.1 is additive-only (no breaking changes), no update needed.scene_manager.py/detect()executed against a real video; fixed a stale placeholder doctest inhistogram_detector.py.)website/pages/download.mdupdated (v0.7.1, July 2026, installer links point at thev0.7.1tag).website/pages/changelog.md: 0.7.1 section moved from the Development section to the top (nested under## PySceneDetect 0.7); fresh 0.7.2 stub left at the bottom.website/pages/index.md: latest release version and date updated.docs/cli.rstregenerated (had pre-existing drift:--frame-raterename,save-edl --start-timecode).3. Tests
static,release-tests,install-matrix,long-stress) on the tag. (Local pre-check: 79 passed / 3 skipped; one test needsffprobe, which is unavailable locally - covered by CI.)pip-auditclean or exceptions documented in the changelog. pillow 11.3.0 (transitive via moviepy'spillow<12.0cap, moviepy#2553) had 5 CVEs fixed only in 12.3.0: overridden to 12.3.0 in the Windows build (appveyor.yml) and Docker image (Dockerfile), noted in the changelog; full test suite passes against 12.3.0. Remainingpipaudit findings are build-tooling only (not shipped). PyPI installs still resolve pillow per moviepy's cap - fixable only upstream.packaging/build_all.pyproduces all 6 artifacts at 0.7.1.4. Prepare Windows Distribution
packaging/windows/requirements.txtupdated (OpenCV 5, PyAV 18, numpy 2.5.1, click 8.4.2, platformdirs 4.11.0, tqdm 4.69.0) and bundled ffmpeg bumped to 8.1.2 inappveyor.yml.scripts/update_installer.pyrun:.aipat ProductVersion 0.7.1, fresh ProductCode, MSI filenamePySceneDetect-0.7.1-win64.msi; parity with__version__verified.5. Tag & Draft Release
releases/0.7.1: "Release v0.7.1".v0.7.1on that commit and push. Wait for all tests/builds to pass.scenedetect-signed.zipscenedetect-signed.zipintodist/signed/, runpython scripts/finalize_windows_dist.py(rebuilds portable .zip from the signed .msi, writes manifest + SHA256SUMS, runsscripts/validate_release.py).PySceneDetect-0.7.1-win64.manifest.json+SHA256SUMS)6. Publish & Release Checks
release.yml(Release Orchestrator) withtag=v0.7.1while the release is still a draft. It runs the verify-then-publish ladder (MSI install/upgrade test -> TestPyPI -> publish Github release -> PyPI -> Docker), verifying each stage before the next.ghcr.io/breakthrough/pyscenedetect:latestand the version tag.generate-website.ymlgenerate-docs.ymlmain), verifydocs/LATEST_VERSIONis correctgenerate-docs.ymlagainstreleases/0.7.1to update www.scenedetect.com/docs/latestpip install scenedetect==0.7.1; CLI launches andscenedetect versionlooks correct.