Skip to content

docs(release): clarify PyPI publisher binding and automatic release #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Si40Code merged 1 commit into from
Sep 23, 2026
Merged

docs(release): clarify PyPI publisher binding and automatic release #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 11 additions & 6 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,9 +13,15 @@ with these values:
- Workflow: `publish-python.yml`
- Environment: `pypi`

Configure the GitHub `pypi` environment with required reviewers, prevent
self-review, and restrict it to protected release tags. The workflow does not
use a long-lived PyPI token.
The GitHub `pypi` environment has no required reviewers and allows `main` and
`v*` release tags. Publication starts automatically after the release checks
pass. The workflow does not use a long-lived PyPI token.

Register these exact values under the existing `calle-ai` project's Publishing
settings on PyPI, not only in GitHub. An `invalid-publisher` response means
PyPI has no publisher matching the repository, workflow and environment claims.
Confirm the project and binding, then retry the failed publish job only after
checking that the candidate version is still absent from PyPI.

## Prepare a release

Expand All @@ -40,9 +46,8 @@ files, and fresh wheel and source-distribution installs.

1. Create a `vX.Y.Z` tag on the intended commit from `main`.
2. Publish a non-prerelease GitHub Release for that tag.
3. Approve the `pypi` environment deployment after checking the tag, version,
commit, changelog, and build result.
4. Confirm that the publish and post-publish verification jobs complete.
3. Confirm that the publish and post-publish verification jobs complete;
no separate environment approval is required.

The workflow rejects a tag that does not exactly match `vX.Y.Z`, differs from
the version in `pyproject.toml`, or points to a commit not contained in
Expand Down
Loading