feat(.goreleaser.yml): add sha256 check to release notes #604
Conversation
This file contains 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
Improve commands so that the checksum of the downloaded file is checked before cosign is checked.
|
|
|
While I'm at it (and maybe I should describe this in an issue), it would be even nicer if the generated notes would include the version, for example for the last release : not familiar with gorelease features though |
|
You should be able to use the template placeholder |
sudermanjr
requested changes
May 26, 2023
Co-authored-by: Andrew Suderman <andy@suderman.dev>
Co-authored-by: Andrew Suderman <andy@suderman.dev>
|
Latest release notes are much nicer. Thanks again! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Improve commands so that the checksum of the downloaded file is checked before cosign is checked.
This PR fixes #
Checklist
Description
What's the goal of this PR?
What changes did you make?
What alternative solution should we consider, if any?