Add CHANGELOG.md with full release history#364
Merged
grosser merged 1 commit intogrosser:masterfrom Apr 4, 2026
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
2 participants
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.
When I noticed that v2.0.0 was released, I came here looking for a changelog and noticed that there was none, so I decided to add one. Or, rather, I decided to prompt an LLM to add one. This is the prompt gave to Claude Opus 4.6:
This changelog covers 99 releases from v0.3.1 through v2.0.0, with compare links for every release. I’m not familiar with this project's release history, but I gave the changelog a once-over and it looked reasonable. And the Markdown is valid.
I also took this opportunity to refactor the gemspec, using the
homepageas a variable to define the metadata URIs.