cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CB-14145) Resolve npm audit issues
Date Fri, 06 Jul 2018 20:16:00 GMT


ASF GitHub Bot commented on CB-14145:

brodybits opened a new pull request #281: CB-14145 resolve npm audit issues in patch fix
   Please make sure the checklist boxes are all checked before submitting the PR. The checklist
   is intended as a quick reference, for complete details please see our Contributor Guidelines:
   ### Platforms affected
   ### What does this PR do?
   - Set VERSION to 6.0.1-dev & update JS snapshot to version 6.0.1-dev via coho, using
local coho with apache/cordova-coho#176 for patch release support (on mac due to some issues
with updating JavaScript on Windows)
   - Update cordova-common to 2.2.5, pinned in this patch fix, to resolve the `npm audit`
   - pin other dependencies in package.json in this patch fix
   - completely reinstall node_modules (ignoring `node_modules/.bin`) using the following
command on npm@6.1.0: `npm install --only=production`
   - Update cordova.js from cordova-js@4.2.4 with the following changes, using local coho
with apache/cordova-coho#176 for patch release support (on mac due to some issues with updating
JavaScript on Windows):
     - CB-9366 log error.stack
   - update `bundledDependencies` to support deprecated Node.js 4 in this patch fix
   - add Node.js 8 & 10 to AppVeyor CI & Travis CI in this patch fix
   - add blank lines to `.travis.yml` in this patch fix
   - 6.0.0 fixes
     - remove extra info (now obsolete)
     - note `cordova.js` update from cordova-js@4.2.2
     - other minor fixes
   ### What testing has been done on this change?
   - able to build and run Cordova Windows app when using deprecated Node.js version 4 without
ugly engine error warnings
   - able to build and run Cordova Windows app on Node.js version 8
   CI testing todo:
   - [ ] verify that `npm test` and other items pass on AppVeyor CI
   - [ ] verify that build tests items pass on Travis CI
   ### Checklist
   - [x] [Reported an issue]( in the JIRA
   - [x] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file
paths", where CB-xxxx is the JIRA ID & "android" is the platform affected. (with some
   - ~~Added automated test coverage as appropriate for this change.~~

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:

> Resolve npm audit issues
> ------------------------
>                 Key: CB-14145
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: cordova-android, cordova-app-hello-world, cordova-browser, cordova-cli,
cordova-coho, cordova-common, cordova-ios, cordova-js, cordova-lib, cordova-osx, cordova-plugman,
>            Reporter: Chris Brody
>            Assignee: Chris Brody
>            Priority: Major
> From private discussions I discovered that running {{npm audit}} on a number of components
would report dependencies with security issues. While we could not see any {{npm audit}} issues
that may affect applications built using Cordova I think it is extremely important to resolve
these issues as soon as possible. Most affect devDependencies used for testing of Cordova
itself; a minority seem to affect Cordova scripts that may be run by Cordova application developers.
Better safe than sorry!
> I would like to resolve this issue as follows:
> * patch release of common library components such as {{cordova-common}}, {{cordova-lib}},
etc. (fixed in minor release branch)
> * patch or minor release of other affected components such as CLI, Cordova platform implementations,
major plugins, etc. (expected to be fixed in minor release branch; do not want to pollute
the master branch with extra reverts, updated node_modules committed, etc.)
> * {{npm audit}} issues resolved in master branch for next major release, which should
NOT be shipped with any {{npm audit}} issues lurking
> * {{npm audit}} step added to CI for both patch release and next major release

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message