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

Shazron Abdullah commented on CB-12237:
---------------------------------------

screen-orientation artifacts removed from CB-12224:
https://lists.apache.org/thread.html/4311b46ab545d2adc4e39e3d22e52b1ddf3da034b2b6882250df6f8d@%3Ccommits.cordova.apache.org%3E

> Plugins Release Dec 12th, 2016
> ------------------------------
>
>                 Key: CB-12237
>                 URL: https://issues.apache.org/jira/browse/CB-12237
>             Project: Apache Cordova
>          Issue Type: Task
>            Reporter: Shazron Abdullah
>
> Following steps at 
> https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md
> cordova-plugin-inappbrowser, the plugin minor version was incremented in 
> plugin.xml to 1.6.0 but not incremented in package.json. Thus when the 
> packaging automation ran, the version had a mismatch, and that this is 
> reflected in cordova-plugin-inappbrowser.
> https://github.com/apache/cordova-plugin-inappbrowser/commit/cfbd3845a893df647ff39ec3c750804d775a0e57
> We should have a version mismatch automation check during release as well in 
> coho, and/or the tests.
> The plugin can't be published this release because package.json shows the 
> version is 1.5.1 while plugin.xml is 1.6.0 (1.6.0 is correct).
> I will have to omit cordova-plugin-inappbrowser in the previous release, and 
> put out another cordova plugins release (this release) which includes:
> 1) Updates in cordova-plugin-battery-status that we discussed (--browserify 
> fixes for Windows)
> 2) The package.json update in cordova-plugin-inappbrowser (same version, 
> 1.6.0)
> 3)  package.json and plugin.xml version bump in 
> cordova-plugin-screen-orientation (to 1.4.3)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to