Fix missing changelog entries on releases #165
Merged
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
Goreleaser requires full git history to generate full changelog. See * https://goreleaser.com/errors/no-history/ * https://goreleaser.com/ci/actions/
|
Changelog of the recent v0.4.22 release shows all the commits: Compare to earlier releases: |
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.
Recent releases https://github.com/grpc-ecosystem/grpc-health-probe/releases are misleading, because they are erroneously only listing the one latest change of the last commit, often just some chore task after more significant changes.
Goreleaser requires full git history to generate full changelog.
See
Please consider manually changing or generating release notes for at least few recent releases or adding compare links.