Upgrade remarkable #126
Merged
Upgrade remarkable #126
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
Only bug fix here https://github.com/jonschlinkert/remarkable/blob/master/CHANGELOG.md#201--2020-05-25 Is it ok to extend version with semver caret? We do not expect major changes now. Now I have two instances of remarkable in my project because of this.
Yeah let's do it. I've often been overly cautious about this because it means trusting the dependency's author to only do non-breaking changes on semvar... I have been burned before! But I feel pretty safe with remarkable. |
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.
Only bug fix here https://github.com/jonschlinkert/remarkable/blob/master/CHANGELOG.md#201--2020-05-25
Is it ok to extend version with semver caret? We do not expect major
changes now. Now I have two instances of remarkable in my project
because of this.