osprey-method-handler icon indicating copy to clipboard operation
osprey-method-handler copied to clipboard

Configure Renovate

Open ghost opened this issue 5 years ago • 0 comments

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

:vertical_traffic_light: To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this Configure Renovate PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Update existing lock files only when package.json is modified
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

:abcd: Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.


You have configured Renovate to use branch master as base branch.

What to Expect

With your current configuration, Renovate will create 11 Pull Requests:

Pin dependencies
Update dependency finalhandler to v1.1.2
  • Schedule: "at any time"
  • Branch name: renovate/finalhandler-1.x
  • Merge into: master
  • Upgrade finalhandler to 1.1.2
Update dependency form-data to v2.5.1
  • Schedule: "at any time"
  • Branch name: renovate/form-data-2.x
  • Merge into: master
  • Upgrade form-data to 2.5.1
Update dependency mocha to v6.2.2
  • Schedule: "at any time"
  • Branch name: renovate/mocha-6.x
  • Merge into: master
  • Upgrade mocha to 6.2.2
Update dependency nyc to v14.1.1
  • Schedule: "at any time"
  • Branch name: renovate/nyc-14.x
  • Merge into: master
  • Upgrade nyc to 14.1.1
Update dependency osprey-router to v0.6.3
  • Schedule: "at any time"
  • Branch name: renovate/osprey-router-0.x
  • Merge into: master
  • Upgrade osprey-router to 0.6.3
Update dependency popsicle to v12.0.5
  • Schedule: "at any time"
  • Branch name: renovate/popsicle-12.x
  • Merge into: master
  • Upgrade popsicle to 12.0.5
Update dependency sinon to v7.5.0
  • Schedule: "at any time"
  • Branch name: renovate/sinon-7.x
  • Merge into: master
  • Upgrade sinon to 7.5.0
Update dependency form-data to v3
  • Schedule: "at any time"
  • Branch name: renovate/form-data-3.x
  • Merge into: master
  • Upgrade form-data to 3.0.0
Update dependency popsicle-server to v3
  • Schedule: "at any time"
  • Branch name: renovate/popsicle-server-3.x
  • Merge into: master
  • Upgrade popsicle-server to 3.0.0
Update dependency standard to v14
  • Schedule: "at any time"
  • Branch name: renovate/standard-14.x
  • Merge into: master
  • Upgrade standard to 14.3.1

:children_crossing: Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for details.


:question: Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here.

ghost avatar Nov 16 '19 19:11 ghost