Update gulp-sourcemaps to version 2.0.1 🚀 #115
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
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.
Hello lovely humans,
gulp-sourcemaps just published its new version 2.0.1.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of gulp-sourcemaps.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 34 commits .
fbaa356Merge branch '1.X'096f882Merge pull request #234 from realtymaps/1.Xdcee23dMerge pull request #235 from TerryMooreII/fix-null-newline-1.xf51b931debug-fabulous for closure debuggingea2e252Fix the detect newline showing null in text :: fix-null-newline-1.x7a8482dfix(array checking css): issue #2325cdad84Merge pull request #194 from nicekiwi/master7b5e269prep v2.0.0 release4e689ecBREAKING CHANGE is due to strip-bom 3.X. Marking 2.0.0-beta 'work in progress branch'. This will be the new master branch.5a351821.7.14d64de8Revert strip-bom to really keep 1.X semver and keep the lib support for0327343v1.7.0: Reverting 2.0.0-alpha there appears to be no breaking changes versioning90f2128doc(issue 25): readme657f09bMerge pull request #206 from waldyrious/patch-15cb3af4commment typoThere are 34 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade