{"action":"created","issue":{"url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/255","labels_url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/255/labels{/name}","comments_url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/255/comments","events_url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/255/events","html_url":"https://github.com/sindresorhus/grunt-sass/issues/255","id":113892133,"number":255,"title":"Why does `grunt-sass` pull in all minor changes of `node-sass`?","user":{"login":"danoc","id":916038,"avatar_url":"https://avatars.githubusercontent.com/u/916038?v=3","gravatar_id":"","url":"https://api.github.com/users/danoc","html_url":"https://github.com/danoc","followers_url":"https://api.github.com/users/danoc/followers","following_url":"https://api.github.com/users/danoc/following{/other_user}","gists_url":"https://api.github.com/users/danoc/gists{/gist_id}","starred_url":"https://api.github.com/users/danoc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/danoc/subscriptions","organizations_url":"https://api.github.com/users/danoc/orgs","repos_url":"https://api.github.com/users/danoc/repos","events_url":"https://api.github.com/users/danoc/events{/privacy}","received_events_url":"https://api.github.com/users/danoc/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-28T18:36:14Z","updated_at":"2015-10-28T18:43:07Z","closed_at":"2015-10-28T18:43:07Z","body":"Hello! \r\n\r\nThe `3.3.0` Libsass release introduced a regression (https://github.com/sass/libsass/issues/1654) that was picked up by `node-sass` `v3.4.0`. This was in turn picked up by `grunt-sass` `v1.0.0`, the version we use, because the `package.json` is configured to pull all minor and patch releases of `node-sass`.\r\n\r\nWe had to fork `grunt-sass` and force it to use an older version of `node-sass` to patch our issue until the Libsass developers respond (https://github.com/sindresorhus/grunt-sass/compare/master...optimizely:daniel/node-sass-3-3-3).\r\n\r\nI'd like to know if there is a particular reason that `grunt-sass` pulls in all minor (`3.X.X`) releases of `node-sass`. I'd recommend only pulling in patches or lock `grunt-sass` to a specific version of `node-sass` and release at the same cadence.\r\n\r\nI'd be happy to elaborate if that made no sense!"},"comment":{"url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/comments/151947683","html_url":"https://github.com/sindresorhus/grunt-sass/issues/255#issuecomment-151947683","issue_url":"https://api.github.com/repos/sindresorhus/grunt-sass/issues/255","id":151947683,"user":{"login":"sindresorhus","id":170270,"avatar_url":"https://avatars.githubusercontent.com/u/170270?v=3","gravatar_id":"","url":"https://api.github.com/users/sindresorhus","html_url":"https://github.com/sindresorhus","followers_url":"https://api.github.com/users/sindresorhus/followers","following_url":"https://api.github.com/users/sindresorhus/following{/other_user}","gists_url":"https://api.github.com/users/sindresorhus/gists{/gist_id}","starred_url":"https://api.github.com/users/sindresorhus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sindresorhus/subscriptions","organizations_url":"https://api.github.com/users/sindresorhus/orgs","repos_url":"https://api.github.com/users/sindresorhus/repos","events_url":"https://api.github.com/users/sindresorhus/events{/privacy}","received_events_url":"https://api.github.com/users/sindresorhus/received_events","type":"User","site_admin":false},"created_at":"2015-10-28T18:43:07Z","updated_at":"2015-10-28T18:43:07Z","body":"That's how npm and semver works. Even with your suggestion it could still break in a patch release. You should be using shrinkwrap on your part.\r\n\r\nhttps://nodesource.com/blog/semver-tilde-and-caret\r\nhttp://semver.org"}}