Skip to content

ci: add GitHub Actions workflow for automated PyPI publishing#128

Open
filhocf wants to merge 1 commit intoIBM:masterfrom
filhocf:feature/pypi-publish-workflow
Open

ci: add GitHub Actions workflow for automated PyPI publishing#128
filhocf wants to merge 1 commit intoIBM:masterfrom
filhocf:feature/pypi-publish-workflow

Conversation

@filhocf
Copy link
Copy Markdown

@filhocf filhocf commented Mar 26, 2026

Summary

Adds a GitHub Actions workflow for automated PyPI publishing when version tags are pushed.

Closes #126

Changes

  • .github/workflows/publish.yml — Workflow that:
    • Triggers on v* tags (e.g., v0.37.0)
    • Builds the package with python -m build
    • Publishes to PyPI using twine

Setup Required

  1. Create a PyPI API token at https://pypi.org/manage/account/token/
  2. Add it as a repository secret named PYPI_TOKEN

Usage

After merging, publishing is as simple as:

git tag v0.37.0
git push origin v0.37.0

The workflow will automatically build and publish to PyPI.

Why

  • Current PyPI version lags behind the GitHub master branch
  • Users needing recent fixes must install from git, which is fragile for production
  • Automated publishing ensures PyPI stays in sync with releases

Automated publishing to PyPI when a version tag (v*) is pushed.
Requires PYPI_TOKEN secret to be configured.

Closes IBM#126

Signed-off-by: Claudio Ferreira Filho <filhocf@gmail.com>
@filhocf filhocf force-pushed the feature/pypi-publish-workflow branch from 6e314af to 4b6175c Compare March 26, 2026 16:32
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.

Feature request: Publish elmclient to PyPI with regular releases

1 participant