Skip to content

Configure Renovate - autoclosed

HTML-validate requested to merge renovate/configure into master

Welcome to Renovate! This is an onboarding MR to help you understand and configure settings before regular Merge Requests begin.

🚦 To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge 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 MR 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 MR creation to a maximum of two per hour
  • Limit to maximum 10 open MRs 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
  • Pin dependency versions for devDependencies and retain SemVer ranges for others
  • If automerging, push the new commit directly to base branch (no MR)
  • Automerge patch and minor upgrades if they pass tests
  • Append Git Signed-off-by: signature to Git commits.
  • Apply label renovate to MRs
  • Wait until branch tests have passed or failed before creating the MR
  • Rebase existing MRs any time the base branch has been updated

🔡 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 Merge 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 10 Merge Requests:

chore(deps): pin dependencies
chore(deps): pin dependencies
chore(deps): update dependency @​vue/compiler-sfc to v3.2.30
  • Schedule: ["at any time"]
  • Branch name: renovate/vue-monorepo
  • Merge into: master
  • Upgrade @vue/compiler-sfc to 3.2.30
chore(deps): update dependency cypress-html-validate to v2.1.3
  • Schedule: ["at any time"]
  • Branch name: renovate/cypress-html-validate-2.x
  • Merge into: master
  • Upgrade cypress-html-validate to 2.1.3
chore(deps): update dependency html-validate-vue to v4.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/html-validate-vue-4.x
  • Merge into: master
  • Upgrade html-validate-vue to 4.0.3
chore(deps): update dependency sass to v1.49.7
  • Schedule: ["at any time"]
  • Branch name: renovate/sass-1.x
  • Merge into: master
  • Upgrade sass to 1.49.7
chore(deps): update dependency cypress to v9.4.1
  • Schedule: ["at any time"]
  • Branch name: renovate/cypress-9.x
  • Merge into: master
  • Upgrade cypress to 9.4.1
chore(deps): update dependency html-validate to v6.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/html-validate-6.x
  • Merge into: master
  • Upgrade html-validate to 6.3.1
chore(deps): update dependency sass-loader to v12
  • Schedule: ["at any time"]
  • Branch name: renovate/sass-loader-12.x
  • Merge into: master
  • Upgrade sass-loader to 12.4.0
fix(deps): update dependency @​fortawesome/fontawesome-free to v6

🚸 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 MR has been generated by Renovate Bot.

Edited by HTML-validate

Merge request reports