release: v0.7.1 — fix version drift in pyproject.toml

The v0.7.0 tag pushed at bb6eedc had `pyproject.toml` still at
`0.6.0` — I bumped `src/shimkit/__init__.py` to `0.7.0` but
forgot the matching change in `pyproject.toml`. The release
workflow's tag-version verifier (release.yml: "Verify tag ==
pyproject.toml == __init__.py") refused the mismatch and exited
1 in 9 seconds, so v0.7.0 never actually published.

Recovery path is append-only — bump to v0.7.1 rather than
mutating the pushed v0.7.0 tag (per the global "don't move
pushed tags" rule). The v0.7.0 surface ships unchanged under the
v0.7.1 label.

Both `pyproject.toml` and `__init__.py` now read `0.7.1`. No
code or test changes; 561 tests still pass; ruff + mypy strict
still clean.

The v0.7.0 tag stays at bb6eedc in tag history as a
documented "never-shipped" marker; future releases continue from
v0.7.1.

Author: imanimanyara

CHANGELOG.md

@@ -6,6 +6,17 @@ This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 ## [Unreleased]
 
+## [0.7.1] — 2026-05-15
+
+### Fixed
+
+- Release-workflow drift: the v0.7.0 tag was pushed with
+  `pyproject.toml` still at `0.6.0` (only `src/shimkit/__init__.py`
+  got bumped). The release workflow's tag-version verifier
+  rejected the mismatch and v0.7.0 never published. v0.7.1 bumps
+  both files to the same value and re-issues the v0.7.0 surface
+  unchanged. No code or test changes.
+
 ## [0.7.0] — 2026-05-15
 
 ### Added

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "shimkit"
-version = "0.6.0"
+version = "0.7.1"
 description = "A toolkit of developer utilities — Java version manager, shell upgrader, and more. Python tools, shimmed by bash."
 readme = "README.md"
 license = { file = "LICENSE" }

src/shimkit/__init__.py

@@ -3,5 +3,5 @@
 Python tools, shimmed by bash.
 """
 
-__version__ = "0.7.0"
+__version__ = "0.7.1"
 __all__ = ["__version__"]