GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.
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-include)
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 Renovate detects semantic commits, it will 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.
A collection of 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
It looks like your repository dependencies are already up-to-date and no Merge Requests will be necessary right away.
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.
