Skip to content
This repository has been archived by the owner on Nov 22, 2019. It is now read-only.

Configure Renovate #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Configure Renovate #20

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 26, 2018

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

  • Dockerfile (dockerfile)
  • package.json (npm)
  • packages/arcturus/package.json (npm)
  • packages/cli/package.json (npm)
  • packages/comet/package.json (npm)
  • packages/common/package.json (npm)
  • packages/core/package.json (npm)
  • packages/plus/package.json (npm)
  • .travis.yml (travis)

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 30 Pull Requests:

chore(deps): pin dependencies
chore(deps): update dependency @​nestjs/testing to v5.7.4
  • Schedule: "at any time"
  • Branch name: renovate/nest-monorepo
  • Merge into: master
  • Upgrade @nestjs/testing to 5.7.4
chore(deps): update dependency @​types/express to v4.17.2
  • Schedule: "at any time"
  • Branch name: renovate/express-4.x
  • Merge into: master
  • Upgrade @types/express to 4.17.2
chore(deps): update dependency @​types/fs-extra to v5.1.0
  • Schedule: "at any time"
  • Branch name: renovate/fs-extra-5.x
  • Merge into: master
  • Upgrade @types/fs-extra to 5.1.0
chore(deps): update dependency @​types/inquirer to v0.0.44
  • Schedule: "at any time"
  • Branch name: renovate/inquirer-0.x
  • Merge into: master
  • Upgrade @types/inquirer to 0.0.44
chore(deps): update dependency @​types/node to v10.17.5
  • Schedule: "at any time"
  • Branch name: renovate/node-10.x
  • Merge into: master
  • Upgrade @types/node to 10.17.5
chore(deps): update dependency @​types/supertest to v2.0.8
  • Schedule: "at any time"
  • Branch name: renovate/supertest-2.x
  • Merge into: master
  • Upgrade @types/supertest to 2.0.8
chore(deps): update dependency git-cz to v1.8.4
  • Schedule: "at any time"
  • Branch name: renovate/git-cz-1.x
  • Merge into: master
  • Upgrade git-cz to 1.8.4
chore(deps): update dependency nodemon to v1.19.4
  • Schedule: "at any time"
  • Branch name: renovate/nodemon-1.x
  • Merge into: master
  • Upgrade nodemon to 1.19.4
chore(deps): update dependency prettier to v1.19.1
  • Schedule: "at any time"
  • Branch name: renovate/prettier-1.x
  • Merge into: master
  • Upgrade prettier to 1.19.1
chore(deps): update dependency pretty-quick to v1.11.1
  • Schedule: "at any time"
  • Branch name: renovate/pretty-quick-1.x
  • Merge into: master
  • Upgrade pretty-quick to 1.11.1
chore(deps): update dependency supertest to v3.4.2
  • Schedule: "at any time"
  • Branch name: renovate/supertest-3.x
  • Merge into: master
  • Upgrade supertest to 3.4.2
chore(deps): update dependency ts-jest to v23.10.5
  • Schedule: "at any time"
  • Branch name: renovate/ts-jest-23.x
  • Merge into: master
  • Upgrade ts-jest to 23.10.5
chore(deps): update dependency tsconfig-paths to v3.9.0
  • Schedule: "at any time"
  • Branch name: renovate/tsconfig-paths-3.x
  • Merge into: master
  • Upgrade tsconfig-paths to 3.9.0
chore(deps): update dependency typescript to v3.7.2
  • Schedule: "at any time"
  • Branch name: renovate/typescript-3.x
  • Merge into: master
  • Upgrade typescript to 3.7.2
fix(deps): update dependency class-transformer to ^0.2.0
  • Schedule: "at any time"
  • Branch name: renovate/class-transformer-0.x
  • Merge into: master
  • Upgrade class-transformer to ^0.2.0
fix(deps): update dependency class-validator to ^0.11.0
  • Schedule: "at any time"
  • Branch name: renovate/class-validator-0.x
  • Merge into: master
  • Upgrade class-validator to ^0.11.0
chore(deps): update dependency @​nestjs/testing to v6
  • Schedule: "at any time"
  • Branch name: renovate/major-nest-monorepo
  • Merge into: master
  • Upgrade @nestjs/testing to 6.10.1
chore(deps): update dependency @​types/fs-extra to v8
  • Schedule: "at any time"
  • Branch name: renovate/fs-extra-8.x
  • Merge into: master
  • Upgrade @types/fs-extra to 8.0.1
chore(deps): update dependency @​types/inquirer to v6
  • Schedule: "at any time"
  • Branch name: renovate/inquirer-6.x
  • Merge into: master
  • Upgrade @types/inquirer to 6.5.0
chore(deps): update dependency @​types/jest to v24
  • Schedule: "at any time"
  • Branch name: renovate/jest-24.x
  • Merge into: master
  • Upgrade @types/jest to 24.0.23
chore(deps): update dependency git-cz to v3
  • Schedule: "at any time"
  • Branch name: renovate/git-cz-3.x
  • Merge into: master
  • Upgrade git-cz to 3.3.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 jest to v24
  • Schedule: "at any time"
  • Branch name: renovate/major-jest-monorepo
  • Merge into: master
  • Upgrade jest to 24.9.0
chore(deps): update dependency nodemon to v2
  • Schedule: "at any time"
  • Branch name: renovate/nodemon-2.x
  • Merge into: master
  • Upgrade nodemon to 2.0.0
chore(deps): update dependency pretty-quick to v2
  • Schedule: "at any time"
  • Branch name: renovate/pretty-quick-2.x
  • Merge into: master
  • Upgrade pretty-quick to 2.0.1
chore(deps): update dependency supertest to v4
  • Schedule: "at any time"
  • Branch name: renovate/supertest-4.x
  • Merge into: master
  • Upgrade supertest to 4.0.2
chore(deps): update dependency ts-jest to v24
  • Schedule: "at any time"
  • Branch name: renovate/ts-jest-24.x
  • Merge into: master
  • Upgrade ts-jest to 24.1.0
chore(deps): update dependency ts-loader to v6
  • Schedule: "at any time"
  • Branch name: renovate/ts-loader-6.x
  • Merge into: master
  • Upgrade ts-loader to 6.2.1
chore(deps): update dependency ts-node to v8
  • Schedule: "at any time"
  • Branch name: renovate/ts-node-8.x
  • Merge into: master
  • Upgrade ts-node to 8.5.2

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


Newsflash: Renovate has joined WhiteSource, and is now free for all use. Learn more or view updated terms and privacy policies.

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.

None yet

1 participant