brodybits commented on a change in pull request #834: CB-14152 add 
[email protected] blog post
URL: https://github.com/apache/cordova-docs/pull/834#discussion_r198153467
 
 

 ##########
 File path: www/_posts/2018-06-22-cordova-js-release-4.2.4.md
 ##########
 @@ -0,0 +1,24 @@
+---
+layout: post
+author:
+    name: Chris Brody
+    url: https://twitter.com/brodybits
+title:  "Cordova-JS release"
+categories: news
+tags: release tools
+---
+
+We are happy to announce that `cordova-js 4.2.4` has been released. This is 
the source of the JavaScript code in `cordova.js` used in each of the Cordova 
platform implementations.
+
+## Release Highlights
+
+The purpose of this release is to include a recent logging update with 
internal `npm audit` messages resolved in the package build. Here are the major 
changes:
+
+* [CB-9366](https://issues.apache.org/jira/browse/CB-9366) log `error.stack` 
data
+* [CB-14145](https://issues.apache.org/jira/browse/CB-14145) `package.json` 
resolve `npm audit` warnings in `devDependencies` (for build and test scripts)
+* [CB-14155](https://issues.apache.org/jira/browse/CB-14155) fix btest build 
target (by using `express` instead of `connect` in `devDependencies`)
+* Other internal test fixes
+
+## Deprecation Note
+
+As NodeJS 4.x support ended on April 30<sup>th</sup>, 2018, we are proceeding 
with our [previously 
announced](https://cordova.apache.org/news/2016/10/01/0.x-4.x-deprecation-timeline.html)
 deprecation timeline.  This is probably the last release that will support 
NodeJS 4.x.
 
 Review comment:
   Gone, then

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to