Skip to content

Causing PyPI Release

Holger Bartel edited this page Jan 6, 2025 · 1 revision

Causing Releasing Steps

1. Local Changes Pushed to GitHub and Merged

  • Create Branch: From develop, create a new branch (e.g., release-2.4.2).
  • Update Version: In setup.py, change version (e.g., version="2.4.1" to version="2.4.2"), then save the file.
  • Push and PR: Push the changes, create a pull request (PR) from your branch to develop, and merge it.

2. Draft Release and Publish

  • Draft Release: Go to Releases on GitHub, click Draft a new release, and create a tag (e.g., v2.4.2.)
  • Generate Notes: Click Generate release notes
  • Publish Release: Review the release notes, check Set as the latest release, then click Publish release.

3. Verify Actions and Check URL

  • Verify Actions: Go to the Actions tab and check if the workflow completes successfully.
  • Check URL: Visit PyPI - Causing url with latest version (e.g, https://pypi.org/project/causing/2.4.2/) to verify the release.