[
https://issues.apache.org/jira/browse/CB-10677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15178767#comment-15178767
]
Steve Gill commented on CB-10677:
---------------------------------
1.3.0 is the latest released version on npm but the pinned version in cordova 6
is 1.2.0.
The reason why we started pinning plugins in cordova 6 was for stability. If
cordova 6 always grabbed the latest and say a future version 2.0.0 of
cordova-plugin-inappbrowser came out and wasn't compatible with cordova 6, then
cordova 6 would be broken. This way, when we release a version of cordova, we
have a stable set of plugins and platforms that have been tested and cordova 6
should always work.
This won't be an issue anymore once the auto plugin fetching code lands. It
will use engine tags for plugins to determine what version of the plugin to
install.
You can always grab the latest yourself by doing `cordova plugin add
cordova-plugin-inappbrowser@latest`
The next tools release (6.1.0) will have updated the default pinned version of
the plugins. You can also use `--save` when adding plugins to save the version
in your projects config.xml.
> inappbrowser defaults to 1.2.0
> ------------------------------
>
> Key: CB-10677
> URL: https://issues.apache.org/jira/browse/CB-10677
> Project: Apache Cordova
> Issue Type: Bug
> Components: Plugin InAppBrowser
> Affects Versions: 6.0.0
> Reporter: Marc Luria
> Priority: Minor
>
> cordova plugin add cordova-plugin-inappbrowser
> gives version 1.2.0 even though the latest release version is 1.3.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
