Fix for https://github.com/machineboy2045/angular-selectize/issues/159 #174
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
Changing version to v3.0.2 since so a new tag/release can be created where the package.json version matches the git tag/release version.
Updated version so a new tag/release can be created where the version in the package.json version matches the tag/release version
Adding changes to v3.0.2
Correcting package.json so it is valid.
|
Thanks! |
|
@machineboy2045 @thepauleh You two are the only ones that have access to update the npm repository. https://www.npmjs.com/package/angular-selectize2 |
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.
This is a fix for issue #159. A new 3.0.2 release/tag should be done and published to NPM and Bower after these changes.