Prevent forks from trying (and failing) to push latest images to GHCR #11213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed on a recent commit to
main
on my personal fork that it's trying/failing to push images to GHCR due to permissions errors: https://github.com/jeffwidman/dependabot-core/actions/runs/12593801189There's no point in forks doing that--they will never have the proper permissions to publish images to the real GitHub GHCR Dependabot image.
We already prevent forks from trying to publish the base updater image here:
dependabot-core/.github/workflows/images-updater-core.yml
Line 14 in 53178c5
We just forgot to also do it in this workflow for the final ecosystem images.
So this rectifies that.