Skip to content

Conversation

@alexcrichton
Copy link
Member

@alexcrichton alexcrichton commented Oct 22, 2025

Backport of #11902 and #11906 to the 36.0.x branch.

[Immutable Releases] look to be a relatively new feature on github which
is a natural fit for us where we have no need to modify release assets
after creation. My failed attempt to enable this earlier turned out to,
expectedly, not work. This commit is an attempt to make things work.
Specifically releases are now created as a draft initially, then release
assets are attached, and finally it's automatically marked as a
non-draft. While one could make a reasonable argument that a human
should be involved in making the release a non-draft there's also
something nice about just hitting merge on a PR and letting the release
ride through CI.

[Immutable Releases]: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/immutable-releases
This is an attempt to fix a bug with bytecodealliance#11901 where for 38.0.2 a draft
release was made but it wasn't published due to a bug, so hopefully
it'll be less buggy next time.
@alexcrichton alexcrichton requested a review from a team as a code owner October 22, 2025 17:29
@alexcrichton alexcrichton requested review from fitzgen and removed request for a team October 22, 2025 17:29
@alexcrichton alexcrichton enabled auto-merge (squash) October 22, 2025 17:29
@alexcrichton alexcrichton merged commit f554fa9 into bytecodealliance:release-36.0.0 Oct 22, 2025
167 checks passed
@alexcrichton alexcrichton deleted the release-36.0.0 branch October 22, 2025 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants