Configure automatic PyPI publishing using a Trusted Publisher#254
Open
Qup42 wants to merge 7 commits intoqlever-dev:mainfrom
Open
Configure automatic PyPI publishing using a Trusted Publisher#254Qup42 wants to merge 7 commits intoqlever-dev:mainfrom
Qup42 wants to merge 7 commits intoqlever-dev:mainfrom
Conversation
Qup42
commented
Jan 23, 2026
Comment on lines
+3
to
+5
| branches: [ main, automatic_pypi_publishing ] | ||
| #tags: | ||
| # - 'v*' |
Collaborator
Author
There was a problem hiding this comment.
ToDo. Testing for now.
Qup42
commented
Jan 23, 2026
Comment on lines
+51
to
+52
| with: | ||
| repository-url: https://test.pypi.org/legacy/ No newline at end of file |
Collaborator
Author
There was a problem hiding this comment.
ToDo: switch to prod PyPI registry
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.
PyPI Trusted Publisher is a mechanism where you configure a trusted workflow. The workflow is then able to publish the package to PyPI without requiring a token.
We could also update the version in the
pyproject.tomlto match the tag instead of checking that they match. This would also encourage the tags as the source of truth for the version. Experience has shown that tagging (and pushing the tag) is easily forgotten.