←back to thread

Immutable releases are now generally available on GitHub

(github.blog)
151 points fastest963 | 2 comments | 31 Oct 25 13:59 UTC | HN request time: 0.001s | source
Show context
hoistbypetard ◴[31 Oct 25 14:45 UTC] No.45772532[source]▶
My instant reaction was: "Wait?! They weren't immutable before?"

I'm glad they're doing this, and it's an unpleasant surprise that they didn't already work this way. I don't understand why they allow mutable releases.

replies(6): >>45772557 #>>45772741 #>>45772761 #>>45773634 #>>45773953 #>>45774010 #
danudey ◴[31 Oct 25 16:05 UTC] No.45773634[source]▶
We've had a few issues in the past where a file wasn't updated during the release process, requiring us to re-publish one small change. It's not optimal, but given the nature of our release process being long and complex it's a lot easier to fix the asset in three minutes rather than spend an entire day re-building and re-publishing an entire release, updating our docs, etc. just because of one line in one file that wasn't updated correctly.
replies(1): >>45773767 #
1. hoistbypetard ◴[31 Oct 25 16:17 UTC] No.45773767[source]▶
I guess I'm just lucky, then, to have only dealt with release processes where it's no big deal to do a bump from 5.0.0 to 5.0.1 so I can address something like that. Some of them were long and complex, but they were scripted to the point where it was uniformly better to jump by a 0.0.1 than risk having two different releases with the exact same version # in the wild.
replies(1): >>45776056 #
2. tuhgdetzhh ◴[31 Oct 25 19:58 UTC] No.45776056[source]▶
Yeah, depending on the size of the project you could end up having thousands of users downloading and installing 5.0.0 and then complaining.