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.
What was the end-user problem that led to this PR?
The problem was that a link to the CHANGELOG was 404ing. So, (in a now-closed PR) I made the link absolute, instead of relative, to work around the problem.
But, that'd take us to another website to look at Bundler's CHANGELOG. It'd be nice if Bundler's website knew about the CHANGELOG - had it locally.
What was your diagnosis of the problem?
My diagnosis was we didn't have all files that would be necessary to create a local CHANGELOG, we'd have to point outside this repo, to some on-GitHub data, not very nice. Not rendered in this nice way.
What is your fix for the problem, implemented in this PR?
Include CHANGELOG as a file in the generated site.
This fixes #1233.
This fixes #846
Why did you choose this fix out of the possible options?
I chose this fix because we mentioned it in #1233.