Based on the default config's presets, Renovate will:
Start dependency updates only once this onboarding MR is merged
Show all Merge Confidence badges for pull requests.
Enable Renovate Dependency Dashboard creation.
Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
Ignore node_modules, bower_components, vendor and various test/tests directories.
Group known monorepo packages together.
Use curated list of recommended non-monorepo package groupings.
Apply crowd-sourced package replacement rules.
Apply crowd-sourced workarounds for known problems with packages.
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 4 Merge Requests:
Update gopkg.in/mgo.v2 digest to 7446a03
Schedule: ["at any time"]
Branch name: renovate/gopkg.in-mgo.v2-digest
Merge into: master
Upgrade gopkg.in/mgo.v2 to 7446a0344b7872c067b3d6e1b7642571eafbae17
Update module github.com/mattn/go-sqlite3 to v1.14.18
Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm 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.
