Skip to content

Add PyPI Trusted Publishing workflow; bump to 1.2.0#100

Merged
Robaina merged 1 commit into
mainfrom
pypi-trusted-publishing
Jun 19, 2026
Merged

Add PyPI Trusted Publishing workflow; bump to 1.2.0#100
Robaina merged 1 commit into
mainfrom
pypi-trusted-publishing

Conversation

@Robaina

@Robaina Robaina commented Jun 19, 2026

Copy link
Copy Markdown
Owner

Sets up automated publishing of Pynteny to PyPI via Trusted Publishing (OIDC — no API tokens or secrets stored), and bumps the version for the first pip-only release.

Changes

  • .github/workflows/publish.yml: on every published GitHub Release, builds the sdist + wheel, runs twine check, and uploads to PyPI using pypa/gh-action-pypi-publish with OIDC. Uses the pypi environment and id-token: write.
  • Version 1.1.21.2.0 (first conda-free release; v1.1.2 was already tagged for the old conda build).

Verified locally

python -m build + twine check both pass; the wheel bundles config.json, installs in a clean venv, reports 1.2.0, and pynteny --help works.

Required one-time setup on PyPI (before the first release)

Add a pending publisher at https://pypi.org/manage/account/publishing/ :

  • PyPI project name: pynteny
  • Owner: Robaina
  • Repository: Pynteny
  • Workflow filename: publish.yml
  • Environment name: pypi

After this PR is merged and the publisher is configured, publishing is triggered by creating a GitHub Release tagged v1.2.0.

🤖 Generated with Claude Code

- .github/workflows/publish.yml: on each published GitHub Release, build the
  sdist+wheel and upload to PyPI via Trusted Publishing (OIDC, no API tokens).
  twine check runs before publishing. The publish job uses the `pypi`
  environment and `id-token: write`.
- Bump version 1.1.2 -> 1.2.0 (first pip-only / conda-free release; v1.1.2 was
  already tagged for the old conda build).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Robaina Robaina merged commit e3b75c5 into main Jun 19, 2026
6 checks passed
@Robaina Robaina deleted the pypi-trusted-publishing branch June 19, 2026 13:15
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