Point the release upload at the repository's current name - #6
Merged
Conversation
The v1.3.0 release built every binary, produced all five archives and pushed the Docker images, then failed to upload a single asset: POST https://uploads.github.com/repos/csnp/qramm-cryptodeps/releases/362570532/ assets?name=cryptodeps_1.3.0_darwin_x86_64.tar.gz: 307 location <nil> The repository was renamed qramm-cryptodeps -> cryptodeps. GitHub answers the old name with a 307 redirect, and GoReleaser's asset uploader does not follow it, so the release was left as a draft with zero assets. Only the upload target moves. Everything else that still names the old path was checked and is correct where it is: - The Go module path stays github.com/csnp/qramm-cryptodeps. Changing it would break every importer, and module resolution follows the redirect. - The ghcr.io image names stay, because those images pushed successfully and renaming them would orphan the published tags. - The curl install line and the compare URL in the release notes use redirect- following clients.
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.
The v1.3.0 release built every binary, produced all five archives and pushed the Docker images, then failed to upload a single asset:
The repository was renamed
qramm-cryptodepstocryptodeps. GitHub answers the old name with a 307 redirect, and GoReleaser's asset uploader does not follow it, so the release was left as a draft with zero assets. That draft has been deleted and the tag will be re-cut on this fix.Only the upload target moves. Everything else still naming the old path was checked individually and is correct where it is: the Go module path (changing it breaks importers, and module resolution follows the redirect), the ghcr.io image tags (those images pushed successfully; renaming orphans them), and the curl install line and compare URL (redirect-following clients).