-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add 'draftRelease' option #379
Conversation
Any plans to merge/review this? Friendly ping, @gr2m |
Yes, as soon as we find the time to review it, I cannot tell when that will be right now, sorry |
No problem! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm waiting for this, can you please prioritize?
Maybe until there's time to review it it could be published on a draft release channel? 😄 Some of us could give feedback, add fixes if needed, etc. |
This would be useful for us too. Happy to help if that's possible. |
This would also be useful to us. We'd like to use I'd also be happy to help test and review code if that's needed. This is pretty much exactly like the implementation I have locally. |
I am also interested in this option. I have a case where I have several assets that need to be built on different operating systems. I can't have them available at release time and associate them with |
Thank you all for your patience, for sharing your use cases and for your offers to help. I know it has been a long time coming. I finally got around to review it and it all looks good. I'll merge and release it shortly |
🎉 This PR is included in version 8.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 9.0.0-beta.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
This PR adds a new
draftRelease
option which, when set to true, will create a GitHub draft release instead of publishing an actual GitHub Release. The option defaults to false and will thus not impact current users.Fixes #275