Sure, but you're ignoring the rightful and practical use of replacing releases. Having immutable releases introduces complexity, so there are tradeoffs. Since by far most cases are "I made a mistake and need to patch this" I'm good with that.
In your specific Ubuntu example, you could 100% keep immutable 3063 events, so I don't see how this spec prevents you from doing that
Login to reply
Replies (1)
Not ignore it, more suggesting a whoopsie can be fixed without hiding the whoopsie. It doesn't need to be displayed, it's just useful to be available. You see whoopsie, I see opportunity for deceit. Beyond that it could allow the community to rely on relays to keep a watch out for this deceit. There is no reason, for example, github releases couldn't have an edit history. You still get the version the dev wants you to get but as the user, I'd get the opportunity to audit why they rug pulled my package.