-
-
Notifications
You must be signed in to change notification settings - Fork 536
Open
Description
π Pitch
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.
Metadata
Metadata
Assignees
Labels
No labels