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 jspm.
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.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Coverage remained the same at 85.083% when pulling 8b6ed3ac3b6ce82189c04046ccbf0105092660e2 on greenkeeper-jspm-0.16.49 into 3fe27f18b42d0e18d9e03f04a20d702fe034121f on master.
Coverage remained the same at 85.083% when pulling 8b6ed3ac3b6ce82189c04046ccbf0105092660e2 on greenkeeper-jspm-0.16.49 into 3fe27f18b42d0e18d9e03f04a20d702fe034121f on master.
Coverage remained the same at 85.083% when pulling 038889dfd5e132191c2d3d3b056c458b1917f046 on greenkeeper-jspm-0.16.49 into 9e6ae094509f5c091252b5abd5b6a63ef33f602a on master.
Coverage remained the same at 85.083% when pulling 038889dfd5e132191c2d3d3b056c458b1917f046 on greenkeeper-jspm-0.16.49 into 9e6ae094509f5c091252b5abd5b6a63ef33f602a on master.
Hello lovely humans,
jspm just published its new version 0.16.49.
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 jspm. 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 :sparkles:
You rock!
:palm_tree:
The new version differs by 6 commits .
909d4a2
0.16.49
cc2ddbc
update systemjs, builder
22dae52
Merge pull request #2172 from tamird/dont-rewrite-package-json
e8e007d
only rewrite package.json if it has changed
a01e434
scope
self
more narrowly3d215bb
whitespace
See the full diff.
Screencast
Try it today. Free for private repositories during beta.