2 ms·
For these major changes that break builds across the entire industry, why does Github insist on rolling out the change first and then publishing a blog post not
by lopkeny12ko 4y ago
For these major changes that break builds across the entire industry, why does Github insist on rolling out the change first and then publishing a blog post notice about it? Is it really so hard to give a week of advance notice?
It wasn't even that long ago that Github changed the checksums of git tarballs which also broke builds everywhere. All we got was a "oh btw we changed the archive behavior" blog post after the change went live [0].
[0] https://github.blog/changelog/2023-01-30-git-archive-checksums-may-change/ https://github.blog/changelog/2023-01-30-git-archive-checksu...
- ihattendorf 4y agoI think changing a key because it was compromised is a little different compared to changing archive behavior, and can be afforded a little leeway with advance notice.
- 8organicbits 4y agobroken builds << migrating off a leaked key I'm upset they haven't sent out an email to every user. This affects their entire usebase and basically everyone needs to take manual action to continue working. If you haven't seen the news then you'll see failed builds/git commands.