Skip to content

Publish a release when its pull request merges - #41

Closed
proxymeshai wants to merge 5 commits into
mainfrom
cursor/one-step-release-79af
Closed

proxymeshai wants to merge 5 commits into
mainfrom
cursor/one-step-release-79af

Conversation

@proxymeshai

@proxymeshai proxymeshai commented Nov 12, 2026 •

Copy link
Copy Markdown
Collaborator

Releasing is one merge, in the same shape as the other ProxyMesh repos.

Prepare release, run from main, bumps pyproject.toml and docs/conf.py, moves the changelog Unreleased section to a dated heading, and runs the version check and package build before it pushes. It opens release/X.Y.Z for a person to merge. A pull request opened with GITHUB_TOKEN does not start pull_request workflows, so those checks have to run in that job.

Merging to main publishes with the existing PyPI trusted publisher and GitHub environment pypi (unchanged), then tags vX.Y.Z and creates the GitHub Release from the changelog section. A version already on PyPI fails the upload. gh release view skips creating a tag that already exists.

Rebased onto main after #38 and #39. The changelog keeps main's Unreleased notes. This PR does not bump the version.

#37 (Release 0.2.4) already merged and published. A later release/* pull request, including one opened by hand the way #37 was, publishes when it merges. Existing tags are already vX.Y.Z.

Don't make Release check a required check: release PRs are opened with GITHUB_TOKEN, so it doesn't run on them unless you close and reopen the PR.

Open in Web Open in Cursor 

Prepare release bumps the manifests, runs the checks, and opens the pull request. Merging release/X.Y.Z publishes to PyPI and tags vX.Y.Z.

Co-authored-by: ProxyMesh AI <[email protected]>
@cursor
cursor Bot force-pushed the cursor/one-step-release-79af branch from 29875de to e8d1e42 Compare November 12, 2026 22:20
Cursor and others added 2 commits November 12, 2026 22:30
Drop the stale minor-version note, and skip the unused lookup checkout and GitHub Release Python setup.

Co-authored-by: ProxyMesh AI <[email protected]>
Trusted publishing uses OIDC only. Leave the PyPI publisher environment field blank.

Co-authored-by: ProxyMesh AI <[email protected]>
Cursor and others added 2 commits November 13, 2026 00:13
Document editing the publisher environment to blank and removing unused GitHub environments after publish.

Co-authored-by: ProxyMesh AI <[email protected]>
Trusted publishing setup stays unchanged; docs drop publishing owner steps.

Co-authored-by: ProxyMesh AI <[email protected]>
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