Fix PyPI publish action reference#235
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #235 +/- ##
==========================================
- Coverage 86.27% 86.23% -0.05%
==========================================
Files 29 29
Lines 4635 4635
Branches 799 799
==========================================
- Hits 3999 3997 -2
- Misses 450 451 +1
- Partials 186 187 +1 🚀 New features to boost your workflow:
|
masa10-f
marked this pull request as ready for review
July 19, 2026 20:05
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
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.
Summary
pypa/gh-action-pypi-publish@v1reference with the supportedpypa/gh-action-pypi-publish@release/v1referenceRoot cause
The release workflow failed while GitHub Actions was resolving required actions because the PyPA publisher action does not provide a
v1ref. The supported v1 release branch isrelease/v1, so no build or publish step could start with the previous reference.Impact
Future tag-triggered release runs can resolve the PyPI publishing action and proceed to the build and trusted-publishing steps.
Validation
.github/workflows/publish-to-pypi.ymlsuccessfully as YAMLgit diff --checkrelease/v1ref exists through the GitHub APIpypa/gh-action-pypi-publish@v1reference remains