Skip to content

ci: publish xrobot to PyPI with Trusted Publisher - #114

Open
Jiu-xiao wants to merge 1 commit into
devfrom
ci/pypi-trusted-publisher-20261029
Open

Jiu-xiao wants to merge 1 commit into
devfrom
ci/pypi-trusted-publisher-20261029

Conversation

@Jiu-xiao

Copy link
Copy Markdown
Member

Replace the long-lived TOKEN secret with PyPI Trusted Publishing (OIDC), as libxr already does in LibXR_CppCodeGenerator.

  • Publish job gets id-token: write; password is removed.
  • Environment stays TOKEN (must match the trusted publisher config).

Do not merge before the PyPI xrobot project lists a trusted publisher: owner xrobot-org, repo XRobot, workflow python-publish.yml, environment TOKEN. After the next release succeeds, delete the old PyPI token and the TOKEN secret.

🤖 Generated with Claude Code

@Jiu-xiao
Jiu-xiao changed the base branch from master to dev October 29, 2026 20:41
Use OIDC (id-token) instead of the long-lived TOKEN secret, as the libxr
package already does. The PyPI project must list this repository, the
python-publish.yml workflow and the TOKEN environment as a trusted
publisher before the next release.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Jiu-xiao
Jiu-xiao force-pushed the ci/pypi-trusted-publisher-20261029 branch from 23bbdc3 to bde513b Compare October 29, 2026 20:42

This branch has not been deployed

No deployments
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