creating a draft release
See original GitHub issueis it possible to create a draft only release?
that is, run the whole process, but keep the release labelled as “draft” in github (otherwise referred to as “pre-release” in GitHub’s UI and not to be confused with semantic-release
’s prerelease
flag on branches)
I looked through issues and examples in this repo and there was no such example, the only reference to “draft” was in-line and doesn’t seem to be specifically flaggable …
to further distinguish from workflow with prerelease
flag, I intend to continue using a single main branch and not looking to implement the workflows as described rather, just make the final github release flagged as “draft” upon publishing.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Managing releases in a repository - GitHub Docs
Creating a release · On GitHub.com, navigate to the main page of the repository. · To the right of the list of files,...
Read more >Cannot create Draft release. The draft release does not have ...
Steps: Navigate to Pipeline > Releases; Select and edit a release definition; Confirm that the release includes tasks and variable definitions.
Read more >Prepare and roll out a release - Play Console Help
Select the Releases tab, then Edit. Review your draft release, make any necessary additional changes, and select Save. Select Review release.
Read more >10. Creating a Release - VisIt User Manual - Read the Docs
If you go to GitHub and go to the Releases tab you will see the newly created tag. Now you are ready to...
Read more >Release Drafter - Probot
Install the Release Drafter GitHub App into the repositories you wish to create releases in. · Add a .github/release-drafter.yml configuration file to each ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
to state in another lens: while
semantic-release
can and should be opinionated on the semantic versioning workflow, I believe additional choices on how the “release” (in GitHub’s terminology, and GH entity named “release”) should be left to the user …e.g.
draft=true
and/orprerelease=true
on the Release Entity …expectation is be able to use
semantic-release
with GitHub releases and still tag every tag in GitHub asprerelease
/draft
if I choose to, regardless of the versioning schema exposes for numbering (-rc
,-beta
, or none at all)the real-world-use-case I’m attempting to enable at the moment:
release.created
withtype = prereleased
: CI publishes version to new environment[version].domain.tld
prerelease
flagrelease.created
withtype = released
: CI promotes this version to productionI am trying to integrate
semantic-release
with electron-builder and was also looking for this option. My goal is to havesemantic-release
create a draft release and thenelectron-builder
will upload the artifacts to that release. Once everything is done the release will be published.This seems like a simple thing to add as most of the code is already there. I would be willing to create a PR for this which implements a
draft
option like @skn-bot mentioned.