The version 2.2.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of coffeescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 371 commits ahead by 371, behind by 7.
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Coverage remained the same at 97.849% when pulling 161e463a28a3a82bc2cd74cb7d4e9a68a9afe0bc on greenkeeper/coffeescript-2.2.0 into 82349d77f30d9b1cffb73ae101c54dc8f801273e on master.
Coverage remained the same at 97.849% when pulling 161e463a28a3a82bc2cd74cb7d4e9a68a9afe0bc on greenkeeper/coffeescript-2.2.0 into 82349d77f30d9b1cffb73ae101c54dc8f801273e on master.
Version 2.2.0 of coffeescript was just published.
The version 2.2.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of coffeescript.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 371 commits ahead by 371, behind by 7.
0490eb9
2.2.0 (#4873)
9e80f6f
Fix #2047: Infinite loop possible when
for
loop withrange
uses variables (#4853)fc5ab1a
Update output
0aa77f1
fix #4871 (#4872)
1849f0d
Fix #4852, @get @set implicit object (#4867)
d86597d
Fix #3306: trailing comma in a function call in the last line throws a syntax error (#4860)
bf91781
Fix #4868: Incorrect ‘Can’t call super with @params’ error (#4869)
dcd6de9
Update output
70b510b
Fix #3933: Missing
then
doesn’t trigger nearby error (#4862)84d596d
Fix #4437: variable scope in chained calls (#4863)
c804087
Fix #3921 & #2342: inline function without parentheses used in condition, inline 'else' (#4838)
74bd537
fix #3909 (#4861)
0217ed5
Fix #1726: expression in property access causes unexpected results (#4851)
e53307b
Fix #3441: parentheses wrapping expression throw invalid error (#4849)
c8c8c16
Fix #4843: bad output when assigning to @prop in destructuring assignment with defaults (#4848)
There are 250 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: