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 #6

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

Configure Renovate #6

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jan 7, 2021

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

  • .github/workflows/build.yml (github-actions)
  • .github/workflows/format.yml (github-actions)
  • .github/workflows/lint.yml (github-actions)
  • 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 20 Pull Requests:

chore(deps): update dependency elliptic to 6.5.4 [security]
  • Branch name: renovate/npm-elliptic-vulnerability
  • Merge into: master
  • Upgrade elliptic to 6.5.4
chore(deps): update dependency ini to 1.3.6 [security]
  • Branch name: renovate/npm-ini-vulnerability
  • Merge into: master
  • Upgrade ini to 1.3.6
chore(deps): update dependency node-fetch to 2.6.1 [security]
  • Branch name: renovate/npm-node-fetch-vulnerability
  • Merge into: master
  • Upgrade node-fetch to 2.6.1
chore(deps): pin dependencies
chore(deps): update dependency @​types/node to v14.14.35
  • Schedule: ["at any time"]
  • Branch name: renovate/node-14.x
  • Merge into: master
  • Upgrade @types/node to 14.14.35
chore(deps): update dependency @​types/react to v17.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/react-17.x
  • Merge into: master
  • Upgrade @types/react to 17.0.3
chore(deps): update dependency eslint to v7.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-7.x
  • Merge into: master
  • Upgrade eslint to 7.22.0
chore(deps): update dependency eslint-plugin-prettier to v3.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-prettier-3.x
  • Merge into: master
  • Upgrade eslint-plugin-prettier to 3.3.1
chore(deps): update dependency eslint-plugin-react to v7.22.0
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-plugin-react-7.x
  • Merge into: master
  • Upgrade eslint-plugin-react to 7.22.0
chore(deps): update dependency husky to v4.3.8
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-4.x
  • Merge into: master
  • Upgrade husky to 4.3.8
chore(deps): update dependency prettier to v2.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/prettier-2.x
  • Merge into: master
  • Upgrade prettier to 2.2.1
chore(deps): update dependency typescript to v4.2.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: master
  • Upgrade typescript to 4.2.3
chore(deps): update typescript-eslint monorepo to v4.18.0
fix(deps): update dependency next to v10.0.9
  • Schedule: ["at any time"]
  • Branch name: renovate/nextjs-monorepo
  • Merge into: master
  • Upgrade next to 10.0.9
fix(deps): update dependency sass to v1.32.8
  • Schedule: ["at any time"]
  • Branch name: renovate/sass-1.x
  • Merge into: master
  • Upgrade sass to 1.32.8
fix(deps): update dependency uuid to v8.3.2
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-8.x
  • Merge into: master
  • Upgrade uuid to 8.3.2
chore(deps): update actions/setup-node action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-node-2.x
  • Merge into: master
  • Upgrade actions/setup-node to v2
chore(deps): update dependency eslint-config-prettier to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-config-prettier-8.x
  • Merge into: master
  • Upgrade eslint-config-prettier to 8.1.0
chore(deps): update dependency eslint-plugin-simple-import-sort to v7
chore(deps): update dependency husky to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/husky-5.x
  • Merge into: master
  • Upgrade husky to 5.1.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.

None yet

1 participant