Alex Crichton (Oct 20 2025 at 15:39): Alex Crichton (Oct 20 2025 at 15:39):I messed up, doing a 38.0.1 release now. Will post more here when out of a meeting
Alex Crichton (Oct 20 2025 at 15:42):tl;dr; -- I saw this button in our github settings -- Screenshot 2025-10-20 at 10.42.05 AM.png
Alex Crichton (Oct 20 2025 at 15:42):I checked that thinking "oh surely this would be good for us"
Alex Crichton (Oct 20 2025 at 15:42):turns out: no, it is not, and it broke the release. I've un-checked the box and the 38.0.1 release is to fix that
Alex Crichton (Oct 20 2025 at 16:48):Also, my mistakes here means that the 38.0.0 release is deleted (I thought I could recreate it in CI) and can never be created again (apparently github remembers it was an "immutable" release).
Now though 38.0.1 is out and should be good
Brett Cannon (Oct 20 2025 at 19:15):Alex Crichton said:
turns out: no, it is not, and it broke the release. I've un-checked the box and the 38.0.1 release is to fix that
Out of curiosity, how did it break the release? Did you upload files post-release (I'm assuming uploading to a draft release is okay)?
Alex Crichton (Oct 20 2025 at 19:16):Yeah it looks like automation makes a release, then publishes artifacts, and that separation of steps broke things
Alex Crichton (Oct 20 2025 at 19:17):it would probably make sense to do the pre-release idea and require a human to go hit "publish"
Till Schneidereit (Oct 21 2025 at 13:33):oh, but this made me revisit the docs and our setup, and realize that immutable releases should be working for us. I thought they would make the moving dev release impossible, but since that's a prerelease it's fine to mutate
Till Schneidereit (Oct 21 2025 at 13:35):@Alex Crichton why would this require a human to publish? I think we should be able to create releases as drafts, attach artifacts, then mark them as final to make them immutable. Or do you just want to have someone in the loop in case something goes wrong and the, now immutable, release would be wrong?
Alex Crichton (Oct 21 2025 at 14:34):Yeah mostly just the latter part, but I don't think it would be required. If starting as a draft, attaching things, then making public -- if that works then we should switch to doing that
Till Schneidereit (Oct 21 2025 at 15:53):looks like that should work: https://docs.github.com/en/code-security/supply-chain-security/understanding-your-software-supply-chain/immutable-releases#best-practices-for-publishing-immutable-releases
Alex Crichton (Oct 22 2025 at 14:57):Screenshot 2025-10-22 at 9.57.03 AM.png
ok immutable things are now enabled
Last updated: Dec 06 2025 at 06:05 UTC