8 ms·
Deletion creates a hole. The hole can be filled by something else. This is a form of mutation. What you probably want instead is one-way revocation. You place
by kbolino 1y ago
Deletion creates a hole. The hole can be filled by something else. This is a form of mutation.
What you probably want instead is one-way revocation. You place a permanent marker that says "do not use this release because it is {broken, malicious, ...}".
- eviks 1y agoNo, you can make the whole immutable, that is if a tag in an immutable repo was used and deleted, it can't be used again
- kbolino 1y agoAn "immutable hole" just sounds like a "revocation marker" without an accompanying message, so I don't think we're really asking for different things, here. Nevertheless, ordinary tag deletion -- what git natively supports -- can't be supported directly.
- eviks 1y agoThe difference is the unavailability of content. For example, you attach the wrong binary and want to avoid confusion/mistaken downloads either manual or via tools that don't support your markers, in the most direct way - by deleting the binary from release. But you can't fix it if you opted into the security benefits of no hidden mutation