[
https://issues.apache.org/jira/browse/CB-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13634556#comment-13634556
]
Michael Brooks commented on CB-3059:
------------------------------------
[Commit
0cf3d0|https://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=commit;h=0cf3d03f41d90850f3fc3db33970d79a868cb59f]
It has also been published to npm:
{code}
cordova-cli:mwbrooks $ npm publish
npm http PUT https://registry.npmjs.org/cordova
npm http 409 https://registry.npmjs.org/cordova
npm http GET https://registry.npmjs.org/cordova
npm http 200 https://registry.npmjs.org/cordova
npm http PUT https://registry.npmjs.org/cordova/2.6.1/-tag/latest
npm http 201 https://registry.npmjs.org/cordova/2.6.1/-tag/latest
npm http GET https://registry.npmjs.org/cordova
npm http 200 https://registry.npmjs.org/cordova
npm http PUT
https://registry.npmjs.org/cordova/-/cordova-2.6.1.tgz/-rev/109-dfb38be21804bfb7a7475a7bd00d0c62
npm http 201
https://registry.npmjs.org/cordova/-/cordova-2.6.1.tgz/-rev/109-dfb38be21804bfb7a7475a7bd00d0c62
+ [email protected]
{code}
> Publish 2.6.1 with Cordova 2.6.0 Framework
> ------------------------------------------
>
> Key: CB-3059
> URL: https://issues.apache.org/jira/browse/CB-3059
> Project: Apache Cordova
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.6.0
> Reporter: Michael Brooks
> Assignee: Michael Brooks
> Fix For: 2.6.0
>
>
> When Cordova 2.6.0 was released, the Cordova-CLI was updated with the new
> framework. However, the {{package.json}} version was not incremented to
> {{2.6.1}} and not published.
> This mistake also exposed the confusing nature of how Cordova-CLI is
> versioned:
> * Cordova 2.6.0rc1 === Cordova-CLI 2.6.0
> * Cordova 2.6.0 === Cordova-CLI 2.6.1
> [Semantic Versioning|http://semver.org] does support release candidates by
> using the {{-}} delimiter. In the future, we will publish with the following
> format:
> * Cordova 2.6.0rc1 === Cordova-CLI 2.6.0-rc1
> * Cordova 2.6.0 === Cordova-CLI 2.6.0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
