Skip to content

use trusted publishing flow rather than pypi token #674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 3, 2025

Conversation

edavidaja
Copy link
Collaborator

Following the directions here: https://docs.pypi.org/trusted-publishers/using-a-publisher/

  • Publishing from main.yml has been set in PyPI
  • the workflow has id-token: write permissions

removing the token means the workflow will obtain the needed oidc token at publish time.

Copy link

github-actions bot commented May 29, 2025

PR Preview Action v1.6.1
Preview removed because the pull request was closed.
2025-06-03 17:05 UTC

@edavidaja edavidaja requested a review from a team May 29, 2025 20:33
Copy link

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
5096 3828 75% 0% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 16f2957 by action🐍

Copy link
Contributor

@nealrichardson nealrichardson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:shipit:

@edavidaja edavidaja merged commit 1108457 into main Jun 3, 2025
15 checks passed
@edavidaja edavidaja deleted the oidc-trusted-publisher branch June 3, 2025 17:05
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