Prepare 0.4.0 release - #4
Merged
Merged
Conversation
Promote the [Unreleased] changelog section to [0.4.0] - 2026-07-28 and add the comparison link for the new version. Co-Authored-By: Claude Opus 5 (1M context) <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
1 participant
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.
Changelog-only release prep for v0.4.0, per step 1 of
RELEASING.md.[Unreleased]section to[0.4.0] - 2026-07-28[Unreleased]heading[0.4.0]comparison link and repoints[Unreleased]atv0.4.0...HEADNo source or dependency changes — the release content is #3, already on
mainasb113fd9.Why minor
The OpenCV distribution swap (
opencv-python→opencv-python-headless) is downstream-visible: both provide the samecv2module, so consumers who also need the full GUI build have to install it explicitly. That is more than a patch.Next steps after merge
Version is
setuptools-scm-driven, so there is no version string to edit — the tag is the bump. Once this merges:git checkout main && git pull git tag v0.4.0 git push origin v0.4.0That triggers
Publish to PyPI, which then needs manual approval on thepypienvironment (Actions → Review pending deployments → Approve and deploy).🤖 Generated with Claude Code