-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't pull the docker image #41
Comments
@floitsch Did you find a solution to this in the meantime? I'm having the same issue - it's breaking my release pipeline. |
Ok, seems the maintainer decided to rename their GitHub account, which breaks all of the ~40 CI pipelines on GitHub using this. Even just renaming the reference in the GitHub CI wasn't enough because of caching. I decided to just drop this action, but if you want to use it, renaming to |
I'm very sorry, guys. As @quexten said, I just changed my username. I didn't expect this to cause so many problems. Now I know that my actions were irresponsible. Once again, I am very sorry. The latest version should fix this problem. |
Ah, sorry didn't mean to come off as blaming you just to be clear. I think it's GitHub's fault to allow this. Imo, CI images should just remain, even if the owning account gets renamed or deleted. But for some reason that's not what GitHub does. Thanks for the update! |
Thanks for the fix. I upgraded our workflow. |
When trying to use the action, I get the following error:
The text was updated successfully, but these errors were encountered: