Skip to content
Snippets Groups Projects

Configure Renovate

Merged Renovate-Bot requested to merge renovate/configure into V2.0

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

:vertical_traffic_light: To activate Renovate, merge this Merge Request. To disable Renovate, simply close this Merge Request unmerged.


Detected Package Files

  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • api/Dockerfile (dockerfile)
  • .gitlab-ci.yml (gitlabci)
  • api/package.json (npm)
  • 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 20 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 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
  • Preserve (but continue to upgrade) any existing SemVer ranges
  • Enable Renovate Dependency Dashboard creation
  • Rebase existing MRs any time the base branch has been updated
  • Raise MR when vulnerability alerts are detected with label 'security'
  • Use curated list of recommended non-monorepo package groupings

:abcd: 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 20 Merge Requests:

chore(deps): update devdependencies (non-major)
chore(deps): update node.js to v12.22
  • Schedule: ["at any time"]
  • Branch name: renovate/node-12.x
  • Merge into: V2.0
  • Upgrade node to 12.22
fix(deps): update angular monorepo to ~13.3.0
fix(deps): update dependency json-server to ^0.17.0
  • Schedule: ["at any time"]
  • Branch name: renovate/json-server-0.x
  • Merge into: V2.0
  • Upgrade json-server to ^0.17.0
fix(deps): update dependency leaflet.locatecontrol to ^0.76.0
  • Schedule: ["at any time"]
  • Branch name: renovate/leaflet.locatecontrol-0.x
  • Merge into: V2.0
  • Upgrade leaflet.locatecontrol to ^0.76.0
chore(deps): update dependency @​types/jasmine to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-4.x
  • Merge into: V2.0
  • Upgrade @types/jasmine to ~4.0.0
chore(deps): update dependency @​types/node to v16
  • Schedule: ["at any time"]
  • Branch name: renovate/node-16.x
  • Merge into: V2.0
  • Upgrade @types/node to ^16.0.0
chore(deps): update dependency jasmine-core to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-jasmine-monorepo
  • Merge into: V2.0
  • Upgrade jasmine-core to ~4.1.0
chore(deps): update dependency jasmine-spec-reporter to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/jasmine-spec-reporter-7.x
  • Merge into: V2.0
  • Upgrade jasmine-spec-reporter to ~7.0.0
chore(deps): update dependency karma-browserify to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-browserify-8.x
  • Merge into: V2.0
  • Upgrade karma-browserify to ^8.0.0
chore(deps): update dependency karma-jasmine to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/karma-jasmine-5.x
  • Merge into: V2.0
  • Upgrade karma-jasmine to ~5.0.0
chore(deps): update dependency ts-node to v10
  • Schedule: ["at any time"]
  • Branch name: renovate/ts-node-10.x
  • Merge into: V2.0
  • Upgrade ts-node to ~10.7.0
chore(deps): update node.js to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/node-18.x
  • Merge into: V2.0
  • Upgrade node to 18.2
fix(deps): update ag-grid monorepo to v27 (major)
fix(deps): update dependency @​asymmetrik/ngx-leaflet to v13
  • Schedule: ["at any time"]
  • Branch name: renovate/asymmetrik-ngx-leaflet-13.x
  • Merge into: V2.0
  • Upgrade @asymmetrik/ngx-leaflet to ^13.0.0
fix(deps): update dependency @ngx-translate/core to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/ngx-translate-core-14.x
  • Merge into: V2.0
  • Upgrade @ngx-translate/core to ^14.0.0
fix(deps): update dependency ag-grid-angular to v27
  • Schedule: ["at any time"]
  • Branch name: renovate/ag-grid-angular-27.x
  • Merge into: V2.0
  • Upgrade ag-grid-angular to ^27.0.0
fix(deps): update dependency luxon to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/luxon-2.x
  • Merge into: V2.0
  • Upgrade luxon to ^2.0.0
fix(deps): update dependency ngx-toastr to v14
  • Schedule: ["at any time"]
  • Branch name: renovate/ngx-toastr-14.x
  • Merge into: V2.0
  • Upgrade ngx-toastr to ^14.0.0
fix(deps): update dependency rxjs to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/rxjs-7.x
  • Merge into: V2.0
  • Upgrade rxjs to ~7.5.0

:children_crossing: 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.


:warning: Dependency Lookup Warnings :warning:

Please correct - or verify that you can safely ignore - these lookup failures before you merge this MR.

  • Failed to look up dependency ${DEPENDENCY_MROXY}node
  • Failed to look up dependency ${CI_DEPENDENCY_MROXY_DIRECT_GROUP_IMAGE_MREFIX}/docker
  • Failed to look up dependency ${CI_DEPENDENCY_MROXY_DIRECT_GROUP_IMAGE_MREFIX}/sonarsource/sonar-scanner-cli

Files affected: Dockerfile, .gitlab-ci.yml


:question: 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.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Loading
Please register or sign in to reply
Loading