Gitlab bot to continuously update your dependency versions. Friendly fork of dependabot-script. The main difference is that the script's source is adjusted to work with RSDP process.

Part of the @kira bots family.

We recommend to copy this project to your Gitlab. And then setup individual CI schedules for each project that you want to enable.

This is a global configuration that you should setup inside your CI variables.

• KIRA_GITLAB_PERSONAL_TOKEN - personal access token for your bot user
• GITLAB_HOSTNAME - (optional) Gitlab domain name, defaults to gitlab.com
• KIRA_GITHUB_PERSONAL_TOKEN - Github personal access token to avoid hitting rate limit

This configuration is best to be setup inside CI schedule's environment.

• PACKAGE_MANAGER_SET - magic variable, package managers to be updated, eg: npm pip docker
• DEPENDABOT_PROJECT_PATH - project to be updated, eg: wemake-services/kira-dependencies
• DEPENDABOT_DIRECTORY - directory to look for package file, defaults to /
• DEPENDABOT_SOURCE_BRANCH - (optional) Source branch for merge requests, defaults to project default branch
• DEPENDABOT_ASSIGNEE_GITLAB_ID - (optional) Gitlab user id to assign to merge requests
• DEPENDABOT_GITLAB_APPROVE_MERGE - (optional) setup to true if you want our bot to approve your merge requests
• DEPENDABOT_GITLAB_AUTO_MERGE - (optional) setup to true if you want to auto merge this request
• DEPENDABOT_MAX_MERGE_REQUESTS - (optional) setup the number of max openened merge requests you want.
• DEPENDABOT_EXTRA_CREDENTIALS - (optional) JSON of extra credential config, for example a private registry authentication (For example FontAwesome Pro: [{"type":"npm_registry","token":"<redacted>","registry":"npm.fontawesome.com"}])

• DEPENDABOT_UPDATE_STRATEGY - (optional) change how each package manager updates your dependency versions, see list of allowed values here