freifunk-bot.meta

Issues/PRs archive for MTRNord/freifunk-bot
git clone git://archive.git.mtrnord.blog/MTRNord/freifunk-bot.meta.git
Log | Files | Refs

111.json (3282B)


      1 {
      2   "number": 111,
      3   "title": "Configure Renovate",
      4   "state": "merged",
      5   "diff_file": "111.diff",
      6   "author": "renovate[bot]",
      7   "created_at": "2018-03-25T15:59:41Z",
      8   "closed_at": "2018-03-25T16:03:43Z",
      9   "merged_at": "2018-03-25T16:03:43Z",
     10   "base_ref": "master",
     11   "head_ref": "renovate/configure",
     12   "labels": [
     13     "enhancement"
     14   ],
     15   "assignees": [
     16     "MTRNord"
     17   ],
     18   "requested_reviewers": [],
     19   "body": "Welcome to [Renovate](https://renovateapp.com)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.\n\nRenovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.\nIf you close this Pull Request unmerged, then Renovate will be disabled.\n\nIf you have any questions, try reading our [Docs](https://renovateapp.com/docs), particularly the Getting Started section.\nYou can post questions in [our Config Help repository](https://github.com/renovateapp/config-help/issues) or @ the app author @rarkins in this PR and he'll probably see it.\n\n---\n## Detected Package Files\n\n * `package.json`\n\n## Configuration Summary\n\nBased on the currently configured presets, Renovate will:\n\n  - Start dependency updates once this Configure Renovate PR is merged or closed\n  - Separate major versions of dependencies into individual branches/PRs\n  - Combine any patch and minor upgrades together into same branch/PR\n  - Upgrade to unstable versions only if the existing version is unstable\n  - Raise PRs immediately (after branch is created)\n  - Use <code>renovate/</code> as prefix for all branch names\n  - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others\n  - Keep existing branches updated even when not scheduled\n  - Disable automerging feature - wait for humans to merge all PRs\n  - Ignore `node_modules`, `bower_components`, and various test/tests directories\n  - Update existing lock files only when <code>package.json</code> is modified\n  - Autodetect whether to pin dependencies or maintain ranges\n  - Rate limit PR creation to a maximum of two per hour\n  - Limit to maximum 20 concurrent Renovate PRs at any time\n\nWould you like to change the way Renovate is upgrading your dependencies? Simply edit the `renovate.json` in this branch and this Pull Request description will be updated the next time Renovate runs. Try to use Config Presets (the `extends` array) when possible rather than raw config, as then this PR will be able to more accurately describe your settings.\n\n---\n\n### What to Expect\n\nWith your current configuration, Renovate will create 2 Pull Requests:\n\n1. **fix(deps): update dependency node-telegram-bot-api to ^0.30.0**\n\n  - Branch name: `renovate/node-telegram-bot-api-0.x`\n  - Upgrades [node-telegram-bot-api](https://github.com/yagop/node-telegram-bot-api) in `dependencies` from `^0.29.0` to `^0.30.0`\n\n\n2. **fix(deps): update dependency yargs to ^11.0.0**\n\n  - Branch name: `renovate/yargs-11.x`\n  - Upgrades [yargs](https://github.com/yargs/yargs) in `dependencies` from `^9.0.1` to `^11.0.0`\n\n\n\n---\n\n\n---\n\nThis PR has been generated by [Renovate Bot](https://renovateapp.com).\n",
     20   "comments": [],
     21   "review_comments": []
     22 }