Skip to content

Add GitHub Actions workflow for releasing to PyPI#22

Closed
HugoKlepsch wants to merge 1 commit into
groodt:mainfrom
HugoKlepsch:add-release-workflow
Closed

Add GitHub Actions workflow for releasing to PyPI#22
HugoKlepsch wants to merge 1 commit into
groodt:mainfrom
HugoKlepsch:add-release-workflow

Conversation

@HugoKlepsch
Copy link
Copy Markdown
Contributor

  • This workflow is started manually by invoking it from the actions page.
  • The action uses the release environment, so store the GITHUB_TOKEN, PYPI_USERNAME and PYPI_PASSWORD secrets in that environment. Configure that environment so that only the desired users (eg. repo owner) can invoke the action.
  • The action is provided a version by the user. It then makes and pushes a git tag for this version. It then builds the package and uploads to PyPi.

@HugoKlepsch
Copy link
Copy Markdown
Contributor Author

Oops, I meant to open this to my fork. I'm still testing it

* This workflow is started manually by invoking it from the actions page.
* The action uses the `release` environment. Configure that environment so that only the desired users (eg. repo owner) can invoke the action.
* Set up a trusted publisher for your Pypi project: https://docs.pypi.org/trusted-publishers/adding-a-publisher/
* The action is provided a version by the user. It then makes and pushes a git tag for this version. It then builds the package and uploads to PyPi.
@HugoKlepsch HugoKlepsch force-pushed the add-release-workflow branch from eee1d62 to f5db1d8 Compare July 14, 2025 12:20
@HugoKlepsch HugoKlepsch deleted the add-release-workflow branch July 14, 2025 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant