[jira] [Comment Edited] (CB-6156) Generate shrinkwrap.json and update package.json to enable
[ https://issues.apache.org/jira/browse/CB-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930588#comment-13930588 ] Carlos Santana edited comment on CB-6156 at 3/11/14 5:03 PM: - [~agrieve] Intentional in tools-release-process only CLI is affected with shrinkwrap, when updating plugman the CLI shrinkwrap needs to be refresh. But I was not sure where to document or to not document at all the other cases when shrinkwrap needs to be refresh outside cutting a release. For example: If the dependency tar for plugman needs to be updated from 0.1.x to 0.2.x then package.json needs to be updated and npm-shrinkwrap.json Or if the dependency q for cli needs to be updated from then both pacakge.json and npm-shrinkwrap.json need to be updated. I think this doc doesn't belong in tools-release-process.md, maybe on the README.md for both CLI and plugman? Let met know what you think. was (Author: csantana): [~agrieve] Intentional in tools-release-process only CLI is affected with shrinkwrap, when updating plugman the CLI shrinkwrap needs to be refresh. But I was not sure where to document or to document at all the other cases when shrinkwrap needs to be refresh outside cutting a release. For example: If the dependency tar for plugman needs to be updated from 0.1.x to 0.2.x then package.json needs to be updated and npm-shrinkwrap.json Or if the dependency q for cli needs to be updated from then both pacakge.json and npm-shrinkwrap.json need to be updated. I think this doc doesn't belong in tools-release-process.md, maybe on the README.md for both CLI and plugman? Let met know what you think. > Generate shrinkwrap.json and update package.json to enable > -- > > Key: CB-6156 > URL: https://issues.apache.org/jira/browse/CB-6156 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, Plugman >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CB-6156) Generate shrinkwrap.json and update package.json to enable
[ https://issues.apache.org/jira/browse/CB-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930588#comment-13930588 ] Carlos Santana edited comment on CB-6156 at 3/11/14 5:02 PM: - [~agrieve] Intentional in tools-release-process only CLI is affected with shrinkwrap, when updating plugman the CLI shrinkwrap needs to be refresh. But I was not sure where to document or to document at all the other cases when shrinkwrap needs to be refresh outside cutting a release. For example: If the dependency tar for plugman needs to be updated from 0.1.x to 0.2.x then package.json needs to be updated and npm-shrinkwrap.json Or if the dependency q for cli needs to be updated from then both pacakge.json and npm-shrinkwrap.json need to be updated. I think this doc doesn't belong in tools-release-process.md, maybe on the README.md for both CLI and plugman? Let met know what you think. was (Author: csantana): [~agrieve] Intentional in tools-release-process only CLI is affected with shrinkwrap, when updating plugman the CLI shrinkwrap needs to be refresh. But I was not sure were to document or to document at all the other cases when shrinkwrap needs to be refresh outside cutting a release. For example: If the dependency tar for plugman needs to be updated from 0.1.x to 0.2.x then package.json needs to be updated and npm-shrinkwrap.json Or if the dependency q for cli needs to be updated from then both pacakge.json and npm-shrinkwrap.json need to be updated. I think this doc doesn't belong in tools-release-process.md, maybe on the README.md for both CLI and plugman? Let met know what you think. > Generate shrinkwrap.json and update package.json to enable > -- > > Key: CB-6156 > URL: https://issues.apache.org/jira/browse/CB-6156 > Project: Apache Cordova > Issue Type: Sub-task > Components: CLI, Plugman >Reporter: Carlos Santana >Assignee: Carlos Santana > Fix For: Master > > -- This message was sent by Atlassian JIRA (v6.2#6252)