[ 
https://issues.apache.org/jira/browse/CB-14145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562669#comment-16562669
 ] 

ASF GitHub Bot commented on CB-14145:
-------------------------------------

brodybits opened a new pull request #56: CB-14145 pin even more added bundled 
deps in 5.0.x only
URL: https://github.com/apache/cordova-browser/pull/56
 
 
   <!--
   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:
   
   http://cordova.apache.org/contribute/contribute_guidelines.html
   
   Thanks!
   -->
   
   ### Platforms affected
   
   browser
   
   ### What does this PR do?
   
   - pin even more added bundled deps in 5.0.x only - needed to clear the red 
highlights in n`pm outdated --depth=0`
   
   ### What testing has been done on this change?
   
   - [ ] `npm audit` shows 0 vulnerabilities (using [email protected])
   - [ ] `npm outdated --depth=0` shows no red entries
   - [ ] `coho audit-license-headers -r browser` shows no missing license 
headers
   - [ ] `coho check-license -r browser` shows no incorrect licenses
   - [ ] `npm test` succeeds on AppVeyor CI & Travis CI
   - [ ] able to add to new Cordova project using `cordova platform add 
github:brodybits/cordova-browser#cb-14145-pin-even-more-added-bundled-deps-in-5.0.x-only`
 then run using [email protected] (bundled with deprecated node v4.9.1 version)
   
   ### Checklist
   
   - [x] [Reported an issue](http://cordova.apache.org/contribute/issues.html) 
in the JIRA database
   - [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.
   - ~~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:
[email protected]


> Resolve npm audit issues
> ------------------------
>
>                 Key: CB-14145
>                 URL: https://issues.apache.org/jira/browse/CB-14145
>             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, cordova-windows
>            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
(v7.6.3#76005)

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

Reply via email to