Skip to content

ci: publish to PyPI via OIDC trusted publishing - #33

Merged
toddbaert merged 1 commit into
mainfrom
ci/pypi-trusted-publishing
Nov 6, 2026
Merged

toddbaert merged 1 commit into
mainfrom
ci/pypi-trusted-publishing

Conversation

@toddbaert

Copy link
Copy Markdown
Collaborator

Switches the PyPI publish step from the API token to OIDC trusted publishing (the token secret is kept for now in case we need to revert).

Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
Copilot AI balanced review requested due to automatic review settings November 5, 2026 19:45

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🔵 Needs a closer look

Publishing depends on external PyPI trusted-publisher registration for this repository, release.yml, and the publish environment, which cannot be confirmed from the PR.

No open issues 🎉

What changed in this PR

Switches the release workflow’s PyPI publishing step from API-token authentication to OIDC trusted publishing.

Changes:

  • Grants the publishing job id-token: write permission.
  • Removes the token password input from the PyPI publish action while leaving attestations disabled.
File Description
.github/​workflows/​release.yml Enables OIDC authentication for PyPI publishing and removes the API-token input.

Review effort: Balanced

@toddbaert
toddbaert merged commit 9bf0fbb into main Nov 6, 2026
18 checks passed
@toddbaert
toddbaert deleted the ci/pypi-trusted-publishing branch November 6, 2026 13:08
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.

3 participants