Repository navigation
fix(ci): pass GITHUB_TOKEN to auto-tag gh dispatch (B15tg) - #41
Merged
Merged
Conversation
JavierGOrdonnez
had a problem deploying
to
testpypi
August 27, 2026 12:21 — with
GitHub Actions
Failure
This branch had an error being deployed
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.
What
.github/workflows/auto-tag.yml: addGITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}to thetag-merged-versionstep'senv:block so the inlinegh workflow run publish.ymlcall inherits a valid token and actually fires the publish.v0.1.0a2TestPyPI publish as B15tg (links to V29yn).Why
The
v0.1.0a2tag was created on the develop merge but no TestPyPI publish followed — the auto-tag dispatch silently no-op'd becauseghhad no token. Recovery one-off (gh workflow run publish.yml --ref develop --field tag=v0.1.0a2 --field registry=testpypi) published a2 manually.Notes
This PR enters the normal
version-check→auto-bump-alpha-versionflow; the alpha counter will bump past the existingv0.1.0a2tag as required.