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/release.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
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
Use semantic prefixes for commit messages and PR titles
If semantic commits detected, use semantic commit type fix for all
Removes rate limit for PR creation per hour
Remove limit for open PRs at any time
Disable Renovate Dependency Dashboard creation
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
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
Use semantic prefixes for commit messages and PR titles
If semantic commits detected, use semantic commit type fix for all
Removes rate limit for PR creation per hour
Remove limit for open PRs at any time
Disable Renovate Dependency Dashboard creation
š” 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 5 Pull Requests:
fix(deps): update npm dependency semantic-release to v19 [security]
- Branch name: `renovate/npm-semantic-release-vulnerability`
- Merge into: `master`
- Upgrade [semantic-release](https://togithub.com/semantic-release/semantic-release) to `19.0.3`
fix(deps): pin dependencies
- Schedule: ["at any time"]
- Branch name: `renovate/pin-dependencies`
- Merge into: `master`
- Pin [@google/semantic-release-replace-plugin](https://togithub.com/google/semantic-release-replace-plugin) to `1.1.0`
- Pin [@semantic-release/github](https://togithub.com/semantic-release/github) to `7.2.3`
fix(deps): update actions/checkout action to v3
- Schedule: ["at any time"]
- Branch name: `renovate/github-tags-actions-checkout-3.x`
- Merge into: `master`
- Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v3`
fix(deps): update actions/setup-node action to v3
- Schedule: ["at any time"]
- Branch name: `renovate/github-tags-actions-setup-node-3.x`
- Merge into: `master`
- Upgrade [actions/setup-node](https://togithub.com/actions/setup-node) to `v3`
fix(deps): update semantic-release monorepo (major)
- Schedule: ["at any time"]
- Branch name: `renovate/major-semantic-release-monorepo`
- Merge into: `master`
- Upgrade [@semantic-release/git](https://togithub.com/semantic-release/git) to `10.0.1`
- Upgrade [@semantic-release/github](https://togithub.com/semantic-release/github) to `8.0.4`
ā 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.
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/release.yml(github-actions)package.json(npm)Configuration Summary
Based on the default config's presets, Renovate will:
fixfor dependencies andchorefor all othersnode_modules,bower_components,vendorand various test/tests directoriesfixfor dependencies andchorefor all othersnode_modules,bower_components,vendorand various test/tests directoriesfixfor allfixfor dependencies andchorefor all othersnode_modules,bower_components,vendorand various test/tests directoriesfixfor dependencies andchorefor all othersnode_modules,bower_components,vendorand various test/tests directoriesfixfor allš” Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.jsonin 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 5 Pull Requests:
fix(deps): update npm dependency semantic-release to v19 [security]
- Branch name: `renovate/npm-semantic-release-vulnerability` - Merge into: `master` - Upgrade [semantic-release](https://togithub.com/semantic-release/semantic-release) to `19.0.3`fix(deps): pin dependencies
- Schedule: ["at any time"] - Branch name: `renovate/pin-dependencies` - Merge into: `master` - Pin [@google/semantic-release-replace-plugin](https://togithub.com/google/semantic-release-replace-plugin) to `1.1.0` - Pin [@semantic-release/github](https://togithub.com/semantic-release/github) to `7.2.3`fix(deps): update actions/checkout action to v3
- Schedule: ["at any time"] - Branch name: `renovate/github-tags-actions-checkout-3.x` - Merge into: `master` - Upgrade [actions/checkout](https://togithub.com/actions/checkout) to `v3`fix(deps): update actions/setup-node action to v3
- Schedule: ["at any time"] - Branch name: `renovate/github-tags-actions-setup-node-3.x` - Merge into: `master` - Upgrade [actions/setup-node](https://togithub.com/actions/setup-node) to `v3`fix(deps): update semantic-release monorepo (major)
- Schedule: ["at any time"] - Branch name: `renovate/major-semantic-release-monorepo` - Merge into: `master` - Upgrade [@semantic-release/git](https://togithub.com/semantic-release/git) to `10.0.1` - Upgrade [@semantic-release/github](https://togithub.com/semantic-release/github) to `8.0.4`ā 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 Renovate Bot.