Include registry manifest in SHA256SUMS for Terraform Registry publish - #4
Merged
Conversation
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
The Terraform Registry rejects the
v0.1.0release with:The registry requires the provider manifest to have a checksum line in
SHA256SUMS. Previously the manifest was only attached viarelease.extra_files, which runs after checksums are computed, so it was never hashed.Change
Add
checksum.extra_filesin.goreleaser.ymlso the manifest is included inSHA256SUMSwith the matching{name}_{version}_manifest.jsonname.Follow-up after merge
Re-cut the
v0.1.0tag frommainso the release workflow regeneratesSHA256SUMSwith the manifest line, then publish on the registry.PR Generated with AI