Skip to content

Switch to trusted publishing (OIDC) for PyPI releases#453

Merged
yeldarby merged 2 commits intomainfrom
trusted-publishing-roboflow-slim
Apr 15, 2026
Merged

Switch to trusted publishing (OIDC) for PyPI releases#453
yeldarby merged 2 commits intomainfrom
trusted-publishing-roboflow-slim

Conversation

@rvirani1
Copy link
Copy Markdown
Contributor

Summary

  • Replaces twine-based publishing with pypa/gh-action-pypi-publish for both roboflow and roboflow-slim packages
  • Uses GitHub OIDC tokens instead of stored PYPI_USERNAME/PYPI_PASSWORD secrets
  • Adds environment: pypi and permissions: id-token: write to both build jobs

Prerequisites

Before merging, two admin steps are needed on PyPI/GitHub:

  1. Register trusted publishers on pypi.org for both roboflow and roboflow-slim
  2. Create a pypi GitHub environment in the repo settings

Test plan

  • Verify the pypi GitHub environment exists in repo settings
  • Confirm trusted publishers are registered on PyPI for both packages
  • Trigger a test release and verify both packages publish successfully

🤖 Generated with Claude Code

rvirani1 and others added 2 commits April 15, 2026 13:55
…roboflow-slim

Replace twine-based publishing with pypa/gh-action-pypi-publish, which uses
GitHub's OIDC tokens instead of stored username/password secrets. Both the
build and build-slim jobs now declare the pypi environment and id-token: write
permission required for the token exchange.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@yeldarby yeldarby merged commit e576f01 into main Apr 15, 2026
13 checks passed
@rvirani1 rvirani1 deleted the trusted-publishing-roboflow-slim branch April 15, 2026 18:48
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