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

Closed
wants to merge 1 commit into from
Closed

Configure Renovate #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Sep 23, 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

  • package.json (npm)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Enable Renovate Dependency Dashboard creation
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • 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
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133

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

chore(deps): pin dependencies
chore(deps): update dependency @​types/jest to v26.0.24
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-26.x
  • Merge into: main
  • Upgrade @types/jest to 26.0.24
chore(deps): update dependency @​types/react-dom to v16.9.14
  • Schedule: ["at any time"]
  • Branch name: renovate/react-dom-16.x
  • Merge into: main
  • Upgrade @types/react-dom to 16.9.14
chore(deps): update dependency rollup-plugin-sass to v1.2.8
  • Schedule: ["at any time"]
  • Branch name: renovate/rollup-plugin-sass-1.x
  • Merge into: main
  • Upgrade rollup-plugin-sass to 1.2.8
chore(deps): update dependency typescript to v3.9.10
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-3.x
  • Merge into: main
  • Upgrade typescript to 3.9.10
chore(deps): update dependency @testing-library/react-hooks to v3.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-react-hooks-3.x
  • Merge into: main
  • Upgrade @testing-library/react-hooks to 3.7.0
chore(deps): update dependency @​types/react to v16.14.15
  • Schedule: ["at any time"]
  • Branch name: renovate/react-16.x
  • Merge into: main
  • Upgrade @types/react to 16.14.15
chore(deps): update dependency jest to v26.6.3
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-monorepo
  • Merge into: main
  • Upgrade jest to 26.6.3
chore(deps): update dependency ts-jest to v26.5.6
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-jest-26.x
  • Merge into: main
  • Upgrade ts-jest to 26.5.6
chore(deps): update react monorepo
chore(deps): update dependency @testing-library/react-hooks to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/testing-library-react-hooks-7.x
  • Merge into: main
  • Upgrade @testing-library/react-hooks to 7.0.2
chore(deps): update dependency @​types/jest to v27
  • Schedule: ["at any time"]
  • Branch name: renovate/jest-27.x
  • Merge into: main
  • Upgrade @types/jest to 27.0.2
chore(deps): update dependency @​types/react to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/react-17.x
  • Merge into: main
  • Upgrade @types/react to 17.0.24
chore(deps): update dependency @​types/react-dom to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/react-dom-17.x
  • Merge into: main
  • Upgrade @types/react-dom to 17.0.9
chore(deps): update dependency typescript to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: main
  • Upgrade typescript to 4.4.3
chore(deps): update jest monorepo (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: main
  • Upgrade jest to 27.2.2
  • Upgrade ts-jest to 27.0.5
chore(deps): update react monorepo to v17 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to 17.0.2
  • Upgrade react-dom to 17.0.2
  • Upgrade react-test-renderer to 17.0.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.


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

@renovate renovate bot force-pushed the renovate/configure branch 3 times, most recently from 2d37fc9 to 09df3e2 Compare September 27, 2021 19:04
@renovate
Copy link
Author

renovate bot commented Sep 28, 2021

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

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

2 participants