Containers are not tagged by release tag when a new release is made #934
Labels
good first issue
Good for newcomers
Milestone
Comments
|
Per 2025-04-07 standup, this isn't critical. I'm moving this out of the active milestones but obviously great if someone just does it. |
|
Hi @BigLep, Can i work on this issue? |
|
Feel free to 👍 |
sumitvekariya
added a commit
to sumitvekariya/go-f3
that referenced
this issue
May 24, 2025
This commit fixes issue filecoin-project#934 where the container publishing CI workflow only tagged containers by commit SHA and not by the release tag. The primary issue was an incorrect nesting of the `workflow_run` trigger within the `push` trigger in the `.github/workflows/publish-ghcr.yml` file. This prevented the workflow from being correctly triggered upon the completion of the `Releaser` workflow, which is responsible for creating Git tags and GitHub releases. This change corrects the workflow trigger syntax, ensuring that the container build and publish workflow runs after a release is made, allowing it to use the semantic version tag for the container image.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like the container publishing CI workflow only tags containers by commit SHA. Investigate why on release containers are not tagged by the release tag.
The text was updated successfully, but these errors were encountered: