Releases: Heknon/pytest-failure-instrumentation
Releases · Heknon/pytest-failure-instrumentation
Release list
v0.11.0
v0.10.0
v0.8.0
v0.6.0
Merge branch 'claude/exec-net-frozen-primary-thread-vjjcqx' The live stack server no longer advises about a bind off loopback when a token is supplied; the refusal without one is unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012xnH8irJ8iqDwWVKZ866tG
v0.5.0
v0.4.0
v0.3.0
v0.2.0
Refuse a mislabelling release before it publishes, not after The check I added for a tag that names a different commit was in the job that writes the tag, and that job runs after publish. So it would have refused the release only once PyPI already held the files - the exact failure it exists to prevent, half done, and unrepeatable because a version cannot be uploaded twice. A gate after the irreversible step is not a gate. It now runs in build, next to the check that the tag and pyproject agree, which is where the question belongs: both ask whether this commit is entitled to this version number, and both can still answer for free. The one in the tagging job stays as the last word before the tag is written, in case it moved while the run was in flight. This is not theoretical. v0.2.0 is on the commit that fails and master is now the commit that does not, so a dispatch aimed at publishing the fix was one job away from uploading it and then declining to tag it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M7qqvypeowm2rM4EdJ4GBw
