alexcrichton opened PR #11901 from alexcrichton:immutable-release to bytecodealliance:main:
[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
<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested wasmtime-default-reviewers for a review on PR #11901.
alexcrichton requested pchickey for a review on PR #11901.
alexcrichton commented on PR #11901:
And full disclosure, I've no idea how to test this JS so I haven't tested this. My plan is to issue 38.0.2 with this as a trial run. Probaby 38.0.3 as well once something inevitably goes wrong.
pchickey submitted PR review.
alexcrichton merged PR #11901.
Last updated: Dec 06 2025 at 07:03 UTC