Repository navigation
fix: release without inspecting the built artifacts' metadata - #120
Merged
Merged
Conversation
The release gate rejected any wheel without exactly 32 entry points, so adding seg2fil, fil2picks and fil2seg (35) failed "Build and inspect release artifacts" for 2.0.0-alpha.3 and alpha.4: both were tagged and released on GitHub but never uploaded to PyPI. Drop the artifact inspection (scripts/inspect_distribution.py) and the smoke test's count of command entry points. The smoke test still loads every command and renders its help, on the released commit before building, and the check that the built version is the release's stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
uermel
pushed a commit
that referenced
this pull request
Oct 6, 2026
🤖 I have created a release *beep* *boop* --- ## [2.0.0-alpha.5](copick-utils-v2.0.0-alpha.4...copick-utils-v2.0.0-alpha.5) (2026-10-06) ### 🐞 Bug Fixes * release without inspecting the built artifacts' metadata ([#120](#120)) ([90c3ce8](90c3ce8)) --- Merging this PR will publish a copick-utils alpha prerelease to PyPI. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
2.0.0-alpha.3 and alpha.4 were tagged and released on GitHub but never reached PyPI. "Build and inspect release artifacts" failed both times with
Expected 32 command entry points, found 35: the release gate hard-coded the number of entry points, and seg2fil, fil2picks and fil2seg made it 35. The version bump fixed in #111 works ("release 2.0.0a4, built 2.0.0a4").scripts/inspect_distribution.pyand its workflow step).test_package_smoke.pystill loads every command and renders its help, on the released commit before building.Merging this
fix:makes release-please open the alpha.5 release PR; merging that publishes 2.0.0a5 to PyPI, with everything alpha.3 and alpha.4 had.Checked: a wheel and sdist of v2.0 at the alpha.4 release commit build with
uv build;tests/test_package_smoke.pypasses in the locked environment.🤖 Generated with Claude Code