Repository navigation
Allow creating Github Release in Draft #322
Description
Hi,
I use this action in several projects where there is no NPM publishing, but a Github Release is the desired platform.
In these instances it is often beneficial to have the action create a "Draft" release in order to append binaries or check/test the release before publishing. An optional input that allows for the Github release that is created to be "draft" would be very useful.
Activity
alexaka1 commentedon Dec 22, 2025
This would be beneficial if one wants to use immutable releases, but customize the created release outside of changesets created one. https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/immutable-releases#best-practices-for-publishing-immutable-releases
soleuniverse101 commentedon Jun 26, 2026
I would like to add to this that it would be nice to be able to append the changelog generated by changesets to the body of the release, or have an option to specify a template that includes the changelog in case we want the body of the release containing some text before / after the changelog (e.g. instructions to install)
Andarist commentedon Jun 26, 2026
If we find the time - we'll be exploring this soon, once Changesets v3 ships.
necipallef commentedon Oct 6, 2026
Hi team! I see that there is already a PR ready to go. I am looking forward to this being implemented because this is preventing us from using immutable releases in our projects.