build: point release artifacts at scaleup-technologies fork - #2
Merged
Conversation
goreleaser was hardcoded to push images to ghcr.io/inovex and create GitHub releases under inovex/external-dns-openstack-webhook, which this fork's own GITHUB_TOKEN has no access to. Repoint at ghcr.io/scaleup-technologies so tagged releases actually publish. Fork-specific, not meant for upstream.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
.goreleaser.yamlandREADME.mdwere still hardcoded toghcr.io/inovex/...andrelease.github.owner: inovex, inherited from upstream.GITHUB_TOKENhas no write access to inovex's package registry or repo.scaleup-technologies.Fork-specific — not meant to go upstream.
Test plan
v0.0.0-test) after merge and confirm goreleaser publishes toghcr.io/scaleup-technologies/external-dns-openstack-webhook