83.md (5186B)
1 # PR #83 Update yargs to version 7.0.2 🚀 2 3 - **Status:** closed 4 - **Author:** @greenkeeperio-bot 5 - **Created:** 2017-03-10T02:16:54Z 6 - **Branch:** greenkeeper-yargs-7.0.2 → master 7 - **Closed:** 2017-06-01T06:15:33Z 8 - **Labels:** greenkeeper 9 - **Diff:** [83.diff](./83.diff) 10 11 --- 12 13 Hello lovely humans, 14 15 [yargs](https://www.npmjs.com/package/yargs) just published its new version 7.0.2. 16 17 <table> 18 <tr> 19 <th align=left> 20 State 21 </th> 22 <td> 23 Update :rocket: 24 </td> 25 </tr> 26 <tr> 27 <th align=left> 28 Dependency 29 </td> 30 <td> 31 yargs 32 </td> 33 </tr> 34 <tr> 35 <th align=left> 36 New version 37 </td> 38 <td> 39 7.0.2 40 </td> 41 </tr> 42 <tr> 43 <th align=left> 44 Type 45 </td> 46 <td> 47 dependency 48 </td> 49 </tr> 50 </table> 51 52 This version is **not covered** by your **current version range**. 53 54 Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though. 55 56 I recommend you look into these changes and try to get onto the latest version of yargs. 57 Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update. 58 59 60 Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? 61 Are you unsure about how things are supposed to work? 62 63 There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and while I’m just a bot, there is a group of people who are happy to teach me new things. [Let them know](https://github.com/greenkeeperio/greenkeeper/issues/new). 64 65 Good luck with your project :sparkles: 66 67 You rock! 68 69 :palm_tree: 70 71 --- 72 The new version differs by 29 commits . 73 74 - [`8756a3c`](https://github.com/yargs/yargs/commit/8756a3c63dfd2ceae303067b46075de5c982af66) <code>chore(release): 7.0.2</code> 75 - [`fa86602`](https://github.com/yargs/yargs/commit/fa866029ec51eba6ec13daa0c4f1a9538651cb4d) <code>chore: fix test message</code> 76 - [`b3eb2fe`](https://github.com/yargs/yargs/commit/b3eb2fe5d994b8273f10fe7cbca80d26bc0459a7) <code>fix: populating placeholder arguments broke validation</code> 77 - [`82c7a4e`](https://github.com/yargs/yargs/commit/82c7a4e2ba300abae72c1283b0bb37aed74d1fca) <code>use console.log instead of util.print, fix #813</code> 78 - [`4df3a10`](https://github.com/yargs/yargs/commit/4df3a109288b166b51ba6aa497138495a5af6eed) <code>chore(release): 7.0.1</code> 79 - [`9c03fa4`](https://github.com/yargs/yargs/commit/9c03fa497bd15111fac9d0592f14a89cc7982ddf) <code>fix: --help with default command should print top-level help (#810)</code> 80 - [`5334370`](https://github.com/yargs/yargs/commit/53343705064194b2b9261b128d3feb47f20efe72) <code>docs: env vars now take precedence over config file/objects (#808)</code> 81 - [`bc56468`](https://github.com/yargs/yargs/commit/bc564685df4aa45b828f22b813ce567ea0565061) <code>docs: a couple small twaks to the CHANGELOG</code> 82 - [`57dc7b5`](https://github.com/yargs/yargs/commit/57dc7b5dad874b716ad522863a480eab92212f00) <code>chore(release): 7.0.0</code> 83 - [`f3f074b`](https://github.com/yargs/yargs/commit/f3f074bd983e9b2dea6df94e21febfeef27b6de4) <code>fix: positional arguments of sub-commands threw strict() exception (#805)</code> 84 - [`a607061`](https://github.com/yargs/yargs/commit/a6070619b85d8d1662afbb26ca45585dae2620ec) <code>fix: console.warn() rather than throwing errors when api signatures are incorrect (#804)</code> 85 - [`d78a0f5`](https://github.com/yargs/yargs/commit/d78a0f5b42d41f3959c451b8e2f81e8fdbac845e) <code>feat: introduces support for default commands, using the '*' identifier (#785)</code> 86 - [`8a992f5`](https://github.com/yargs/yargs/commit/8a992f535e395e0994afdfebf5c40b5838b5280d) <code>fix: errors were not bubbling appropriately from sub-commands to top-level (#802)</code> 87 - [`07e39b7`](https://github.com/yargs/yargs/commit/07e39b79dbaf64cb03d05ea23e0741b3b80b1fcb) <code>fix: running parse() multiple times on the same yargs instance caused exception if help() enabled (#790)</code> 88 - [`48575cd`](https://github.com/yargs/yargs/commit/48575cd50d53818491d48aeaec84436be51c4085) <code>fix: context variables are now recognized in strict() mode (#796)</code> 89 90 91 There are 29 commits in total. See the [full diff](https://github.com/yargs/yargs/compare/e5613f0355dbf75f6e4c51836affb20b4ef0e2fc...8756a3c63dfd2ceae303067b46075de5c982af66). 92 93 --- 94 | ✨ Try the all new [Greenkeeper GitHub Integration](https://git.io/uptodate) ✨ | 95 | --- | 96 | With [Integrations](https://developer.github.com/early-access/integrations/) **first-class bot support** landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. **Simpler setup, fewer pull-requests, faster than ever**.<br><br> <details><summary>Screencast</summary><img src="https://cloud.githubusercontent.com/assets/908178/19868156/20c1c0c4-9fa7-11e6-9f17-611c51677dbd.gif" /></details><br> [**Try it today**](https://git.io/uptodate). Free for private repositories during beta. | 97