mutmut-v3.5.1
·
117 commits
to main
since this release
chore(mutmut-fork): bump fork to 3.5.1, fix wheel glob for renamed dist Vendor template was already renamed to `interlocks-mutmut` in e96d681 but the release workflow's wheel-glob still expected the old `interlock_mutmut-*.whl` filename, so the next tag push would break at the artifact-validation step. Bumps the fork to 3.5.1 because PyPI already holds `interlock-mutmut==3.5.0` under the old name; same upstream SHA, distribution metadata only. Tagging mutmut-v3.5.1 publishes `interlocks-mutmut==3.5.1` to PyPI; the consumer-side pin migration follows in a separate commit so the runtime resolver only flips to the new name once the artifact is available.