37.json (4114B)
1 { 2 "number": 37, 3 "title": "Update dependencies to enable Greenkeeper \ud83c\udf34", 4 "state": "closed", 5 "diff_file": "37.diff", 6 "author": "greenkeeper[bot]", 7 "created_at": "2017-06-02T08:07:55Z", 8 "closed_at": "2018-04-09T13:51:27Z", 9 "merged_at": null, 10 "base_ref": "master", 11 "head_ref": "greenkeeper/initial", 12 "labels": [ 13 "greenkeeper" 14 ], 15 "assignees": [], 16 "requested_reviewers": [], 17 "body": "\nLet\u2019s get started with automated dependency management for nBot :muscle:\n\n\n\nThis pull request **updates all your dependencies to their latest version**. Having them all up to date really is the best starting point. I will look out for further dependency updates and make sure to handle them in isolation and in real-time, **as soon as you merge this pull request**.\n\n**I won\u2019t start sending you further updates, unless you have merged this very pull request**.\n\n\n\n---\n<details>\n<summary>\ud83d\ude48 How to ignore certain dependencies</summary>\n\nIn case you can not, or do not want to update a certain dependency right now, you can of course just [change the `package.json` file back to your liking](https://github.com/MTRNord/nBot/edit/greenkeeper/initial/package.json).\n\nAdd a `greenkeeper.ignore` field to your `package.json`, containing a list of dependencies you don\u2019t want to update right now.\n\n```js\n// package.json\n{\n \u2026\n \"greenkeeper\": {\n \"ignore\": [\n \"package-names\",\n \"you-want-me-to-ignore\"\n ]\n }\n}\n```\n</details>\n<details>\n<summary>\ud83d\udc69\u200d\ud83d\udcbb How to update this pull request</summary>\n\n```bash\n # change into your repository\u2019s directory\n git fetch\n git checkout greenkeeper/initial\n npm install-test\n # adapt your code, so it\u2019s working again\n git commit -m 'chore: adapt code to updated dependencies'\n git push origin greenkeeper/initial\n```\n</details>\n<details>\n<summary>\u2728 How the updates will look like</summary>\n\nAs soon as you merge this pull request **I\u2019ll create a branch for every dependency update**, with the new version applied. The branch creation should trigger your testing services to check the new version. Using the results of these tests I\u2019ll try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.\n\n```diff\n- \"underscore\": \"^1.6.0\"\n+ \"underscore\": \"^1.7.0\"\n```\n\nIn the above example you can see an in-range update. `1.7.0` is included in the old `^1.6.0` range, because of the [caret `^` character ](https://docs.npmjs.com/misc/semver#ranges).\nWhen the test services report success I\u2019ll delete the branch again, because no action needs to be taken \u2013 everything is fine.\nWhen there is a failure however, I\u2019ll create an issue so you know about the problem immediately.\n\nThis way every single version update of your dependencies will either continue to work with your project, or you\u2019ll get to know of potential problems immediately.\n\n```diff\n- \"lodash\": \"^3.0.0\"\n+ \"lodash\": \"^4.0.0\"\n```\n\nIn this example the new version `4.0.0` is not included in the old `^3.0.0` range.\nFor version updates like these \u2013 let\u2019s call them \u201cout of range\u201d updates \u2013 you\u2019ll receive a pull request.\n\nNow **you no longer need to check for exciting new versions by hand** \u2013 I\u2019ll just let you know automatically.\nAnd the pull request will not only serve as a reminder to update. In case it passes your decent test suite that\u2019s a strong reason to merge right away :shipit:\n</details>\n<details>\n<summary>\ud83d\udc81\u200d\u2642\ufe0f Not sure how things are going to work exactly?</summary>\n\nThere is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).\n</details>\n\n---\n\n\nGood luck with your project and see you soon :sparkles:\n\nYour [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:\n", 18 "comments": [], 19 "review_comments": [] 20 }