Drop CHANGELOG.md in favor of GitHub release notes#218
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
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
Removes
CHANGELOG.mdfrom the repo. From v6.0.0 onward, release notes live on the GitHub Releases page instead.Why
CHANGELOG.mdand the GitHub Release saying different thingsFollow-up
When tagging
v6.0.0, paste the content from the merged-then-deletedCHANGELOG.md(d79ef68:CHANGELOG.md) as the GitHub Release body. From v6.0.1 onward, draft release notes can be auto-generated from merged PRs.Test plan
CHANGELOG.md(grep -ri changelogreturns nothing)git ls-filesso the deleted file just stops shipping with the gem