Skip to content

Publish 0.1.29 through configured trusted publisher - #296

Merged
uriahf merged 3 commits into
mainfrom
agent/use-trusted-publisher-workflow
Aug 12, 2026
Merged

Publish 0.1.29 through configured trusted publisher#296
uriahf merged 3 commits into
mainfrom
agent/use-trusted-publisher-workflow

Conversation

@uriahf

@uriahf uriahf commented Aug 12, 2026

Copy link
Copy Markdown
Owner

What changed

  • moves the release job into .github/workflows/python-package.yml, matching the workflow identity already configured as the PyPI trusted publisher
  • gates publishing on a dedicated .github/release-version marker changing on main, so ordinary pushes still do not publish
  • validates that the marker exactly matches the package version before publishing
  • creates the GitHub Release after a successful PyPI upload
  • removes the separate release.yml, whose OIDC token PyPI correctly rejected because that workflow was not the configured trusted publisher

Why

The attempted release.yml publish reached PyPI but failed with invalid-publisher: the token was valid, but its job_workflow_ref did not match the publisher configured for the project. The historical successful publisher is python-package.yml.

Release

This PR adds .github/release-version with 0.1.29. Its merge commit will therefore trigger the release job exactly once and publish the already-bumped rtichoke==0.1.29. Future releases require intentionally changing both the package version and this marker.

@uriahf
uriahf merged commit 504d493 into main Aug 12, 2026
4 checks passed
@github-actions

github-actions Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-08-12 11:19 UTC

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