Backport of Added support for go-changelog automations into release/1.1.x #1958
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.
Backport
This PR is auto-generated from #1947 to be assessed for backporting due to the inclusion of the label backport/1.1.x.
The below text is copied from the body of the original PR.
I always add details to my commits and there isn't any crossover, so reviewing commit by commit is usually the best way to review my PRs
Changes proposed in this PR:
This PR adds go-changelog support to the Consul-K8s repo. This will be a new way of managing changelog items throughout the release cycle.
go-changelog
required templates and directoriespr/no-changelog
for ignoring missing changelogs if necessary otherwise a changelog is now requiredgo-changelog
toolprepare-release
to automatically rungo-changelog
and add the changes to theCHANGELOG.MD
fileHow I've tested this PR:
v1.0.4
and it generated a valid changelog:make prepare-release
and confirmed that it adds the changes with the correct version and date toCHANGELOG.MD
How I expect reviewers to test this PR:
👀
Checklist:
Overview of commits