Update CHANGELOG for 2.0.0 #232
Closed
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
swcraig
force-pushed
the
update-changelog-for-2.0
branch
from
3ceed07 to
05eeb55
Compare
|
Thanks for pushing this along @swcraig! 🚢 |
Adds the code changes since v1.0.3.
swcraig
force-pushed
the
update-changelog-for-2.0
branch
from
05eeb55 to
f964bbc
Compare
|
Talked to @gr8bit. We are going to do a v1.1.0 release instead. |
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.
Adds references to PRs that made code changes since the 1.0.3 release.
I think this next release should be a major version bump. Both #177 and #180 include API breaking changes. I would prefer to release this version now with these changes before beginning any further work on the project.
I didn't include a reference to each data change that was made since v1.0.3. I think in the future PRs should include a CHANGELOG entry. We could possibly have two headings for new versions in the CHANGELOG, "Code changes" and "Data changes" (or something along those lines).
Once this and #231 are merged I will update the version and push a release to RubyGems.