Re:Git archive checksums may change
by phphphphp on Monday January 30, 2023 @05:30PM
(#34587441)
Consumers often mistake hasn’t changed for a commitment to never change: any sufficiently large product will be littered with these kind of implicit commitments made by the product to consumers that nobody has visibility into. You’re unfortunate that we were all relying on this commitment you’ve never made, but the quick reversion is the best we can hope for. People will theorise how this could have been avoided but c’est la vie — easy mistake that you’ve responded well to.
[ Parent
| on HN ]
At this point they'll be stuck on old git for all of eternity unless they just roll their own archive/compress step out of band so the old hashes still work. Yikes.
They could also brownout the implied contract over a longer timespan.
They could use the old behavior for archives in which all the inputs predate the changeover.
New git has a flag for keeping the old behavior, so it's not as bad.
Hyrum's Law:
With a sufficient number of users of an API, it does not matter what you promise in the contract: all observable behaviors of your system will be depended on by somebody.
Re:Git archive checksums may change
by drexlspivey on Monday January 30, 2023 @06:22PM
(#34588147)
Re:Git archive checksums may change
by modderation on Tuesday January 31, 2023 @06:24AM
(#34593809)
Incidentally, I'm still waiting for GitHub to implement Spacebar Heating: https://m.xkcd.com/1172/
Re:Git archive checksums may change
by nickitolas on Monday January 30, 2023 @05:50PM
(#34587750)
FWIW according to https://github.com/bazel-contrib/SIG-rules-authors/issues/11... a commitment was made, although in an exchange in some support ticket, and not in documentation.