Update gulp-sourcemaps to version 2.2.0 🚀 #120
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.2.0.
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 58 commits .
ec9b51dMerge branch '1.X': Bumped to 2.2.X for engines >=40290827bumping to 1.9.X for engines def6aa5eb4Merge branch '1.X'3f76e4bchanged file creation which was shallow cloning anyways to use clone always with deep:false, and contents: false4bb8d2dMerge cherry-pick675ef67.gitignorebfd155bAdds an clone options to gulp-sourcemaps.write()8b50f13Merge branch '1.X'8abf069getting line coverage back to 100% and identifying the publish tests with 'publsh:'14fd483attempt to avert disaster issue 24648759d9Merge branch '1.X'93db5f5package.json foobar.. i am sorry worlda427021Merge branch '1.X', bump to 2.1.X for PLUGIN_NAME change to point to613ecedbumping to 1.8.X due to PLUGIN_NAME change to reflect package.name8db077cindenting uniformity via jsbeautifierThere are 58 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade