Version-drift recovery. v0.7.0 was tagged but never shipped — the
release workflow caught a version drift in pyproject.toml (only
src/shimkit/__init__.py got bumped). v0.7.1 re-ships the v0.7.0
surface unchanged with both files at the matching version.
For the full machine-readable changelog, see
CHANGELOG.md. For the v0.7.0 surface (which
is what v0.7.1 actually ships), see
v0.7.0.md.
pyproject.toml: 0.6.0 → 0.7.1
src/shimkit/__init__.py: 0.7.0 → 0.7.1That's the whole change. Zero code edits, zero test edits.
Per shimkit's tag-handling policy
(~/.claude/CLAUDE.md section
"History: additive, never destructive"), pushed git tags are
append-only. Even though the v0.7.0 release workflow halted at the
verify step before publishing anything to GitHub Releases — so no
consumer ever saw v0.7.0 — moving the v0.7.0 tag to a new SHA
would have violated the rule. v0.7.1 is the rule-compliant
recovery path.
The v0.7.0 tag stays at the original SHA in tag history as a documented "never-shipped" marker; future releases continue from v0.7.1.
Identical to v0.7.0. shimkit framework laravel
with four commands: perms, env, cron-install, artisan.