Prepare for 2.3.0 release#791
Merged
Merged
Conversation
Contributor
Great question. What I've done so far is keep the NPM version the same as the RubyGems version. But I can't think of any real reason to do that. Let me see if I documented it anyplace ... No, I don't think so. So IMO no need to publish to NPM. This is gonna be sweet! |
rmosolgo
approved these changes
Sep 27, 2017
Contributor
Author
|
Off it goes! |
Contributor
|
|
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.
@rmosolgo Thanks for the readme additions for a release. Do we need to publish to NPM even if there is no JS change?
If so I'll get set up there and let you know the details for it, and if not then I will try a gem release.
Believe I already updated the Changelog with both PRs merged since 2.2.1 so that should be everything.
In this release:
Planned next point release: