Post #4284088

@mgorny@social.treehouse.systems This is definitely a bug on GitHub's side and I believe it's been rolled back. My team runs that service, so it definitely was not intentional. When we make intentional user-visible changes to SSH, we announce them publicly, as with our previous algorithm changes.