🚨🔥⚠️ Action required: Switch to the new Greenkeeper now! 🚨🔥⚠️
This version of Greenkeper will be shutdown on May 31st.
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.
Hello lovely humans,
coffee-script just published its new version 1.12.6.
State
Update :rocket:
Dependency
coffee-script
New version
1.12.6
Type
devDependency
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 coffee-script.
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.
fecdbacA particular REPL test is broken in Node 4.8.2 because of a regression that was fixed in Node 5.11.0; just disable the test for Node < 6. Fixes #4502. (#4510)
473e8a1Merge pull request #4507 from GeoffreyBooth/tests-exit-code
faf6d17cake build:browser should just assemble the browser build, not also test it; add cake build:browser:full to additionally run the tests
d141d5cIf the tests fail, return a non-zero exit code
a36b454Merge branch 'master' of github.com:jashkenas/coffeescript
Hello lovely humans,
coffee-script just published its new version 1.12.6.
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 coffee-script. 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 48 commits .
f0e98371.12.6 missing updated outputf661f911.12.6 (#4548)e00fa5dFix #4533: chained calls incorrectly wrapping enclosing implicit objects (#4534)51c0657Fix #4150: Correctly outdent ternary followed by method call (#4535)26cb24areturnandexport defaultcan now accept implicit objects (#4532)ac1b2b5Iss4248 unicode code point escapes (cleanup) (#4522)96b6c5fFix #4248: Unicode code point escapes (#4498)bfce054Fix parenthesized conditions in if-else assignment (#4519)ff60e6afix 'future reserved words' test (#4518)0da9d71Fix broken links, update redirected links (#4505)fecdbacA particular REPL test is broken in Node 4.8.2 because of a regression that was fixed in Node 5.11.0; just disable the test for Node < 6. Fixes #4502. (#4510)473e8a1Merge pull request #4507 from GeoffreyBooth/tests-exit-codefaf6d17cake build:browsershould just assemble the browser build, not also test it; addcake build:browser:fullto additionally run the testsd141d5cIf the tests fail, return a non-zero exit codea36b454Merge branch 'master' of github.com:jashkenas/coffeescriptThere are 48 commits in total. See the full diff.