Repository navigation
Cut 0.5.1 - #40
Merged
Merged
Cut 0.5.1#40
Conversation
Rolls `## Unreleased` into `## 0.5.1 (2026-09-16)`, covering the `uv build` switch and the two release-workflow fixes. The two fixes are already inside the `v0.5.0` tag, but that tag never reached PyPI -- the trusted-publisher claim found no matching publisher, so the upload failed while the GitHub release went out. For anyone installing the package, 0.4.0 is still the latest, so these reach a user first in 0.5.1. The heading note records that rather than leaving the gap between the tag list and PyPI unexplained. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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.
Rolls
## Unreleasedinto## 0.5.1 (2026-09-16). No code changes.The section keeps all three entries -- the
uv buildswitch (#39) and the two release-workflow fixes (#37, #38). The latter two are already inside thev0.5.0tag, butv0.5.0never reached PyPI: its trusted-publisher claim found no matching publisher and the upload failed on all three pushes of that tag, while the GitHub release went out anyway (which is #38 behaving as designed). PyPI's latest is still 0.4.0, so for anyone installing the package these fixes ship first in 0.5.1. The heading note says so, since a reader comparing the tag list against PyPI would otherwise find the gap unexplained.Before this can publish
Tagging
v0.5.1fails exactly asv0.5.0did until a trusted publisher exists on PyPI. The claims the last run presented were correct, so the registration just needs to match them:panoptes-data-> Manage -> Publishing -> Add a new publisherpanoptes, repositorypanoptes-data, workflowcreate-release.yml, environment blankThe project already exists on PyPI, so this goes under the existing project rather than as a pending publisher.
🤖 Generated with Claude Code