Repository navigation
chore: release 0.2.1 - #46
Merged
Merged
Conversation
A patch that carries no application change. 0.2.0 is the release this one is: the same cut transform stage, the same DirectML segmentation on Windows, the same rembg 2.0.75 namespace with its outdated-weight handling. Nothing in src/matteloop differs beyond the version string. 0.2.0 exists only as a tag. Its release run built both bundles and then aborted in the step that reports compile cache statistics, before the upload, because an unterminated quote in release.yml made the shell refuse the script. The publish job never ran, so the tag names a commit that never produced an artifact anyone can install. Retagging 0.2.0 would leave two different meanings attached to one version, so the artifacts get their own number instead. The workflow is repaired and the repair is verified, not assumed: a manual run of the release workflow on main reached the upload step on Windows and macOS, and skipped publish because the ref is a branch. Every run block in the JSON-shaped workflows now goes through bash -n in the test suite, so the next quote of this kind fails locally. The version lives in src/matteloop/__init__.py and hatch reads it from there. A local checkout needs uv sync --reinstall-package matteloop after the bump: the editable install keeps the old dist metadata, and the --version smoke test compares against exactly that. 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.
Bumps
src/matteloop/__init__.pyto 0.2.1. No application code changes.Why a new number instead of retagging
The
v0.2.0release run built both bundles and then aborted in the compilecache statistics step, before the upload.
publishnever ran, so the tagnames a commit that produced no installable artifact. Retagging it would
attach two meanings to one version, so the artifacts get 0.2.1 instead.
The workflow bug (an unterminated quote in
release.yml) is fixed in #45,and the fix is verified rather than assumed: a manual run of the release
workflow on
mainreachedUpload unsigned bundleon bothwindows-2022-x64 and macos-15-arm64, and correctly skipped
publishbecause the ref is a branch, not a tag.
Release notes will carry the known-issue note for #32 before publication.
Test plan
uv sync --reinstall-package matteloop, thenuv run matteloop --versionprints 0.2.1.uv run ruff check . && uv run mypy src && QT_QPA_PLATFORM=offscreen uv run pytest -qpass.main(run 33926359716).🤖 Generated with Claude Code