renovate

dependency-management

Run Locally Via Docker

For Azure DevOps

Set the environment variables: export AZURE_DEVOPS_ORG=foo, AZURE_DEVOPS_EXT_PAT, and replace PROJECTNAME/REPO as required.

docker run --rm -it \
    -e RENOVATE_PLATFORM="azure" \
    -e RENOVATE_ENDPOINT="https://dev.azure.com/${AZURE_DEVOPS_ORG}/" \
    -e GITHUB_COM_TOKEN=$(gh auth token) \
    -e SYSTEM_ACCESSTOKEN=$AZURE_DEVOPS_EXT_PAT \
    -e RENOVATE_TOKEN=$AZURE_DEVOPS_EXT_PAT \
    -e RENOVATE_DRY_RUN=full \
    -e LOG_LEVEL=debug \
    -v ${PWD}/config.js:/usr/src/app/config.js \
    -v /var/run/docker.sock:/var/run/docker.sock \
    renovate/renovate:latest --include-forks=false --dry-run=full PROJECTNAME/REPO

Centralizing Config

Create a config.js in the renovate-config repo you created. According to the Renovate documentation, this type of config supports NuGet, npm, and GitHub authentication.

Change various options by reviewing the Renovate documentation. Options like the creation of closed pull requests can be configured by flags or environment variables.

For Azure DevOps Pipelines, see the example below. For GitHub, consider using the Renovatebot GitHub app for a smoother integration, which also checks the status by default every 3 hours.