Skip to content

feat(hvcs-github): support creating GitHub releases as drafts - #1480

Open
sudo-ai-git wants to merge 1 commit into
python-semantic-release:masterfrom
sudo-ai-git:feat/add-draft-release-support
Open

sudo-ai-git wants to merge 1 commit into
python-semantic-release:masterfrom
sudo-ai-git:feat/add-draft-release-support

Conversation

@sudo-ai-git

Copy link
Copy Markdown

Closes #1193. Adds support for creating GitHub releases as drafts (previously only pre-releases were supported).

Change: add draft: bool = False to create_release / create_or_update_release across the HVCS interface (github, bitbucket, gitea, gitlab + base). Backward-compatible. The GitHub provider now sends "draft": draft instead of a hardcoded False; other providers accept+ignore the param (default False preserves current behavior).

Verified: python-semantic-release's github HVCS unit tests pass (179 passed; the test_upload_release_asset_fails errors are pre-existing test-env issues, present on clean master too). Added one assertion update to test_create_or_update_release_when_create_succeeds for the new call signature.

Note: only wires the HVCS-layer param. A follow-up can expose a release_type=draft/CLI+config option if maintainers want it surfaced end-to-end — happy to add if direction is confirmed.

Add a draft param (default False) to create_release / create_or_update_release
across the HVCS interface (github, bitbucket, gitea, gitlab) so GitHub releases
can be created as draft. Backward compatible; threads through the GitHub API's
draft field. 179 unit tests pass (asset-upload test errors are pre-existing).

This branch has not been deployed

No deployments
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.

Add support for draft Github releases

1 participant