Add trusted-publishing workflow for PyPI - #3
Merged
Merged
Conversation
publish.yml uploads the wheel on v* tags (or workflow_dispatch) via OIDC. No API token. First v0.1.0 publish is a manual run because that tag already exists. RELEASING.md has the one-time PyPI / GitHub environment setup.
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.
Adds
.github/workflows/publish.ymlsoroamhqcan go to PyPI without an API token.Does not publish anything. The job only runs on
v*tags or Actions → Publish → Run workflow.Before the first upload, still needed in the UIs (see
RELEASING.md):pypiroamhq, workflowpublish.yml, environmentpypiv0.1.0already exists, so after this lands, publish that version with Run workflow, not by retagging.