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

Merged
merged 1 commit into from
Apr 13, 2022
Merged

Configure Renovate #729

merged 1 commit into from
Apr 13, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 16, 2022

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/close-milestone.yml (github-actions)
  • .github/workflows/dependabot-merge.yml (github-actions)
  • .github/workflows/draft-release.yml (github-actions)
  • .github/workflows/publish-nuget.yml (github-actions)
  • .github/workflows/sync-labels.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • .github/workflows/update-milestone.yml (github-actions)
  • dotnet/actions/install-dotnet-sdk/action.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
  • 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 10 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • 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
  • Do not upgrade from Alpine stable to edge
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Automerge patch upgrades if they pass tests
  • Raise PR when vulnerability alerts are detected with label :old_key: security

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

Update dependency json-schema to 0.4.0 [SECURITY]
  • Branch name: renovate/npm-json-schema-vulnerability
  • Merge into: master
  • Upgrade json-schema to 0.4.0
Pin dependencies
Update dependency typescript to v4.1.6
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.1.x
  • Merge into: master
  • Upgrade typescript to 4.1.6
Update github actions (patch)
  • Schedule: ["at any time"]
  • Branch name: renovate/patch-github-actions
  • Merge into: master
  • Upgrade actions/checkout to v2.3.5
  • Upgrade gittools/actions to v0.9.13
Update RocketSurgeonsGuild/actions action to v0.3.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rocket-surgery-other
  • Merge into: master
  • Upgrade RocketSurgeonsGuild/actions to v0.3.0
Update actions/checkout action to v2.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github-actions
  • Merge into: master
  • Upgrade actions/checkout to v2.4.0
Update dependency ix to v4.5.2
  • Schedule: ["at any time"]
  • Branch name: renovate/ix-4.x
  • Merge into: master
  • Upgrade ix to 4.5.2
Update dependency typescript to v4.6.3
  • Schedule: ["at any time"]
  • Branch name: renovate/typescript-4.x
  • Merge into: master
  • Upgrade typescript to 4.6.3
Update dependency @​actions/github to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-github-5.x
  • Merge into: master
  • Upgrade @actions/github to 5.0.1
Update dependency eslint to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/eslint-8.x
  • Merge into: master
  • Upgrade eslint to 8.13.0
Update dependency rxjs to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rxjs-7.x
  • Merge into: master
  • Upgrade rxjs to 7.5.5
Update github actions (major)
Update jest monorepo (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jest-monorepo
  • Merge into: master
  • Upgrade jest to 27.5.1
  • Upgrade ts-jest to 27.1.4
Update typescript-eslint monorepo to v5 (major)

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

@github-actions github-actions bot added this to the v0.3.1 milestone Feb 16, 2022
@renovate renovate bot force-pushed the renovate/configure branch 7 times, most recently from ec3bf9d to 44a1103 Compare February 24, 2022 03:05
@renovate renovate bot force-pushed the renovate/configure branch 5 times, most recently from 1a0de02 to 7e7bb76 Compare March 7, 2022 03:06
@renovate renovate bot force-pushed the renovate/configure branch 10 times, most recently from ee2eb05 to 7b07807 Compare March 22, 2022 03:04
@renovate renovate bot force-pushed the renovate/configure branch 6 times, most recently from 52f5e8d to baf0436 Compare March 28, 2022 03:06
@renovate renovate bot force-pushed the renovate/configure branch 5 times, most recently from 899f988 to b884c8f Compare April 11, 2022 03:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ mysterious We forgot to label this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants