You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sub-issue of #8. This needs an owner of the openshell project on PyPI.
Why
PyPI trusts only core's release workflow to publish openshell today. #8 publishes from sdk-python's release.yml through trusted publishing (OIDC), so PyPI needs a second trusted publisher for this repository. No API token is created or stored anywhere.
Workflow name: the file name only, not the path. PyPI matches the workflow file that contains the publishing job. In ci: tag lockstep releases and publish to PyPI with trusted publishing #8 that is release.yml itself. For comparison, core's publisher names its reusable wheel-publish.yml, with environment pypi.
Don't remove core's existing publisher. Core may still publish one more wheel (decision 1 in #8). It is removed in ai-openshell/openshell#5287, phase 5.
2. Add the trusted publisher on TestPyPI
TestPyPI has an openshell project too (only 0.0.0.dev0). Its owners are separate from PyPI's.
Under Collaborators on the PyPI project, check who can manage it once publishing moves here. Consider adding an SDK maintainer as a second owner, so the project doesn't depend on one account. Every owner needs 2FA.
Done when
pypi.org lists the publisher ai-openshell/sdk-python, release.yml, environment pypi. Core's publisher is unchanged.
test.pypi.org lists the same publisher with environment testpypi, or this issue says why not.
Activity
[-]Python SDK migration: PyPI trusted publisher for sdk-python[/-][+]ci: PyPI trusted publisher for sdk-python[/+]pimlock commentedon Nov 8, 2026
Trusted publisher has now been added:
pimlock commentedon Nov 9, 2026
The environment is now in place as well: #10
We decided to skip
testpypifor now.