Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S spring-batch-utils
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mainz
  • spring-batch-utils
  • Merge requests
  • !1

Merged
Created Nov 06, 2020 by Renovate Bot@renovatebotContributor

Configure Renovate

  • Overview 0
  • Commits 1
  • Changes 1

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

  • .gitlab-ci.yml (gitlabci)
  • pom.xml (maven)

Configuration Summary

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

  • Start dependency updates only once this onboarding MR is merged
  • Preserve (but continue to upgrade) any existing semver ranges
  • Group all updates together
  • Separate major versions of dependencies into individual branches/MRs
  • Do not separate patch and minor upgrades into separate MRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise MRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all MRs
  • 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
  • Ignore wrongly tagged actions/setup-node v2 releases

🔡 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 1 Merge Request:

chore(deps): update all dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/all
  • Merge into: master
  • Upgrade org.apache.maven.plugins:maven-compiler-plugin to 3.8.1
  • Upgrade org.springframework.batch:spring-batch-core to 4.3.0

❓ 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 Nov 15, 2020 by Renovate Bot
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: renovate/configure