Heroku's GitHub integration has been stopped due to attack. Are you affected?

Luke Cartwright - Apr 16 '22 - - Dev Community

This morning heroku blocked all github integrations 'until further notice' (see the note here).

This means that users can't deploy new features to heroku via automatic deployments. I only found this out after an email was sent at 4am this morning informing me of this.

I am now fully understanding the impact.

When I push features to Github, there is an automatic deployment to Heroku. This returned an error of unauthorised. I went to the Heroku dashboard and saw I needed to reconnect my Github. Odd I thought.So I disconnected and tried to reconnect but then I get an internal error. Brilliant.

So now 'until further notice', I am unable to deploy any new features to my heroku app. There is a suggestion to deploy directly via git but that is a big work around to set up the heroku remote and use heroku instead of Github.

Surely I'm not the only one affected. Anyone else having these issues?

[Update] Upon further research, Heroku has blocked current github tokens and any created ones to protect against future attacks at the moment. It was noticed an attacker had stolen some Github access tokens to get private repos on github. To protect all users this integration between github and heroku has been stopped until this has been fixed. Please read more at:
https://github.blog/2022-04-15-security-alert-stolen-oauth-user-tokens/

. . . . . . . . . . . . . . . . . . . . .