Skip to content

ci: move to PyPy Trusted Publishing - #81

Merged
qkaiser merged 1 commit into
masterfrom
trusted-publishing
Sep 15, 2026
Merged

qkaiser merged 1 commit into
masterfrom
trusted-publishing

Conversation

@qkaiser

@qkaiser qkaiser commented Aug 31, 2026 •

Copy link
Copy Markdown
Contributor

Move to PyPi Trusted Publishing using an ID token instead of relying on a fixed token.

Split the release workflow in 3 steps:

  • build phase with uv, followed by an artifact upload
  • publication to PyPi by pulling built artifacts first
  • publications to Test PyPi by pulling built artifacts first

This follows official guidance from
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/

@qkaiser qkaiser self-assigned this Aug 31, 2026
@qkaiser
qkaiser marked this pull request as draft August 31, 2026 09:33
@qkaiser
qkaiser marked this pull request as ready for review August 31, 2026 09:54
@qkaiser
qkaiser requested a review from martonilles August 31, 2026 10:00
@martonilles

Copy link
Copy Markdown
Contributor

looks good, but conflicts with recent publish fixes

@qkaiser
qkaiser force-pushed the trusted-publishing branch 3 times, most recently from 21c0ec3 to a7ddca2 Compare September 15, 2026 10:02
@martonilles

Copy link
Copy Markdown
Contributor

One more thing as I am looking at the details, why do we need this ci: standardize package publishing. After looking at our other repos we do not do it there, what is the use-case here?

@qkaiser
qkaiser enabled auto-merge September 15, 2026 12:38
Move to PyPi Trusted Publishing using an ID token instead of relying on
a fixed token.

Split the release workflow in 3 steps:
- build phase with uv, followed by an artifact upload
- publication to PyPi by pulling built artifacts first
- publications to Test PyPi by pulling built artifacts first

Publication to PyPi happens when pushing a tag to master.

Publication to Test PyPi happens when pushing commits to master.

This follows official guidance from
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
@qkaiser

qkaiser commented Sep 15, 2026

Copy link
Copy Markdown
Contributor Author

One more thing as I am looking at the details, why do we need this ci: standardize package publishing. After looking at our other repos we do not do it there, what is the use-case here?

I got rid of it. Remnants of old experiments. Branch is cleaner now, single commit. Sorry about that.

@qkaiser
qkaiser added this pull request to the merge queue Sep 15, 2026
Merged via the queue into master with commit 9df345f Sep 15, 2026
2 checks passed
@qkaiser
qkaiser deleted the trusted-publishing branch September 15, 2026 12:59
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.

2 participants