Repository navigation
Publish a release when its pull request merges - #41
Closed
proxymeshai wants to merge 5 commits into
Closed
proxymeshai wants to merge 5 commits into
proxymeshai wants to merge 5 commits into
Conversation
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
Bot
force-pushed
the
cursor/one-step-release-79af
branch
from
November 12, 2026 22:20
29875de to
e8d1e42
Compare
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]>
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]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Releasing is one merge, in the same shape as the other ProxyMesh repos.
Prepare release, run from
main, bumpspyproject.tomlanddocs/conf.py, moves the changelog Unreleased section to a dated heading, and runs the version check and package build before it pushes. It opensrelease/X.Y.Zfor a person to merge. A pull request opened withGITHUB_TOKENdoes not startpull_requestworkflows, so those checks have to run in that job.Merging to
mainpublishes with the existing PyPI trusted publisher and GitHub environmentpypi(unchanged), then tagsvX.Y.Zand creates the GitHub Release from the changelog section. A version already on PyPI fails the upload.gh release viewskips creating a tag that already exists.Rebased onto
mainafter #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 alreadyvX.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.