Remove changelog entries for v1.14.0+ #381
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
The changelog renderer doesn't know the difference between a closed issue and a resolved one so it adds confusing things to the log Ex: we currently have `Resource to control the new style of alerting provided in Grafana 8.X #348` in the v1.19.0 changelog The release notes builder that comes in Github Releases produces a much nicer result so let's only use that It also simplifies the release process, no need for a Github token
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.
The changelog renderer doesn't know the difference between a closed issue and a resolved one so it adds confusing things to the log
Ex: we currently have
Resource to control the new style of alerting provided in Grafana 8.X #348in the v1.19.0 changelog but that's only going to be released with Grafana 8.5The release notes builder that comes in Github Releases produces a much nicer result so let's only use that
It also simplifies the release process, no need for a Github token