Add PyPI publish CD (release-labelled PR -> build & upload)#296
Open
poissoncorp wants to merge 1 commit into
Open
Add PyPI publish CD (release-labelled PR -> build & upload)#296poissoncorp wants to merge 1 commit into
poissoncorp wants to merge 1 commit into
Conversation
Adds two GitHub Actions workflows: - prepare-release.yml: manual dispatch; bumps version= in setup.py and RequestExecutor.CLIENT_VERSION in ravendb/http/request_executor.py (with .postN/.devN/rcN suffixes stripped from CLIENT_VERSION), then opens a PR labelled "release". - publish.yml: on merge of the labelled PR, builds sdist+wheel, uploads to PyPI via twine, then creates the version git tag + GitHub release. Requires repo secret PYPI_API_TOKEN and the "Allow GitHub Actions to create and approve pull requests" setting enabled.
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
1 participant
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.
What
Adds a two-stage, PR-gated CD pipeline that publishes
ravendb(the Python client) to PyPI via GitHub Actions.prepare-release.yml(manual): run from the Actions tab with aversioninput. Bumps bothversion=insetup.pyandRequestExecutor.CLIENT_VERSIONinravendb/http/request_executor.py(matching how releases are bumped today), then opens a PR labelledrelease.setup.pygets the full PEP 440 version (incl. any.postN/.devN/rcNsuffix);CLIENT_VERSIONgets the clean release number only — e.g. a7.2.1.post1hotfix keepsCLIENT_VERSION = "7.2.1", exactly as in commit 80e29f9.publish.yml: when a PR carrying thereleaselabel is merged, buildssdist+bdist_wheel, uploads to PyPI viatwineusing__token__, then creates the<version>git tag + GitHub release (matching the existing7.2.xtag convention, novprefix). Also runnable manually as a fallback.How to release
7.2.3.setup.pyandrequest_executor.pyshould be bumped).releaselabel) → the package publishes automatically.Remove the
releaselabel before merging to merge without publishing.Required setup (one-time)
PYPI_API_TOKEN— a project-scoped PyPI API token.Notes
GITHUB_TOKENdoes not auto-trigger).publish.ymlevaluates on every closed PR but only proceeds for merged +release-labelled PRs.twine --skip-existingkeeps re-runs idempotent.RavenClient.yml(tests) is untouched.