ci: docker image not built for release tags

[lidel]

Problem

CI job is not triggered on tag creation due to github's limitation, so we don't have ghcr.io/ipshipyard/p2p-forge:v0.1.0
Potential fix is to use PAT from a bot that has write permission to this repo.

Workaround for now

We have images for commit in main branch (ghcr.io/ipshipyard/p2p-forge:main-2024-11-27-a588b19 matching tag v0.1.0) as a workaround

[lidel]

@galargh are you able to set UCI_GITHUB_TOKEN in this repo,
like we have in https://github.com/ipfs/rainbow/ ? 🙏

(my understanding is that is why tag created by CI job does not trigger workflow on that tag -- by default job cant trigger other jobs, but if custom token is used, then it works again)

[lidel]

Token set, let's wait for next release.

• If docker image is automatically created for >v0.1.0 then this can be closed.
• If not, a workaround is to manually dispatch https://github.com/ipshipyard/p2p-forge/actions/workflows/docker.yml against the new release tag.

[lidel]

https://github.com/ipshipyard/p2p-forge/releases/tag/v0.2.0 did not trigger https://github.com/ipshipyard/p2p-forge/actions/workflows/docker.yml, I had to manually dispatch it (https://github.com/ipshipyard/p2p-forge/actions/runs/12418821850).

Fix in #27

Keeping this open until the next release.