We noticed this yesterday trying to release a minor bug fix. As of this morning it appears to still be broken. It's hard to see how it could be anything other

We noticed this yesterday trying to release a minor bug fix. As of this morning it appears to still be broken. It's hard to see how it could be anything other than an issue on Docker's side - we are seeing a 500 after all. I need to unblock development ASAP so for now the workaround for us has been to migrate our container registry to Azure.