From 263ee0f0baea170e7bf91bcaf05de84c5e753ca6 Mon Sep 17 00:00:00 2001 From: smb Date: Sat, 5 Sep 2026 01:12:25 +0200 Subject: [PATCH] chore: release 0.2.1 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) --- src/matteloop/__init__.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/matteloop/__init__.py b/src/matteloop/__init__.py index c9476b6..64b5ef2 100644 --- a/src/matteloop/__init__.py +++ b/src/matteloop/__init__.py @@ -2,7 +2,7 @@ from PIL import Image -__version__ = "0.2.0" +__version__ = "0.2.1" # Pillow warns above this value and errors above twice this value. Align the # warning boundary with the largest legal MatteLoop canvas without disabling the