chore(release): cover the last two commits in the 1.3.0 notes - #120
Merged
Conversation
#118 and #119 landed after the 1.3.0 section was written, so the notes did not mention them. #118 in particular adds a user-facing command and a network fetch, which the notes must state. The FFmpeg entry says plainly that neither artifact carries FFmpeg bytes and that nothing downloads unless the operator asks. Verified against the built wheel and source archive rather than taken from the commit message. The version stays 1.3.0. The highest bump implied since v1.2.2 is still minor, and 1.3.0 is already the minor. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The 1.3.0 notes were written before the last two commits landed
#118and#119merged after the section was prepared, so neither appeared in it.#118matters most: it adds a user-facing command and a network fetch, and release notes that omit that are misleading.The FFmpeg entry, and why it is worded that way
#118addscapture install-ffmpeg, which downloads a LGPL-2.1-or-later build. This repository must not ship copyleft material inside an MIT artifact, so I verified the boundary against the built artifacts rather than trusting the commit message:Only the downloader source, which is this project's own MIT code. No FFmpeg binaries, no native libraries, in either artifact. The wheel is 265K, consistent with pure Python.
The fetch is opt-in and pinned: 34 sha256 digests in
ffmpeg_runtime.py, and nothing executes at import time. Both repository gates agree:That is a pinned, hash-verified, opt-in upstream fetch, which is the shape the licensing policy asks for. The notes now state it so a reader does not have to re-derive it.
The version is unchanged
Still 1.3.0. Since v1.2.2 the highest implied bump is minor,
#118is anotherfeat, and#119is a fix. A feature does not push a minor further; only a breaking change would. Re-checked rather than assumed.Verified
Documentation only. No code, no version, no lock change.