Update Action broken [workaround found for v2.0.72]

[ronsonm]

Check update action broke on 25 okt
https://github.com/factoriotools/factorio-docker/actions/runs/18804265960

Error log:

Fetching the repository
/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +3221b1db5b6df77cd45ffa14381188150049fcec:refs/remotes/origin/master
Error: fatal: could not read Username for 'https://github.com/': terminal prompts disabled
The process '/usr/bin/git' failed with exit code

This is probably an expired access token I presume?
If so could one of the maintainers update this token? Factorio pushed an update today to 2.0.72 so this action is required to get the container working again.

[ronsonm]

Confirmed that it is an expired key. I've created a fork and adjusted the key there.
https://github.com/ronsonm/factorio-docker

I've also created my own docker repo with the new updated version [2.0.72].
I was able to create a container and push that to dockerhub, feel free to use that as a workaround until the maintainers have had a chance to fix the expired key.
https://hub.docker.com/r/ronsonm/factorio

[yghern]

You could also use latest tag to use experimental version (which currently is 2.0.72).

[ronsonm]

Well yes, latest would run a 2.0.72 version but that would be the experimental version, not the latest stable one. (I think)
I personally try to stay away from experimental versions and I noticed the fix was easy enough so I went for it.

[jessielw]

Confirmed that it is an expired key. I've created a fork and adjusted the key there. https://github.com/ronsonm/factorio-docker

I've also created my own docker repo with the new updated version [2.0.72]. I was able to create a container and push that to dockerhub, feel free to use that as a workaround until the maintainers have had a chance to fix the expired key. https://hub.docker.com/r/ronsonm/factorio

Thanks using the fork for now!

[putnam]

There is no reason for there to be a token defined in the action in the first place. That would only be needed if you're checking out a private repo. Because it is defined, the expired token is now breaking the action. But updating the token means it will break again in the future. It builds fine without it defined, so the default Github-provided token is used.