Since this was essentially a potential organizational administrator account takeover security vulnerability, I can see why this got a write up. And as others ha

Since this was essentially a potential organizational administrator account takeover security vulnerability, I can see why this got a write up. And as others have said, it's impressive. Github Actions has had many problems that affect many people this year alone. While the missed deadlines and stress for people can't be quantified by Github, they are happening. I'd urge Github to take ongoing service interruptions in Github Actions more seriously. I hope Github will take a stronger stance on providing customer communication on migration timelines between Packages and Container Registry. Just because a bug or service interruption doesn't risk random user session exposure doesn't mean it isn't important to communicate about and describe how the business is working to prevent it from happening again.