Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configure Renovate #1

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

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 11, 2020

WhiteSource Renovate

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 onboarding 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
  • 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
  • Ignore spring cloud 1.x releases
  • Ignore http4s digest-based 1.x milestones

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


What to Expect

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

Update dependency elliptic to 6.5.4 [SECURITY]
  • Branch name: renovate/npm-elliptic-vulnerability
  • Merge into: master
  • Upgrade elliptic to 6.5.4
Update dependency ini to 1.3.6 [SECURITY]
  • Branch name: renovate/npm-ini-vulnerability
  • Merge into: master
  • Upgrade ini to 1.3.6
Update dependency socket.io to 2.4.0 [SECURITY]
  • Branch name: renovate/npm-socket.io-vulnerability
  • Merge into: master
  • Upgrade socket.io to 2.4.0
Update dependency ssri to 8.0.1 [SECURITY]
  • Branch name: renovate/npm-ssri-vulnerability
  • Merge into: master
  • Upgrade ssri to 8.0.1
Pin dependencies
Update angular monorepo
Update angularcli monorepo
Update dependency @​ionic/angular to v4.11.13
  • Schedule: ["at any time"]
  • Branch name: renovate/ionic-angular-4.x
  • Merge into: master
  • Upgrade @ionic/angular to 4.11.13
Update dependency @​ionic/angular-toolkit to v1.5.1
  • Schedule: ["at any time"]
  • Branch name: renovate/ionic-angular-toolkit-1.x
  • Merge into: master
  • Upgrade @ionic/angular-toolkit to 1.5.1
Update dependency @​types/jasmine to v2.8.17
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-2.x
  • Merge into: master
  • Upgrade @types/jasmine to 2.8.17
Update dependency @​types/jasminewd2 to v2.0.8
  • Schedule: ["at any time"]
  • Branch name: renovate/jasminewd2-2.x
  • Merge into: master
  • Upgrade @types/jasminewd2 to 2.0.8
Update dependency @​types/node to v10.17.55
  • Schedule: ["at any time"]
  • Branch name: renovate/node-10.x
  • Merge into: master
  • Upgrade @types/node to 10.17.55
Update dependency core-js to v2.6.12
  • Schedule: ["at any time"]
  • Branch name: renovate/core-js-2.x
  • Merge into: master
  • Upgrade core-js to 2.6.12
Update dependency karma-coverage-istanbul-reporter to v2.1.1
Update dependency protractor to v5.4.4
  • Schedule: ["at any time"]
  • Branch name: renovate/protractor-5.x
  • Merge into: master
  • Upgrade protractor to 5.4.4
Update dependency rxjs to v6.6.6
  • Schedule: ["at any time"]
  • Branch name: renovate/rxjs-6.x
  • Merge into: master
  • Upgrade rxjs to 6.6.6
Update dependency ts-node to v8.10.2
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-8.x
  • Merge into: master
  • Upgrade ts-node to 8.10.2
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
Update dependency typescript to v3.9.9
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-3.x
  • Merge into: master
  • Upgrade typescript to 3.9.9
Update ionic-native monorepo to v5.31.1
Update angular monorepo to v11 (major)
Update angularcli monorepo to v11 (major)
Update dependency @​ionic/angular to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/ionic-angular-5.x
  • Merge into: master
  • Upgrade @ionic/angular to 5.6.2
Update dependency @​ionic/angular-toolkit to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/ionic-angular-toolkit-3.x
  • Merge into: master
  • Upgrade @ionic/angular-toolkit to 3.1.1
Update dependency @​types/jasmine to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-3.x
  • Merge into: master
  • Upgrade @types/jasmine to 3.6.7
Update dependency codelyzer to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/codelyzer-6.x
  • Merge into: master
  • Upgrade codelyzer to 6.0.1
Update dependency core-js to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/core-js-3.x
  • Merge into: master
  • Upgrade core-js to 3.9.1
Update dependency jasmine-core to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jasmine-monorepo
  • Merge into: master
  • Upgrade jasmine-core to 3.7.1
Update dependency jasmine-spec-reporter to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-spec-reporter-6.x
  • Merge into: master
  • Upgrade jasmine-spec-reporter to 6.0.0
Update dependency karma to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-6.x
  • Merge into: master
  • Upgrade karma to 6.2.0
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
Update dependency karma-coverage-istanbul-reporter to v3
Update dependency karma-jasmine to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-jasmine-4.x
  • Merge into: master
  • Upgrade karma-jasmine to 4.0.1
Update dependency karma-jasmine-html-reporter to v1
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-jasmine-html-reporter-1.x
  • Merge into: master
  • Upgrade karma-jasmine-html-reporter to 1.5.4
Update dependency protractor to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/protractor-7.x
  • Merge into: master
  • Upgrade protractor to 7.0.0
Update dependency ts-node to v9
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-9.x
  • Merge into: master
  • Upgrade ts-node to 9.1.1
Update dependency typescript to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: master
  • Upgrade typescript to 4.2.3

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


This PR has been generated by WhiteSource Renovate. View repository job log here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant