René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Do not pin versions on ng update","articleBody":"### Versions\r\n```\r\ncli 6.0.0-rc.4\r\n```\r\n\r\n### Repro steps\r\nFrom an Angular 5 project:\r\n* update the CLI to v6 and migrate\r\n* `ng update @angular/core --next`\r\n\r\n### Observed behavior\r\nPinned versions in `package.json`:\r\n```json\r\n\"@angular/compiler\": \"6.0.0-rc.5\",\r\n\"@angular/core\": \"6.0.0-rc.5\",\r\n\"typescript\": \"2.7.2\"\r\n...\r\n```\r\n\r\n### Desired behavior\r\nKeep semantic versionning in `package.json`:\r\n```json\r\n\"@angular/compiler\": \"^6.0.0-rc.5\",\r\n\"@angular/core\": \"^6.0.0-rc.5\",\r\n\"typescript\": \"~2.7.2\"\r\n...\r\n```\r\n\r\n### Mention any other details that might be useful (optional)\r\nPinned versions mean we can't do anymore minor/patch updates of the whole project simply with `npm update` and goes against semver.\r\n\r\nIt's not the role of the CLI to pin the versions. It's the role of the package manager, and as Angular 6 and CLI 6 require Node \u003e= 8.9 and npm \u003e= 5.5, it means the job is already done in a proper way by the `package-lock.json`.","author":{"url":"https://github.com/cyrilletuzi","@type":"Person","name":"cyrilletuzi"},"datePublished":"2018-04-16T13:01:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/10356/angular-cli/issues/10356"}