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.md (3046B)


      1 # PR #111 Configure Renovate
      2 
      3 - **Status:** merged
      4 - **Author:** @renovate[bot]
      5 - **Created:** 2018-03-25T15:59:41Z
      6 - **Branch:** renovate/configure → master
      7 - **Merged:** 2018-03-25T16:03:43Z
      8 - **Labels:** enhancement
      9 - **Assignees:** @MTRNord
     10 - **Diff:** [111.diff](./111.diff)
     11 
     12 ---
     13 
     14 Welcome to [Renovate](https://renovateapp.com)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
     15 
     16 Renovate will begin keeping your dependencies up-to-date only once you merge this Pull Request.
     17 If you close this Pull Request unmerged, then Renovate will be disabled.
     18 
     19 If you have any questions, try reading our [Docs](https://renovateapp.com/docs), particularly the Getting Started section.
     20 You 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.
     21 
     22 ---
     23 ## Detected Package Files
     24 
     25  * `package.json`
     26 
     27 ## Configuration Summary
     28 
     29 Based on the currently configured presets, Renovate will:
     30 
     31   - Start dependency updates once this Configure Renovate PR is merged or closed
     32   - Separate major versions of dependencies into individual branches/PRs
     33   - Combine any patch and minor upgrades together into same branch/PR
     34   - Upgrade to unstable versions only if the existing version is unstable
     35   - Raise PRs immediately (after branch is created)
     36   - Use <code>renovate/</code> as prefix for all branch names
     37   - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others
     38   - Keep existing branches updated even when not scheduled
     39   - Disable automerging feature - wait for humans to merge all PRs
     40   - Ignore `node_modules`, `bower_components`, and various test/tests directories
     41   - Update existing lock files only when <code>package.json</code> is modified
     42   - Autodetect whether to pin dependencies or maintain ranges
     43   - Rate limit PR creation to a maximum of two per hour
     44   - Limit to maximum 20 concurrent Renovate PRs at any time
     45 
     46 Would 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.
     47 
     48 ---
     49 
     50 ### What to Expect
     51 
     52 With your current configuration, Renovate will create 2 Pull Requests:
     53 
     54 1. **fix(deps): update dependency node-telegram-bot-api to ^0.30.0**
     55 
     56   - Branch name: `renovate/node-telegram-bot-api-0.x`
     57   - Upgrades [node-telegram-bot-api](https://github.com/yagop/node-telegram-bot-api) in `dependencies` from `^0.29.0` to `^0.30.0`
     58 
     59 
     60 2. **fix(deps): update dependency yargs to ^11.0.0**
     61 
     62   - Branch name: `renovate/yargs-11.x`
     63   - Upgrades [yargs](https://github.com/yargs/yargs) in `dependencies` from `^9.0.1` to `^11.0.0`
     64 
     65 
     66 
     67 ---
     68 
     69 
     70 ---
     71 
     72 This PR has been generated by [Renovate Bot](https://renovateapp.com).
     73 
     74