Skip to content

Commit ff59a92

Browse files
committed
docs: clarify pypi trusted publishing setup
1 parent 9aacd12 commit ff59a92

1 file changed

Lines changed: 9 additions & 1 deletion

File tree

RELEASE.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,11 @@ least one backend integration.
6969
## Registry identity notes
7070

7171
PyPI Trusted Publishing is preferred once the repository is ready for public
72-
release. Configure a pending publisher for:
72+
release. Because `calle-ai` has not been published yet, configure a pending
73+
publisher first. TestPyPI and PyPI are separate registries, so configure the
74+
publisher separately in each registry you plan to use.
75+
76+
Configure the pending publisher for:
7377

7478
- Owner: `CALLE-AI`
7579
- Repository: `server-sdk-python`
@@ -81,3 +85,7 @@ release. Configure a pending publisher for:
8185
When using Trusted Publishing, run the workflow with auth
8286
`trusted-publishing`. When using API tokens, run it with auth `token` and
8387
configure `TEST_PYPI_API_TOKEN` or `PYPI_API_TOKEN`.
88+
89+
If the package already exists on PyPI later, use the project's Publishing page
90+
to add or update the trusted publisher with the same owner, repository, workflow
91+
filename, and environment.

0 commit comments

Comments
 (0)