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

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

brodybits opened a new pull request #55: CB-14230 patch release 5.0.4
URL: https://github.com/apache/cordova-browser/pull/55
 
 
   <!--
   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?
   
   - Update RELEASENOTES.md with major changes for `5.0.4`
   - Update JS snapshot, VERSION, and version to `5.0.4` on `5.0.x` branch 
using the following command with updates from apache/cordova-coho#176: 
`./cordova-coho/coho prepare-platform-release-branch --version 5.0.4 -r browser 
5.0.x`
   
   This release includes the following changes:
   * [CB-9366](https://issues.apache.org/jira/browse/CB-9366) - log 
`error.stack` in `cordova.js` (update from `[email protected]`) in `5.0.x` 
(ef012e389996d27f580063a7b271f2ae08c484e9)
   * add Node.js 10 to AppVeyor CI and Travis CI in `5.0.x` 
(57fdfc8735f6aa5b91b397f7822180ea86bdb0bf)
   * [CB-14145](https://issues.apache.org/jira/browse/CB-14145) update 
dependencies to resolve `npm audit` issues, pinned in `5.0.x` only (GH-53)
   * GH-54 - pin more added bundled dependencies in 5.0.x only (needed to clear 
the red highlights in `npm 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 local machine
   - [ ] `npm test` succeeds on AppVeyor CI & Travis CI
   - [ ] able to add to 
<https://github.com/brodybits/cordova-dialogs-bootstrap-test> using `cordova 
platform add github:brodybits/cordova-browser#5.0.x`, run, and try a couple 
dialogs with [email protected] (bundled with deprecated node v4.9.1)
   - [ ] able to add to 
<https://github.com/brodybits/cordova-dialogs-bootstrap-test> using `cordova 
platform add github:brodybits/cordova-browser#5.0.x`, run, and try a couple 
dialogs with [email protected] (bundled with node v8.11.3)
   
   ### Checklist
   
   - ~~[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. (manual changes only)
   - ~~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]


> cordova-browser patch release July 2018
> ---------------------------------------
>
>                 Key: CB-14230
>                 URL: https://issues.apache.org/jira/browse/CB-14230
>             Project: Apache Cordova
>          Issue Type: Task
>          Components: cordova-browser
>            Reporter: Chris Brody
>            Assignee: Chris Brody
>            Priority: Major
>
> Patch release of cordova-browser package with CB-14145 (npm audit issues) 
> resolved.
> Following steps at 
> [https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md](with
>  some modifications)



--
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