[Feature Request] Update release workflow for compatibility with Immutable Releases

[jkylekelly]

With the upcoming launch of GitHub's Immutable Releases (github/roadmap#1138), release assets and tags will be locked against modification once a release is published. This significantly strengthens supply chain security and aligns with best practices for provenance and integrity.

I believe the default behavior of this Action creates a release and immediately publishes it, with assets uploaded only after the release has been published. If users enable Immutable Releases, the Action will fail when attempting to upload assets to the release.

Proposed solution:

• Modify the workflow to initialize the release in draft mode
• Upload assets to the drafted release
• Once complete, publish the release

This will ensure seamless compatibility with Immutable Releases and align with GitHub's recommended practices.

[ncipollo]

Sounds like this is slated to land in Q4 2025, is that correct? Do you have any additional documentation on immutable releases?

The solution you proposed sound reasonable to me but I would like to learn more about how this is implemented on the GitHub side, how you opt in, etc.