Skip to content
This repository was archived by the owner on Jan 19, 2024. It is now read-only.

Conversation

@ghost
Copy link

@ghost ghost commented Nov 15, 2019

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

🚦 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

🔡 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 22 Pull Requests:

chore(deps): pin dependencies
chore(deps): update commitlint monorepo
chore(deps): update dependency browserify to v16.5.0
  • Schedule: "at any time"
  • Branch name: renovate/browserify-16.x
  • Merge into: master
  • Upgrade browserify to 16.5.0
chore(deps): update dependency eslint-config-airbnb-base to v13.2.0
  • Schedule: "at any time"
  • Branch name: renovate/eslint-config-airbnb-base-13.x
  • Merge into: master
  • Upgrade eslint-config-airbnb-base to 13.2.0
chore(deps): update dependency eslint-plugin-import to v2.18.2
  • Schedule: "at any time"
  • Branch name: renovate/eslint-plugin-import-2.x
  • Merge into: master
  • Upgrade eslint-plugin-import to 2.18.2
chore(deps): update dependency express to v4.17.1
  • Schedule: "at any time"
  • Branch name: renovate/express-4.x
  • Merge into: master
  • Upgrade express to 4.17.1
chore(deps): update dependency tslint to v5.20.1
  • Schedule: "at any time"
  • Branch name: renovate/tslint-5.x
  • Merge into: master
  • Upgrade tslint to 5.20.1
chore(deps): update dependency tslint-config-airbnb to v5.11.2
  • Schedule: "at any time"
  • Branch name: renovate/tslint-config-airbnb-5.x
  • Merge into: master
  • Upgrade tslint-config-airbnb to 5.11.2
chore(deps): update commitlint monorepo to v8 (major)
chore(deps): update dependency commitizen to v4
  • Schedule: "at any time"
  • Branch name: renovate/commitizen-4.x
  • Merge into: master
  • Upgrade commitizen to 4.0.3
chore(deps): update dependency eslint to v6
  • Schedule: "at any time"
  • Branch name: renovate/eslint-6.x
  • Merge into: master
  • Upgrade eslint to 6.7.0
chore(deps): update dependency eslint-config-airbnb-base to v14
  • Schedule: "at any time"
  • Branch name: renovate/eslint-config-airbnb-base-14.x
  • Merge into: master
  • Upgrade eslint-config-airbnb-base to 14.0.0
chore(deps): update dependency husky to v3
  • Schedule: "at any time"
  • Branch name: renovate/husky-3.x
  • Merge into: master
  • Upgrade husky to 3.1.0
chore(deps): update dependency karma to v4
  • Schedule: "at any time"
  • Branch name: renovate/karma-4.x
  • Merge into: master
  • Upgrade karma to 4.4.1
chore(deps): update dependency karma-browserify to v6
  • Schedule: "at any time"
  • Branch name: renovate/karma-browserify-6.x
  • Merge into: master
  • Upgrade karma-browserify to 6.1.0
chore(deps): update dependency karma-chrome-launcher to v3
  • Schedule: "at any time"
  • Branch name: renovate/karma-chrome-launcher-3.x
  • Merge into: master
  • Upgrade karma-chrome-launcher to 3.1.0
chore(deps): update dependency karma-coverage to v2
  • Schedule: "at any time"
  • Branch name: renovate/karma-coverage-2.x
  • Merge into: master
  • Upgrade karma-coverage to 2.0.1
chore(deps): update dependency mocha to v6
  • Schedule: "at any time"
  • Branch name: renovate/mocha-6.x
  • Merge into: master
  • Upgrade mocha to 6.2.2
chore(deps): update dependency nock to v11
  • Schedule: "at any time"
  • Branch name: renovate/nock-11.x
  • Merge into: master
  • Upgrade nock to 11.7.0
chore(deps): update dependency sinon to v7
  • Schedule: "at any time"
  • Branch name: renovate/sinon-7.x
  • Merge into: master
  • Upgrade sinon to 7.5.0
chore(deps): update dependency typescript to v3
  • Schedule: "at any time"
  • Branch name: renovate/typescript-3.x
  • Merge into: master
  • Upgrade typescript to 3.7.2
fix(deps): update dependency javascript-stringify to v2
  • Schedule: "at any time"
  • Branch name: renovate/javascript-stringify-2.x
  • Merge into: master
  • Upgrade javascript-stringify to ^2.0.0

🚸 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.


❓ 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.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 52.427% when pulling 0908762 on renovate/configure into eb7ef4c on master.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants