{"config":{"lang":["en"],"separator":"[\\s\\-,:!?=\\[\\]()<>{}\"/\\\\]+|\\.(?!\\d)|&[lg]t;","pipeline":["stopWordFilter"],"fields":{"title":{"boost":1000.0},"text":{"boost":1.0},"tags":{"boost":1000000.0}}},"docs":[{"location":"","title":"Renovate documentation","text":"

Automated dependency updates. Multi-platform and multi-language.

"},{"location":"#why-use-renovate","title":"Why use Renovate?","text":""},{"location":"#supported-platforms","title":"Supported Platforms","text":"

Renovate works on these platforms:

"},{"location":"#who-uses-renovate","title":"Who Uses Renovate?","text":"

A non-exhaustive list of companies and projects using Renovate can be seen below:

List of companies and projects that use Renovate "},{"location":"#ways-to-run-renovate","title":"Ways to run Renovate","text":"

You can run Renovate as:

Or you can use the Mend Renovate App which is hosted by Mend.

Install the Mend Renovate app for GitHub Check out our tutorial

"},{"location":"about-us/","title":"About us","text":"

Renovate was created by Mend staff and they continue to work on Renovate.

More than 1000 outside contributors helped improve Renovate.

"},{"location":"about-us/#special-thanks","title":"Special thanks","text":"

We want to highlight the work of these awesome people. Thank you for your time and effort!

"},{"location":"about-us/#maintainers","title":"Maintainers","text":"

Renovate is maintained by:

"},{"location":"about-us/#maintainers-for-features","title":"Maintainers for features","text":"

Next up, we have these people who help maintain parts of Renovate:

"},{"location":"about-us/#valuable-contributions","title":"Valuable contributions","text":"

We want to highlight these valuable contributions, even if they are one-offs. Some features made a lot of people happy, and efficient!

"},{"location":"about-us/#renovate-development","title":"Renovate development","text":"

The source code for Renovate is available on GitHub at renovatebot/renovate. This is where we do most of the development.

"},{"location":"about-us/#getting-more-paid-help","title":"Getting more paid help","text":"

If you need more assistance than what this project offers, you have two options:

  1. Become a Mend.io customer, such as by buying Renovate Enterprise, or
  2. Hire an experienced Renovate contributor privately for consulting. Mend.io staff do not offer this service, but one of our volunteer maintainers, @secustor, does
"},{"location":"about-us/#about-these-docs","title":"About these docs","text":"

The Renovate docs are built from Markdown files in our renovatebot/renovate repository. Most of the source files can be found in the docs/usage/ directory.

We use MkDocs and Material for MkDocs to build our docs.

"},{"location":"bazel/","title":"Bazel","text":"

Renovate upgrades dependencies in Bazel WORKSPACE files and MODULE.bazel files.

"},{"location":"bazel/#how-it-works","title":"How it works","text":"
  1. Bazel support is enabled automatically
  2. Renovate searches the repository for any WORKSPACE and MODULE.bazel files
  3. Renovate extracts the dependencies it finds from the files (see below for the supported dependency declarations)
  4. Renovate updates old dependencies to the latest version
"},{"location":"bazel/#bazel-module-modulebazel-support","title":"Bazel module (MODULE.bazel) support","text":""},{"location":"bazel/#bazel-registry-discovery","title":"Bazel registry discovery","text":"

Renovate searches Bazel registries to find new Bazel module versions. You customize the registries your Bazel workspace uses by including --registry entries in your .bazelrc files. Renovate checks the workspace's .bazelrc files for custom registry entries. If no registries are found, Renovate defaults to the Bazel Central Registry.

Here are some important points about Renovate's Bazel registry searches. Renovate:

"},{"location":"bazel/#example-multiple-bazelrc-files","title":"Example: multiple .bazelrc files","text":"

In this example, there is a .bazelrc file which imports another file called .registry.bazelrc. Both files have --registry values:

.bazelrc
import .registry.bazelrc\nbuild --registry=https://raw.githubusercontent.com/bazelbuild/bazel-central-registry/main\n
.registry.bazelrc
build --registry=https://example.com/custom_registry\n

The final registry list is:

  1. <https://example.com/custom_registry>
  2. <https://raw.githubusercontent.com/bazelbuild/bazel-central-registry/main>
"},{"location":"bazel/#example-registry-entries-using-bazel-configuration","title":"Example: registry entries using Bazel configuration","text":"

In this example, a .bazelrc file has registry values with and without a configuration:

.bazelrc
build:ci --registry=https://internal.server/custom_registry\nbuild --registry=https://raw.githubusercontent.com/bazelbuild/bazel-central-registry/main\n

In this case the https://internal.server/custom_registry is ignored. The final registry list is:

  1. <https://raw.githubusercontent.com/bazelbuild/bazel-central-registry/main>
"},{"location":"bazel/#supported-bazel-module-declarations","title":"Supported Bazel module declarations","text":""},{"location":"bazel/#bazel_dep","title":"bazel_dep","text":"

Renovate updates the version value for a bazel_dep declaration.

bazel_dep(name = \"cgrindel_bazel_starlib\", version = \"0.15.0\")\n

In the example above, Renovate evaluates the 0.15.0 version against the repository's registries. If Renovate finds a newer version, it updates 0.15.0 to match that version.

"},{"location":"bazel/#git_override","title":"git_override","text":"

If Renovate finds a git_override, it ignores the related bazel_dep entry and instead evaluates the commit value at the specified remote. When using git_override, the version parameter on the bazel_dep is optional.

bazel_dep(name = \"cgrindel_bazel_starlib\", version = \"0.15.0\")\n\ngit_override(\n    module_name = \"cgrindel_bazel_starlib\",\n    commit = \"fb47f0e9f7c376a7700fc9fe3319231ae57880df\",\n    remote = \"https://github.com/cgrindel/bazel-starlib.git\",\n)\n\nbazel_dep(name = \"rules_foo\")\ngit_override(\n    module_name = \"rules_foo\",\n    remote = \"https://github.com/foo/rules_foo.git\",\n    commit = \"8a1e9abe415eda7cd7f2a744fdac7499ce42cdca\",\n)\n

If the primary branch has a newer commit than in the list, Renovate updates the commit value.

"},{"location":"bazel/#single_version_override","title":"single_version_override","text":"

The single_version_override is a declaration with many purposes. Renovate only evaluates two attributes from this declaration: version and registry.

If a version is specified, it overrides the version in the bazel_dep. In the following example, Renovate notices that the version is pinned to 1.2.3. This results in rules_foo being ignored for update evaluation. When using single_version_override, the version parameter on the bazel_dep is optional.

bazel_dep(name = \"rules_foo\", version = \"1.2.4\")\n\nsingle_version_override(\n  module_name = \"rules_foo\",\n  version = \"1.2.3\",\n)\n\nbazel_dep(name = \"rules_bar\")\n\nsingle_version_override(\n  module_name = \"rules_bar\",\n  version = \"1.2.3\",\n)\n

If a registry is specified, Renovate uses the specified registry URL to check for a new version. In the following example, Renovate only uses the https://example.com/custom_registry registry to discover rules_foo versions. Any registry values specified in the repository's .bazelrc files are ignored for the rules_foo module.

bazel_dep(name = \"rules_foo\", version = \"1.2.3\")\n\nsingle_version_override(\n  module_name = \"rules_foo\",\n  registry = \"https://example.com/custom_registry\",\n)\n
"},{"location":"bazel/#archive_override-and-local_path_override","title":"archive_override and local_path_override","text":"

If Renovate finds an archive_override or a local_path_override, it ignores the related bazel_dep. Because these declarations lack versionable attributes, Renovate does not update them. When using archive_override and local_path_override, the version parameter on the bazel_dep is optional.

bazel_dep(name = \"rules_foo\", version = \"1.2.3\")\n\narchive_override(\n  module_name = \"rules_foo\",\n  urls = [\n    \"https://example.com/archive.tar.gz\",\n  ],\n)\n\nbazel_dep(name = \"rules_bar\")\n\narchive_override(\n  module_name = \"rules_bar\",\n  urls = [\n    \"https://example.com/archive.tar.gz\",\n  ],\n)\n
"},{"location":"bazel/#multiple_version_override","title":"multiple_version_override","text":"

Renovate ignores multiple_version_override. multiple_version_override does not affect the processing of version updates for a module.

"},{"location":"bazel/#lockfile-support","title":"Lockfile support","text":"

Renovate updates the MODULE.bazel.lock file after modifying dependencies in MODULE.bazel. When Renovate changes a bazel_dep version, it runs bazel mod deps to regenerate the lockfile.

For this to work:

  1. Your repository must already have a MODULE.bazel.lock file
  2. Bazelisk must be available in the environment, or Renovate must be configured to install tools via containerbase (binarySource=install)

Renovate uses Bazelisk, which determines the correct Bazel version from the .bazelversion file in your repository.

If no MODULE.bazel.lock file exists, Renovate skips the lockfile update step.

"},{"location":"bazel/#git_repository","title":"git_repository","text":"

If Renovate finds a git_repository, it evaluates the commit value at the specified remote. remote is limited to github repos: https://github.com/<owner>/<repo>.git

git_repository(\n    name = \"rules_foo\",\n    remote = \"https://github.com/fooexample/rules_foo.git\",\n    commit = \"8c94e11c2b05b6f25ced5f23cd07d0cfd36edc1a\",\n)\n
"},{"location":"bazel/#legacy-workspace-files","title":"Legacy WORKSPACE files","text":"

Renovate extracts dependencies from the following repository rules:

It also recognizes when these repository rule names are prefixed with an underscore. For example, _http_archive is treated the same as http_archive.

"},{"location":"bazel/#git_repository-legacy","title":"git_repository (legacy)","text":"

Renovate updates any git_repository declaration that has the following:

  1. name
  2. remote matching https://github.com/<owner>/<repo>.git
  3. tag using a valid SemVer

e.g.:

git_repository(\n    name = \"build_bazel_rules_typescript\",\n    remote = \"https://github.com/bazelbuild/rules_typescript.git\",\n    tag = \"0.6.1\",\n)\n

Renovate uses the list of tags on the remote repository (GitHub) to detect a new version.

"},{"location":"bazel/#http_archive-and-http_file","title":"http_archive and http_file","text":"

Renovate updates any http_archive or http_file declaration that has the following:

  1. name
  2. url matching https://github.com/<owner>/<repo>/releases/download/<semver>/<repo>.tar.gz
  3. sha256

e.g.:

http_archive(\n    name = \"io_bazel_rules_go\",\n    url = \"https://github.com/bazelbuild/rules_go/releases/download/0.7.1/rules_go-0.7.1.tar.gz\",\n    sha256 = \"341d5eacef704415386974bc82a1783a8b7ffbff2ab6ba02375e1ca20d9b031c\",\n)\n

Renovate uses the list of releases that it finds at the url to detect a new version.

"},{"location":"bazel/#maven_install","title":"maven_install","text":"

By default, Maven dependencies are extracted in the context of Gradle versioning scheme. To change it, configure packageRules like this:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"bazel\"],\n      \"matchDatasources\": [\"maven\"],\n      \"versioning\": \"maven\"\n    }\n  ]\n}\n
"},{"location":"bazel/#future-work","title":"Future work","text":"

We welcome contributions or feature requests to support more patterns or use cases.

"},{"location":"bicep/","title":"Bicep","text":"

Renovate supports upgrading API versions in resource references. Upgrading module versions is not supported.

"},{"location":"bicep/#how-it-works","title":"How it works","text":"
  1. Renovate searches for .bicep files.
  2. Renovate parses the files for resource types and API versions.
  3. Renovate looks up the latest version in the Azure/bicep-types-az repository.
"},{"location":"bicep/#known-issues","title":"Known issues","text":"

API version updates of nested resources are not supported.

The API version of the blobServices resource below for example, will not be upgraded:

resource storageAccount 'Microsoft.Storage/storageAccounts@2022-05-01' = {\n  name: 'test'\n  kind: 'StorageV2'\n  sku: {\n    name: 'Standard_LRS'\n  }\n  location: location\n\n  resource blobServices 'blobServices@2022-05-01' = {\n    name: 'default'\n  }\n}\n
"},{"location":"bicep/#future-work","title":"Future work","text":""},{"location":"bot-comparison/","title":"Bot comparison","text":"

This page explains the key differences between Renovate and Dependabot, to help you choose a bot. We're trying to be as objective as possible, so this is not a \"versus\" or anti-Dependabot page.

If you see anything wrong on this page, please let us know by creating a Discussion, or edit this page with a PR.

"},{"location":"bot-comparison/#table-of-features","title":"Table of features","text":"Feature Renovate Dependabot Dependency Dashboard Yes No Grouped updates Yes, use community-provided groups, or create your own Yes, create groups manually or handled automatically by dependabot Upgrades common monorepo packages at once Yes Yes Officially supported platforms Azure, Bitbucket, Forgejo, Gitea, GitHub, GitLab, SCM-Manager, see full list GitHub and Azure DevOps Supported languages List for Renovate List for Dependabot Show changelogs Yes Yes Compatibility score badges Four badges showing: Age, Adoption, Passing, Confidence One badge with overall compatibility score Built-in to GitHub No, requires app or self-hosting Yes Scheduling By default, Renovate runs as often as it is allowed to, read Renovate scheduling to learn more Yes: daily, weekly, monthly, quarterly, semiannually, yearly or cron License GNU Affero General Public License MIT License Programming language of project TypeScript Ruby Project pulse renovatebot/renovate pulse dependabot-core pulse Contributor graph renovatebot/renovate contributor graph dependabot-core contributor graph"},{"location":"bot-comparison/#hosted-app","title":"Hosted app","text":"

This section explains the key differences between the Mend Renovate app and the GitHub-native Dependabot.

Even if you're going to self-host a bot, read the hosted app section first, because many features and concepts are similar. Then read the self-hosted section.

"},{"location":"bot-comparison/#dependency-dashboard","title":"Dependency Dashboard","text":"

One big feature of Renovate is the Dependency Dashboard, which is enabled by default. Read the Key concepts, Dependency Dashboard page to learn more.

Dependabot does not have a similar feature.

"},{"location":"bot-comparison/#grouped-updates","title":"Grouped updates","text":"

Renovate comes with community-provided groupings of dependencies. So Renovate groups common dependencies into a single PR, out-of-the-box.

Dependabot can group dependencies into a single PR too, but you must set your own groups first.

"},{"location":"bot-comparison/#upgrades-common-monorepo-packages-at-once","title":"Upgrades common monorepo packages at once","text":"

Renovate has a group:monorepos preset, that upgrades common monorepo packages in a single PR.

Dependabot does not update common monorepo packages in a single PR.

"},{"location":"bot-comparison/#supported-platforms","title":"Supported platforms","text":"

Platform means the Git-hosting site or program, for example GitHub, GitLab or Azure.

Renovate works on multiple platforms, including GitHub. Read the list of Renovate platforms to learn more.

The official Dependabot program only works on GitHub. If you're an advanced user, you may use the dependabot-core repository as a base to build your own Dependabot, which you can run on other platforms.

"},{"location":"bot-comparison/#supported-languages","title":"Supported languages","text":""},{"location":"bot-comparison/#show-changelogs","title":"Show changelogs","text":"Feature Renovate Dependabot Link to GitHub release Yes, to specific release tag Yes, to \"releases landing page\" Link to GitHub's comparing changes UI Yes Yes Release notes Yes Yes Links to issues Yes Yes Upstream CHANGELOG file No Yes Recent commits No Yes Link to individual commits No Yes"},{"location":"bot-comparison/#compatibility-score-badges","title":"Compatibility score badges","text":"

Renovate shows four Merge Confidence badges in its PRs:

Read the Merge Confidence badges page to learn more.

Dependabot shows one compatibility score badge in its PRs. This score tells you how many other repositories have passing CI tests for the proposed update. Read the GitHub Docs, Dependabot's compatibility scores to learn more about Dependabot's badge.

"},{"location":"bot-comparison/#built-in-to-github-vs-app","title":"Built-in to GitHub vs app","text":"

Renovate needs app installation or self-hosting.

Dependabot is built-in to GitHub.

"},{"location":"bot-comparison/#scheduling","title":"Scheduling","text":"

You can set a schedule for Renovate, per dependency, manager, or even a global schedule. Read Renovate scheduling to learn more.

Dependabot has four options that apply at a language level:

"},{"location":"bot-comparison/#license","title":"License","text":"

Renovate uses the GNU Affero General Public License.

Dependabot uses the MIT License.

Neither license is relevant to the end user though if consuming through an App/SaaS.

"},{"location":"bot-comparison/#programming-language-of-project","title":"Programming language of project","text":"

Renovate uses TypeScript.

dependabot-core uses Ruby.

"},{"location":"bot-comparison/#self-hosting-a-bot","title":"Self-hosting a bot","text":"

This section explains how to self-host each bot.

"},{"location":"bot-comparison/#self-hosting-renovate","title":"Self-hosting Renovate","text":"

You can self-host Renovate on all officially supported platforms.

If you decide to self-host Renovate, read the items from the Self-hosting Renovate reading list.

Available Renovate distributions:

"},{"location":"bot-comparison/#self-hosting-dependabot","title":"Self-hosting Dependabot","text":"

You can self-host Dependabot on other platforms than GitHub but none are officially supported.

"},{"location":"bot-comparison/#as-a-github-actions-workflow-on-github","title":"As a GitHub Actions workflow on GitHub","text":"

You can run Dependabot as a GitHub Actions workflow on hosted and self-hosted runners. Learn more by reading the:

"},{"location":"bot-comparison/#dependabot-core","title":"dependabot-core","text":"

If you want to customize Dependabot, or self-host on another platform, you can use dependabot-core. Quote from the dependabot-core readme:

It [dependabot-core] currently supports opening Pull Requests against repositories hosted on GitHub, Github Enterprise, Azure DevOps, GitLab, BitBucket, and AWS CodeCommit.

"},{"location":"bot-comparison/#dependabot-script","title":"dependabot-script","text":"

The Dependabot team has a community-maintained collection of scripts to start self-hosting Dependabot: dependabot-script but the repository has included a message warning that the scripts are broken since March 2023.

"},{"location":"bot-comparison/#dependabot-gitlabdependabot","title":"dependabot-gitlab/dependabot","text":"

There's also a community-maintained Dependabot for GitLab: dependabot-gitlab/dependabot.

"},{"location":"calling-aws-services/","title":"Calling AWS Services from Renovate","text":"

When one of Renovate's inbuilt datasources interacts with AWS services, Renovate uses the AWS SDK for JavaScript. This allows you to provide credentials and configuration to it, as if you were interacting with other tools, like the aws CLI.

For example:

Tip

Read the AWS Developer Guide - Configuring the SDK for JavaScript for more information on these configuration options.

"},{"location":"community-tools/","title":"Community Tools","text":"

This page lists community-maintained tools that extend or complement Renovate. These tools are not officially supported by the Renovate team, but may be useful for your workflow.

Note

If you have a community tool you'd like to add to this page, please open a pull request.

"},{"location":"community-tools/#renovate-operator-kubernetes","title":"Renovate Operator (Kubernetes)","text":"

The Renovate Operator lets you run Renovate on Kubernetes in a native way. It wraps the Renovate CLI in a Kubernetes operator and adds features like:

"},{"location":"community-tools/#renovate-pretty-log","title":"renovate-pretty-log","text":"

renovate-pretty-log is a set of utilities to provide a richer, local-only view, for your Renovate debug logs.

The project is maintained by Renovate maintainer Jamie Tanna.

"},{"location":"community-tools/#renovate-pretty-log-tui","title":"renovate-pretty-log-tui","text":"

renovate-pretty-log-tui is a Terminal User Interface (TUI) to provide a richer, local-only view, for your Renovate debug logs.

It also provides more advanced searching and filtering:

And can be used to surface issues in repository runs more visually:

"},{"location":"community-tools/#html-exports","title":"HTML exports","text":"

There are some additional utilities in the project, including the ability to generate a single-page HTML view of the logs:

renovate-pretty-log -path /path/to/debug.log -html > report.html\n

You can see a live example of what this looks like from one of Renovate's own runs.

"},{"location":"community-tools/#renovate-config-debugger","title":"Renovate Config Debugger","text":"

The Renovate Config Debugger shows what Renovate does with a config before you commit it. It runs Renovate's own code in the browser, so the config never leaves the page.

The project is maintained by Renovate maintainer Sebastian Poxhofer ( @secustor ). The blog post Renovate: It was a packageRule all along walks through debugging a config with it.

"},{"location":"config-migration/","title":"Config Migration","text":"

As part of continuous improvement and refinement, the Renovate maintainers often rename, remove or combine configuration options.

When the Renovate maintainers change configuration options, they add \"config migration\" code. The migration code allows \"legacy\" config from users to keep working. Config migration works by migrating legacy config internally, before the config is used. If done right, config migration \"just works\" silently and legacy configs continue working indefinitely. The only sign that \"config migration\" is needed is the debug message in the Renovate logs, noting the old and newly migrated configs.

"},{"location":"config-migration/#enabling-config-migration-pull-requests","title":"Enabling config migration pull requests","text":"

Even though Renovate allows you to keep using \"legacy config\", we recommend you update the configuration names in your config regularly. Using the latest names:

Renovate can create a config migration Pull Request, to migrate legacy config in your configuration file. To get automated config migration Pull Requests from Renovate: set the configMigration config option to true.

Config migration PRs are disabled by default. But we recommend you enable config migration PRs, because:

"},{"location":"config-migration/#config-migration-scenarios","title":"Config migration scenarios","text":"

The scenarios for config migration are:

"},{"location":"config-migration/#no-config-migration-needed","title":"No config migration needed","text":"

Renovate takes no action.

"},{"location":"config-migration/#config-migration-needed-and-enabled","title":"Config migration needed, and enabled","text":"

Renovate will:

  1. Create a Config Migration PR
  2. If the Dependency Dashboard issue is enabled, then Renovate puts a link to the Config Migration PR on the dashboard
"},{"location":"config-migration/#config-migration-needed-but-disabled","title":"Config migration needed, but disabled","text":"

If config migration is needed, but disabled then Renovate adds a checkbox to the Dependency Dashboard (if the dashboard exists). This is known as \"on-demand\" config migration, because migration PRs are only created at the request of the user by ticking the checkbox.

The checkbox looks like this:

- [ ] Select this checkbox to let Renovate create an automated Config Migration PR.\n

When you select the checkbox:

  1. Renovate creates a config migration PR
  2. Renovate replaces the checkbox with a link to the Config Migration PR

For example:

See Config Migration PR: #1.\n
"},{"location":"config-migration/#config-migration-needed-but-there-is-a-closed-migration-pr","title":"Config migration needed, but there is a closed migration PR","text":"

In this case, it does not matter if Config Migration is enabled, or not. Renovate will:

"},{"location":"config-overview/","title":"Renovate configuration overview","text":"

Each time Renovate runs on a repository it reads the configuration files listed below and creates a final config. This final config describes what Renovate will do during its run.

The final config is internal to Renovate, and is not saved or cached for a later run. But you can always find the final config in Renovate's logs.

Renovate reads the configuration files in this order (from top to bottom):

  1. Default config
  2. Global config
  3. Inherited config
  4. Resolved presets referenced in config
  5. Repository config

Items with a higher number override items that have lower numbers. If the item has the mergeable property, it will merge with lower numbers instead.

Note

If you use a Mend-hosted app, please read Mend-hosted Apps Configuration after reading this page.

"},{"location":"config-overview/#types-of-config","title":"Types of config","text":""},{"location":"config-overview/#default-config","title":"Default config","text":"

Every Renovate config option has a default value/setting. That default value/setting may even be null. You can find the default values on the Renovate docs website.

For example:

The default config is loaded first, and may be superseded/overridden by the configuration types listed below.

"},{"location":"config-overview/#global-config","title":"Global config","text":"

Global config means: the config defined by the person or team responsible for running the deployment of Renovate.

Global config can contain config which is \"global only\" as well as any configuration options which are valid in Inherited config or Repository config.

Previously, this may have been referred to as \"bot config\", because it is the config passed to Renovate by the person running it. We no longer use \"bot\" terminology, so it is now called \"global self-hosted configuration\".

If you are an end user of Renovate, for example if you're using the Mend Renovate App, then you don't need to care as much about any global config. As a end-user you can not change some settings because those settings are global-only. If you are an end user, you can skip the rest of this \"Global config\" section and proceed to \"Inherited config\".

Global config can be read from a file, environment variable, or CLI parameters. You must configure at least one of these for Renovate to have the information it needs to run. For example: you may need to give Renovate the correct credentials.

"},{"location":"config-overview/#file-config","title":"File config","text":"

Renovate first tries to read the global config from a file. By default Renovate checks for a config.js file in the current working directory. But you can override this by defining RENOVATE_CONFIG_FILE in env, for example: RENOVATE_CONFIG_FILE=/tmp/my-renovate-config.js.

By default Renovate allows the config file to be missing and does not error if it cannot find it. But if you have configured RENOVATE_CONFIG_FILE and the path you specified is not found then Renovate will error and exit, because it assumes you have a configuration problem. If the file is found but cannot be parsed then Renovate will also error and exit.

Global config files can be .js or .json files. You may use synchronous or asynchronous methods inside a .js file, including even to fetch config information from remote hosts.

"},{"location":"config-overview/#additional-file-config","title":"Additional file config","text":"

Renovate tried to read an additional config file only if the env var RENOVATE_ADDITIONAL_CONFIG_FILE is set, for example: RENOVATE_ADDITIONAL_CONFIG_FILE=/tmp/my-additional-renovate-config.js.

By default Renovate allows the config file to be missing and does not error if it cannot find it. But if you have configured RENOVATE_ADDITIONAL_CONFIG_FILE and the path you specified is not found then Renovate will error and exit, because it assumes you have a configuration problem. If the file is found but cannot be parsed then Renovate will also error and exit.

Global config files can be .js or .json files. You may use synchronous or asynchronous methods inside a .js file, including even to fetch config information from remote hosts.

Warning

Do not name the additional config file config.js as it is reserved for file config.

"},{"location":"config-overview/#environment-config","title":"Environment config","text":"

Global config can be defined using environment variables. The config options that you can use in environment variables all have the prefix RENOVATE_. For example, RENOVATE_PLATFORM=gitlab is the same as setting \"platform\": \"gitlab\" in File config.

Usually there's a clear mapping from configuration option name to the corresponding Environment config name. But we recommend you still check the documentation for the field env for each option to make sure. If the configuration option lacks a env field, the config option also lacks a Environment config variable name.

A special case for Environment config is the RENOVATE_CONFIG \"meta\" config option. The RENOVATE_CONFIG option accepts a stringified full config, for example: RENOVATE_CONFIG={\"platform\":\"gitlab\",\"onboarding\":false}. Any additional Environment config variables take precedence over values in RENOVATE_CONFIG. For mergeable options, like hostRules, packageRules or registryAliases, the values are combined instead: lists are appended to the list in RENOVATE_CONFIG, and objects are merged into the object in RENOVATE_CONFIG, with the Environment config variable winning for keys that exist in both.

"},{"location":"config-overview/#environment-variable-examples","title":"Environment variable examples","text":"

Warning

Make sure to escape any punctuation. Be extra careful if you're passing stringified values.

Boolean:

String:

Number:

List with numbers or strings:

Objects, or lists with objects:

Tip

Use \"stringify\" (Example online service) for strings and objects.

"},{"location":"config-overview/#experimental-variables","title":"Experimental variables","text":"

Renovate has \"experimental\" environment variables, which start with RENOVATE_X_. These variables are experimental, can be changed at any time, and are not parsed as part of regular configuration. Read the Self-hosted experimental environment variables docs to learn more.

"},{"location":"config-overview/#logging-variables","title":"Logging variables","text":"

Finally, there are some special environment variables that are loaded before configuration parsing because they are used during logging initialization:

"},{"location":"config-overview/#cli-config","title":"CLI config","text":"

The final way to configure Global config is through CLI parameters. For example, the CLI parameter --platform=gitlab is the same as setting \"platform\": \"gitlab\" in File config or RENOVATE_PLATFORM=gitlab in Environment config.

CLI config is read last and takes precedence over Environment and File config. For example, if you configure conflicting values in Environment, File config and CLI config, then the CLI config will be merged last and \"win\" if values conflict.

It is important that you:

"},{"location":"config-overview/#inherited-config","title":"Inherited config","text":""},{"location":"config-overview/#use-cases","title":"Use cases","text":"

The primary purpose of Inherited config is to allow for default settings of an organization/group. Two main use cases for Inherited config are:

We recommend that organizations use shared presets instead of Inherited config, if possible. But default settings through Inherited config are useful if:

"},{"location":"config-overview/#how-its-found","title":"How it's found","text":"

If inheritConfig is true in Global config then Renovate will look for Inherited config before processing each repository.

The repository and file name which Renovate looks for can be configured using the other inheritConfig* settings documented in Global config. Default values are {{parentOrg}}/renovate-config for repository name (inheritConfigRepoName) and org-inherited-config.json for file name (inheritConfigFileName).

Note: For Azure DevOps, {{parentOrg}} is the Project the repo belongs to, and for Bitbucket, the {{parentOrg}} is the Workspace of the repo, as shown in the table below.

Repo Inherited config file location GitHub {parentOrg} / renovate-config / org-inherited-config.json Bitbucket {parentWorkspace} / renovate-config / org-inherited-config.json Azure DevOps {parentProject} / renovate-config / org-inherited-config.json

If found, Inherited config will be merged on top (i.e. override) Global config. Avoid putting any global-only setting in a Inherited config, as doing so will result in an error.

Inherited config may use all Repository config settings, and any Global config options which have the \"supportsInheritConfig\" property in the docs.

For information on how the Mend Renovate App supports Inherited config, see the dedicated \"Mend Renovate App Config\" section toward the end of this page.

"},{"location":"config-overview/#presets-handling","title":"Presets handling","text":"

If the inherited config contains extends presets, then Renovate will:

  1. Resolve the presets
  2. Add the resolved preset config to the beginning of the inherited config
  3. Merge the presets on top of the global config
"},{"location":"config-overview/#you-can-not-ignore-presets-from-inherited-config","title":"You can not ignore presets from inherited config","text":"

You can not use ignorePresets in your repository config to ignore presets within inherited config. This is because inherited config is resolved before the repository config.

"},{"location":"config-overview/#repository-config","title":"Repository config","text":"

Repository config is the config loaded from a config file in the repository. Alternative file names are supported, but the default is renovate.json. If Renovate finds more than one configuration file in the same repository, then Renovate will use the first configuration file it finds and ignores the other(s).

"},{"location":"config-overview/#config-precedence","title":"Config precedence","text":"

Once Repository config is loaded, it is merged over the top of the previously loaded Global and Inherited config, meaning it takes precedence over them. Presets referenced with an \"extends\" config are resolved first and take lower precedence over regular/raw config in the same file or config object.

"},{"location":"config-overview/#onboarding","title":"Onboarding","text":"

When Renovate processes a repository, one of the first decisions it makes is \"Does this repository need to be onboarded?\". By default, Renovate will create an \"Onboarding PR\" with a default config if a repository does not have a Repository config file committed to the default branch.

"},{"location":"config-overview/#onboarding-config","title":"Onboarding Config","text":"

When Renovate creates an Onboarding PR it will propose a Repository config file to be merged. By default, it is essentially an empty config with only the Renovate JSON schema referenced, but you can change this behavior if desired.

If you configure onboardingConfig in either Global config or Inherited config then Renovate will use that config directly instead of the default.

If you self-host Renovate in GitLab using renovate-runner, the CI will contain a default RENOVATE_ONBOARDING_CONFIG that will merge with your own configuration settings. For example, the CI by default contains:

RENOVATE_ONBOARDING_CONFIG: '{\"$$schema\": \"https://docs.renovatebot.com/renovate-schema.json\", \"extends\": [\"config:recommended\"] }'\n

If you want to change the extends in your own configuration, you need to override the variable in your own .gitlab-ci.yml:

variables:\n  RENOVATE_ONBOARDING_CONFIG: '{\"$$schema\":\"https://docs.renovatebot.com/renovate-schema.json\",\"extends\":[\"platform>organization/repo:renovate-config\"]}'\n

Your renovate.js where you run Renovate cannot contain any extends definition, it will pick the extends from the RENOVATE_ONBOARDING_CONFIG variable. For example, your config can look like this:

module.exports = {\n  // ...\n  onboardingConfig: {\n    argocd: {\n      managerFilePatterns: ['application\\\\.yaml$'],\n    },\n  },\n};\n

The resulting onboarding config will be:

{\n  '$schema': 'https://docs.renovatebot.com/renovate-schema.json',\n  'argocd': { 'managerFilePatterns': [\"/application\\\\.yaml$/\"] },\n  'extends': ['platform>organization/repo:renovate-config'],\n}\n

Alternatively if you follow Renovate's naming convention for shared presets then it can automatically detect those instead. If the repository {{parentOrg}}/renovate-config has a default.json file then this will be treated as the organization's default preset and included in the Onboarding config. Additionally for platforms which support nested Organization/Group hierarchies, Renovate will \"hunt\" up such hierarchies for a renovate-config repository with default config and stop when it finds the first.

Note

Renovate will also check for a renovate.json file if it cannot find a default.json file in a preset, however this option is deprecated and not recommended.

If a default config is not found in a renovate-config repository within the Organization, Renovate will also check for the presence of a renovate-config.json file within a .{{platform}} repository parallel to the current repository. For example if the repository being onboarded is abc/def on a GitHub platform then Renovate will look for the existence of an abc/.github repository containing a renovate-config.json file.

"},{"location":"config-overview/#changing-default-behavior","title":"Changing default behavior","text":"

Default onboarding behavior for an Organization can be changed either in Global or Inherited config.

For example, if you set onboarding=false then Renovate will not onboard repositories, and skip any repositories without a Repository config. In other words, users need to manually push a valid Repository config file to activate Renovate on the repository.

If you set onboarding=false plus requireConfig=optional then it means Renovate will skip onboarding and proceed to run on a repository, even if Renovate does not find any Repository config.

"},{"location":"config-overview/#shared-presets","title":"Shared Presets","text":""},{"location":"config-overview/#overview","title":"Overview","text":"

The concept of shared configuration is covered in detail on the Presets page, so please read that first.

"},{"location":"config-overview/#use-of-presets-in-global-config","title":"Use of Presets in Global config","text":"

Presets should be used cautiously in Global config as they often lead to misunderstandings.

"},{"location":"config-overview/#globalextends","title":"globalExtends","text":"

Sometimes you may not wish to put all settings within the Global config itself and instead commit it to a repository which is then referenced from the Global config. In such cases, use globalExtends instead of extends so that it is resolved immediately and used as part of Global config.

"},{"location":"config-overview/#extends","title":"extends","text":"

If you use extends within Global config then it's important to note that these are not resolved/expanded during Global config processing and instead are passed through unresolved to be part of Repository config. Passing extends through to be part of Repository config has two major consequences:

"},{"location":"config-overview/#using-a-centralized-config","title":"Using a centralized config","text":"

Using \"centralized\" configs through Renovate presets is important in order to be able to:

Once you've created a centralized preset config, there are multiple ways you can pass it through to repositories:

The above possibilities go from least to most transparent when it comes to end users.

Global config may be invisible to developers without log access, meaning they could be confused by any settings you apply - via presets or directly - within Global config. For example the developers wonder why Renovate is behaving differently to its documented default behavior and may even think it's a bug.

Inherited config is visible to developers (it's within a repository they can see) although it's implicitly applied so without log access and if they're not aware to look for an Inherited config repository then they may again be a little confused as to why default behavior has changed.

The recommended approach for using a centralized preset is to explicitly \"extend\" it from every repository, which can be achieved easily if it's part of your onboardingConfig. By having your centralized preset part of each Repository config extends, it has these two benefits:

"},{"location":"config-overview/#other","title":"Other","text":"

The below contains edge cases which you should avoid if possible, and likely don't need to use. They are included here because they can cause \"exceptions\" to some of the previously mentioned rules of config.

"},{"location":"config-overview/#optimize-for-disabled","title":"Optimize for Disabled","text":"

The optimizeForDisabled option was designed for an edge case where a large percentage of repos are disabled by config. If this option is set to true, Renovate will use a platform API call to see if a renovate.json exists and if it contains \"enabled\": false. If so, the repository will be skipped without a clone necessary. If the file is not present or does not disable Renovate, then Renovate continues as before (having \"wasted\" that extra API call).

"},{"location":"config-overview/#force-config","title":"Force config","text":"

We recommend you avoid the force config option, if possible.

It can be used to \"force\" config over the top of other config or rules which might be merged later, so at times can cause confusion - especially if it's defined in Global config and overriding settings in Repository config.

"},{"location":"config-presets/","title":"Shareable Config Presets","text":"

This page describes how to configure your shared presets. Read the Key concepts, presets page to learn more about presets in general.

Shareable config presets must use the JSON, JSONC or JSON5 formats, other formats are not supported.

Tip

Describe what your preset does in the \"description\" field or add comments as Renovate supports JSONC syntax within its preset files.

"},{"location":"config-presets/#extending-from-a-preset","title":"Extending from a preset","text":"

To use a preset put it in an extends array within your Renovate config. Presets can be nested.

"},{"location":"config-presets/#preset-hosting","title":"Preset Hosting","text":"

Presets should be hosted in repositories, which usually means the same platform host as Renovate is running against.

Alternatively, Renovate can fetch preset files from an HTTP server.

Warning

We deprecated npm-based presets. We plan to drop the npm-based presets feature in a future major release of Renovate.

You can set a Git tag (like a SemVer) to use a specific release of your shared config.

"},{"location":"config-presets/#preset-file-naming","title":"Preset File Naming","text":"

Presets are repo-hosted, and you can have one or more presets hosted per repository. If you omit a file name from your preset (e.g. github>abc/foo) then Renovate will look for a default.json file in the repo. If you wish to have an alternative file name, you need to specify it (e.g. github>abc/foo//alternative-name.json5).

Warning

We've deprecated using a renovate.json file for the default preset file name in a repository. If you're using a renovate.json file to share your presets, rename it to default.json.

"},{"location":"config-presets/#github","title":"GitHub","text":"name example use preset resolves as filename Git tag GitHub default github>abc/foo default https://github.com/abc/foo default.json Default branch GitHub with preset name github>abc/foo:xyz xyz https://github.com/abc/foo xyz.json Default branch GitHub with preset name (JSONC) github>abc/foo:xyz.jsonc xyz https://github.com/abc/foo xyz.jsonc Default branch GitHub with preset name (JSON5) github>abc/foo:xyz.json5 xyz https://github.com/abc/foo xyz.json5 Default branch GitHub with preset name and path github>abc/foo//path/xyz xyz https://github.com/abc/foo path/xyz.json Default branch GitHub default with a tag github>abc/foo#1.2.3 default https://github.com/abc/foo default.json 1.2.3 GitHub with preset name with a tag github>abc/foo:xyz#1.2.3 xyz https://github.com/abc/foo xyz.json 1.2.3 GitHub with preset name and path with a tag github>abc/foo//path/xyz#1.2.3 xyz https://github.com/abc/foo path/xyz.json 1.2.3 GitHub with subpreset name and tag github>abc/foo:xyz/sub#1.2.3 sub https://github.com/abc/foo xyz.json 1.2.3"},{"location":"config-presets/#gitlab","title":"GitLab","text":"name example use preset resolves as filename Git tag GitLab default gitlab>abc/foo default https://gitlab.com/abc/foo default.json Default branch GitLab with preset name gitlab>abc/foo:xyz xyz https://gitlab.com/abc/foo xyz.json Default branch GitLab with preset name (JSONC) gitlab>abc/foo:xyz.jsonc xyz https://gitlab.com/abc/foo xyz.jsonc Default branch GitLab with preset name (JSON5) gitlab>abc/foo:xyz.json5 xyz https://gitlab.com/abc/foo xyz.json5 Default branch GitLab default with a tag gitlab>abc/foo#1.2.3 default https://gitlab.com/abc/foo default.json 1.2.3 GitLab with preset name with a tag gitlab>abc/foo:xyz#1.2.3 xyz https://gitlab.com/abc/foo xyz.json 1.2.3 GitLab with preset name and path with a tag gitlab>abc/foo//path/xyz#1.2.3 xyz https://gitlab.com/abc/foo path/xyz.json 1.2.3 GitLab with subpreset name and tag gitlab>abc/foo:xyz/sub#1.2.3 sub https://gitlab.com/abc/foo xyz.json 1.2.3"},{"location":"config-presets/#gitea","title":"Gitea","text":"name example use preset resolves as filename Git tag Gitea default gitea>abc/foo default https://gitea.com/abc/foo default.json Default branch Gitea with preset name gitea>abc/foo:xyz xyz https://gitea.com/abc/foo xyz.json Default branch Gitea with preset name (JSON5) gitea>abc/foo:xyz.json5 xyz https://gitea.com/abc/foo xyz.json5 Default branch Gitea default with a tag gitea>abc/foo#1.2.3 default https://gitea.com/abc/foo default.json 1.2.3 Gitea with preset name with a tag gitea>abc/foo:xyz#1.2.3 xyz https://gitea.com/abc/foo xyz.json 1.2.3 Gitea with preset name and path with a tag gitea>abc/foo//path/xyz#1.2.3 xyz https://gitea.com/abc/foo path/xyz.json 1.2.3 Gitea with subpreset name and tag gitea>abc/foo:xyz/sub#1.2.3 sub https://gitea.com/abc/foo xyz.json 1.2.3"},{"location":"config-presets/#forgejo","title":"Forgejo","text":"name example use preset resolves as filename Git tag Forgejo default forgejo>abc/foo default https://codeberg.org/abc/foo default.json Default branch Forgejo with preset name forgejo>abc/foo:xyz xyz https://codeberg.org/abc/foo xyz.json Default branch Forgejo with preset name (JSON5) forgejo>abc/foo:xyz.json5 xyz https://codeberg.org/abc/foo xyz.json5 Default branch Forgejo default with a tag forgejo>abc/foo#1.2.3 default https://codeberg.org/abc/foo default.json 1.2.3 Forgejo with preset name with a tag forgejo>abc/foo:xyz#1.2.3 xyz https://codeberg.org/abc/foo xyz.json 1.2.3 Forgejo with preset name and path with a tag forgejo>abc/foo//path/xyz#1.2.3 xyz https://codeberg.org/abc/foo path/xyz.json 1.2.3 Forgejo with subpreset name and tag forgejo>abc/foo:xyz/sub#1.2.3 sub https://codeberg.org/abc/foo xyz.json 1.2.3"},{"location":"config-presets/#self-hosted-git-current-git-server","title":"Self-hosted Git / current Git server","text":"

Note

If you're self-hosting your platform, for instance a GitHub Enterprise Server instance, you'll want to use local> to look up presets on the current Git server. You can also use local> if you're running on github.com, and this will work as if you had written github>. This can make your presets more portable if you run across many different Git platforms.

For instance, if you have platform=github and endpoint=https://github.company.com:

name example use preset resolves as filename Git tag Local default local>abc/foo default https://github.company.com/abc/foo default.json Default branch Local with preset path local>abc/foo:xyz xyz https://github.company.com/abc/foo xyz.json Default branch Local with preset path (JSON5) local>abc/foo:xyz.json5 xyz https://github.company.com/abc/foo xyz.json5 Default branch Local with preset name and path local>abc/foo//path/xyz xyz https://github.company.com/abc/foo path/xyz.json Default branch Local default with a tag local>abc/foo#1.2.3 default https://github.company.com/abc/foo default.json 1.2.3 Local with preset name with a tag local>abc/foo:xyz#1.2.3 xyz https://github.company.com/abc/foo xyz.json 1.2.3 Local with preset name and path with a tag local>abc/foo//path/xyz#1.2.3 xyz https://github.company.com/abc/foo path/xyz.json 1.2.3 Local with subpreset name and tag local>abc/foo:xyz/sub#1.2.3 sub https://github.company.com/abc/foo xyz.json 1.2.3

Tip

You can't combine the path and sub-preset syntaxes. This means that anything in the form provider>owner/repo//path/to/file:subsubpreset is not supported. One workaround is to use distinct files instead of sub-presets.

"},{"location":"config-presets/#example-configs","title":"Example configs","text":"

An example of a small rule is :preserveSemverRanges, which has the description \"Preserve (but continue to upgrade) any existing SemVer ranges.\". It simply sets the configuration option rangeStrategy to replace.

An example of a full config is config:recommended, which is Renovate's default configuration. It mostly uses Renovate config defaults but adds a few smart customizations such as grouping monorepo packages together.

Note

The :xyz naming convention (with : prefix) is shorthand for the default: presets. For example: :xyz is the same as default:xyz.

"},{"location":"config-presets/#how-to-use-preset-configs","title":"How to Use Preset Configs","text":"

By default, Renovate App's onboarding PR suggests the [\"config:recommended\"] preset. If you're self hosting, and want to use the config:recommended preset, then you must add \"onboardingConfig\": { \"extends\": [\"config:recommended\"] } to your self-hosted config.

Read the Full Config Presets page to learn more about our config: presets.

A typical onboarding renovate.json looks like this:

{\n  \"extends\": [\"config:recommended\"]\n}\n

Here's an example of using presets to change Renovate's behavior. You're happy with the config:recommended preset, but want Renovate to create PRs when you're not at the office. You look at our schedule: presets, and find the schedule:nonOfficeHours preset. You put schedule:nonOfficeHours in the extends array of your renovate.json file, like this:

{\n  \"extends\": [\"config:recommended\", \"schedule:nonOfficeHours\"]\n}\n
"},{"location":"config-presets/#preset-parameters","title":"Preset Parameters","text":"

If you browse the \"default\" presets, you will see some that have parameters, e.g.:

{\n  \"labels\": {\n    \"description\": \"Apply labels <code>{{arg0}}</code> and <code>{{arg1}}</code> to PRs\",\n    \"labels\": [\"{{arg0}}\", \"{{arg1}}\"]\n  },\n  \"assignee\": {\n    \"description\": \"Assign PRs to <code>{{arg0}}</code>\",\n    \"assignees\": [\"{{arg0}}\"]\n  }\n}\n

Here is how you would use these in your Renovate config:

{\n  \"extends\": [\":labels(dependencies,devops)\", \":assignee(renovate-tests)\"]\n}\n

In short, the number of {{argx}} parameters in the definition is how many parameters you need to provide. Parameters must be strings, non-quoted, and separated by commas if there are more than one.

If you find that you are repeating config a lot, you might consider publishing one of these types of parameterized presets yourself. Or if you think your preset would be valuable for others, please contribute a PR to the Renovate repository, see Contributing to presets.

Also, the entire parameter string is available as {{args}}. It includes everything between parentheses, verbatim, without the parentheses themselves. If you want to include a comma in the parameter value, you need to use {{args}} instead of {{arg0}}.

"},{"location":"config-presets/#github-hosted-presets","title":"GitHub-hosted Presets","text":"

To host your preset config on GitHub:

From then on Renovate will use the Renovate config from the preset repo's default branch. You do not need to add it as a devDependency or add any other files to the preset repo.

"},{"location":"config-presets/#gitlab-hosted-presets","title":"GitLab-hosted Presets","text":"

For a private GitLab repository Renovate requires at least Reporter level access.

To host your preset config on GitLab:

"},{"location":"config-presets/#gitea-hosted-presets","title":"Gitea-hosted Presets","text":"

To host your preset config on Gitea:

"},{"location":"config-presets/#forgejo-hosted-presets","title":"Forgejo-hosted Presets","text":"

To host your preset config on Forgejo:

"},{"location":"config-presets/#local-presets","title":"Local presets","text":"

Renovate also supports local presets, e.g. presets that are hosted on the same platform as the target repository. This is especially helpful in self-hosted scenarios where public presets cannot be used. Local presets are specified either by leaving out any prefix, e.g. owner/name, or explicitly by adding a local> prefix, e.g. local>owner/name. Renovate will determine the current platform and look up the preset from there.

"},{"location":"config-presets/#relative-preset-references","title":"Relative preset references","text":"

Presets can reference other presets from the same repository with a relative path. Renovate resolves the relative reference to the source, repository and tag of the preset which contains the reference. This means you can move or fork a preset repository, or pin it to a tag, without editing the references inside the presets.

Syntax Resolves relative to ./x the directory of the preset file with the reference ../x the parent directory of the preset file with the reference /x the root of the preset repository

For example, take a preset repository with this layout:

default.json\nsystem/registries.json\nsecurity/base.json\n

The default.json file can reference the other presets like this:

{\n  \"extends\": [\"./system/registries\", \"/security/base\"]\n}\n

If a repository extends github>org/repo#v2.0.0, then Renovate resolves the two references to github>org/repo//system/registries#v2.0.0 and github>org/repo//security/base#v2.0.0. The tag v2.0.0 is inherited, so all presets are read from the same tag.

Note

Relative references only work inside presets. Renovate does not accept them in a repository's own renovate.json, in an inherited config, or in globalExtends. The renovate-config-validator accepts relative references in any file, so a relative reference in a repository's own config only fails when Renovate runs, and not during validation.

Some more things to know about relative references:

Note

Relative references inside an onboardingConfig are canonicalized as well, including the inherited tag. This means an onboarded repository gets an absolute preset string like github>org/repo//system/registries#v2.0.0, which resolves from that repository.

"},{"location":"config-presets/#ignoring-relative-references","title":"Ignoring relative references","text":"

Renovate matches ignorePresets entries against the preset string which it resolved, and not against the relative reference which is written inside the preset. This means you must always use the absolute form, including the inherited tag.

Take the repository from above. A repository which extends that catalog can skip security/base.json like this:

{\n  \"extends\": [\"github>org/repo#v2.0.0\"],\n  \"ignorePresets\": [\"github>org/repo//security/base#v2.0.0\"]\n}\n

This works at any depth, so a preset which is only reached through another preset, for example a /security/base reference inside system/registries.json, is skipped in the same way.

Using the relative form does not work, because the references are already resolved when the ignorePresets entries are matched:

{\n  \"extends\": [\"github>org/repo#v2.0.0\"],\n  \"ignorePresets\": [\"/security/base\"]\n}\n

To find the absolute string of a preset, run Renovate with LOG_LEVEL=debug and read the visitedPresets field of the Resolved shallow config, without merging internal presets message. It lists every merged preset in its absolute form.

A preset may also ignore the presets which it pulls in itself, and may use the relative form for that:

{\n  \"extends\": [\"./system/registries\"],\n  \"ignorePresets\": [\"/security/base\"]\n}\n

Note

Renovate uses the ignorePresets of the repository config when there is one, and only falls back to the ignorePresets of a preset otherwise. A preset can therefore only ignore its own references when the repository which extends it does not set ignorePresets.

If a relative reference can not be resolved, for example because it escapes the repository root, then Renovate keeps the raw reference. Use that raw string to neutralize it:

{\n  \"extends\": [\"github>org/repo#v2.0.0\"],\n  \"ignorePresets\": [\"../oops\"]\n}\n

Warning

A relative reference which cannot be resolved causes a configuration error in every repository which extends the preset. Preset authors should therefore validate their preset repository in CI, for example with the renovate-config-validator CLI.

"},{"location":"config-presets/#fetching-presets-from-an-http-server","title":"Fetching presets from an HTTP server","text":"

If your desired platform is not yet supported, or if you want presets to work when you run Renovate with --platform=local, you can specify presets using HTTP URLs:

{\n  \"extends\": [\n    \"http://my.server/users/me/repos/renovate-presets/raw/default.json?at=refs%2Fheads%2Fmain\"\n  ]\n}\n

Parameters are supported similar to other methods:

{\n  \"extends\": [\n    \"http://my.server/users/me/repos/renovate-presets/raw/default.json?at=refs%2Fheads%2Fmain(param)\"\n  ]\n}\n

Note

Renovate warns about HTTP requests to internal hosts (loopback, private ranges, and similar) by default, and can be set to block them - see internalHostAccess. Because a preset's response becomes configuration, fetching presets from an internal host needs a deliberate grant from the self-hosted administrator: a hostRules entry in their own configuration setting allowInternal=true, scoped with a hostType or a URL-prefix matchHost. This applies to npm: presets too, where the scoped grant names the registry, for example { \"matchHost\": \"https://registry.corp/\", \"hostType\": \"npm\", \"allowInternal\": true }.

"},{"location":"config-presets/#templating-presets","title":"Templating presets","text":"

You can use Handlebars templates to be flexible with your presets. This can be handy when you want to include presets conditionally.

Note

The template only supports a small subset of options, but you can extend them via customEnvVariables.

Read the templates section to learn more.

"},{"location":"config-presets/#example-use-case","title":"Example use-case","text":"

The following example shows a self-hosted Renovate preset located in a GitLab repository called renovate/presets.

{\n  \"extends\": [\"local>renovate/presets\"]\n}\n

Usually you want to validate the preset before you put it in your Renovate configuration Here is an example of how you can use templating to validate and load the preset on a branch level:

// config.js\nmodule.exports = {\n  customEnvVariables: {\n    GITLAB_REF: process.env.CI_COMMIT_REF_NAME || 'main',\n  },\n  extends: ['local>renovate/presets#{{ env.GITLAB_REF }}'],\n};\n
"},{"location":"config-presets/#contributing-to-presets","title":"Contributing to presets","text":"

Have you configured a rule that could help others? Please consider contributing it to the Renovate repository so that it gains higher visibility and saves others from reinventing the same thing.

Create a discussion to propose your preset to the Renovate maintainers. The maintainers can also help improve the preset, and let you know where to put it in the code. If you are proposing a \"monorepo\" preset addition then it's OK to raise a PR directly as that can be more efficient than a GitHub Discussion.

"},{"location":"config-presets/#grouporganization-level-presets","title":"Group/Organization level presets","text":"

Whenever repository onboarding happens, Renovate checks for a a default config to extend. Renovate will check for a repository called renovate-config with a default.json file in the parent user/group/org of the repository. On platforms that support nested groups (e.g. GitLab), Renovate will check for this repository at each level of grouping, from nearest to furthest, and use the first one it finds. On all platforms, it will then look for a repository named like .{{platform}} (e.g. .github) with a renovate-config.json, under the same top-level user/group/org.

If found, that repository's preset will be suggested as the sole extended preset, and any existing onboardingConfig config will be ignored/overridden. For example the result may be:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"extends\": [\"local>myorgname/.github:renovate-config\"]\n}\n
"},{"location":"config-presets/#npm-hosted-presets","title":"npm-hosted presets","text":"

Warning

Using npm-hosted presets is deprecated, we recommend you do not follow these instructions and instead use a local preset.

If you manage multiple repositories using Renovate and want the same custom config across all or most of them, then you might want to consider publishing your own preset config so that you can \"extend\" it in every applicable repository. That way when you want to change your Renovate configuration you can make the change in one location rather than having to copy/paste it to every repository individually.

Let's say that your username on npm and elsewhere is \"fastcore\". In that case, you can choose between publishing your preset config package as @fastcore/renovate-config or renovate-config-fastcore. Let's assume you choose renovate-config-fastcore as the package name.

You then need to publish the renovate-config-fastcore package where the package.json has the field renovate-config and then put your config under the field default. For example:

{\n  \"name\": \"renovate-config-fastcore\",\n  \"version\": \"0.0.1\",\n  \"renovate-config\": {\n    \"default\": {\n      \"extends\": [\"config:recommended\", \"schedule:nonOfficeHours\"]\n    }\n  }\n}\n

Then in each of your repositories you can add your Renovate config like:

{\n  \"extends\": [\"fastcore\"]\n}\n

Any repository including this config will then adopt the rules of the default library preset but schedule it on weeknights or weekends.

If you prefer to publish using the namespace @fastcore/renovate-config then you would use the @ prefix instead:

{\n  \"extends\": [\"@fastcore\"]\n}\n
"},{"location":"config-validation/","title":"Config Validation","text":"

You can check your Renovate configuration with a standalone program called renovate-config-validator. All renovate distributions include this program.

"},{"location":"config-validation/#default-behavior","title":"Default behavior","text":"

When you run renovate-config-validator with no arguments it will check:

For example:

$ npx --yes --package renovate -- renovate-config-validator\n INFO: Validating renovate.json\n INFO: Config validated successfully\n

If you want to run renovate-config-validator while using a custom filename for your renovate config file, you will need to pass the filename as cli argument.

"},{"location":"config-validation/#strict-mode","title":"Strict mode","text":"

By default, the validator program fails with a non-zero exit code if there are any validation warnings or errors. You can pass the --strict flag to make it fail if a scanned config needs migration:

Strict mode validation
$ npx --yes --package renovate -- renovate-config-validator --strict\n INFO: Validating renovate.json\n WARN: Config migration necessary\n       \"oldConfig\": {\n         \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n         \"extends\": [ \"config:base\" ]\n       },\n       \"newConfig\": {\n         \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n         \"extends\": [ \"config:recommended\" ]\n       },\n
"},{"location":"config-validation/#pass-file-to-check-as-cli-arguments","title":"Pass file to check as CLI arguments","text":"

You can pass the file you want to check to the renovate-config-validator program with a CLI argument. This can be handy to check a config file with a non-default name, like when you're using preset repositories. For example:

$ npx --yes --package renovate -- renovate-config-validator first_config.json\n INFO: Validating first_config_.json\n INFO: Config validated successfully\n

Note

If you specify the filename, renovate-config-validator treats the file(s) as global self-hosted configuration instead of repo-level configuration. If this isn't intentional - for instance if you're validating a shared config preset or a non-standard filename - make sure you specify --no-global, i.e. renovate-config-validator --no-global go-presets.json.

"},{"location":"config-validation/#providing-global-configuration","title":"Providing global configuration","text":"

If renovate-config-validator detects a config.js, or any global self-hosed environment variables, they will be set as global configuration.

For instance, if you had a config.js:

module.exports = {\n  // to mirror the Mend-hosted Renovate\n  globalExtends: ['global:safeEnv'],\n};\n

And a renovate.json:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"env\": {\n    \"GONOSUMDB\": \"off\"\n  }\n}\n

The renovate-config-validator would allow this to pass.

"},{"location":"config-validation/#validate-your-config-automatically","title":"Validate your config automatically","text":"

You can create a pre-commit hook to validate your configuration automatically. Go to the renovatebot/pre-commit-hooks repository for more information.

"},{"location":"config-validation/#validation-of-renovate-config-change-prs","title":"Validation of Renovate config change PRs","text":"

Tip

Using the Mend-hosted apps? Push a branch to renovate/reconfigure for feedback (via status check), and if there's a PR, Renovate will add comments to it!

Renovate can validate configuration changes in Pull Requests when you use a special branch name.

Follow these steps to validate your configuration:

  1. Create a new Git branch that matches the {{branchPrefix}}reconfigure pattern. For example, if you're using the default prefix renovate/, your branch name must be renovate/reconfigure.
  2. Commit your updated Renovate config file to this branch, and push it to your Git hosting platform.

The next time Renovate runs on that repo it will:

  1. Search for a branch that matches the special reconfigure pattern.
  2. Check for a config file in the reconfigure branch. Renovate can even find a renamed configuration file (compared to the config file in the default branch).
  3. Add a passing or failing status to the branch, depending on the outcome of the config validation run.
  4. If there's an open pull request with validation errors from the reconfigure branch then Renovate comments in the PR with details.
  5. Validate each commit the next time Renovate runs on the repository, until the PR is merged.

Note

The reconfigure branch must be pushed to the source repository that Renovate runs against, not a fork.

"},{"location":"configuration-options/","title":"Configuration Options","text":"

This document describes all the configuration options you may use in a Renovate configuration file. Any config you define applies to the whole repository (e.g. if you have a monorepo).

A subtype in the configuration table specifies what type you're allowed to use within the main element.

If a config option has a parent defined, it means it's only allowed to configure it within an object with the parent name, such as packageRules or hostRules.

When an array or object configuration option is mergeable, it means that values inside it will be added to any existing object or array that existed with the same name.

Tip

This documentation corresponds with the JSON schema in docs.renovatebot.com/renovate-schema.json.

Note

Config options with type=string are always non-mergeable, so mergeable=false.

"},{"location":"configuration-options/#locations-for-configuration-filenames","title":"Locations for configuration filenames","text":"

You can store your Renovate configuration file in one of these locations:

  1. renovate.json
  2. renovate.jsonc
  3. renovate.json5
  4. .github/renovate.json
  5. .github/renovate.jsonc
  6. .github/renovate.json5
  7. .gitlab/renovate.json
  8. .gitlab/renovate.jsonc
  9. .gitlab/renovate.json5
  10. .renovaterc
  11. .renovaterc.json
  12. .renovaterc.jsonc
  13. .renovaterc.json5
  14. package.json (within a \"renovate\" section)

Also, be sure to check out Renovate's shareable config presets to save yourself from reinventing any wheels. Shareable config presets work with JSON and JSON5 file formats.

If you have any questions about the config options, or want to get help/feedback about a config, go to the discussions tab in the Renovate repository and start a new \"Request Help\" discussion. We will do our best to answer your question(s).

Or in a custom file present within the configFileNames.

When Renovate runs on a repository, it tries to find the configuration files in the order listed above. Renovate first checks all the files in the configFileNames array before checking from the above file list. Renovate stops the search after it finds the first match.

Warning

Storing the Renovate configuration in a package.json file is deprecated and support may be removed in the future.

Note

Renovate supports JSONC for .json files and any config files without file extension (e.g. .renovaterc). We also recommend you prefer using a .jsonc file if you want to add comments to your configuration, instead of a .json5 file. Using an explicit .jsonc file is preferred over using a .json file with comments, as it can cause issues with editors and syntax highlighting.

Renovate always uses the config from the repository's default branch, even if that configuration specifies baseBranchPatterns. Renovate does not read/override the config from within each base branch if present.

"},{"location":"configuration-options/#abandonmentthreshold","title":"abandonmentThreshold","text":"

Flags packages that have not been updated within this period as abandoned.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string cli --abandonment-threshold env RENOVATE_ABANDONMENT_THRESHOLD

The abandonmentThreshold option allows Renovate to flag packages as abandoned when they haven't received updates for a specified period of time.

Renovate adds an isAbandoned boolean property to the package lookup result when:

The mostRecentTimestamp timestamp represents the release date of the highest version, but only if that version also has the most recent timestamp among all releases. This ensures abandonment detection is based on normal package release patterns.

If a package's most recent release date plus the abandonmentThreshold duration is in the past, the package is marked as abandoned (isAbandoned: true).

This option accepts time duration strings like 1 year, 6 months, 90 days, etc.

Example usage:

{\n  \"abandonmentThreshold\": \"2 years\"\n}\n

You can also apply this setting selectively using packageRules:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"abandonmentThreshold\": \"1 year\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#addlabels","title":"addLabels","text":"

Labels to add to Pull Request.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string mergeable true supportsTemplating true cli --add-labels env RENOVATE_ADD_LABELS default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

The labels field is non-mergeable, meaning that any config setting a list of PR labels will replace any existing list. If you want to append labels for matched rules, then define an addLabels array with one (or more) label strings. All matched addLabels strings will be attached to the PR.

Consider this example:

{\n  \"labels\": [\"dependencies\"],\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"labels\": [\"linting\"]\n    },\n    {\n      \"matchDepTypes\": [\"optionalDependencies\"],\n      \"addLabels\": [\"optional\"]\n    }\n  ]\n}\n

With the above config:

If you want to use dynamic labels, you can use templates such as this example using depName for addLabels:

{\n  \"addLabels\": [\"{{depName}}\"]\n}\n

Note

Keep your labels within the maximum character limit for your Git hosting platform. Renovate usually truncates labels to 50 characters, except for GitLab, which has a 255 character limit.

"},{"location":"configuration-options/#additionalbranchprefix","title":"additionalBranchPrefix","text":"

Additional string value to be appended to branchPrefix.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"\" supportsTemplating true env RENOVATE_ADDITIONAL_BRANCH_PREFIX previouslyKnownAs 
[\"managerBranchPrefix\"]\n

This option supports Renovate's template syntax

See templates for available variables and helpers.

By default, the value for this config option is an empty string. Normally you don't need to set this config option.

Here's an example where additionalBranchPrefix can help you. Say you're using a monorepo and want to split pull requests based on the location of the package definition, so that individual teams can manage their own Renovate pull requests. This can be done with this configuration:

{\n  \"additionalBranchPrefix\": \"{{parentDir}}-\"\n}\n
"},{"location":"configuration-options/#additionalreviewers","title":"additionalReviewers","text":"

Additional reviewers for Pull Requests (in contrast to reviewers, this option adds to the existing reviewer list, rather than replacing it).

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string mergeable true cli --additional-reviewers env RENOVATE_ADDITIONAL_REVIEWERS default []

This option adds to the existing reviewer list, rather than replacing it like reviewers.

Use additionalReviewers when you want to add to a preset or base list, without replacing the original. For example, when adding focused reviewers for a specific package group.

Please note that Reviewers are only added during creation of a PR, but are not modified afterwards.

"},{"location":"configuration-options/#assignautomerge","title":"assignAutomerge","text":"

Assign reviewers and assignees even if the PR is to be automerged.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --assign-automerge env RENOVATE_ASSIGN_AUTOMERGE

By default, Renovate will not assign reviewers and assignees to an automerge-enabled PR unless it fails status checks. By configuring this setting to true, Renovate will instead always assign reviewers and assignees for automerging PRs at time of creation.

"},{"location":"configuration-options/#assignees","title":"assignees","text":"

Assignees for Pull Request (either username or email address depending on the platform).

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --assignees env RENOVATE_ASSIGNEES default []

Must be valid usernames on the platform in use. Teams are not supported, and Renovate passes team: entries to the platform unchanged. To request a review from a team, use reviewers instead.

"},{"location":"configuration-options/#assigneesfromcodeowners","title":"assigneesFromCodeOwners","text":"

Determine assignees based on configured code owners and changes in PR.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --assignees-from-code-owners env RENOVATE_ASSIGNEES_FROM_CODE_OWNERS

If enabled Renovate tries to determine PR assignees by matching rules defined in a CODEOWNERS file against the changes in the PR.

Read the docs for your platform for details on syntax and allowed file locations:

"},{"location":"configuration-options/#assigneessamplesize","title":"assigneesSampleSize","text":"

Take a random sample of given size from assignees.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer cli --assignees-sample-size env RENOVATE_ASSIGNEES_SAMPLE_SIZE

If configured, Renovate will take a random sample of given size from assignees and assign them only, instead of assigning the entire list of assignees you have configured.

"},{"location":"configuration-options/#autoapprove","title":"autoApprove","text":"

Set to true to automatically approve PRs.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms azure, gerrit, gitlab cli --auto-approve env RENOVATE_AUTO_APPROVE previouslyKnownAs 
[\"azureAutoApprove\"]\n

Setting this to true will automatically approve the PRs.

You can also configure this using packageRules if you want to use it selectively (e.g. per-package).

"},{"location":"configuration-options/#autoreplaceglobalmatch","title":"autoReplaceGlobalMatch","text":"

Control whether replacement regular expressions are global matches or only the first match.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true cli --auto-replace-global-match env RENOVATE_AUTO_REPLACE_GLOBAL_MATCH

Setting this to false will replace only the first match during replacements updates.

Disabling this is useful for situations where values are repeated within the dependency string, such as when the currentVersion is also featured somewhere within the currentDigest, but you only want to replace the first instance.

Consider this example:

FROM java:8@sha256:0e8b2a860\n
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"java\"],\n      \"replacementName\": \"eclipse-temurin\",\n      \"replacementVersion\": \"11\"\n    }\n  ]\n}\n

With the above replacement scenario, the current dependency has a version of 8, which also features several times within the digest section.

When using the default autoReplaceGlobalMatch configuration, Renovate will try to replace all instances of 8 within the dependency string with the replacementVersion value of 11. This will replace more than is intended and will be caught during replacement validation steps, resulting in the replacement PR to not be created.

When setting autoReplaceGlobalMatch configuration to false, Renovate will only replace the first occurrence of 8 and will successfully create a replacement PR.

"},{"location":"configuration-options/#automerge","title":"automerge","text":"

Whether to automerge branches/PRs automatically, without human intervention.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --automerge env RENOVATE_AUTOMERGE

By default, Renovate raises PRs but leaves them to someone or something else to merge them. By configuring this setting, you allow Renovate to automerge PRs or even branches. Using automerge reduces the amount of human intervention required.

Usually you won't want to automerge all PRs, for example most people would want to leave major dependency updates to a human to review first. You could configure Renovate to automerge all but major this way:

{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"minor\", \"patch\", \"pin\", \"digest\"],\n      \"automerge\": true\n    }\n  ]\n}\n

Also note that this option can be combined with other nested settings, such as dependency type. So for example you could choose to automerge all (passing) devDependencies only this way:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"automerge\": true\n    }\n  ]\n}\n

Note

Branches creation follows schedule and the automerge follows automergeSchedule.

Note

On Azure there can be a delay between a PR being set as completed by Renovate, and Azure merging the PR / finishing its tasks. Renovate tries to delay until Azure is in the expected state, but it will continue if it takes too long. In some cases this can result in a dependency not being merged, and a fresh PR being created for the dependency.

Note

By default, Renovate will not assign reviewers and assignees to an automerge-enabled PR unless it fails status checks. By configuring assignAutomerge setting to true, Renovate will instead always assign reviewers and assignees for automerging PRs at time of creation.

Automerge and GitHub branch protection rules

You must select at least one status check in the Require status checks to pass before merging section of your branch protection rules on GitHub, if you match all three conditions:

If you don't select any status check, and you use platform automerge, then GitHub might automerge PRs with failing tests!

"},{"location":"configuration-options/#automergecomment","title":"automergeComment","text":"

PR comment to add to trigger automerge. Only used if automergeType=pr-comment.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"automergeComment\" cli --automerge-comment env RENOVATE_AUTOMERGE_COMMENT

Use this only if you configure automergeType=\"pr-comment\".

Example use:

{\n  \"automerge\": true,\n  \"automergeType\": \"pr-comment\",\n  \"automergeComment\": \"bors: r+\"\n}\n
"},{"location":"configuration-options/#automergeschedule","title":"automergeSchedule","text":"

Limit automerge to these times of day or week.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --automerge-schedule default 
[\"at any time\"]\n

Use the automergeSchedule option to define times of week or month during which Renovate may automerge its PRs. The default value for automergeSchedule is \"at any time\", which functions the same as setting a null schedule. To configure this option refer to schedule as the syntax is the same.

Warning

When platformAutomerge is enabled, Renovate enqueues the platform PR automerge at time of creation, so the schedule specified in automergeSchedule cannot be followed. If it's essential that automerging only happens within the specific automergeSchedule time window, then you need to set platformAutomerge to false and instead rely on Renovate's automerge instead of the platform one.

"},{"location":"configuration-options/#automergestrategy","title":"automergeStrategy","text":"

The merge strategy to use when automerging PRs. Used only if automergeType=pr.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"auto\", \"fast-forward\", \"merge-commit\", \"rebase\", \"rebase-merge\", \"squash\"]\n
default \"auto\" supportedPlatforms azure, bitbucket, forgejo, gitea, github cli --automerge-strategy env RENOVATE_AUTOMERGE_STRATEGY

The automerge strategy defaults to auto, so Renovate decides how to merge pull requests as best it can. If possible, Renovate follows the merge strategy set on the platform itself for the repository.

If you've set automerge=true and automergeType=pr for any of your dependencies, then you may choose what automerge strategy Renovate uses by setting the automergeStrategy config option. If you're happy with the default behavior, you don't need to do anything.

On supported platforms, automergeStrategy also applies when using platform-native automerge.

You may choose from these values:

Platforms may only support some of these merge strategies.

If the chosen automerge strategy is not supported on your platform then Renovate stops automerging. In that case you'll have to set a supported automerge strategy.

"},{"location":"configuration-options/#automergetype","title":"automergeType","text":"

How to automerge, if enabled.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"branch\", \"pr\", \"pr-comment\"]\n
default \"pr\" cli --automerge-type env RENOVATE_AUTOMERGE_TYPE

This setting is only applicable if you opt in to configure automerge to true for any of your dependencies.

Automerging defaults to using Pull Requests (automergeType=\"pr\"). In that case Renovate first creates a branch and associated Pull Request, and then automerges the PR on a subsequent run once it detects the PR's status checks are \"green\". If by the next run the PR is already behind the base branch it will be automatically rebased, because Renovate only automerges branches which are up-to-date and green. If Renovate is scheduled for hourly runs on the repository but commits are made every 15 minutes to the main branch, then an automerge like this will keep getting deferred with every rebase.

Tip

If you have no tests but still want Renovate to automerge, you need to add \"ignoreTests\": true to your configuration.

If you prefer that Renovate more silently automerge without Pull Requests at all, you can configure \"automergeType\": \"branch\". In this case Renovate will:

Note that \"automergeType\": \"branch\" only works with GitHub merge queues or GitLab merge trains if Renovate is on the merge queue's bypass list, because the merge queue does not allow pushing directly to the base branch otherwise. If the push is rejected, Renovate falls back to creating a PR.

The final value for automergeType is \"pr-comment\", intended only for users who already have a \"merge bot\" such as bors-ng and want Renovate to not actually automerge by itself and instead tell bors-ng to merge for it, by using a comment in the PR. If you're not already using bors-ng or similar, don't worry about this option.

"},{"location":"configuration-options/#azureworkitemid","title":"azureWorkItemId","text":"

The id of an existing work item on Azure Boards to link to each PR.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 0 supportedPlatforms azure cli --azure-work-item-id env RENOVATE_AZURE_WORK_ITEM_ID

When creating a PR in Azure DevOps, some branches can be protected with branch policies to check for linked work items. Creating a work item in Azure DevOps is beyond the scope of Renovate, but Renovate can link an already existing work item when creating PRs.

"},{"location":"configuration-options/#azureworkitemtype","title":"azureWorkItemType","text":"

The work item type Renovate uses for its issues (e.g. the Dependency Dashboard) on Azure DevOps.

Name Value scopes repo type string default \"Issue\" supportedPlatforms azure cli --azure-work-item-type env RENOVATE_AZURE_WORK_ITEM_TYPE

The work item type Renovate uses when creating its issues (such as the Dependency Dashboard) on Azure DevOps.

Azure DevOps has no dedicated \"issue\" concept, so Renovate creates a work item instead. It defaults to the Issue type, which only exists in the Basic process. Projects using another process (for example Agile or Scrum), or a custom inherited process, may not have an Issue type, in which case creation fails. Set this to a work item type that exists in your project, such as Task.

Note

Renovate finds its existing issues by title, not by work item type. If you change azureWorkItemType while an issue (such as the Dependency Dashboard) already exists, Renovate keeps using the existing work item and does not recreate it with the new type. To switch an existing issue to the new type, either rename the old work item (so its title no longer matches) and close it, or close and delete the old work item. Renovate then creates a fresh work item of the configured type on the next run.

"},{"location":"configuration-options/#basebranchpatterns","title":"baseBranchPatterns","text":"

List of one or more custom base branches defined as exact strings and/or via regex expressions.

Name Value scopes repo type array subType string cli --base-branch-patterns env RENOVATE_BASE_BRANCH_PATTERNS previouslyKnownAs 
[\"baseBranches\"]\n
default []

This configuration option was formerly known as baseBranches.

By default, Renovate will detect and process only the repository's default branch. For most projects, this is the expected approach. Renovate also allows users to explicitly configure baseBranchPatterns, e.g. for use cases such as:

{\n  \"baseBranchPatterns\": [\"dev\"]\n}\n
{\n  \"baseBranchPatterns\": [\"main\", \"next\"]\n}\n
{\n  \"baseBranchPatterns\": [\"main\", \"/^release\\\\/.*/\"]\n}\n

It's possible to add this setting into the renovate.json file as part of the \"Configure Renovate\" onboarding PR. If so then Renovate will reflect this setting in its description and use package file contents from the custom base branch(es) instead of default.

Also, check useBaseBranchConfig if you want to configure different configuration for each base branch.

The simplest approach is exact matches, e.g. [\"main\", \"dev\"]. baseBranchPatterns also supports Regular Expressions that must begin and end with /, e.g.:

{\n  \"baseBranchPatterns\": [\"main\", \"/^release\\\\/.*/\"]\n}\n

You can negate the regex by prefixing it with !. Only use a single negation and do not mix it with other branch names, since all branches are combined with or. With a negation, all branches except those matching the regex will be added to the result:

{\n  \"baseBranchPatterns\": [\"!/^pre-release\\\\/.*/\"]\n}\n

You can also use the special \"$default\" string to denote the repository's default branch, which is useful if you have it in an org preset, e.g.:

{\n  \"baseBranchPatterns\": [\"$default\", \"/^release\\\\/.*/\"]\n}\n

Note

Do not use the baseBranchPatterns config option when you've set a forkToken. You may need a forkToken when you're using the Forking Renovate app.

"},{"location":"configuration-options/#bbautoresolveprtasks","title":"bbAutoResolvePrTasks","text":"

The PR tasks will be automatically completed after the PR is raised.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms bitbucket cli --bb-auto-resolve-pr-tasks env RENOVATE_BB_AUTO_RESOLVE_PR_TASKS

Configuring this to true means that Renovate will mark all PR Tasks as complete.

"},{"location":"configuration-options/#bbusedefaultreviewers","title":"bbUseDefaultReviewers","text":"

Use the default reviewers (Bitbucket only).

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true supportedPlatforms bitbucket, bitbucket-server cli --bb-use-default-reviewers env RENOVATE_BB_USE_DEFAULT_REVIEWERS

Configuring this to true means that Renovate will detect and apply the default reviewers rules to PRs (Bitbucket only).

"},{"location":"configuration-options/#branchconcurrentlimit","title":"branchConcurrentLimit","text":"

Limit to a maximum of x concurrent branches. 0 means no limit, null (default) inherits value from prConcurrentLimit.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer cli --branch-concurrent-limit env RENOVATE_BRANCH_CONCURRENT_LIMIT

By default, Renovate doesn\u2019t enforce its own concurrent branch limit. However, it inherits the prConcurrentLimit, which defaults to 10. This effectively caps concurrent branches at 10, though in many repositories a lower limit, such as 3 or 5, tends to be more efficient.

If you want the same limit for both concurrent branches and concurrent PRs, then set a value for prConcurrentLimit and it will be reused for branch calculations too. But if you want to allow more concurrent branches than concurrent PRs, you can configure both values (e.g. branchConcurrentLimit=5 and prConcurrentLimit=3).

This limit is enforced on a per-repository basis.

Example config:

{\n  \"branchConcurrentLimit\": 3\n}\n

Warning

Leaving PRs/branches as unlimited or as a high number increases the time it takes for Renovate to process a repository. If you find that Renovate is too slow when rebasing out-of-date branches, decrease the branchConcurrentLimit.

If you have too many concurrent branches which rebase themselves each run, Renovate can take a lot of time to rebase. Solutions:

"},{"location":"configuration-options/#branchname","title":"branchName","text":"

Branch name template.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"{{{branchPrefix}}}{{{additionalBranchPrefix}}}{{{branchTopic}}}\" supportsTemplating true env RENOVATE_BRANCH_NAME

This option supports Renovate's template syntax

See templates for available variables and helpers.

This feature has been deprecated

We strongly recommended that you avoid configuring this field directly. Please edit branchPrefix, additionalBranchPrefix, or branchTopic instead.

If you truly need to configure this then it probably means either:

"},{"location":"configuration-options/#branchnamestrict","title":"branchNameStrict","text":"

Whether to be strict about the use of special characters within the branch name.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --branch-name-strict env RENOVATE_BRANCH_NAME_STRICT

If true, Renovate removes special characters when slugifying the branch name:

The default false behavior will mean that special characters like . and / may end up in the branch name.

Note

Renovate will not apply any search/replace to the branchPrefix part of the branch name. If you don't want any / in your branch name then you will also need to change branchPrefix from the default renovate/ value to something like renovate-.

"},{"location":"configuration-options/#branchprefix","title":"branchPrefix","text":"

Prefix to use for all branch names.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"renovate/\" supportsTemplating true cli --branch-prefix env RENOVATE_BRANCH_PREFIX

This option supports Renovate's template syntax

See templates for available variables and helpers.

You can modify this field if you want to change the prefix used. For example if you want branches to be like deps/eslint-4.x instead of renovate/eslint-4.x then you configure branchPrefix = deps/. Or if you wish to avoid forward slashes in branch names then you could use renovate_ instead, for example.

branchPrefix must be configured at the root of the configuration (e.g. not within any package rule) and is not allowed to use template values. e.g. instead of renovate/{{parentDir}}-, configure the template part in additionalBranchPrefix, like \"additionalBranchPrefix\": \"{{parentDir}}-\".

Note

This setting does not change the default onboarding branch name, i.e. renovate/configure. If you wish to change that too, you need to also configure the field onboardingBranch in your global self-hosted config.

"},{"location":"configuration-options/#branchprefixold","title":"branchPrefixOld","text":"

Old branchPrefix value to check for existing PRs.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"renovate/\" cli --branch-prefix-old env RENOVATE_BRANCH_PREFIX_OLD

Renovate uses branch names as part of its checks to see if an update PR was created previously, and already merged or ignored. If you change branchPrefix, then no previously closed PRs will match, which could lead to Renovate recreating PRs in such cases. Instead, set the old branchPrefix value as branchPrefixOld to allow Renovate to look for those branches too, and avoid this happening.

"},{"location":"configuration-options/#branchtopic","title":"branchTopic","text":"

Branch topic.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"{{{depNameSanitized}}}-{{{newMajor}}}{{#if separateMinorPatch}}{{#if isPatch}}.{{{newMinor}}}{{/if}}{{/if}}{{#if separateMultipleMinor}}{{#if isMinor}}.{{{newMinor}}}{{/if}}{{/if}}.x{{#if isLockfileUpdate}}-lockfile{{/if}}\" supportsTemplating true env RENOVATE_BRANCH_TOPIC

This option supports Renovate's template syntax

See templates for available variables and helpers.

This field is combined with branchPrefix and additionalBranchPrefix to form the full branchName. branchName uniqueness is important for dependency update grouping or non-grouping so be cautious about ever editing this field manually. This is an advanced field, and it's recommend you seek a config review before applying it.

"},{"location":"configuration-options/#bumpversion","title":"bumpVersion","text":"

Bump the version in the package file being updated.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"major\", \"minor\", \"patch\", \"prerelease\"]\n
supportedManagers helmv3, npm, nuget, maven, sbt cli --bump-version env RENOVATE_BUMP_VERSION default null

Currently, this config option only works with these managers:

Raise a feature request if you want to use this config option with other package managers.

Use bumpVersion if you want Renovate to update the version field in your package file when it updates the dependencies in that file. This can be handy when you have automated your package's release, as you you don't need extra steps after the Renovate upgrade, you can just release a new version.

Configure this value to \"prerelease\", \"patch\", \"minor\" or \"major\" to have Renovate update the version in your edited package file. e.g. if you wish Renovate to always increase the target package.json version with a patch update, configure this to \"patch\".

For npm only you can also configure this field to \"mirror:x\" where x is the name of a package in the package.json. Doing so means that the package.json version field will mirror whatever the version is that x depended on. Make sure that version is a pinned version of course, as otherwise it won't be valid.

For sbt note that Renovate will update the version string only for packages that have the version string in their project's built.sbt file.

"},{"location":"configuration-options/#bumpversions","title":"bumpVersions","text":"

A list of bumpVersion config options to bump generic version numbers.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType object default []

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

The bumpVersions option allows Renovate to update semantic version strings in your code when dependencies are updated. This is useful for files or version fields that Renovate does not natively support or for custom versioning needs.

The option is an array of rules, each specifying how and where to bump versions. Each rule includes the following fields:

Tip

You can use templates in filePatternTemplates, bumpType, and matchStrings. This way you can leverage the power of Renovate's templating engine to change based on the context of the upgrade.

Here is an example of a bumpVersions configuration:

{\n  \"bumpVersions\": [\n    {\n      \"name\": \"Updating release version file\",\n      \"filePatterns\": [\".release-version\"],\n      \"bumpType\": \"minor\",\n      \"matchStrings\": [\"^(?<version>.+)$\"]\n    }\n  ]\n}\n

In this example:

Conditional Bumping with packageRules:

You can use packageRules to apply bumpVersions conditionally. For example, to bump versions only for updates in the charts/ directory:

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"charts/**\"],\n      \"bumpVersions\": [\n        {\n          \"filePatterns\": [\"{{packageFileDir}}/Chart.{yaml,yml}\"],\n          \"matchStrings\": [\"version:\\\\s(?<version>[^\\\\s]+)\"],\n          \"bumpType\": \"{{#if isPatch}}patch{{else}}minor{{/if}}\"\n        }\n      ]\n    }\n  ]\n}\n

In this configuration:

debugging bumpVersions

Use logLevelRemap to remap, trace log level messages to a higher level e.g. debug. All messages are prefixed with bumpVersions or bumpVersions(<name>) to help you filter them in the logs.

{\n  \"logLevelRemap\": [\n    {\n      \"matchMessage\": \"/bumpVersions/\",\n      \"newLogLevel\": \"debug\"\n    }\n  ]\n}\n

short versions

It's possible to bump short versions:

"},{"location":"configuration-options/#bumpversionsbumptype","title":"bumpVersions.bumpType","text":"

The semver level to use when bumping versions. This is used by the bumpVersions feature.

Name Value type string parents bumpVersions allowedValues 
[\"major\", \"minor\", \"patch\", \"prerelease\", \"sync\"]\n
supportsTemplating true cli --bump-type env RENOVATE_BUMP_TYPE default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

The bumpType field specifies the type of version bump to apply. Supported values are:

This field supports templates for conditional logic. For example:

{\n  \"bumpType\": \"{{#if isPatch}}patch{{else}}minor{{/if}}\"\n}\n

In this example, the bump type is set to patch for patch updates and minor for all other cases.

Using sync to sync with dependency updates

The sync type is special: it uses the same version as the dependency manager update that triggered the branch. This is useful when you want to keep version files in sync with actual dependency updates.

For example, if you have a .release-version file that should always match the version of a specific dependency:

{\n  \"bumpVersions\": [\n    {\n      \"filePatterns\": [\".release-version\"],\n      \"bumpType\": \"sync\",\n      \"matchStrings\": [\"^(?<version>.+)$\"]\n    }\n  ]\n}\n

When Renovate updates a dependency to version 2.5.3, it will also update the .release-version file to 2.5.3.

Note

When using bumpType: \"sync\", Renovate uses the newVersion from the first upgrade in the branch. If no upgrades are found in the branch, the version bump will be skipped and a debug message will be logged.

"},{"location":"configuration-options/#bumpversionsfilepatterns","title":"bumpVersions.filePatterns","text":"

A list of patterns to match files that contain the version string.

Name Value type array subType string parents bumpVersions supportsTemplating true cli --file-patterns env RENOVATE_FILE_PATTERNS default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

The filePatterns field defines which files should be scanned for version strings. It accepts one or more patterns following Renovate's string pattern matching syntax. Templates can also be used for dynamic patterns. See Templates for more information.

For example:

{\n  \"filePatterns\": [\"**/version.txt\", \"{{packageFileDir}}/Chart.yaml\"]\n}\n

This configuration matches files named version.txt in any directory and Chart.yaml files in specific package directories.

"},{"location":"configuration-options/#bumpversionsmatchstrings","title":"bumpVersions.matchStrings","text":"

Queries to use. Valid only within bumpVersions or customManagers object. Templating is supported within bumpVersions only.

Name Value type array subType string parents customManagersbumpVersions supportsTemplating true default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

Use matchStrings within bumpVersions to define patterns to match version strings in files. See customManagers.matchStrings for full documentation.

"},{"location":"configuration-options/#bumpversionsname","title":"bumpVersions.name","text":"

A name for the bumpVersion config. This is used for logging and debugging.

Name Value type string parents bumpVersions cli --name env RENOVATE_NAME default null

The name field is an optional identifier for the bump version rule. It is used in logs to help identify which rule is being applied.

For example:

{\n  \"name\": \"Update release version\"\n}\n

This name will appear in Renovate logs, making it easier to debug or trace specific rules.

"},{"location":"configuration-options/#clonesubmodules","title":"cloneSubmodules","text":"

Set to true to initialize submodules during repository clone.

Name Value scopes repo type boolean default false cli --clone-submodules env RENOVATE_CLONE_SUBMODULES

Enabling this option will mean that detected Git submodules will be cloned at time of repository clone. By default all will be cloned, but this can be customized by configuring cloneSubmodulesFilter too. Submodules are always cloned recursively.

Important: private submodules aren't supported by Renovate, unless the underlying ssh layer already has the correct permissions.

"},{"location":"configuration-options/#clonesubmodulesfilter","title":"cloneSubmodulesFilter","text":"

List of submodules names or patterns to clone when cloneSubmodules=true.

Name Value scopes repo type array subType string default 
[\"*\"]\n
cli --clone-submodules-filter env RENOVATE_CLONE_SUBMODULES_FILTER

Use this option together with cloneSubmodules if you wish to clone only a subset of submodules.

This config option supports regex and glob filters, including negative matches. For more details on this syntax see Renovate's string pattern matching documentation.

"},{"location":"configuration-options/#commitbody","title":"commitBody","text":"

Commit message body template. Will be appended to commit message, separated by two line returns.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true env RENOVATE_COMMIT_BODY default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Configure this if you wish Renovate to add a commit body, otherwise Renovate uses a regular single-line commit.

For example, To add [skip ci] to every commit you could configure:

{\n  \"commitBody\": \"[skip ci]\"\n}\n

Onboarding and config migration commits expose only {{{gitAuthor}}} from the repository config to this template.

To add git trailers like Signed-off-by to commits, use commitTrailers instead.

"},{"location":"configuration-options/#commitbodytable","title":"commitBodyTable","text":"

If enabled, append a table in the commit message body describing all updates in the commit.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --commit-body-table env RENOVATE_COMMIT_BODY_TABLE"},{"location":"configuration-options/#commithourlylimit","title":"commitHourlyLimit","text":"

Rate limit commits to maximum x per hour. 0 means no limit.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 0 cli --commit-hourly-limit env RENOVATE_COMMIT_HOURLY_LIMIT

This config option limits the number of commits Renovate pushes in an hour. It includes commits pushed while creating a new branch or rebasing an existing one.

Use commitHourlyLimit to strictly control the rate at which Renovate triggers CI runs. Both branch creation and rebasing trigger CI runs, so limiting these operations helps you control your CI load.

For example, with commitHourlyLimit: 2, in a given hour Renovate might:

This limit is enforced on a per-repository basis and per hourly period (:00 through :59).

This setting differs from prHourlyLimit in an important way:

If you want strict control over CI load, use commitHourlyLimit. If you only want to limit the rate of new PRs, use prHourlyLimit.

Tip

Manual rebases (requested via checkbox, Dependency Dashboard, or rebase label) always bypass this limit.

"},{"location":"configuration-options/#commitmessage","title":"commitMessage","text":"

Message to use for commit messages and pull request titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"{{{commitMessagePrefix}}} {{{commitMessageAction}}} {{{commitMessageTopic}}} {{{commitMessageExtra}}} {{{commitMessageSuffix}}}\" supportsTemplating true env RENOVATE_COMMIT_MESSAGE

This option supports Renovate's template syntax

See templates for available variables and helpers.

This feature has been deprecated

We deprecated editing the commitMessage directly, and we recommend you stop using this config option. Instead use config options like commitMessageAction, commitMessageExtra, and so on, to create the commit message you want.

"},{"location":"configuration-options/#commitmessageaction","title":"commitMessageAction","text":"

Action verb to use in commit messages and PR titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"Update\" supportsTemplating true env RENOVATE_COMMIT_MESSAGE_ACTION

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

This is used to alter commitMessage and prTitle without needing to copy/paste the whole string. Actions may be like Update, Pin, Roll back, Refresh, etc. Check out the default value for commitMessage to understand how this field is used.

"},{"location":"configuration-options/#commitmessageextra","title":"commitMessageExtra","text":"

Extra description used after the commit message topic - typically the version.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"to {{#if isPinDigest}}{{{newDigestShort}}}{{else}}{{#if isMajor}}{{prettyNewMajor}}{{else}}{{#if isSingleVersion}}{{prettyNewVersion}}{{else}}{{#if newValue}}{{{newValue}}}{{else}}{{{newDigestShort}}}{{/if}}{{/if}}{{/if}}{{/if}}\" supportsTemplating true env RENOVATE_COMMIT_MESSAGE_EXTRA

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

This is used to alter commitMessage and prTitle without needing to copy/paste the whole string. The \"extra\" is usually an identifier of the new version, e.g. \"to v1.3.2\" or \"to tag 9.2\".

"},{"location":"configuration-options/#commitmessagelowercase","title":"commitMessageLowerCase","text":"

Lowercase PR- and commit titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"auto\", \"never\"]\n
default \"auto\" cli --commit-message-lower-case env RENOVATE_COMMIT_MESSAGE_LOWER_CASE

With semanticCommits pr- and commit-titles will by default (\"auto\") be converted to all-lowercase. Set this to \"never\" to leave the titles untouched, allowing uppercase characters in semantic commit titles.

"},{"location":"configuration-options/#commitmessageprefix","title":"commitMessagePrefix","text":"

Prefix to add to start of commit messages and PR titles. Uses a semantic prefix if semanticCommits is enabled.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true env RENOVATE_COMMIT_MESSAGE_PREFIX default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

This is used to alter commitMessage and prTitle (which also affects how it's displayed in the Dependency Dashboard) without needing to copy/paste the whole string. The \"prefix\" is usually an automatically applied semantic commit prefix, but it can also be statically configured.

"},{"location":"configuration-options/#commitmessagesuffix","title":"commitMessageSuffix","text":"

Suffix to add to end of commit messages and PR titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true env RENOVATE_COMMIT_MESSAGE_SUFFIX default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

This is used to add a suffix to commit messages. Usually left empty except for internal use (multiple base branches, and vulnerability alerts).

"},{"location":"configuration-options/#commitmessagetopic","title":"commitMessageTopic","text":"

The upgrade topic/noun used in commit messages and PR titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"dependency {{depName}}\" supportsTemplating true env RENOVATE_COMMIT_MESSAGE_TOPIC

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

You can use commitMessageTopic to change the commitMessage and prTitle without copy/pasting the whole string. The \"topic\" usually refers to the dependency being updated, for example: \"dependency react\".

We recommend you use matchManagers and commitMessageTopic in a packageRules array to set the commit message topic, like this:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"github-actions\"],\n      \"commitMessageTopic\": \"{{depName}}\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#committrailers","title":"commitTrailers","text":"

Structured git trailers (Key: value lines) to add in the final block of the commit message.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string mergeable true supportsTemplating true env RENOVATE_COMMIT_TRAILERS default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

Use this option to add git trailers to the commits Renovate creates. Each entry must be a full trailer line in the form Key: value, where the key may only have letters, digits and -. Repeated keys are allowed.

For example:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"commitTrailers\": [\"Changelog: skip\"]\n    }\n  ]\n}\n

If you want Renovate to sign off its commits, you can add the :gitSignOff preset to your extends array:

{\n  \"extends\": [\":gitSignOff\"]\n}\n

Onboarding and config migration commits expose only {{{gitAuthor}}} from the repository config to this template.

"},{"location":"configuration-options/#composerignoreplatformreqs","title":"composerIgnorePlatformReqs","text":"

Configure use of --ignore-platform-reqs or --ignore-platform-req for the Composer package manager.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --composer-ignore-platform-reqs env RENOVATE_COMPOSER_IGNORE_PLATFORM_REQS default []

By default, Renovate will ignore Composer platform requirements as the PHP platform used by Renovate most probably won't match the required PHP environment of your project as configured in your composer.json file.

Composer 2.2 and up will be run with --ignore-platform-req='ext-*' --ignore-platform-req='lib-*', which ignores extension and library platform requirements but not the PHP version itself and should work in most cases.

Older Composer versions will be run with --ignore-platform-reqs, which means that all platform constraints (including the PHP version) will be ignored by default. This can result in updated dependencies that are not compatible with your platform.

To customize this behavior, you can explicitly ignore platform requirements (for example ext-zip) by setting them separately in this array. Each item will be added to the Composer command with --ignore-platform-req, resulting in it being ignored during its invocation. Note that this requires your project to use Composer V2, as V1 doesn't support excluding single platform requirements. The used PHP version will be guessed automatically from your composer.json definition, so php should not be added as explicit dependency.

If an empty array is configured, Renovate uses its default behavior.

Set to null (not recommended) to fully omit --ignore-platform-reqs/--ignore-platform-req during Composer invocation. This requires the Renovate image to be fully compatible with your Composer platform requirements in order for the Composer invocation to succeed, otherwise Renovate will fail to create the updated lock file. The Composer output should inform you about the reasons the update failed.

"},{"location":"configuration-options/#confidential","title":"confidential","text":"

If enabled, issues created by Renovate are set as confidential.

Name Value scopes repo type boolean default false supportedPlatforms gitlab cli --confidential env RENOVATE_CONFIDENTIAL

If enabled, all issues created by Renovate are set as confidential, even in a public repository.

Note

The Dependency Dashboard issue will also be confidential. By default issues created by Renovate are visible to all users.

Note

This option is applicable to GitLab only.

"},{"location":"configuration-options/#configmigration","title":"configMigration","text":"

Enable this to get config migration PRs when needed.

Name Value scopes repo type boolean default false cli --config-migration env RENOVATE_CONFIG_MIGRATION

This feature is flagged as experimental

Config migration PRs are still being improved, in particular to reduce the amount of reordering and whitespace changes.To track this feature visit the following GitHub issue #16359.

If enabled, Renovate raises a pull request when it needs to migrate the Renovate config file. Renovate only performs configMigration on .json and .json5 files.

We're adding new features to Renovate often. Often you can keep using your Renovate config and use the new features right away. But sometimes you need to update your Renovate configuration. To help you with this, Renovate will create config migration pull requests, when you enable configMigration.

Example:

After we changed the baseBranchPatterns feature, the Renovate configuration migration pull request would make this change:

{\n- \"baseBranch\": \"main\"\n+ \"baseBranchPatterns\": [\"main\"]\n}\n

Warning

The configMigration feature writes plain JSON for .json files, and JSON5 for .json5 files. Renovate may downgrade JSON5 content to plain JSON. When downgrading JSON5 to JSON Renovate may also remove the JSON5 comments. This can happen because Renovate wrongly converts JSON5 to JSON, thus removing the comments.

For more details, read the config migration documentation.

"},{"location":"configuration-options/#configwarningreuseissue","title":"configWarningReuseIssue","text":"

Set this to true to make Renovate reuse/reopen an existing closed Config Warning issue, instead of opening a new one each time.

Name Value scopes repo type boolean default false cli --config-warning-reuse-issue env RENOVATE_CONFIG_WARNING_REUSE_ISSUE

If no existing issue is found, Renovate's default behavior is to create a new Config Warning issue. Accordingly, you'll get a new issue each time you have a Config Warning, although never more than one open at a time. Configure this option to true if you prefer Renovate to reopen any found matching closed issue whenever there is a config warning. The downside of this is that you may end up with a very old issue getting \"recycled\" each time and it will sort older than others.

"},{"location":"configuration-options/#constraints","title":"constraints","text":"

Configuration object to define language or manager version constraints.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object default 
{\"ghActionsLock\": \"v0.4.1\"}\n
mergeable true supportedManagers bundler, composer, github-actions, gomod, mise, npm, pep621, pipenv, poetry freeChoice true env RENOVATE_CONSTRAINTS

Constraints are used in package managers which use third-party tools to update \"artifacts\" like lock files or checksum files. Typically, the constraint is detected automatically by Renovate from files within the repository and there is no need to manually configure it.

Constraints are also used to manually restrict which datasource versions are possible to upgrade to based on their language support. For now this datasource constraint feature only supports python, other compatibility restrictions will be added in the future.

{\n  \"constraints\": {\n    \"python\": \"2.7\"\n  }\n}\n

If you need to override constraints that Renovate detects from the repository, wrap it in the global self-hosted configuration's force object like so:

module.exports = {\n  force: {\n    constraints: {\n      node: '< 15.0.0',\n    },\n  },\n};\n

The following constraints are available to specify which package managers/language constraints/tools Renovate will install for your repository:

Tool Additional Information Versioning Datasource apm semver github-releases bazelisk semver github-releases bun npm github-releases bundler ruby rubygems cocoapods ruby rubygems composer composer github-releases conan pep440 pypi copier pep440 pypi corepack npm npm deno deno github-releases devbox semver github-releases dotnet semver dotnet-version erlang semver-coerced github-releases elixir semver github-releases flux semver github-releases gh semver github-releases gleam semver github-releases golang npm github-releases gradle gradle gradle-version hashin pep440 pypi helm semver github-releases helmfile semver github-releases java npm java-version jb loose github-releases kustomize semver github-releases maven maven github-releases mise npm github-releases nix semver github-releases node node github-releases npm npm npm paket paket nuget pdm semver github-releases php composer github-releases pip-tools pep440 pypi pipenv pep440 pypi pnpm npm npm pixi conda github-releases poetry pep440 pypi python python github-releases ruby Also used in the rubygems Datasource ruby github-releases rust rust-release-channel rust-version uv pep440 pypi yarn npm npm yarn-slim npm npm dart npm dart-version flutter npm github-releases vendir semver github-releases

Note

When using binarySource=global, the constraints options do not take effect.

Additionally, there are several additional constraints that can be specified:

Constraint Additional Information ghActionsLock Used in the github-actions manager to specify a release tag for the github/gh-actions-lock gh CLI extension, which regenerates .github/workflows/actions.lock.Must be a full release tag, prefixed with v, such as v0.1.7. Set it to an empty string to always install the latest release. go Used in the gomod manager to specify the version of the Go toolchain to use.In precedence order:1. config: constraints.go1. go.mod: toolchain directive1. go.mod: go directiveNOTE that the constraints.golang is not used (https://github.com/renovatebot/renovate/issues/42601) gomodMod Used in the gomod manager to specify a tag for github.com/marwan-at-work/mod.Must be prefixed with v. jenkins Used in the jenkins-plugins datasource to specify a minimum version of Jenkins that a plugin must support. pipTools Used in the pip-compile manager to specify a version of pip-tools to use. @deprecated TODO remove in #42599 platform Used in the rubygems datasource to specify the platform that the Gem dependency supports. rubygems Used in the rubygems datasource to specify the version of the rubygems tool that is needed to use this Gem. vscode Used in the npm manager to track the version of VSCode that the package is compatible with. dotnet-sdk Used in the nuget manager to track .NET SDK version required. perl Used in the cpanfile manager to track Perl version required. %goMod Used in the gomod manager to determine the minimum version of Go required to use this module.Note that this is prefixed with a % to explicitly note that this is not a tool that Containerbase knows.

Note

Make sure not to mix this up with the term compatibility, which Renovate uses in the context of version releases, e.g. if a Docker image is node:12.16.0-alpine then the -alpine suffix represents compatibility.

"},{"location":"configuration-options/#constraintsfiltering","title":"constraintsFiltering","text":"

Perform release filtering based on language constraints.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string allowedValues 
[\"none\", \"strict\"]\n
default \"none\" env RENOVATE_CONSTRAINTS_FILTERING

This option controls whether Renovate filters new releases based on configured or detected constraints. Renovate supports two options:

More advanced filtering options may come in future.

There must be a constraints object in your Renovate config, or constraints detected from package files, for this to work. Additionally, the \"datasource\" within Renovate must be capable of returning constraints values about each package's release.

This feature is limited to the following datasources:

Sometimes when using private registries they may omit constraints information, which then is another reason such filtering may not work even if the datasource and corresponding default public registry supports it.

Warning

Enabling this feature may result in many package updates being filtered out silently. See below for a description of how it works.

Warning

Enabling this feature when using binarySource=global can lead to situations where Renovate suggests updates that it cannot then update, as it does not have the right tool versions installed.

When constraintsFiltering=strict, the following logic applies:

Here are some examples:

Your repo engines.node Dependency release engines.node Result 18 16 \\|\\| 18 allowed ^18.10.0 >=18 allowed ^16.10.0 \\|\\| >=18.0.0 >= 16.0.0 allowed >=16 16 \\|\\| 18 filtered 16 ^16.10.0 filtered

When using with npm, we recommend you:

"},{"location":"configuration-options/#constraintsversioning","title":"constraintsVersioning","text":"

Override the versioning scheme used when filtering releases by specific constraint names. Does not apply to tools.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object mergeable true freeChoice true

Use constraintsVersioning to override the versioning scheme used when filtering releases by specific constraint names with constraintsFiltering.

Note

Each key must be an additional constraint name (i.e. not a tool name), and each value must be a valid versioning scheme ID.

Datasources that support constraints filtering may set sensible defaults for their constraints. You can override these defaults in your Renovate config.

For example, to use a SemVer-style versioning scheme when defining the rubygems constraint:

Use SemVer-style range for defining version constraint, instead of 'ruby' versioning
{\n  \"constraints\": {\n    \"rubygems\": \"^1.3\"\n  },\n  \"constraintsVersioning\": {\n    \"rubygems\": \"semver-coerced\"\n  }\n}\n
"},{"location":"configuration-options/#customdatasources","title":"customDatasources","text":"

Defines custom datasources for usage by managers.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object additionalProperties 
{\"type\": \"object\"}\n
mergeable true cli --custom-datasources env RENOVATE_CUSTOM_DATASOURCES

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.To track this feature visit the following GitHub issue #23286.

Use customDatasources to fetch releases from APIs or statically hosted sites and Renovate has no own datasource. These datasources can be referred by customManagers or can be used to overwrite default datasources.

For more details see the custom datasource documentation.

"},{"location":"configuration-options/#customdatasourcesdefaultregistryurltemplate","title":"customDatasources.defaultRegistryUrlTemplate","text":"

Template for generating a defaultRegistryUrl for custom datasource.

Name Value type string default \"\" parents customDatasources supportsTemplating true

This option supports Renovate's template syntax

See templates for available variables and helpers.

This field is used to build a registryUrl for the dependency. It is not needed if either:

{\n  customDatasources: {\n    foo: {\n      defaultRegistryUrlTemplate: 'https://example.foo.bar/v1/{{ packageName }}',\n    },\n  },\n}\n
"},{"location":"configuration-options/#customdatasourcesformat","title":"customDatasources.format","text":"

Format of the custom datasource.

Name Value type string parents customDatasources default \"json\" allowedValues 
[\"html\", \"json\", \"plain\", \"toml\", \"yaml\"]\n

Defines which format the API is returning. Currently json or plain are supported, see the custom datasource documentation for more information.

"},{"location":"configuration-options/#customdatasourcestransformtemplates","title":"customDatasources.transformTemplates","text":"

List of jsonata transformation rules.

Name Value type array subType string parents customDatasources supportsTemplating true cli --transform-templates env RENOVATE_TRANSFORM_TEMPLATES default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

transformTemplates is a list of jsonata rules which get applied serially. Use this if the API does not return a Renovate compatible schema.

"},{"location":"configuration-options/#custommanagers","title":"customManagers","text":"

Custom managers using regex matching.

Name Value scopes repo type array subType object cli --custom-managers mergeable true env RENOVATE_CUSTOM_MANAGERS previouslyKnownAs 
[\"regexManagers\"]\n
default []

Use customManagers(previously regexManagers) entries to configure the custom managers in Renovate.

You can define custom managers to handle:

Renovate has two custom managers:

Custom manager Matching engine regex Regular Expression, with named capture groups. jsonata JSONata query.

To use a custom manager, you must give Renovate this information:

  1. managerFilePatterns: regex/glob pattern of the file to extract deps from
  2. matchStrings: regex patterns or jsonata queries used to process the file

The matchStrings must capture/extract the following three fields:

Alternatively, you could also use corresponding templates (e.g. depNameTemplate) for these fields. But, we recommend you use only one of these methods, or you'll get confused.

Also, we recommend you explicitly set which versioning Renovate should use.

Renovate defaults to semver-coerced versioning if both condition are met:

For more details and examples regarding each custom manager, see our documentation for the regex manager and the JSONata manager. For template fields, use the triple brace {{{ }}} notation to avoid Handlebars escaping any special characters.

Tip

Look at our Custom Manager Presets, they may have what you need.

"},{"location":"configuration-options/#custommanagersautoreplacestringtemplate","title":"customManagers.autoReplaceStringTemplate","text":"

Optional extractVersion for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Allows overwriting how the matched string is replaced. This allows for some migration strategies. E.g. moving from one Docker image repository to another one.

helm-values.yaml
# The image of the service <registry>/<repo>/<image>:<tag>\nimage: my.old.registry/aRepository/andImage:1.18-alpine\n
The regex definition
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/values.yaml$/\"],\n      \"matchStrings\": [\n        \"image:\\\\s+(?<depName>my\\\\.old\\\\.registry/aRepository/andImage):(?<currentValue>[^\\\\s]+)\"\n      ],\n      \"depNameTemplate\": \"my.new.registry/aRepository/andImage\",\n      \"autoReplaceStringTemplate\": \"image: {{{depName}}}:{{{newValue}}}\",\n      \"datasourceTemplate\": \"docker\"\n    }\n  ]\n}\n

This will lead to following update where 1.21-alpine is the newest version of my.new.registry/aRepository/andImage:

# The image of the service <registry>/<repo>/<image>:<tag>\nimage: my.new.registry/aRepository/andImage:1.21-alpine\n

Note

Can only be used with the custom regex manager.

"},{"location":"configuration-options/#custommanagerscurrentvaluetemplate","title":"customManagers.currentValueTemplate","text":"

Optional currentValue for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If the currentValue for a dependency is not captured with a named group then it can be defined in config using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#custommanagerscustomtype","title":"customManagers.customType","text":"

Custom manager to use. Valid only within a customManagers object.

Name Value type string allowedValues 
[\"jsonata\", \"regex\"]\n
parents customManagers default null

It specifies which custom manager to use. There are two available options: regex and jsonata.

Example:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/values.yaml$/\"],\n      \"matchStrings\": [\n        \"ENV .*?_VERSION=(?<currentValue>.*) # (?<datasource>.*?)/(?<depName>.*?)\\\\s\"\n      ]\n    }\n  ]\n}\n
Parsing a JSON file with a custom manager
{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"json\",\n      \"managerFilePatterns\": [\"/file.json/\"],\n      \"matchStrings\": [\n        \"packages.{ \\\"depName\\\": package, \\\"currentValue\\\": version }\"\n      ],\n      \"datasourceTemplate\": \"github-tags\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#custommanagersdatasourcetemplate","title":"customManagers.datasourceTemplate","text":"

Optional datasource for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If the datasource for a dependency is not captured with a named group, then it can be defined in config using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#custommanagersdepnametemplate","title":"customManagers.depNameTemplate","text":"

Optional depName for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If depName cannot be captured with a named capture group in matchString then it can be defined manually using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#custommanagersdeptypetemplate","title":"customManagers.depTypeTemplate","text":"

Optional depType for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If depType cannot be captured with a named capture group in matchString then it can be defined manually using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#custommanagersextractversiontemplate","title":"customManagers.extractVersionTemplate","text":"

Optional extractVersion for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If extractVersion cannot be captured with a named capture group in matchString, then it can be defined manually using this field. It will be compiled using Handlebars and the regex groups result. See extractVersion for how the value is used.

"},{"location":"configuration-options/#custommanagersfileformat","title":"customManagers.fileFormat","text":"

It specifies the syntax of the package file being managed by the custom JSONata manager.

Name Value type string allowedValues 
[\"json\", \"toml\", \"yaml\"]\n
parents customManagers requiredIf [object Object] default null

Note

Can only be used with the custom jsonata manager.

It specifies the syntax of the package file that's managed by the custom jsonata manager. This setting helps the system correctly parse and interpret the configuration file's contents.

Only the json, toml and yaml formats are supported. yaml files are parsed as multi document YAML files.

Parsing a JSON file with a custom manager
{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"json\",\n      \"managerFilePatterns\": [\"/.renovaterc/\"],\n      \"matchStrings\": [\n        \"packages.{ 'depName': package, 'currentValue': version }\"\n      ],\n      \"datasourceTemplate\": \"github-tags\"\n    }\n  ]\n}\n
Parsing a YAML file with a custom manager
{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"yaml\",\n      \"managerFilePatterns\": [\"/file.yml/\"],\n      \"matchStrings\": [\n        \"packages.{ 'depName': package, 'currentValue': version }\"\n      ],\n      \"datasourceTemplate\": \"github-tags\"\n    }\n  ]\n}\n
Parsing a TOML file with a custom manager
{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"toml\",\n      \"managerFilePatterns\": [\"/file.toml/\"],\n      \"matchStrings\": [\n        \"packages.{ 'depName': package, 'currentValue': version }\"\n      ],\n      \"datasourceTemplate\": \"github-tags\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#custommanagersmatchstrings","title":"customManagers.matchStrings","text":"

Queries to use. Valid only within bumpVersions or customManagers object. Templating is supported within bumpVersions only.

Name Value type array subType string parents customManagersbumpVersions supportsTemplating true default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

Each matchStrings must be one of the following:

  1. A valid regular expression, which may optionally include named capture groups (if using customType=regex)
  2. Or, a valid, escaped JSONata query (if using customType=json)

Example:

matchStrings with a valid regular expression
{\n  \"matchStrings\": [\n    \"ENV .*?_VERSION=(?<currentValue>.*) # (?<datasource>.*?)/(?<depName>.*?)\\\\s\"\n  ]\n}\n
matchStrings with a valid JSONata query
{\n  \"matchStrings\": [\n    \"packages.{ \\\"depName\\\": package, \\\"currentValue\\\": version }\"\n  ]\n}\n

Note

You do not need to add leading and trailing slashes in matchStrings.

"},{"location":"configuration-options/#custommanagersmatchstringsstrategy","title":"customManagers.matchStringsStrategy","text":"

Strategy how to interpret matchStrings.

Name Value type string default \"any\" allowedValues 
[\"any\", \"recursive\", \"combination\"]\n
parents customManagers

matchStringsStrategy controls behavior when multiple matchStrings values are provided. Three options are available:

Note

matchStringsStrategy can only be used in a custom regex manager config!

"},{"location":"configuration-options/#any","title":"any","text":"

Each provided matchString will be matched individually to the content of the packageFile. If a matchString has multiple matches in a file each will be interpreted as an independent dependency.

As example the following configuration will update all three lines in the Dockerfile.

renovate.json
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^Dockerfile$/\"],\n      \"matchStringsStrategy\": \"any\",\n      \"matchStrings\": [\n        \"ENV [A-Z]+_VERSION=(?<currentValue>.*) # (?<datasource>.*?)/(?<depName>.*?)(\\\\&versioning=(?<versioning>.*?))?\\\\s\",\n        \"FROM (?<depName>\\\\S*):(?<currentValue>\\\\S*)\"\n      ],\n      \"datasourceTemplate\": \"docker\"\n    }\n  ]\n}\n
Dockerfile
FROM amd64/ubuntu:24.04\nENV GRADLE_VERSION=6.2 # gradle-version/gradle&versioning=maven\nENV NODE_VERSION=10.19.0 # github-tags/nodejs/node&versioning=node\n
"},{"location":"configuration-options/#recursive","title":"recursive","text":"

If using recursive the matchStrings will be looped through and the full match of the last will define the range of the next one. This can be used to narrow down the search area to prevent multiple matches. But the recursive strategy still allows the matching of multiple dependencies as described below. All matches of the first matchStrings pattern are detected, then each of these matches will be used as basis for the input for the next matchStrings pattern, and so on. If the next matchStrings pattern has multiple matches then it will split again. This process will be followed as long there is a match plus a next matchingStrings pattern is available.

Matched groups will be available in subsequent matching layers.

This is an example how this can work. The first custom manager will only upgrade grafana/loki as looks for the backup key then looks for the test key and then uses this result for extraction of necessary attributes. But the second custom manager will upgrade both definitions as its first matchStrings matches both test keys.

renovate.json
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^example.json$/\"],\n      \"matchStringsStrategy\": \"recursive\",\n      \"matchStrings\": [\n        \"\\\"backup\\\":\\\\s*{[^}]*}\",\n        \"\\\"test\\\":\\\\s*\\\\{[^}]*}\",\n        \"\\\"name\\\":\\\\s*\\\"(?<depName>.*)\\\"[^\\\"]*\\\"type\\\":\\\\s*\\\"(?<datasource>.*)\\\"[^\\\"]*\\\"value\\\":\\\\s*\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"datasourceTemplate\": \"docker\"\n    },\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^example.json$/\"],\n      \"matchStringsStrategy\": \"recursive\",\n      \"matchStrings\": [\n        \"\\\"test\\\":\\\\s*\\\\{[^}]*}\",\n        \"\\\"name\\\":\\\\s*\\\"(?<depName>.*)\\\"[^\\\"]*\\\"type\\\":\\\\s*\\\"(?<datasource>.*)\\\"[^\\\"]*\\\"value\\\":\\\\s*\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"datasourceTemplate\": \"docker\"\n    }\n  ]\n}\n
example.json
{\n  \"backup\": {\n    \"test\": {\n      \"name\": \"grafana/loki\",\n      \"type\": \"docker\",\n      \"value\": \"1.6.1\"\n    }\n  },\n  \"setup\": {\n    \"test\": {\n      \"name\": \"python\",\n      \"type\": \"docker\",\n      \"value\": \"3.9.0\"\n    }\n  }\n}\n
"},{"location":"configuration-options/#combination","title":"combination","text":"

You may use this option to combine the values of multiple lines inside a file. You can combine multiple lines with matchStringStrategy values, but the combination approach is less susceptible to white space or line breaks stopping a match.

combination can only match one dependency per file. To update multiple dependencies with combination you must define multiple custom managers.

Matched group values will be merged to form a single dependency.

renovate.json
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^main.yml$/\"],\n      \"matchStringsStrategy\": \"combination\",\n      \"matchStrings\": [\n        \"prometheus_image:\\\\s*\\\"(?<depName>.*)\\\"\\\\s*//\",\n        \"prometheus_version:\\\\s*\\\"(?<currentValue>.*)\\\"\\\\s*//\"\n      ],\n      \"datasourceTemplate\": \"docker\"\n    },\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^main.yml$/\"],\n      \"matchStringsStrategy\": \"combination\",\n      \"matchStrings\": [\n        \"thanos_image:\\\\s*\\\"(?<depName>.*)\\\"\\\\s*//\",\n        \"thanos_version:\\\\s*\\\"(?<currentValue>.*)\\\"\\\\s*//\"\n      ],\n      \"datasourceTemplate\": \"docker\"\n    }\n  ]\n}\n
Ansible variable file (YAML)
prometheus_image: \"prom/prometheus\"  // a comment\nprometheus_version: \"v2.21.0\" // a comment\n------\nthanos_image: \"prom/prometheus\"  // a comment\nthanos_version: \"0.15.0\" // a comment\n

In the above example, each custom manager will match a single dependency each.

"},{"location":"configuration-options/#custommanagerspackagenametemplate","title":"customManagers.packageNameTemplate","text":"

Optional packageName for extracted dependencies, else defaults to depName value. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true previouslyKnownAs 
[\"lookupNameTemplate\"]\n
default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

packageName is used for looking up dependency versions. It will be compiled using Handlebars and the regex groups result. It will default to the value of depName if left unconfigured/undefined.

"},{"location":"configuration-options/#custommanagersregistryurltemplate","title":"customManagers.registryUrlTemplate","text":"

Optional registry URL for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If the registryUrls for a dependency is not captured with a named group then it can be defined in config using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#custommanagersversioningtemplate","title":"customManagers.versioningTemplate","text":"

Optional versioning for extracted dependencies. Valid only within a customManagers object.

Name Value type string parents customManagers supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

If the versioning for a dependency is not captured with a named group then it can be defined in config using this field. It will be compiled using Handlebars and the regex groups result.

"},{"location":"configuration-options/#customizedashboard","title":"customizeDashboard","text":"

Customize sections in the Dependency Dashboard issue.

Name Value scopes repo type object freeChoice true additionalProperties 
{\"type\": \"string\"}\n
cli --customize-dashboard env RENOVATE_CUSTOMIZE_DASHBOARD

You may use the customizeDashboard object to customize the Dependency Dashboard.

Supported fields:

"},{"location":"configuration-options/#defaultregistryurls","title":"defaultRegistryUrls","text":"

List of registry URLs to use as the default for a datasource.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type array subType string default []

Override a datasource's default registries with this config option. The datasources's customRegistrySupport value must be true for the config option to work.

Default registries are only used when both:

Think of defaultRegistryUrls as a way to specify the \"fallback\" registries for a datasource, for use when no registryUrls are extracted or configured. Compare that to registryUrls, which are a way to override registries.

"},{"location":"configuration-options/#dependencydashboard","title":"dependencyDashboard","text":"

Whether to create a \"Dependency Dashboard\" issue in the repository.

Name Value scopes repo type boolean default false cli --dependency-dashboard env RENOVATE_DEPENDENCY_DASHBOARD previouslyKnownAs 
[\"masterIssue\"]\n

Starting from version v26.0.0 the \"Dependency Dashboard\" is enabled by default as part of the commonly-used config:recommended preset.

To disable the Dependency Dashboard, add the preset :disableDependencyDashboard or set dependencyDashboard to false.

{\n  \"extends\": [\"config:recommended\", \":disableDependencyDashboard\"]\n}\n

Configuring dependencyDashboard to true will lead to the creation of a \"Dependency Dashboard\" issue within the repository. This issue has a list of all PRs pending, open, closed (unmerged) or in error. The goal of this issue is to give visibility into all updates that Renovate is managing.

Examples of what having a Dependency Dashboard will allow you to do:

Tip

Enabling the Dependency Dashboard by itself does not change the \"control flow\" of Renovate. Renovate still creates and manages PRs, and still follows your schedules and rate limits. The Dependency Dashboard gives you extra visibility and control over your updates.

"},{"location":"configuration-options/#dependencydashboardapproval","title":"dependencyDashboardApproval","text":"

Controls if updates need manual approval from the Dependency Dashboard issue before PRs are created.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --dependency-dashboard-approval env RENOVATE_DEPENDENCY_DASHBOARD_APPROVAL previouslyKnownAs 
[\"masterIssueApproval\"]\n

This feature allows you to use Renovate's Dependency Dashboard to force approval of updates before they are created.

By setting dependencyDashboardApproval to true in config (including within packageRules), you can tell Renovate to wait for your approval from the Dependency Dashboard before creating a branch/PR. You can approve a pending PR by selecting the checkbox in the Dependency Dashboard issue.

Tip

When you set dependencyDashboardApproval to true the Dependency Dashboard issue will be created automatically, you do not need to turn on dependencyDashboard explicitly.

You can configure Renovate to wait for approval for:

If you want to require approval for all upgrades, set dependencyDashboardApproval to true:

{\n  \"dependencyDashboardApproval\": true\n}\n

If you want to require approval for major updates, set dependencyDashboardApproval to true within a major object:

{\n  \"major\": {\n    \"dependencyDashboardApproval\": true\n  }\n}\n

If you want to approve specific packages, set dependencyDashboardApproval to true within a packageRules entry where you have defined a specific package or pattern.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"/^@package-name/\"],\n      \"dependencyDashboardApproval\": true\n    }\n  ]\n}\n
"},{"location":"configuration-options/#dependencydashboardautoclose","title":"dependencyDashboardAutoclose","text":"

Set to true to let Renovate close the Dependency Dashboard issue if there are no more updates.

Name Value scopes repo type boolean default false cli --dependency-dashboard-autoclose env RENOVATE_DEPENDENCY_DASHBOARD_AUTOCLOSE previouslyKnownAs 
[\"masterIssueAutoclose\"]\n

You can configure this to true if you prefer Renovate to close an existing Dependency Dashboard whenever there are no outstanding PRs left.

"},{"location":"configuration-options/#dependencydashboardcategory","title":"dependencyDashboardCategory","text":"

The category to group branches on the Dependency Dashboard issue.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string

You can use this to categorize updates on the Dependency Dashboard. For example, to visually distinguish between production and dev updates, or to split between teams or logical parts of a monorepo. In practice this means it introduces an extra level of hierarchy/heading in the Dashboard's markdown.

To create a category for all CI/CD updates, you can configure a package rule like this:

{\n  \"packageRules\": [\n    {\n      \"matchCategories\": [\"cd\", \"ci\"],\n      \"dependencyDashboardCategory\": \":hammer_and_wrench: Continuous Integration & Continuous Deployment\"\n    }\n  ]\n}\n

When you configure categories, updates that do not match any of the configured categories will be grouped under the \"Other\" category.

Some sections in the Dependency Dashboard also contain an action that applies to all updates in that section, such as to approve or rebase all updates. If there are categories in that section, the action will be put in an extra \"All\" category at the end of the section. This is to explicitly clarify that the action applies to all updates in the section, not to just a specific category.

The Dependency Dashboard categories are only used to visually organize updates within the Dependency Dashboard issue. They do not impact grouping of updates into a single update like how e.g. branchName and groupName do.

"},{"location":"configuration-options/#dependencydashboardfooter","title":"dependencyDashboardFooter","text":"

Any text added here will be placed last in the Dependency Dashboard issue body, with a divider separator before it.

Name Value scopes repo type string supportsTemplating true cli --dependency-dashboard-footer env RENOVATE_DEPENDENCY_DASHBOARD_FOOTER previouslyKnownAs 
[\"masterIssueFooter\"]\n
default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

"},{"location":"configuration-options/#dependencydashboardheader","title":"dependencyDashboardHeader","text":"

Any text added here will be placed first in the Dependency Dashboard issue body.

Name Value scopes repo type string default \"This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.\" supportsTemplating true cli --dependency-dashboard-header env RENOVATE_DEPENDENCY_DASHBOARD_HEADER previouslyKnownAs 
[\"masterIssueHeader\"]\n

This option supports Renovate's template syntax

See templates for available variables and helpers.

"},{"location":"configuration-options/#dependencydashboardlabels","title":"dependencyDashboardLabels","text":"

These labels will always be applied on the Dependency Dashboard issue, even when they have been removed manually.

Name Value scopes repo type array subType string cli --dependency-dashboard-labels env RENOVATE_DEPENDENCY_DASHBOARD_LABELS previouslyKnownAs 
[\"masterIssueLabels\"]\n
default []

The labels only get updated when the Dependency Dashboard issue updates its content and/or title. It is pointless to edit the labels, as Renovate restores the labels on each run.

"},{"location":"configuration-options/#dependencydashboardosvvulnerabilitysummary","title":"dependencyDashboardOSVVulnerabilitySummary","text":"

Control if the Dependency Dashboard issue lists CVEs supplied by osv.dev.

Name Value scopes repo type string allowedValues 
[\"none\", \"all\", \"unresolved\"]\n
default \"none\" cli --dependency-dashboard-o-s-v-vulnerability-summary env RENOVATE_DEPENDENCY_DASHBOARD_O_S_V_VULNERABILITY_SUMMARY

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Use this option to control if the Dependency Dashboard lists the OSV-sourced CVEs for your repository. You can choose from:

You will only get OSV-based vulnerability alerts for direct dependencies.

This feature is independent of the osvVulnerabilityAlerts option.

The source of these CVEs is OSV.dev.

"},{"location":"configuration-options/#dependencydashboardreportabandonment","title":"dependencyDashboardReportAbandonment","text":"

Controls whether abandoned packages are reported in the dependency dashboard.

Name Value scopes repo type boolean default true cli --dependency-dashboard-report-abandonment env RENOVATE_DEPENDENCY_DASHBOARD_REPORT_ABANDONMENT

Controls whether abandoned packages are reported in the dependency dashboard.

When enabled (default), Renovate will display a collapsible section in the dependency dashboard listing packages that have been identified as abandoned based on the abandonmentThreshold configuration. This helps you identify dependencies that may need attention due to lack of maintenance.

Set this to false if you prefer not to see abandoned packages in your dependency dashboard.

"},{"location":"configuration-options/#dependencydashboardtitle","title":"dependencyDashboardTitle","text":"

Title for the Dependency Dashboard issue.

Name Value scopes repo type string default \"Dependency Dashboard\" cli --dependency-dashboard-title env RENOVATE_DEPENDENCY_DASHBOARD_TITLE previouslyKnownAs 
[\"masterIssueTitle\"]\n

Configure this option if you prefer a different title for the Dependency Dashboard.

"},{"location":"configuration-options/#description","title":"description","text":"

Plain text description for a config or preset.

Name Value scopes any type array subType string mergeable true default []

The description field can be used inside any configuration object to add a human-readable description of the object's config purpose. A description field embedded within a preset is also collated as part of the onboarding description unless the preset only consists of presets itself. Presets which consist only of other presets have their own description omitted from the onboarding description because they will be fully described by the preset descriptions within.

[!NOTE] To overwrite descriptions of child presets, use overrideDescription in place of description.

"},{"location":"configuration-options/#digest","title":"digest","text":"

Configuration to apply when updating a digest (no change in tag/version).

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"branchTopic\": \"{{{depNameSanitized}}}-digest\",\n  \"commitMessageExtra\": \"to {{newDigestShort}}\",\n  \"commitMessageTopic\": \"{{{depName}}} digest\"\n}\n
mergeable true env RENOVATE_DIGEST

Add to this object if you wish to define rules that apply only to PRs that update digests.

"},{"location":"configuration-options/#draftpr","title":"draftPR","text":"

If set to true then Renovate creates draft PRs, instead of normal status PRs.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms azure, bitbucket, forgejo, gitea, github, gitlab, scm-manager cli --draft-p-r env RENOVATE_DRAFT_P_R

If you want the PRs created by Renovate to be considered as drafts rather than normal PRs, you could add this property to your renovate.json:

{\n  \"draftPR\": true\n}\n

This option is evaluated at PR/MR creation time.

Note

Forgejo, Gitea and GitLab implement draft status by checking if the PR's title starts with certain strings. This means that draftPR on Forgejo, Gitea and GitLab are incompatible with the legacy method of triggering Renovate to rebase a PR by renaming the PR to start with rebase!.

"},{"location":"configuration-options/#enabled","title":"enabled","text":"

Enable or disable corresponding functionality.

Name Value type boolean default true scopes repo, packageRule, manager, updateType parents vulnerabilityAlertshostRules cli --enabled env RENOVATE_ENABLED

The most common use of enabled is if you want to turn Renovate's functionality off, for some reason.

For example, if you wanted to disable Renovate completely on a repository, you could make this your renovate.json:

{\n  \"enabled\": false\n}\n

Note

When Renovate is disabled on a repository entirely (via enabled=false), if Renovate runs against the repo again, it will perform a one-time cleanup of the repository, closing open Issues, PRs and deleting any branches.

To disable Renovate for all eslint packages, you can configure a package rule like:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"eslint**\"],\n      \"enabled\": false\n    }\n  ]\n}\n

To disable Renovate for npm devDependencies but keep it for dependencies you could configure:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"npm\"],\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"configuration-options/#enabledmanagers","title":"enabledManagers","text":"

A list of package managers to enable. Only managers on the list are enabled.

Name Value scopes repo type array subType string allowedValues 
[\n  \"ansible\",\n  \"ansible-galaxy\",\n  \"ant\",\n  \"apm\",\n  \"argocd\",\n  \"asdf\",\n  \"azure-pipelines\",\n  \"batect\",\n  \"batect-wrapper\",\n  \"bazel\",\n  \"bazel-module\",\n  \"bazelisk\",\n  \"bicep\",\n  \"bitbucket-pipelines\",\n  \"bitrise\",\n  \"buildkite\",\n  \"buildpacks\",\n  \"bun\",\n  \"bun-version\",\n  \"bundler\",\n  \"cake\",\n  \"cargo\",\n  \"cdnurl\",\n  \"circleci\",\n  \"cloudbuild\",\n  \"cocoapods\",\n  \"composer\",\n  \"conan\",\n  \"copier\",\n  \"cpanfile\",\n  \"crossplane\",\n  \"crow\",\n  \"deno\",\n  \"deps-edn\",\n  \"devbox\",\n  \"devcontainer\",\n  \"docker-compose\",\n  \"dockerfile\",\n  \"droneci\",\n  \"fleet\",\n  \"flux\",\n  \"fvm\",\n  \"git-submodules\",\n  \"github-actions\",\n  \"gitlabci\",\n  \"gitlabci-include\",\n  \"glasskube\",\n  \"gleam\",\n  \"gomod\",\n  \"gradle\",\n  \"gradle-wrapper\",\n  \"haskell-cabal\",\n  \"helm-requirements\",\n  \"helm-values\",\n  \"helmfile\",\n  \"helmsman\",\n  \"helmv3\",\n  \"hermit\",\n  \"homeassistant-manifest\",\n  \"homebrew\",\n  \"html\",\n  \"jenkins\",\n  \"jsonnet-bundler\",\n  \"kotlin-script\",\n  \"kubernetes\",\n  \"kustomize\",\n  \"leiningen\",\n  \"maven\",\n  \"maven-wrapper\",\n  \"meteor\",\n  \"mint\",\n  \"mise\",\n  \"mix\",\n  \"nix\",\n  \"nodenv\",\n  \"npm\",\n  \"nuget\",\n  \"nvm\",\n  \"ocb\",\n  \"osgi\",\n  \"paket\",\n  \"pep621\",\n  \"pep723\",\n  \"pip-compile\",\n  \"pip_requirements\",\n  \"pip_setup\",\n  \"pipenv\",\n  \"pixi\",\n  \"poetry\",\n  \"pre-commit\",\n  \"proto\",\n  \"pub\",\n  \"puppet\",\n  \"pyenv\",\n  \"quadlet\",\n  \"renovate-config\",\n  \"ruby-version\",\n  \"runtime-version\",\n  \"rust-toolchain\",\n  \"sbt\",\n  \"scalafmt\",\n  \"setup-cfg\",\n  \"smithy\",\n  \"sveltos\",\n  \"swift\",\n  \"tekton\",\n  \"terraform\",\n  \"terraform-version\",\n  \"terragrunt\",\n  \"terragrunt-version\",\n  \"tflint-plugin\",\n  \"travis\",\n  \"typst\",\n  \"unity3d\",\n  \"velaci\",\n  \"vendir\",\n  \"woodpecker\",\n  \"xcodegen\",\n  \"jsonata\",\n  \"regex\",\n  \"custom.jsonata\",\n  \"custom.regex\"\n]\n
mergeable false cli --enabled-managers env RENOVATE_ENABLED_MANAGERS default []

This is a way to allow only certain package managers and implicitly disable all others.

Example:

{\n  \"enabledManagers\": [\"dockerfile\", \"npm\"]\n}\n

To enable custom managers you will need to add custom. prefix before their names

Example:

{\n  \"enabledManagers\": [\"custom.regex\"]\n}\n

For the full list of available managers, see the Supported Managers documentation.

"},{"location":"configuration-options/#encrypted","title":"encrypted","text":"

An object containing configuration encrypted with project key.

Name Value scopes any type object additionalProperties 
{\"type\": \"string\"}\n
cli --encrypted env RENOVATE_ENCRYPTED

Before you put any secrets in your repository configuration, encrypt the secrets. You can encrypt secrets using either a HTML page, or the CLI.

To encrypt secrets for the Mend Renovate App for github.com with a HTML page, go to app.renovatebot.com/encrypt and complete the form. If you're self-hosting Renovate, you may download and edit the form, to use your own PGP public key.

You can also encrypt secrets from the CLI, using the curl, echo, jq, gpg, grep and tr CLI programs. Here is an example:

curl https://app.renovatebot.com/renovate.pgp --output renovate.pgp\necho -n '{\"o\":\"your-organization\", \"r\":\"your-repository (optional)\", \"v\":\"your-secret-value\"}' | jq . -c | gpg --encrypt -a --recipient-file renovate.pgp | grep -v '^----' | tr -d '\\n'\n

The above script uses:

The jq step is optional, you can leave it out if you wish. Its primary value is validating that the string you echo to gpg is valid JSON, and compact.

Note

Encrypted secrets must have at least an org/group scope, and optionally a repository scope. This means that Renovate will check if a secret's scope matches the current repository before applying it, and warn/discard if there is a mismatch.

Encrypted secrets usually have a single organization. But you may encrypt a secret with more than one organization, for example: org1,org2. This way the secret can be used in both the org1 and org2 organizations.

For more information on how to use secrets for private packages, read Private package support.

"},{"location":"configuration-options/#env","title":"env","text":"

Environment variables that Renovate uses when executing package manager commands.

Name Value scopes repo type object additionalProperties 
{\"type\": \"string\"}\n
cli --env env RENOVATE_ENV

This option allows users to specify explicit environment variables values. It is valid only as a top-level configuration option and not, for example, within packageRules.

Warning

The administrator of your Renovate deployment must configure a list of allowed environment names in the allowedEnv config option, before users can use those allowed names in the env option.

Behavior:

Example renovate.json with env configuration
{\n  \"env\": {\n    \"SOME_ENV_VARIABLE\": \"SOME_STRING_VALUE\"\n  }\n}\n
"},{"location":"configuration-options/#excludecommitpaths","title":"excludeCommitPaths","text":"

A file matching any of these glob patterns will not be committed, even if the file has been updated.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --exclude-commit-paths env RENOVATE_EXCLUDE_COMMIT_PATHS default []

Warning

For advanced use only! Use at your own risk!

Be careful you know what you're doing with this option. The initial intended use is to allow the user to exclude certain dependencies from being added/removed/modified when \"vendoring\" dependencies. Example:

{\n  \"excludeCommitPaths\": [\"vendor/golang.org/x/text/**\"]\n}\n

The above would mean Renovate would not include files matching the above glob pattern in the commit, even if it thinks they should be updated.

"},{"location":"configuration-options/#expandcodeownersgroups","title":"expandCodeOwnersGroups","text":"

Expand the configured code owner groups into a full list of group members.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms gitlab cli --expand-code-owners-groups env RENOVATE_EXPAND_CODE_OWNERS_GROUPS

If configured, Renovate will expand any matching CODEOWNERS groups into a full list of group members and assign them individually instead of the group. This is particularly useful when combined with assigneesSampleSize and assigneesFromCodeOwners, so that only a subset of the Codeowners are assigned instead of the whole group.

On GitLab, this also expands role handles (@@developer, @@maintainer, @@owner) into the project members who hold that exact role.

"},{"location":"configuration-options/#extends","title":"extends","text":"

Configuration presets to use or extend.

Name Value scopes any type array subType string env RENOVATE_EXTENDS default []

See shareable config presets for details. Learn how to use presets by reading the Key concepts, Presets page.

"},{"location":"configuration-options/#extractversion","title":"extractVersion","text":"

A regex (re2) to extract a version from a datasource's raw version string.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string format regex default null

Only use this config option when the raw version strings from the datasource do not match the expected format that you need in your package file. You must define a \"named capture group\" called version like in the examples below.

extractVersion is only applied to the versions returned by the datasource. It is not applied to the currentValue from your package file, so currentValue must already be in the extracted format.

For example, to extract only the major.minor precision from a GitHub release, the following would work:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"foo\"],\n      \"extractVersion\": \"^(?<version>v\\\\d+\\\\.\\\\d+)\"\n    }\n  ]\n}\n

The above will change a raw version of v1.31.5 to v1.31, for example.

Alternatively, to strip a release- prefix:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"bar\"],\n      \"extractVersion\": \"^release-(?<version>.*)$\"\n    }\n  ]\n}\n

The above will change a raw version of release-2.0.0 to 2.0.0, for example. A similar one could strip leading v prefixes:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"baz\"],\n      \"extractVersion\": \"^v(?<version>.*)$\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#fetchchangelogs","title":"fetchChangeLogs","text":"

Controls if and when changelogs/release notes are fetched.

Name Value type string allowedValues 
[\"off\", \"branch\", \"pr\"]\n
default \"pr\" parents packageRules(the root document) env RENOVATE_FETCH_CHANGE_LOGS

Use this config option to configure changelogs/release notes fetching. The available options are:

Avoid setting fetchChangeLogs=branch, because this slows down Renovate. But if you're embedding changelogs in commit information, you may use fetchChangeLogs=branch.

Renovate can fetch changelogs when they are hosted on one of these platforms:

If you are running on any platform except github.com, you need to configure a Personal Access Token to allow Renovate to fetch changelogs notes from github.com.

You may use package rules to override the value of fetchChangeLogs for matching dependencies, with later rules overriding earlier ones.

The following re-enables fetching of changelogs when creating pull-requests for lodash updates.

{\n  \"fetchChangeLogs\": \"off\",\n  \"packageRules\": [\n    {\n      \"matchSourceUrls\": [\"https://github.com/lodash/lodash\"],\n      \"fetchChangeLogs\": \"pr\"\n    }\n  ]\n}\n

The following disables fetching of changelogs for any package in aws-sdk-go-v2, which can be time-consuming due to the repository's large number of tags:

{\n  \"packageRules\": [\n    {\n      \"matchSourceUrls\": [\"https://github.com/aws/aws-sdk-go-v2{/**,}\"],\n      \"fetchChangeLogs\": \"off\"\n    }\n  ]\n}\n

Note

Renovate can only show changelogs from some platforms and some package managers. We're planning improvements so that Renovate can show more changelogs. Read issue 14138 on GitHub to get an overview of the planned work.

"},{"location":"configuration-options/#filterunavailableusers","title":"filterUnavailableUsers","text":"

Filter reviewers and assignees based on their availability.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms gitlab cli --filter-unavailable-users env RENOVATE_FILTER_UNAVAILABLE_USERS

When this option is enabled PRs are not assigned to users that are unavailable. This option only works on platforms that support the concept of user availability. For now, you can only use this option on the GitLab platform.

"},{"location":"configuration-options/#followtag","title":"followTag","text":"

If defined, packages will follow this release tag exactly.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string default null

Warning

For advanced use only! Use at your own risk!

For followTag to work, the datasource must support distribution streams or tags, like for example npm does.

The main use case is to follow a pre-release tag of a dependency, say TypeScripts's \"insiders\" build:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"typescript\"],\n      \"followTag\": \"insiders\"\n    }\n  ]\n}\n

If you've set a followTag then Renovate skips its normal major/minor/patch upgrade logic and stable/unstable consistency logic, and instead keeps your dependency version synced strictly to the version in the tag.

Renovate follows tags strictly, this can cause problems when a tagged stream is no longer maintained. For example: you're following the next tag, but later the stream you actually want is called stable instead. If next is no longer getting updates, you must switch your followTag to stable to get updates again.

"},{"location":"configuration-options/#forkmodedisallowmaintaineredits","title":"forkModeDisallowMaintainerEdits","text":"

Disallow maintainers to push to Renovate pull requests when running in fork mode.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false supportedPlatforms github cli --fork-mode-disallow-maintainer-edits env RENOVATE_FORK_MODE_DISALLOW_MAINTAINER_EDITS

Use forkModeDisallowMaintainerEdits to disallow maintainers from editing Renovate's pull requests when in fork mode.

If GitHub pull requests are created from a fork repository, the PR author can decide to allow upstream repository to modify the PR directly.

Allowing maintainers to edit pull requests directly is helpful when Renovate pull requests require more changes. The reviewer can simply push to the pull request without having to create a new PR. More details here.

You may decide to disallow edits to Renovate pull requests in order to workaround issues in Renovate where modified fork branches are not deleted properly: See this issue. If this option is enabled, reviewers will need to create a new PR if more changes are needed.

Note

This option is only relevant if you set forkToken.

"},{"location":"configuration-options/#forkprocessing","title":"forkProcessing","text":"

Whether to process forked repositories. By default, all forked repositories are skipped when in autodiscover mode.

Name Value scopes repo type string allowedValues 
[\"auto\", \"enabled\", \"disabled\"]\n
default \"auto\" cli --fork-processing env RENOVATE_FORK_PROCESSING

By default, Renovate skips any forked repositories when in autodiscover mode. It even skips a forked repository that has a Renovate configuration file, because Renovate doesn't know if that file was added by the forked repository.

Process a fork in autodiscover mode

If you want Renovate to run on a forked repository when in autodiscover mode then:

Process a fork in other modes

If you're running Renovate in some other mode, for example when giving a list of repositories to Renovate, but want to skip forked repositories: set \"forkProcessing\": \"disabled\" in your global config.

When using the Mend Renovate App

The behavior of forkProcessing depends on how you allow Renovate to run on your account.

Renovate runs on all repositories

If you allow Renovate to run on all your repositories, forkProcessing will be \"disabled\". To run Renovate on a fork: add \"forkProcessing\": \"enabled\" to the forked repository's renovate.json file.

Renovate runs on selected repositories

If you allow Renovate to run on \"Selected\" repositories, forkProcessing will be \"enabled\" for each \"Selected\" repository.

Allowed filenames

Only the onboardingConfigFileName (which defaults to renovate.json) is supported for forkProcessing. You can't use other filenames because Renovate only checks the default filename when using the Git-hosting platform's API.

"},{"location":"configuration-options/#gitauthor","title":"gitAuthor","text":"

Author to use for Git commits. Must conform to RFC5322.

Name Value scopes repo type string supportsTemplating true cli --git-author env RENOVATE_GIT_AUTHOR default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

You can customize the Git author that's used whenever Renovate creates a commit, although we do not recommend this. When this field is unset (default), Renovate will use its platform credentials (e.g. token) to learn/discover its account's git author automatically.

Note

If running as a GitHub App and using platformCommit, GitHub itself sets the git author in commits so you should not configure this field.

The gitAuthor option accepts a RFC5322-compliant string. It's recommended to include a name followed by an email address, e.g.

Development Bot <dev-bot@my-software-company.com>\n

Danger

We strongly recommend that the Git author email you use is unique to Renovate. Otherwise, if another bot or human shares the same email and pushes to one of Renovate's branches then Renovate will mistake the branch as unmodified and potentially force push over the changes.

"},{"location":"configuration-options/#gitignoredauthors","title":"gitIgnoredAuthors","text":"

Git author emails ignored by Renovate. Entries can be exact RFC5322 strings, glob patterns, or regex patterns using Renovate regex syntax.

Name Value scopes repo type array subType string cli --git-ignored-authors env RENOVATE_GIT_IGNORED_AUTHORS default []

Specify commit author emails ignored by Renovate.

By default, Renovate will treat any PR as modified if another Git author has added to the branch. When a PR is considered modified, Renovate won't perform any further commits such as if it's conflicted or needs a version update. If you have other bots which commit on top of Renovate PRs, and don't want Renovate to treat these PRs as modified, then add the other Git author(s) to gitIgnoredAuthors.

{\n  \"gitIgnoredAuthors\": [\"some-bot@example.org\"]\n}\n

gitIgnoredAuthors values can be exact RFC5322-compliant email strings, glob patterns, or regex patterns. For more details on the syntax and supported patterns, see Renovate's string pattern matching documentation.

"},{"location":"configuration-options/#gitlabignoreapprovals","title":"gitLabIgnoreApprovals","text":"

Ignore approval rules for MRs created by Renovate, which is useful for automerge.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --git-lab-ignore-approvals env RENOVATE_GIT_LAB_IGNORE_APPROVALS

Ignore the default project level approval(s), so that Renovate can automerge its merge requests, without needing approval(s). Under the hood, it creates a MR-level approval rule where approvals_required is set to 0. This option works only when automerge=true and either automergeType=pr or automergeType=branch. Also, approval rules overriding should not be prevented in GitLab settings.

"},{"location":"configuration-options/#gogetdirs","title":"goGetDirs","text":"

Directory pattern to run go get on.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string default 
[\"./...\"]\n
supportedManagers gomod cli --go-get-dirs env RENOVATE_GO_GET_DIRS

By default, Renovate will run go get -d -t ./... to update the go.sum. If you need to modify this path, for example in order to ignore directories, you can override the default ./... value using this option:

{\n  \"goGetDirs\": [\"./some-project/\", \"./tools/...\"]\n}\n
"},{"location":"configuration-options/#group","title":"group","text":"

Config if groupName is enabled.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object default 
{\"branchTopic\": \"{{{groupSlug}}}\", \"commitMessageTopic\": \"{{{groupName}}}\"}\n
mergeable true

Warning

For advanced use only! Use at your own risk!

The default configuration for groups are essentially internal to Renovate and you normally shouldn't need to modify them. But you may add settings to any group by defining your own group configuration object.

"},{"location":"configuration-options/#groupname","title":"groupName","text":"

Human understandable name for the dependency group.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true cli --group-name env RENOVATE_GROUP_NAME

This option supports Renovate's template syntax

See templates for available variables and helpers.

There are multiple cases where it can be useful to group multiple upgrades together. Internally Renovate uses this for branches such as \"Pin Dependencies\", \"Lock File Maintenance\", etc. Another example used previously is to group together all related eslint packages, or perhaps angular or babel. To enable grouping, you configure the groupName field to something non-null.

The groupName field allows free text and does not have any semantic interpretation by Renovate. All updates sharing the same groupName will be placed into the same branch/PR. For example, to group all non-major devDependencies updates together into a single PR:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"matchUpdateTypes\": [\"patch\", \"minor\"],\n      \"groupName\": \"devDependencies (non-major)\"\n    }\n  ]\n}\n

Note

Replacement updates will never be grouped. Lock file maintenance will never be grouped with other dependency updates.

"},{"location":"configuration-options/#groupsingleupdates","title":"groupSingleUpdates","text":"

Apply group settings even when the group contains only one update.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false

Note

This option was recently made opt-in, instead of opt-out.

"},{"location":"configuration-options/#groupslug","title":"groupSlug","text":"

Slug to use for group (e.g. in branch name). Slug is calculated from groupName if null.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true

This option supports Renovate's template syntax

See templates for available variables and helpers.

By default, Renovate will \"slugify\" the groupName to determine the branch name. For example if you named your group \"devDependencies (non-major)\" then the branchName would be renovate/devdependencies-non-major. If you wished to override this then you could configure like this:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"matchUpdateTypes\": [\"patch\", \"minor\"],\n      \"groupName\": \"devDependencies (non-major)\",\n      \"groupSlug\": \"dev-dependencies\"\n    }\n  ]\n}\n

As a result of the above, the branchName would be renovate/dev-dependencies instead.

Note

You shouldn't usually need to configure this unless you really care about your branch names.

"},{"location":"configuration-options/#hashedbranchlength","title":"hashedBranchLength","text":"

If enabled, branch names will use a hashing function to ensure each branch has that length.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer env RENOVATE_HASHED_BRANCH_LENGTH

Some code hosting systems have restrictions on the branch name lengths, this option lets you get around these restrictions. You can set the hashedBranchLength option to a number of characters that works for your system and then Renovate will generate branch names with the correct length by hashing additionalBranchPrefix and branchTopic, and then truncating the hash so that the full branch name (including branchPrefix) has the right number of characters.

Example: If you have set branchPrefix: \"deps-\" and hashedBranchLength: 12 it will result in a branch name like deps-5bf36ec instead of the traditional pretty branch name like deps-react-17.x.

"},{"location":"configuration-options/#hostrules","title":"hostRules","text":"

Host rules/configuration including credentials.

Name Value scopes repo type array subType object cli --host-rules mergeable true env RENOVATE_HOST_RULES previouslyKnownAs 
[\"endpoints\"]\n
default []

The primary purpose of hostRules is to configure credentials for host authentication. You tell Renovate how to match against the host you need authenticated, and then you also tell it which credentials to use.

The lookup keys for hostRules are: hostType and matchHost, both of which are optional.

Supported credential fields are token, username, password, timeout, enabled and insecureRegistry.

Example for configuring docker auth:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"docker.io\",\n      \"username\": \"<some-username>\",\n      \"password\": \"<some-password>\"\n    }\n  ]\n}\n

If multiple hostRules match a request, then they will be applied in the following order/priority:

  1. rules with only hostType specified
  2. rules with only matchHost specified (sorted by matchHost length if multiple match)
  3. rules with both matchHost and hostType specified (sorted by matchHost length if multiple match)

To disable requests to a particular host, you can configure a rule like:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"registry.npmjs.org\",\n      \"enabled\": false\n    }\n  ]\n}\n

A preset alternative to the above is:

{\n  \"extends\": [\":disableHost(registry.npmjs.org)\"]\n}\n

To match a specific port, add the port to matchHost:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://domain.com:9118\",\n      \"enabled\": false\n    }\n  ]\n}\n

Note

A matchHost with a port or a path but no scheme, like domain.com:9118 or domain.com/path, is treated as https://domain.com:9118 or https://domain.com/path. To match a port over plain http, include the scheme.

Note

Disabling a host is only 100% effective if added to self-hosted config. Renovate currently still checks its cache for results first before trying to connect, so if a public host is blocked in your repository config (e.g. renovate.json) then it's possible you may get cached results from that host if another repository using the same Renovate deployment has successfully queried for the same dependency recently.

Note

enabled is not resolved by specificity alone: host rules from the self-hosted administrator's own config are resolved at a higher trust level than those from repository config or a preset. So if the administrator's own rules set enabled for a host, repository config or a preset cannot re-enable - or disable - that host, no matter how specific its matchHost is.

"},{"location":"configuration-options/#hostrulesabortignorestatuscodes","title":"hostRules.abortIgnoreStatusCodes","text":"

A list of HTTP status codes safe to ignore even when abortOnError=true.

Name Value type array subType number parents hostRules default []

This field can be used to configure status codes that Renovate ignores and passes through when abortOnError is set to true. For example to also skip 404 responses then configure the following:

{\n  \"hostRules\": [\n    {\n      \"abortOnError\": true,\n      \"abortIgnoreStatusCodes\": [404]\n    }\n  ]\n}\n

Tip

This field is not mergeable, so the last-applied host rule takes precedence.

"},{"location":"configuration-options/#hostrulesabortonerror","title":"hostRules.abortOnError","text":"

If enabled, Renovate aborts its run when HTTP request errors occur.

Name Value type boolean default false parents hostRules

Use this field to configure Renovate to abort runs for custom hosts. By default, Renovate will only abort for known public hosts, which has the downside that transient errors for other hosts can cause autoclosing of PRs.

To abort Renovate runs for HTTP failures from any host:

{\n  \"hostRules\": [\n    {\n      \"abortOnError\": true\n    }\n  ]\n}\n

To abort Renovate runs for any docker datasource failures:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"docker\",\n      \"abortOnError\": true\n    }\n  ]\n}\n

To abort Renovate for errors for a specific docker host:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"docker.company.com\",\n      \"abortOnError\": true\n    }\n  ]\n}\n

When this field is enabled, Renovate will abort its run if it encounters either (a) any low-level http error (e.g. ETIMEDOUT) or (b) gets a response not matching any of the configured abortIgnoreStatusCodes (e.g. 500 Internal Error);

"},{"location":"configuration-options/#hostrulesartifactauth","title":"hostRules.artifactAuth","text":"

A list of package managers to enable artifact auth. Only managers on the list are enabled. All are enabled if null.

Name Value type array subType string parents hostRules allowedValues 
[\"composer\"]\n
default []

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

You may use this field whenever it is needed to only enable authentication for a specific set of managers.

For example, using this option could be used whenever authentication using Git for private composer packages is already being handled through the use of SSH keys, which results in no need for also setting up authentication using tokens.

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"gitlab\",\n      \"matchHost\": \"gitlab.myorg.com\",\n      \"token\": \"abc123\",\n      \"artifactAuth\": [\"composer\"]\n    }\n  ]\n}\n

Supported artifactAuth and hostType combinations:

artifactAuth hostTypes composer gitlab, packagist, github, git-tags"},{"location":"configuration-options/#hostrulesauthtype","title":"hostRules.authType","text":"

Authentication type for HTTP header. e.g. \"Bearer\" or \"Basic\". Use \"Token-Only\" to use only the token without an authorization type.

Name Value type string parents hostRules default \"Bearer\"

You may use the authType option to create a custom HTTP authorization header. For authType to work, you must also set your own token.

Do not set authType=Bearer: it's the default setting for Renovate anyway. Do not set a username or password when you're using authType, as authType doesn't use usernames or passwords.

An example for npm basic auth with token:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"npm.custom.org\",\n      \"token\": \"<some-token>\",\n      \"authType\": \"Basic\"\n    }\n  ]\n}\n

This will generate the following header: authorization: Basic <some-token>.

To use a bare token in the authorization header (required by e.g. Hex) - use the authType \"Token-Only\":

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://hex.pm/api/repos/private_repo/\",\n      \"token\": \"<some-token>\",\n      \"authType\": \"Token-Only\"\n    }\n  ]\n}\n

This will generate the header authorization: <some-token>.

"},{"location":"configuration-options/#hostrulesconcurrentrequestlimit","title":"hostRules.concurrentRequestLimit","text":"

Limit concurrent requests per host.

Name Value type integer parents hostRules

Usually the default setting is fine, but you can use concurrentRequestLimit to limit the number of concurrent outstanding requests. You only need to adjust this setting if a datasource is rate limiting Renovate or has problems with the load. The limit will be set for any host it applies to.

Example config:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"api.github.com\",\n      \"concurrentRequestLimit\": 2\n    }\n  ]\n}\n

Use an exact host for matchHost and not a domain (e.g. api.github.com as shown above and not github.com). Do not combine with hostType in the same rule or it won't work.

"},{"location":"configuration-options/#hostrulesdnscache","title":"hostRules.dnsCache","text":"

Enable got DNS cache.

Name Value type boolean default false parents hostRules

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

This feature has been deprecated

This option is deprecated and will be removed in a future release.

This option is deprecated and has no effect. Renovate removed its DNS cache in v38.0.0.

"},{"location":"configuration-options/#hostrulesenablehttp2","title":"hostRules.enableHttp2","text":"

Enable got HTTP/2 support.

Name Value type boolean default false parents hostRules

Enable got http2 support.

"},{"location":"configuration-options/#hostrulesheaders","title":"hostRules.headers","text":"

Put fields to be forwarded to the HTTP request headers in the headers config option.

Name Value type object additionalProperties 
{\"type\": \"string\"}\n
parents hostRules

Warning

For advanced use only! Use at your own risk!

You can provide a headers object that includes fields to be forwarded to the HTTP request headers. By default, all headers starting with \"X-\" are allowed.

A self-hosted administrator may configure an override for allowedHeaders to configure more permitted headers.

headers you configure in a repository config file, or a preset it extends, are checked against allowedHeaders. Any header which is not permitted is dropped, and a warning is logged.

allowedHeaders does not constrain the self-hosted administrator's own hostRules (for example in a config.js file, or a repositories[] entry): their headers are always applied, regardless of allowedHeaders.

When more than one of your host rules matches a request, the headers of the most specific matching rule are used, and replace the headers of the broader rules it matched alongside.

A self-hosted administrator's own host rules are resolved the same way, and whichever headers that leaves them sending to the host are then applied on top of yours:

This covers the headers the administrator actually sends to that host. One they set in a broader rule of their own, but masked with a narrower rule of their own, is not sent there - and so is yours to set.

For example:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://domain.com/all-versions\",\n      \"headers\": {\n        \"X-custom-header\": \"secret\"\n      }\n    }\n  ]\n}\n
"},{"location":"configuration-options/#hostruleshosttype","title":"hostRules.hostType","text":"

hostType for a package rule. Can be a platform name or a datasource name.

Name Value type string parents hostRules default null

hostType is another way to filter rules and can be either a platform such as github and bitbucket-server, or it can be a datasource such as docker and rubygems. You usually don't need to configure it in a host rule if you have already configured matchHost and only one host type is in use for those, as is usually the case. hostType can help for cases like an enterprise registry that serves multiple package types and has different authentication for each, although it's often the case that multiple matchHost rules could achieve the same thing.

"},{"location":"configuration-options/#hostruleshttpscertificate","title":"hostRules.httpsCertificate","text":"

The certificate chains in PEM format.

Name Value type string parents hostRules

Specifies the Certificate chains in PEM format for mTLS authentication.

"},{"location":"configuration-options/#hostruleshttpscertificateauthority","title":"hostRules.httpsCertificateAuthority","text":"

The overriding trusted CA certificate.

Name Value type string parents hostRules

By default, Renovate uses the curated list of well-known CAs by Mozilla. You may use another Certificate Authority instead, by setting it in the httpsCertificateAuthority config option.

"},{"location":"configuration-options/#hostruleshttpsprivatekey","title":"hostRules.httpsPrivateKey","text":"

The private key in PEM format.

Name Value type string parents hostRules

Specifies the private key in PEM format for mTLS authentication.

Warning

Do not put your private key into this field, to avoid losing confidentiality completely. You must use secrets to pass it down securely instead.

"},{"location":"configuration-options/#hostrulesinsecureregistry","title":"hostRules.insecureRegistry","text":"

Explicitly turn on insecure Docker registry access (HTTP).

Name Value type boolean default false parents hostRules

Warning

For advanced use only! Use at your own risk!

Enable this option to allow Renovate to connect to an insecure Docker registry that is HTTP only. This is insecure and is not recommended.

Example:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"reg.insecure.com\",\n      \"insecureRegistry\": true\n    }\n  ]\n}\n
"},{"location":"configuration-options/#hostruleskeepalive","title":"hostRules.keepAlive","text":"

Enable HTTP keep-alive for hosts.

Name Value type boolean default false parents hostRules previouslyKnownAs 
[\"keepalive\"]\n

Warning

For advanced use only! Use at your own risk!

If enabled, this allows a single TCP connection to remain open for multiple HTTP(S) requests/responses.

"},{"location":"configuration-options/#hostrulesmatchhost","title":"hostRules.matchHost","text":"

A domain name, host name or base URL to match against.

Name Value type string parents hostRules default null

This can be a base URL (e.g. https://api.github.com) or a hostname like github.com or api.github.com. If the value starts with http(s) then it will only match against URLs which start with the full base URL. Otherwise, it will be matched by checking if the URL's hostname matches the matchHost directly or ends with it. When checking the end of the hostname, a single dot is prefixed to the value of matchHost, if one is not already present, to ensure it can only match against whole domain segments.

A base URL ending in / (e.g. https://gitlab.com/api/v4/projects/1/) matches that path and everything below it, also when the URL has no trailing /, but not a sibling path like https://gitlab.com/api/v4/projects/10.

The matchHost URL must be the same as the registryUrl set in .npmrc, or you'll get authentication issues when the artifacts are updated when yarn or npm runs.

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://gitlab.myorg.com/api/v4/packages/npm/\",\n      \"token\": \"abc123\"\n    }\n  ]\n}\n

The above corresponds with an .npmrc like the following:

registry=https://gitlab.myorg.com/api/v4/packages/npm/\n

Note

Values containing a URL path or a port but missing a scheme will be prepended with https:// (e.g. domain.com/path \u2192 https://domain.com/path, domain.com:9118 \u2192 https://domain.com:9118).

"},{"location":"configuration-options/#hostrulesmaxrequestspersecond","title":"hostRules.maxRequestsPerSecond","text":"

Limit requests rate per host.

Name Value type integer parents hostRules default 0

In addition to concurrentRequestLimit, you can limit the maximum number of requests that can be made per one second. It can be used to set minimal delay between two requests to the same host. Fractional values are allowed, e.g. 0.25 means 1 request per 4 seconds. Default value 0 means no limit.

Example config:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"api.github.com\",\n      \"maxRequestsPerSecond\": 2\n    }\n  ]\n}\n
"},{"location":"configuration-options/#hostrulesmaxretryafter","title":"hostRules.maxRetryAfter","text":"

Maximum retry-after header value to wait for before retrying a failed request.

Name Value type integer default 60 parents hostRules

A remote host may return a 4xx response with a Retry-After header value, which indicates that Renovate has been rate-limited. Renovate may try to contact the host again after waiting a certain time, that's set by the host. By default, Renovate tries again after the Retry-After header value has passed, up to a maximum of 60 seconds. If the Retry-After value is more than 60 seconds, Renovate will abort the request instead of waiting.

You can configure a different maximum value in seconds using maxRetryAfter:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"api.github.com\",\n      \"maxRetryAfter\": 25\n    }\n  ]\n}\n
"},{"location":"configuration-options/#hostrulesreadonly","title":"hostRules.readOnly","text":"

Match against requests that only read data and do not mutate anything.

Name Value type boolean parents hostRules default true

If the readOnly field is being set to true inside the host rule, it will match only against the requests that are known to be read operations. Examples are GET requests or HEAD requests, but also it could be certain types of GraphQL queries.

This option could be used to avoid rate limits for certain platforms like GitHub or Bitbucket, by offloading the read operations to a different user.

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"api.github.com\",\n      \"readOnly\": true,\n      \"token\": \"********\"\n    }\n  ]\n}\n

If more than one token matches for a read-only request then the readOnly token will be given preference.

"},{"location":"configuration-options/#hostrulestimeout","title":"hostRules.timeout","text":"

Timeout (in milliseconds) for queries to external endpoints.

Name Value type integer parents hostRules

Use this figure to adjust the timeout for queries. The default is 60s, which is quite high. To adjust it down to 10s for all queries, do this:

{\n  \"hostRules\": [\n    {\n      \"timeout\": 10000\n    }\n  ]\n}\n
"},{"location":"configuration-options/#ignoredeprecated","title":"ignoreDeprecated","text":"

Avoid upgrading from a non-deprecated version to a deprecated one.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default true cli --ignore-deprecated env RENOVATE_IGNORE_DEPRECATED

By default, Renovate won't update a dependency version to a deprecated release unless the current version was itself deprecated. The goal of this is to make sure you don't upgrade from a non-deprecated version to a deprecated one, only because it's higher than the current version.

If for some reason you wish to force deprecated updates with Renovate, you can configure ignoreDeprecated to false, which we do not recommend for most situations.

"},{"location":"configuration-options/#ignoredeps","title":"ignoreDeps","text":"

Dependencies to ignore.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type array subType string mergeable true cli --ignore-deps env RENOVATE_IGNORE_DEPS default []

The ignoreDeps configuration field allows you to define a list of dependency names to be ignored by Renovate. Currently it supports only \"exact match\" dependency names and not any patterns. e.g. to ignore both eslint and eslint-config-base you would add this to your config:

{\n  \"ignoreDeps\": [\"eslint\", \"eslint-config-base\"]\n}\n

The above is the same as if you wrote this package rule:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"eslint\", \"eslint-config-base\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"configuration-options/#ignorepaths","title":"ignorePaths","text":"

Skip any package file whose path matches one of these. Can be a string or glob pattern.

Name Value scopes repo, manager type array mergeable false subType string default 
[\"**/node_modules/**\", \"**/bower_components/**\"]\n
cli --ignore-paths env RENOVATE_IGNORE_PATHS

Renovate will extract dependencies from every file it finds in a repository, unless that file is explicitly ignored. With this setting you can selectively ignore package files that would normally be \"autodiscovered\" and updated by Renovate.

For instance if you have a project with an \"examples/\" directory you wish to ignore:

{\n  \"ignorePaths\": [\"**/examples/**\"]\n}\n

Renovate's default ignore is node_modules and bower_components only. If you are extending from the popular config:recommended preset then it adds ignore patterns for vendor, examples, test(s) and fixtures directories too.

"},{"location":"configuration-options/#ignoreplugins","title":"ignorePlugins","text":"

Set this to true if allowPlugins=true but you wish to skip running plugins when updating lock files.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --ignore-plugins env RENOVATE_IGNORE_PLUGINS

Set this to true if running plugins causes problems. Applicable for Composer only for now.

"},{"location":"configuration-options/#ignorepresets","title":"ignorePresets","text":"

A list of presets to ignore, including any that are nested inside an extends array.

Name Value scopes any type array subType string env RENOVATE_IGNORE_PRESETS default []

Use this if you are extending a complex preset but don't want to use every \"sub preset\" that it includes. For example, consider this config:

{\n  \"extends\": [\"config:recommended\"],\n  \"ignorePresets\": [\"group:monorepos\"]\n}\n

It would take the entire \"config:recommended\" preset - which has a lot of sub-presets - but ignore the \"group:monorepos\" rule.

"},{"location":"configuration-options/#ignorereviewers","title":"ignoreReviewers","text":"

Reviewers to be ignored in PR reviewers presence (either username or email address depending on the platform).

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --ignore-reviewers env RENOVATE_IGNORE_REVIEWERS default []

By default, Renovate does not add assignees or reviewers to PRs which are configured for automerge. If tests have failed, Renovate then does add them, but only if the assignees and reviewers list is empty. In the case that a user is automatically added as reviewer (such as Renovate Approve bot) and you want to ignore it for the purpose of this decision, add it to the ignoreReviewers list.

{\n  \"reviewers\": [\"foo\"],\n  \"ignoreReviewers\": [\"renovate-approve\"]\n}\n

Please note that Reviewers are only added during creation of a PR, but are not modified afterwards.

"},{"location":"configuration-options/#ignorescripts","title":"ignoreScripts","text":"

Set this to false if allowScripts=true and you wish to run scripts when updating lock files.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true supportedManagers npm, bun, composer, copier cli --ignore-scripts env RENOVATE_IGNORE_SCRIPTS

By default, Renovate will disable package manager scripts. Allowing packager manager scripts is a risk:

No script execution on free Mend-hosted Renovate

The Mend Renovate App does not allow scripts to run. We do not plan to let users on free tiers run scripts, because the risk of abuse is too high.

Renovate Enterprise Cloud can be configured to run scripts

Scripts can be enabled for paying customers on Mend.io hosted apps. Please ask Mend.io sales about \"Renovate Enterprise Cloud\".

Allowing scripts if self-hosting Renovate

If you are self-hosting Renovate, and want to allow Renovate to run any scripts:

  1. Set the self-hosted config option allowScripts to true in your admin configuration
  2. Set ignoreScripts to false for the package managers you want to allow to run scripts (only works for the supportedManagers listed in the table above)
"},{"location":"configuration-options/#ignoretests","title":"ignoreTests","text":"

Set to true to enable automerging without tests.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --ignore-tests env RENOVATE_IGNORE_TESTS

Currently Renovate's default behavior is to only automerge if every status check has succeeded.

Setting this option to true means that Renovate will ignore all status checks. You can set this if you don't have any status checks but still want Renovate to automerge PRs. Beware: configuring Renovate to automerge without any tests can lead to broken builds on your base branch, please think again before enabling this!

"},{"location":"configuration-options/#ignoreunstable","title":"ignoreUnstable","text":"

Ignore versions with unstable SemVer.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default true cli --ignore-unstable env RENOVATE_IGNORE_UNSTABLE

By default, Renovate won't update any package versions to unstable versions (e.g. 4.0.0-rc3) unless the current version has the same major.minor.patch and was already unstable (e.g. it was already on 4.0.0-rc2). Renovate will also not \"jump\" unstable versions automatically, e.g. if you are on 4.0.0-rc2 and newer versions 4.0.0 and 4.1.0-alpha.1 exist then Renovate will update you to 4.0.0 only. If you need to force permanent unstable updates for a package, you can add a package rule setting ignoreUnstable to false. In that case you will usually also want to set respectLatest to false so that Renovate considers versions ahead of latest.

Also check out the followTag configuration option above if you wish Renovate to keep you pinned to a particular release tag.

"},{"location":"configuration-options/#includepaths","title":"includePaths","text":"

Include package files only within these defined paths.

Name Value scopes repo, manager type array subType string cli --include-paths env RENOVATE_INCLUDE_PATHS default []

If you wish for Renovate to process only select paths in the repository, use includePaths.

Alternatively, if you need to exclude certain paths in the repository then consider ignorePaths instead. If you are more interested in including only certain package managers (e.g. npm), then consider enabledManagers instead.

"},{"location":"configuration-options/#internalchecksassuccess","title":"internalChecksAsSuccess","text":"

Whether to consider passing internal checks such as minimumReleaseAge when determining branch status.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --internal-checks-as-success env RENOVATE_INTERNAL_CHECKS_AS_SUCCESS

By default, internal Renovate checks such as renovate/stability-days are not counted towards a branch being \"green\" or not. This is primarily to prevent automerge when the only check is a passing Renovate check.

Internal checks will always be counted/considered if they are in pending or failed states. If there are multiple passing checks for a branch, including non-Renovate ones, then this setting won't make any difference.

Change this setting to true if you want to use internal Renovate checks towards a passing branch result.

"},{"location":"configuration-options/#internalchecksfilter","title":"internalChecksFilter","text":"

When and how to filter based on internal checks.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert, updateType type string allowedValues 
[\"strict\", \"flexible\", \"none\"]\n
default \"strict\" cli --internal-checks-filter env RENOVATE_INTERNAL_CHECKS_FILTER

This setting determines whether Renovate controls when and how filtering of internal checks are performed, particularly when multiple versions of the same update type are available. Currently this applies to the minimumReleaseAge check only.

The flexible mode can result in \"flapping\" of Pull Requests, for example: a pending PR with version 1.0.3 is first released but then downgraded to 1.0.2 once it passes minimumReleaseAge. We recommend that you use the strict mode, and enable the dependencyDashboard so that you can see suppressed PRs.

"},{"location":"configuration-options/#keepupdatedlabel","title":"keepUpdatedLabel","text":"

If set, users can add this label to PRs to request they be kept updated with the base branch.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportedPlatforms azure, forgejo, gerrit, gitea, github, gitlab cli --keep-updated-label env RENOVATE_KEEP_UPDATED_LABEL default null

On supported platforms you may add a label to a PR so that Renovate recreates/rebases the PR when the branch falls behind the base branch. Adding the keepUpdatedLabel label to a PR makes Renovate behave as if rebaseWhen were set to behind-base-branch, but only for the given PR. Renovate does not remove the label from the PR after it finishes rebasing. This is different from the rebaseLabel option, where Renovate removes the label from the PR after rebasing.

keepUpdatedLabel can be useful when you have approved certain PRs and want Renovate to keep the PRs up-to-date until you're ready to merge them. The setting keepUpdatedLabel is best used in this scenario:

"},{"location":"configuration-options/#labels","title":"labels","text":"

Labels to set in Pull Request.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string supportsTemplating true cli --labels env RENOVATE_LABELS default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

By default, Renovate won't add any labels to PRs. If you want Renovate to add labels to PRs it creates then define a labels array of one or more label strings. If you want the same label(s) for every PR then you can configure it at the top level of config. However you can also fully override them on a per-package basis.

Consider this example:

{\n  \"labels\": [\"dependencies\"],\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"labels\": [\"linting\"]\n    }\n  ]\n}\n

With the above config, every PR raised by Renovate will have the label dependencies while PRs containing eslint-related packages will instead have the label linting.

Behavior details:

The labels array is non-mergeable, meaning if multiple packageRules match then Renovate uses the last value for labels. If you want to add/combine labels, use the addLabels config option, which is mergeable.

Note

Keep your labels within the maximum character limit for your Git hosting platform. Renovate usually truncates labels to 50 characters, except for GitLab, which has a 255 character limit.

"},{"location":"configuration-options/#lockfilemaintenance","title":"lockFileMaintenance","text":"

Configuration for lock file maintenance.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"enabled\": false,\n  \"recreateWhen\": \"always\",\n  \"branchTopic\": \"lock-file-maintenance\",\n  \"commitMessageAction\": \"Lock file maintenance\",\n  \"commitMessageTopic\": null,\n  \"commitMessageExtra\": null,\n  \"schedule\": [\"before 4am on monday\"],\n  \"groupName\": null,\n  \"prBodyDefinitions\": {\"Change\": \"All locks refreshed\"}\n}\n
mergeable true env RENOVATE_LOCK_FILE_MAINTENANCE

You can use lockFileMaintenance to refresh lock files to keep them up-to-date.

When Renovate performs lockFileMaintenance it deletes the lock file and runs the relevant package manager. That package manager creates a new lock file, where all dependency versions are updated to the latest version. Renovate then commits that lock file to the update branch and creates the lock file update PR.

Supported lock files:

Manager Lockfile apm apm.lock.yaml bazel-module MODULE.bazel.lock bazelisk MODULE.bazel.lock bun bun.lockb, bun.lock bundler Gemfile.lock cargo Cargo.lock composer composer.lock conan conan.lock deno deno.lock devbox devbox.lock gleam manifest.toml gradle gradle.lockfile helmfile helmfile.lock helmv3 Chart.lock jsonnet-bundler jsonnetfile.lock.json mise mise.lock mix mix.lock nix flake.lock npm package-lock.json, pnpm-lock.yaml, yarn.lock nuget packages.lock.json paket paket.lock pep621 pdm.lock, uv.lock pip-compile requirements.txt pipenv Pipfile.lock pixi pixi.lock poetry poetry.lock pub pubspec.lock terraform .terraform.lock.hcl terragrunt .terraform.lock.hcl vendir vendir.lock.yml

Support for new lock files may be added via feature request.

By default, lockFileMaintenance is disabled. To enable lockFileMaintenance add this to your configuration:

{\n  \"lockFileMaintenance\": { \"enabled\": true }\n}\n

To reduce \"noise\" in the repository, Renovate performs lockFileMaintenance \"before 4am on monday\", i.e. to achieve once-per-week semantics. Depending on its running schedule, Renovate may run a few times within that time window - even possibly updating the lock file more than once - but it hopefully leaves enough time for tests to run and automerge to apply, if configured.

"},{"location":"configuration-options/#loglevelremap","title":"logLevelRemap","text":"

Remap log levels to different levels.

Name Value scopes repo type array subType object mergeable true default []

This option allows you to remap log levels for specific messages.

Be careful with remapping warn or error messages to lower log levels, as it may hide important information.

{\n  \"logLevelRemap\": [\n    {\n      \"matchMessage\": \"/^pip-compile:/\",\n      \"newLogLevel\": \"info\"\n    },\n    {\n      \"matchMessage\": \"Package lookup error\",\n      \"newLogLevel\": \"warn\"\n    },\n    {\n      \"matchMessage\": \"/^Please upgrade the version of Node.js/\",\n      \"newLogLevel\": \"info\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#loglevelremapmatchmessage","title":"logLevelRemap.matchMessage","text":"

Regex/minimatch expression to match against log message.

Name Value type string parents logLevelRemap default null

Use matchMessage to match the log message you want to remap. Accepts a string or regex pattern.

"},{"location":"configuration-options/#loglevelremapnewloglevel","title":"logLevelRemap.newLogLevel","text":"

New log level to use if matchMessage matches.

Name Value type string allowedValues 
[\"trace\", \"debug\", \"info\", \"warn\", \"error\", \"fatal\"]\n
parents logLevelRemap default null

For log level remapping, newLogLevel will set for the particular log message:

{\n  \"logLevelRemap\": [\n    {\n      \"matchMessage\": \"/Error executing maven wrapper update command/\",\n      \"newLogLevel\": \"warn\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#major","title":"major","text":"

Configuration to apply when an update type is major.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object mergeable true env RENOVATE_MAJOR

Add to this object if you wish to define rules that apply only to major updates.

"},{"location":"configuration-options/#maxmajorincrement","title":"maxMajorIncrement","text":"

Limit the maximum major version increment allowed. Set to 0 to disable.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type integer default 500

This is particularly useful for preventing upgrades from SemVer-based versions to CalVer-based ones.

For example, if you're on version 19.0.0, Renovate will upgrade to 22.0.0 but filter out versions like 999.0.0 and 2025.0.0.

You can use packageRules to customize this behavior for specific packages:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Allow to upgrade Home Assistant from 0.x to 2025.x\",\n      \"matchPackageNames\": [\"homeassistant\"],\n      \"maxMajorIncrement\": 0\n    }\n  ]\n}\n

The above allows unlimited major version upgrades by setting maxMajorIncrement to 0.

Alternatively, to limit major upgrades to within 10 versions:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Limit xmldoc major upgrades to within 10 versions\",\n      \"matchPackageNames\": [\"xmldoc\"],\n      \"maxMajorIncrement\": 10\n    }\n  ]\n}\n
"},{"location":"configuration-options/#managerfilepatterns","title":"managerFilePatterns","text":"

RegEx (re2) and glob patterns for matching manager files.

Name Value type array subType string mergeable true scopes manager parents customManagers default []

Formerly known as fileMatch, which supported regex-only.

managerFilePatterns supports both regex and glob patterns. Any existing config containing fileMatch patterns will be automatically migrated.

Do not use the below guide for fileMatch if you are using an older version of Renovate.

managerFilePatterns tells Renovate which repository files to parse and extract. Patterns in the user config are added to the default values, they do not replace the default values.

The default managerFilePatterns patterns can not be removed. If you need to include, or exclude, specific paths then use the ignorePaths or includePaths instead.

Some managers have sensible defaults. For example, the Go manager looks for any go.mod file by default, which covers most cases without extra configuration.

At other times, the possible files is too vague for Renovate to have any default. For example, Kubernetes manifests can exist in any *.yaml file. We do not want Renovate to parse every YAML file in every repository, just in case some of them have a Kubernetes manifest. Therefore Renovate's default managerFilePatterns for the kubernetes manager is an empty array ([]). Because the array is empty, you as user must tell Renovate which directories/files to check.

Finally, there are cases where Renovate's default managerFilePatterns is good, but you may be using non-standard filenames. For example, Renovate's default managerFilePatterns for Dockerfile is ['/(^|/|\\\\.)([Dd]ocker|[Cc]ontainer)file$/', '/(^|/)([Dd]ocker|[Cc]ontainer)file[^/]*$/']. This will catch files like backend/Dockerfile, prefix.Dockerfile or Dockerfile-suffix, but it will miss files like ACTUALLY_A_DOCKERFILE.template. Because managerFilePatterns is \"mergeable\", you can add the missing file to the filePattern like this:

{\n  \"dockerfile\": {\n    \"managerFilePatterns\": [\"/^ACTUALLY_A_DOCKERFILE\\\\.template$/\"]\n  }\n}\n

You must configure managerFilePatterns inside a manager object. In the example above, the manager object is the dockerfile. For reference, here is a list of supported managers.

"},{"location":"configuration-options/#milestone","title":"milestone","text":"

The number of a milestone. If set, the milestone will be set when Renovate creates the PR.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer supportedPlatforms github cli --milestone env RENOVATE_MILESTONE

If set to the number of an existing GitHub milestone, Renovate will add that milestone to its PR. Renovate will only add a milestone when it creates the PR.

Example Renovate config
{\n  \"milestone\": 12\n}\n
"},{"location":"configuration-options/#minimumgroupsize","title":"minimumGroupSize","text":"

The minimum number of updates which must be in a group for branches to be created.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 1 cli --minimum-group-size env RENOVATE_MINIMUM_GROUP_SIZE

If set to to a positive value x then branch creation will be postponed until x or more updates are available in the branch.

This applies to both these scenarios:

Example:

Create only a grouped update when there are 3 or more node updates
{\n  \"packageRules\": [\n    {\n      \"description\": \"We need to update Node in two places - always wait until both upgrades are available\",\n      \"matchDepNames\": [\"node\"],\n      \"groupName\": \"Node.js\",\n      \"minimumGroupSize\": 3\n    }\n  ]\n}\n
"},{"location":"configuration-options/#minimumreleaseage","title":"minimumReleaseAge","text":"

Time required before a new release is considered stable.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert, updateType type string cli --minimum-release-age env RENOVATE_MINIMUM_RELEASE_AGE

minimumReleaseAge is a feature that requires Renovate to wait for a specified amount of time before suggesting a dependency update.

Note

Minimum Release Age has a separate documentation page for more in-depth documentation about the functionality. This also includes documentation that was previously in this section, regarding how to specify release timestamps for custom registries.

If minimumReleaseAge is set to a time duration and the update has a release timestamp header, then Renovate will check if the set duration has passed. This behaviour can be changed using minimumReleaseAgeBehaviour.

Note: Renovate will wait for the set duration to pass for each separate version. Renovate does not wait until the package has seen no releases for x time-duration(minimumReleaseAge).

Do not use minimumReleaseAge to slow down fast releasing project updates. Instead setup a custom schedule for that package, read our selective-scheduling help to learn how.

When the time passed since the release is less than the set minimumReleaseAge: Renovate adds a \"pending\" status check to that update's branch. After enough days have passed: Renovate replaces the \"pending\" status with a \"passing\" status check.

The datasource that Renovate uses must have a release timestamp for the minimumReleaseAge config option to work. Some datasources may have a release timestamp, but in a format Renovate does not support. In those cases a feature request needs to be implemented.

You can confirm if your datasource supports the release timestamp by viewing the documentation for the given datasource.

Note

Configuring this option will add a renovate/stability-days option to the status checks.

Note

As of Renovate 42.19.5, using minimumReleaseAge=0 days is treated the same as minimumReleaseAge=null.

Examples of how you can use minimumReleaseAge:

"},{"location":"configuration-options/#suppress-branchpr-creation-for-x-days","title":"Suppress branch/PR creation for X days","text":"

If you use minimumReleaseAge=3 days, prCreation=\"not-pending\" and internalChecksFilter=\"strict\" then Renovate only creates branches when 3 (or more days) have passed since the version was released. We recommend you set dependencyDashboard=true, so you can see these pending PRs.

Warning

prCreation=\"not-pending\" only opens the PR once branch checks complete. If your CI runs only on pull_request events (so Renovate branches have no checks), also set internalChecksAsSuccess=true so the release-age check can turn the branch green - otherwise PR creation may be deferred indefinitely.

"},{"location":"configuration-options/#prevent-holding-broken-npm-packages","title":"Prevent holding broken npm packages","text":"

npm packages less than 72 hours (3 days) old can be unpublished from the npm registry, which could result in a service impact if you have already updated to it. Set minimumReleaseAge to 3 days for npm packages to prevent relying on a package that can be removed from the registry:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"minimumReleaseAge\": \"3 days\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#await-x-time-duration-before-automerging","title":"Await X time duration before Automerging","text":"

If you enable automerge and minimumReleaseAge, Renovate Renovate will create PRs immediately, but only automerge them when the minimumReleaseAge time-duration has passed.

Renovate adds a \"renovate/stability-days\" pending status check to each branch/PR. This pending check prevents the branch going green to automerge before the time has passed.

"},{"location":"configuration-options/#minimumreleaseagebehaviour","title":"minimumReleaseAgeBehaviour","text":"

When set in conjunction with minimumReleaseAge, controls whether the releaseTimestamp for a dependency update is required.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert, updateType type string default \"timestamp-required\" allowedValues 
[\"timestamp-required\", \"timestamp-optional\"]\n
cli --minimum-release-age-behaviour env RENOVATE_MINIMUM_RELEASE_AGE_BEHAVIOUR

When minimumReleaseAge is set to a time duration, the minimumReleaseAgeBehaviour will be used to control whether the release timestamp is required.

When set to timestamp-required, this version is not treated stable unless there is release timestamp, and that release timestamp is past the minimumReleaseAge.

When set to timestamp-optional, Renovate will treat a release without a releaseTimestamp as stable.

This only applies when used with minimumReleaseAge.

"},{"location":"configuration-options/#minimumreleaseagebuffer","title":"minimumReleaseAgeBuffer","text":"

Extra time added to minimumReleaseAge before an update is considered stable.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert, updateType type string default \"30 minutes\" nullable true cli --minimum-release-age-buffer env RENOVATE_MINIMUM_RELEASE_AGE_BUFFER

Use this option to extend the time Renovate waits before suggesting an update, on top of minimumReleaseAge.

Some projects publish a set of related packages, where companion packages (like platform-specific binaries) are published after the main package. For example, @biomejs/biome@2.5.10 may be published some minutes before @biomejs/cli-linux-x64@2.5.10. If your package manager enforces its own release age cooldown, like pnpm's minimumReleaseAge setting or npm's --before flag, Renovate may suggest the main package as soon as it passes minimumReleaseAge, while a companion package published later is still within the package manager's cooldown. The package manager then refuses to update the lock file, and the update fails with an artifact error.

minimumReleaseAgeBuffer avoids this by letting Renovate wait longer than the package manager's cooldown. Renovate defers the update until minimumReleaseAge plus the buffer duration has passed, while the package manager keeps using the plain minimumReleaseAge cutoff. This way, packages published up to the buffer time after the suggested release have also passed the package manager's cooldown.

By default, Renovate uses a buffer of 30 minutes. Set minimumReleaseAgeBuffer to null to disable the buffer.

For example, with the following configuration Renovate waits 3 days plus 1 hour before suggesting an update, while the package manager's cooldown stays at 3 days:

{\n  \"minimumReleaseAge\": \"3 days\",\n  \"minimumReleaseAgeBuffer\": \"1 hour\"\n}\n

This only applies when used with minimumReleaseAge.

"},{"location":"configuration-options/#minor","title":"minor","text":"

Configuration to apply when an update type is minor.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object mergeable true env RENOVATE_MINOR

Add to this object if you wish to define rules that apply only to minor updates.

"},{"location":"configuration-options/#mode","title":"mode","text":"

Mode of operation.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"full\" allowedValues 
[\"full\", \"silent\"]\n
cli --mode env RENOVATE_MODE

This configuration option was created primarily for use with Mend's hosted app, but can also be useful for some self-hosted use cases.

It enables a new silent mode to allow repos to be scanned for updates and for users to be able to request such updates be opened in PRs on demand through the Mend UI, without needing the Dependency Dashboard issue in the repo.

Although similar, the options mode=silent and dryRun can be used together. When both are configured, dryRun takes precedence, so for example PRs won't be created.

Configuring silent mode is quite similar to dryRun=lookup except:

When in silent mode Renovate will:

"},{"location":"configuration-options/#npmtoken","title":"npmToken","text":"

npm token used to authenticate with the default registry.

Name Value scopes repo type string cli --npm-token env RENOVATE_NPM_TOKEN default null

See Private npm module support for details on how this is used. Typically you would encrypt it and put it inside the encrypted object.

"},{"location":"configuration-options/#npmrc","title":"npmrc","text":"

String copy of .npmrc file. Use \\n instead of line breaks.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string cli --npmrc env RENOVATE_NPMRC default null

See Private npm module support for details on how this is used.

"},{"location":"configuration-options/#npmrcmerge","title":"npmrcMerge","text":"

Whether to merge config.npmrc with repo .npmrc content if both are found.

Name Value scopes repo, manager type boolean default false cli --npmrc-merge env RENOVATE_NPMRC_MERGE

This option exists to provide flexibility about whether npmrc strings in config should override .npmrc files in the repo, or be merged with them. In some situations you need the ability to force override .npmrc contents in a repo (npmrcMerge=false) while in others you might want to simply supplement the settings already in the .npmrc (npmrcMerge=true). A use case for the latter is if you are a Renovate admin and wish to provide a default token for npmjs.org without removing any other .npmrc settings which individual repositories have configured (such as scopes/registries).

If false (default), it means that defining config.npmrc will result in any .npmrc file in the repo being overridden and its values ignored. If configured to true, it means that any .npmrc file in the repo will have config.npmrc prepended to it before running npm.

"},{"location":"configuration-options/#osvvulnerabilityalerts","title":"osvVulnerabilityAlerts","text":"

Use vulnerability alerts from osv.dev.

Name Value scopes repo type boolean default false cli --osv-vulnerability-alerts env RENOVATE_OSV_VULNERABILITY_ALERTS

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.To track this feature visit the following GitHub issue #20542.

Renovate integrates with OSV, an Open Source vulnerability database, to check if extracted dependencies have known vulnerabilities. Set osvVulnerabilityAlerts to true to get pull requests with vulnerability fixes (once they are available).

You will only get OSV-based vulnerability alerts for direct dependencies. Renovate only queries the OSV database for dependencies that use one of these datasources:

The entire database is downloaded locally by osv-offline and queried offline.

If you self-host Renovate, you can change how the database is downloaded with these osv-offline environment variables:

If you persist the cacheDir, the database (roughly 85 MB compressed) is kept as well.

Read the osv-offline readme for all options, mirrors, and which hosts to allow.

"},{"location":"configuration-options/#malicious-package-detection-and-protection","title":"Malicious package detection and protection","text":"

Note

This functionality is currently experimental, being actively worked on, and will soon be available for usage outside of osvVulnerabilityAlerts.

If Renovate detects a malicious dependency using data from OSV, it will surface this in log warnings, and prevent PRs from being created.

If you currently have a dependency that is using a malicious version, Renovate will report this via a warning log.

If Renovate finds a dependency update available, and that dependency update is found to be malicious, Renovate will skip any updates to the dependency, marking it with skipReason: malicious-update-proposed, and report this via a warning log.

"},{"location":"configuration-options/#overridedescription","title":"overrideDescription","text":"

Description which replaces the descriptions of any presets which this config extends.

Name Value scopes any type array subType string default []

Use overrideDescription instead of description if this config's description should replace, and not be added to, the descriptions collated from the presets which this config extends.

This is useful for a preset which extends many other presets, and where a single line describes them better than one line per preset would. For example, workarounds:all extends around twenty presets, but its overrideDescription means the onboarding PR shows only:

- Apply crowd-sourced workarounds for known problems with packages.\n

Renovate applies overrideDescription when it resolves presets, so the resolved config only ever has a description.

"},{"location":"configuration-options/#packagerules","title":"packageRules","text":"

Rules for matching packages.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert type array mergeable true cli --package-rules env RENOVATE_PACKAGE_RULES default []

packageRules is a powerful feature that lets you apply rules to individual packages or to groups of packages using regex pattern matching.

packageRules is a collection of rules, that are all evaluated. If multiple rules match a dependency, configurations from matching rules will be merged together. The order of rules matters, because later rules may override configuration options from earlier ones, if they both specify the same option.

The matching process for a package rule:

For more details on positive and negative pattern syntax see Renovate's string pattern matching documentation.

Here is an example if you want to group together all packages starting with eslint into a single branch/PR:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"eslint**\"],\n      \"groupName\": \"eslint packages\"\n    }\n  ]\n}\n

Note how the above uses matchPackageNames with a prefix pattern.

Here's an example config to limit the \"noisy\" AWS SDK packages to weekly updates:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Schedule AWS SDK updates on Sunday nights (9 PM - 12 AM)\",\n      \"matchPackageNames\": [\"@aws-sdk/*\"],\n      \"schedule\": [\"* 21-23 * * 0\"]\n    }\n  ]\n}\n

For Maven dependencies, the package name is <groupId:artefactId>, e.g. \"matchPackageNames\": [\"com.thoughtworks.xstream:xstream\"]

Note how the above uses an exact match string for matchPackageNames instead of a pattern However you can mix together both patterns and exact matches in the same package rule and the rule will be applied if either match. Example:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"neutrino\", \"@neutrino/**\"],\n      \"groupName\": \"neutrino monorepo\"\n    }\n  ]\n}\n

The above rule will group together the neutrino package and any package starting with @neutrino/.

File name matches are convenient to use if you wish to apply configuration rules to certain package or lock files using patterns. For example, if you have an examples directory and you want all updates to those examples to use the chore prefix instead of fix, then you could add this configuration:

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"examples/**\"],\n      \"extends\": [\":semanticCommitTypeAll(chore)\"]\n    }\n  ]\n}\n

If you wish to limit Renovate to apply configuration rules to certain files in the root repository directory, you have to use matchFileNames with a minimatch glob (which can include an exact file name match) or RE2 regex.

For more details on supported syntax see Renovate's string pattern matching documentation.

For example you have multiple package.json and want to use dependencyDashboardApproval only on the root package.json:

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"package.json\"],\n      \"dependencyDashboardApproval\": true\n    }\n  ]\n}\n

Tip

Order your packageRules so the least important rules are at the top, and the most important rules at the bottom. This way important rules override settings from earlier rules if needed.

Warning

Avoid nesting any object-type configuration in a packageRules array, such as a major or minor block.

"},{"location":"configuration-options/#packagerulesallowedversions","title":"packageRules.allowedVersions","text":"

A version range or regex pattern capturing allowed versions for dependencies.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

You can use allowedVersions - usually within a packageRules entry - to limit how far to upgrade a dependency.

For example, if you want to upgrade to Angular v1.5 but not to angular v1.6 or higher, you could set allowedVersions to <= 1.5 or < 1.6.0:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"angular\"],\n      \"allowedVersions\": \"<=1.5\"\n    }\n  ]\n}\n

Renovate calculates the valid syntax for this at runtime, because it depends on the dynamic versioning scheme.

You can also use the following template fields with allowedVersions:

For example, if you want to upgrade to Angular to only the next major, you could set allowedVersions like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"angular\"],\n      \"allowedVersions\": \"<={{add major 1}}\"\n    }\n  ]\n}\n

Warning

allowedVersions and matchUpdateTypes cannot be used in the same package rule.

"},{"location":"configuration-options/#using-regular-expressions","title":"Using regular expressions","text":"

You can use Regular Expressions in the allowedVersions config. You must begin and end your Regular Expression with the / character!

For example, this config only allows 3 or 4-part versions, without any prefixes in the version:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"com.thoughtworks.xstream:xstream\"],\n      \"allowedVersions\": \"/^[0-9]+\\\\.[0-9]+\\\\.[0-9]+(\\\\.[0-9]+)?$/\"\n    }\n  ]\n}\n

Again: note how the Regular Expression begins and ends with the / character.

"},{"location":"configuration-options/#ignore-versions-with-negated-regex-syntax","title":"Ignore versions with negated regex syntax","text":"

You can use a special negated regex syntax to ignore certain versions. You must use the !/ / syntax, like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"chalk\"],\n      \"allowedVersions\": \"!/java$/\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packageruleschangelogurl","title":"packageRules.changelogUrl","text":"

Set a custom URL for the changelog. Renovate will put this URL in the PR body text.

Name Value type string parents packageRules supportsTemplating true previouslyKnownAs 
[\"customChangelogUrl\"]\n
default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Sometimes Renovate does not show the correct changelog for a package. As a workaround for this problem, you can give Renovate the URL to the changelog with the changelogUrl config option. When set, Renovate will put a link to the changelogs in the Renovate PR body.

Renovate does not show the complete changelogs from the changelogUrl in its PR body text, you only get the URL from Renovate. To read the changelogs you must use the link.

Setting the changelog URL for the dummy package
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"dummy\"],\n      \"changelogUrl\": \"https://github.com/org/dummy\"\n    }\n  ]\n}\n

changelogUrl supports template compilation.

Setting the changelog URL for the dummy package using a template
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"dummy\"],\n      \"changelogUrl\": \"https://github.com/org/monorepo/blob/{{{sourceDirectory}}}/my-custom-changelog.txt\"\n    }\n  ]\n}\n

Note

Renovate can fetch changelogs from Bitbucket, Bitbucket Server / Data Center, Forgejo, Gitea, GitHub and GitLab platforms only, and setting the URL to an unsupported host/platform type won't change that.

For more details on supported syntax see Renovate's string pattern matching documentation.

"},{"location":"configuration-options/#packagerulesmatchbasebranches","title":"packageRules.matchBaseBranches","text":"

List of strings containing exact matches (e.g. [\"main\"]) and/or regex expressions (e.g. [\"/^release/.*/\"]). Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use this field to restrict rules to a particular branch. e.g.

{\n  \"baseBranchPatterns\": [\"main\"],\n  \"packageRules\": [\n    {\n      \"matchBaseBranches\": [\"main\"],\n      \"matchPackageNames\": [\"!/^eslint/\"],\n      \"enabled\": false\n    }\n  ]\n}\n

This field also supports Regular Expressions if they begin and end with /. e.g.

{\n  \"baseBranchPatterns\": [\"main\", \"/^release\\\\/.*/\"],\n  \"packageRules\": [\n    {\n      \"matchBaseBranches\": [\"/^release/.*/\"],\n      \"matchPackageNames\": [\"!/^eslint/\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchcategories","title":"packageRules.matchCategories","text":"

List of categories to match (for example: [\"python\"]). Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use matchCategories to restrict rules to a particular language or group. Matching is done using \"any\" logic, i.e. \"match any of the following categories\". The categories can be found in the manager documentation.

Note

Rules with matchCategories are only applied after extraction of dependencies. If you want to configure which managers are being extracted at all, use enabledManagers instead.

{\n  \"packageRules\": [\n    {\n      \"matchCategories\": [\"python\"],\n      \"addLabels\": [\"py\"]\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchconfidence","title":"packageRules.matchConfidence","text":"

Merge confidence levels to match against (low, neutral, high, very high). Valid only within packageRules object.

Name Value type array subType string allowedValues 
[\"low\", \"neutral\", \"high\", \"very high\"]\n
parents packageRules mergeable true default []

Warning

This configuration option needs a Mend API key, and is in private beta testing only. API keys are not available for free or via the renovatebot/renovate repository.

Grouping high merge confidence updates
{\n  \"packageRules\": [\n    {\n      \"matchConfidence\": [\"high\", \"very high\"],\n      \"groupName\": \"high merge confidence\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchcurrentage","title":"packageRules.matchCurrentAge","text":"

Matches the current age of the package derived from its release timestamp. Valid only within a packageRules object.

Name Value type string parents packageRules mergeable true default null

Use this field if you want to match packages based on the age of the current (existing, in-repo) version.

For example, if you want to group updates for dependencies where the existing version is more than 2 years old:

{\n  \"packageRules\": [\n    {\n      \"matchCurrentAge\": \"> 2 years\",\n      \"groupName\": \"old dependencies\"\n    }\n  ]\n}\n

The matchCurrentAge string must start with one of >, >=, < or <=.

Only one date part is supported, so you cannot do > 1 year 1 month. Instead you should do > 13 months.

Note

We recommend you only use the words hour(s), day(s), week(s), month(s) and year(s) in your time ranges.

"},{"location":"configuration-options/#packagerulesmatchcurrentvalue","title":"packageRules.matchCurrentValue","text":"

A regex or glob pattern to match against the raw currentValue string of a dependency. Valid only within a packageRules object.

Name Value type string parents packageRules mergeable true default null

This option is matched against the currentValue field of a dependency.

matchCurrentValue supports Regular Expressions and glob patterns. For example, the following enforces that updates from 1.* versions will be merged automatically:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchCurrentValue\": \"1.*\",\n      \"automerge\": true\n    }\n  ]\n}\n

Regular Expressions must begin and end with /.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchCurrentValue\": \"/^1\\\\./\"\n    }\n  ]\n}\n

This field also supports a special negated regex syntax to ignore certain versions. Use the syntax !/ / like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchCurrentValue\": \"!/^0\\\\./\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchcurrentversion","title":"packageRules.matchCurrentVersion","text":"

A version, or range of versions, to match against the current version of a package. Valid only within a packageRules object.

Name Value type string parents packageRules mergeable true default null

The currentVersion field will be one of the following (in order of preference):

Consider using instead matchCurrentValue if you wish to match against the raw string value of a dependency.

matchCurrentVersion can be an exact version or a version range:

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=1.0.0\",\n      \"matchPackageNames\": [\"angular\"]\n    }\n  ]\n}\n

The syntax of the version range must follow the versioning scheme used by the matched package(s). This is usually defined by the manager which discovered them or by the default versioning for the package's datasource. For example, a Gradle package would typically need Gradle constraint syntax (e.g. [,7.0)) and not SemVer syntax (e.g. <7.0).

This field also supports Regular Expressions which must begin and end with /. For example, the following enforces that only 1.* versions will be used:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchCurrentVersion\": \"/^1\\\\./\"\n    }\n  ]\n}\n

This field also supports a special negated regex syntax to ignore certain versions. Use the syntax !/ / like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchCurrentVersion\": \"!/^0\\\\./\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchdatasources","title":"packageRules.matchDatasources","text":"

List of datasources to match (e.g. [\"orb\"]). Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use this field to restrict rules to a particular datasource. e.g.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"orb\"],\n      \"labels\": [\"circleci-orb!!\"]\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchdepnames","title":"packageRules.matchDepNames","text":"

Dep names to match. Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

This field behaves the same as matchPackageNames except it matches against depName instead of packageName.

"},{"location":"configuration-options/#packagerulesmatchdeptypes","title":"packageRules.matchDepTypes","text":"

List of depTypes to match (e.g. [peerDependencies]). Valid only within packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use this field if you want to limit a packageRule to certain depType values. This matching can be an exact match, Glob match, or Regular Expression match.

For more details on supported syntax see Renovate's string pattern matching documentation. Note that Glob matching (including exact name matching) is case-insensitive.

Invalid if used outside of a packageRule.

"},{"location":"configuration-options/#packagerulesmatchfilenames","title":"packageRules.matchFileNames","text":"

List of patterns to match against package and lock file paths. Valid only within a packageRules object.

Name Value type array subType string parents packageRules default []

Renovate will compare matchFileNames glob or RE2 regex matching against the dependency's package file and also lock file if one exists.

For more details on supported syntax see Renovate's string pattern matching documentation.

The following example matches package.json but not package/frontend/package.json:

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"package.json\"],\n      \"labels\": [\"npm\"]\n    }\n  ]\n}\n

The following example matches any package.json, including files like backend/package.json:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group dependencies from package.json files\",\n      \"matchFileNames\": [\"**/package.json\"],\n      \"groupName\": \"All package.json changes\"\n    }\n  ]\n}\n

The following example matches any file in directories starting with app/:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group all dependencies from the app directory\",\n      \"matchFileNames\": [\"app/**\"],\n      \"groupName\": \"App dependencies\"\n    }\n  ]\n}\n

The following example matches any .toml file in a v1, v2 or v3 directory:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group all dependencies from legacy projects\",\n      \"matchFileNames\": [\"/v[123]/.*\\\\.toml/\"],\n      \"groupName\": \"Legacy project dependencies\"\n    }\n  ]\n}\n

It is recommended that you avoid using \"negative\" globs, like **/!(package.json), because such patterns might still return true if they match against the lock file name (e.g. package-lock.json).

"},{"location":"configuration-options/#packagerulesmatchisbreaking","title":"packageRules.matchIsBreaking","text":"

Matches only if the update is considered breaking (e.g. major, or minor for 0.x in ecosystems like Cargo) when true, or non-breaking when false. Valid only within a packageRules object.

Name Value type boolean parents packageRules default true

Use matchIsBreaking to match updates based on whether Renovate considers them breaking. Set it to true to match only breaking updates, or false to match only non-breaking updates.

What counts as breaking depends on the versioning of the dependency:

Rules with matchIsBreaking never match when there is no update to evaluate, for example for lockFileMaintenance.

The following example automerges all non-breaking updates of packages in the @myorg scope:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"@myorg{/,}**\"],\n      \"matchIsBreaking\": false,\n      \"automerge\": true\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchjsonata","title":"packageRules.matchJsonata","text":"

A JSONata expression to match against the full config object. Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use the matchJsonata field to define custom matching logic using JSONata query logic. Renovate will evaluate the provided JSONata expressions against the passed values (manager, packageName, etc.).

See the JSONata docs for more details on JSONata syntax.

Here are some example matchJsonata strings for inspiration:

$exists(deprecationMessage)\n$exists(vulnerabilityFixVersion)\nmanager = 'dockerfile' and depType = 'final'\nupdateType = 'major' and newVersionAgeInDays < 7\n$detectPlatform(sourceUrl) = 'github'\n$matchRegexOrGlob(packageName, [\"@myorg{/,}**\"]) or $matchRegexOrGlob(registryUrls, [\"https://registry.example.com/**\"])\n

matchJsonata accepts an array of strings, and will return true if any of those JSONata expressions evaluate to true.

Renovate provides the following custom JSONata functions:

"},{"location":"configuration-options/#packagerulesmatchmanagers","title":"packageRules.matchManagers","text":"

List of package managers to match (e.g. [\"pipenv\"]). Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use this field to restrict rules to a particular package manager. e.g.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"node\"],\n      \"matchManagers\": [\"dockerfile\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchnewvalue","title":"packageRules.matchNewValue","text":"

A regex or glob pattern to match against the raw newValue string of a dependency. Valid only within a packageRules object.

Name Value type string parents packageRules mergeable true default null

This option is matched against the newValue field of a dependency.

matchNewValue supports Regular Expressions and glob patterns. For example, the following enforces that updates to 1.* versions will be merged automatically:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchNewValue\": \"1.*\",\n      \"automerge\": true\n    }\n  ]\n}\n

Regular Expressions must begin and end with /.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchNewValue\": \"/^1\\\\./\"\n    }\n  ]\n}\n

This field also supports a special negated regex syntax to ignore certain versions. Use the syntax !/ / like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"io.github.resilience4j**\"],\n      \"matchNewValue\": \"!/^0\\\\./\"\n    }\n  ]\n}\n

For more details on this syntax see Renovate's string pattern matching documentation.

"},{"location":"configuration-options/#packagerulesmatchpackagenames","title":"packageRules.matchPackageNames","text":"

Package names to match. Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []

Use this field to match against the packageName field. This matching can be an exact match, Glob match, or Regular Expression match.

For more details on supported syntax see Renovate's string pattern matching documentation. Note that Glob matching (including exact name matching) is case-insensitive.

exact name match
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"matchPackageNames\": [\"angular\"],\n      \"rangeStrategy\": \"pin\"\n    }\n  ]\n}\n

The above will configure rangeStrategy to pin only for the npm package angular.

prefix match using Glob
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"@angular/**\", \"!@angular/abc\"],\n      \"rangeStrategy\": \"replace\"\n    }\n  ]\n}\n

The above will set a replaceStrategy for any npm package which starts with @angular/ except @angular/abc.

pattern match using RegEx
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"matchPackageNames\": [\"/^angular/\"],\n      \"groupName\": \"Angular\"\n    }\n  ]\n}\n

The above will group together any npm package which starts with the string angular.

"},{"location":"configuration-options/#packagerulesmatchregistryurls","title":"packageRules.matchRegistryUrls","text":"

A list of URLs (or URL patterns) to match against registryUrls.

Name Value type array subType string parents packageRules mergeable true default []

Use this option to match packages based on their registryUrls. Any package whose registryUrls array contains at least one URL matching any of the provided patterns will be selected.

Here's an example of where you use this to disable updates from a specific private registry:

{\n  \"packageRules\": [\n    {\n      \"matchRegistryUrls\": [\"https://private.registry.example.com/**\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesmatchrepositories","title":"packageRules.matchRepositories","text":"

List of repositories to match (e.g. [\"**/*-archived\"]). Valid only within a packageRules object.

Name Value type array subType string parents packageRules mergeable true default []"},{"location":"configuration-options/#packagerulesmatchsourceurls","title":"packageRules.matchSourceUrls","text":"

A list of exact match URLs (or URL patterns) to match sourceUrl against.

Name Value type array subType string parents packageRules mergeable true default []

Here's an example of where you use this to group together all packages from the Vue monorepo:

{\n  \"packageRules\": [\n    {\n      \"matchSourceUrls\": [\"https://github.com/vuejs/vue\"],\n      \"groupName\": \"Vue monorepo packages\"\n    }\n  ]\n}\n

For more details on supported syntax see Renovate's string pattern matching documentation.

"},{"location":"configuration-options/#packagerulesmatchupdatetypes","title":"packageRules.matchUpdateTypes","text":"

Update types to match against (major, minor, pin, pinDigest, etc). Valid only within packageRules object.

Name Value type array subType string allowedValues 
[\n  \"major\",\n  \"minor\",\n  \"patch\",\n  \"pin\",\n  \"pinDigest\",\n  \"digest\",\n  \"lockFileMaintenance\",\n  \"lockfileUpdate\",\n  \"rollback\",\n  \"bump\",\n  \"replacement\"\n]\n
parents packageRules mergeable true default []

Use matchUpdateTypes to match rules against types of updates. For example to apply a special label to major updates:

{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"major\"],\n      \"labels\": [\"UPDATE-MAJOR\"]\n    }\n  ]\n}\n

For more details on supported syntax see Renovate's string pattern matching documentation.

Warning

Packages that follow SemVer are allowed to make breaking changes in any 0.x version, even patch and minor. Check if you're using any 0.x package, and see if you need custom packageRules for it. When setting up automerge for dependencies, make sure to stop accidental automerges of 0.x versions. Read the automerge non-major updates docs for a config example that blocks 0.x updates.

Warning

matchUpdateTypes and allowedVersions cannot be used in the same package rule.

Tokens can be configured via hostRules using the \"merge-confidence\" hostType:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"merge-confidence\",\n      \"token\": \"********\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesoverridedatasource","title":"packageRules.overrideDatasource","text":"

Override the datasource value.

Name Value type string parents packageRules default null

Warning

For advanced use only! Use at your own risk!

If a particular datasource/packageName combination has a lookup problem, you may be able to fix it by changing datasource and potentially also packageName. Here is an example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"renovate/renovate\"],\n      \"overrideDatasource\": \"npm\",\n      \"overridePackageName\": \"renovate\"\n    }\n  ]\n}\n

overrideDatasource does not support template compilation. Be cautious as using this setting incorrectly could break all lookups.

"},{"location":"configuration-options/#packagerulesoverridedepname","title":"packageRules.overrideDepName","text":"

Override the depName value.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

Be careful using this feature because it may cause undesirable changes such as to branch names.

In Renovate terminology, packageName is the exact package name needing to be looked up on a registry, while depName is essentially the \"pretty\" name. For example, the packageName is docker.io/library/node while the depName might be node for short.

depName is used in PR titles as well as branch names, so changes to depName will have effects on those.

overrideDepName supports template compilation. Example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"overrideDepName\": \"{{replace 'docker.io/library/' '' depName}}\"\n    }\n  ]\n}\n

Be cautious as using this setting incorrectly could break all lookups.

"},{"location":"configuration-options/#packagerulesoverridepackagename","title":"packageRules.overridePackageName","text":"

Override the packageName value.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Warning

For advanced use only! Use at your own risk!

See the packageRules.overrideDatasource documentation for an example of use. overridePackageName supports template compilation.

Be cautious as using this setting incorrectly could break all lookups.

"},{"location":"configuration-options/#packagerulesprpriority","title":"packageRules.prPriority","text":"

Set sorting priority for PR creation. PRs with higher priority are created first, negative priority last.

Name Value type integer allowNegative true default 0 parents packageRules

Sometimes Renovate needs to rate limit its creation of PRs, e.g. hourly or concurrent PR limits. By default, Renovate sorts/prioritizes based on the update type, going from smallest update to biggest update. Renovate creates update PRs in this order:

  1. pinDigest
  2. pin
  3. digest
  4. patch
  5. minor
  6. major

If you have dependencies that are more or less important than others then you can use the prPriority field for PR sorting. The default value is 0, so setting a negative value will make dependencies sort last, while higher values sort first.

Here's an example of how you would define PR priority so that devDependencies are raised last and react is raised first:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"prPriority\": -1\n    },\n    {\n      \"matchPackageNames\": [\"react\"],\n      \"prPriority\": 5\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesreplacementname","title":"packageRules.replacementName","text":"

The name of the new dependency that replaces the old deprecated dependency.

Name Value type string parents packageRules default null

This config option only works with some managers. We're working to support more managers, subscribe to issue renovatebot/renovate#24883 to follow our progress.

Managers which do not support replacement:

Use the replacementName config option to set the name of a replacement package.

Can be used in combination with replacementVersion.

You can suggest a new community package rule by editing the replacements.json file on the Renovate repository and opening a pull request.

Note

Replacement updates will never be grouped. Lock file maintenance will never be grouped with other dependency updates.

"},{"location":"configuration-options/#packagerulesreplacementnametemplate","title":"packageRules.replacementNameTemplate","text":"

Controls what the replacement package name.

Name Value type string default \"{{{packageName}}}\" parents packageRules supportsTemplating true

This option supports Renovate's template syntax

See templates for available variables and helpers.

Note

replacementName will take precedence if used within the same package rule.

Use the replacementNameTemplate config option to control the replacement name.

Use the triple brace {{{ }}} notation to avoid Handlebars escaping any special characters.

For example, the following package rule can be used to replace the registry for docker images:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"docker.io/**\"],\n      \"replacementNameTemplate\": \"{{{replace 'docker\\\\.io/' 'ghcr.io/' packageName}}}\"\n    }\n  ]\n}\n

Or, to add a registry prefix to any docker images that do not contain an explicit registry:

{\n  \"packageRules\": [\n    {\n      \"description\": \"official images\",\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"/^[a-z-]+$/\"],\n      \"replacementNameTemplate\": \"some.registry.org/library/{{{packageName}}}\"\n    },\n    {\n      \"description\": \"non-official images\",\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"/^[a-z-]+/[a-z-]+$/\"],\n      \"replacementNameTemplate\": \"some.registry.org/{{{packageName}}}\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesreplacementversion","title":"packageRules.replacementVersion","text":"

The version of the new dependency that replaces the old deprecated dependency.

Name Value type string parents packageRules default null

This config option only works with some managers. We're working to support more managers, subscribe to issue renovatebot/renovate#14149 to follow our progress. For a list of managers which do not support replacement read the replacementName config option docs.

Use the replacementVersion config option to set the version of a replacement package. Must be used with replacementName. For example to replace the npm package jade with version 2.0.0 of the package pug:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"matchPackageNames\": [\"jade\"],\n      \"replacementName\": \"pug\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulesreplacementversiontemplate","title":"packageRules.replacementVersionTemplate","text":"

Template field for the version of the new dependency that replaces the old deprecated dependency.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Note

replacementVersion will take precedence if used within the same package rule.

Use the replacementVersionTemplate config option to control the replacement version.

For example, the following package rule can be used to replace version with major-only version (17.0.1 \u2192 17):

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"dummy\"],\n      \"replacementVersionTemplate\": \"{{ lookup (split currentValue '.') 0 }}\"\n    }\n  ]\n}\n
"},{"location":"configuration-options/#packagerulessourcedirectory","title":"packageRules.sourceDirectory","text":"

The source directory in which the package is present at its source.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Use this field to set the directory in which the package is present at the source of the package.

Setting the source directory for the kube-prometheus package from bitnami charts repo
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"dummy\"],\n      \"sourceUrl\": \"https://github.com/bitnami/charts\",\n      \"sourceDirectory\": \"bitnami/kube-prometheus\"\n    }\n  ]\n}\n

Note

sourceDirectory should be only be configured along with sourceUrl.

"},{"location":"configuration-options/#packagerulessourceurl","title":"packageRules.sourceUrl","text":"

The source URL of the package.

Name Value type string parents packageRules supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

Use this field to set the source URL for a package, including overriding an existing one. Source URLs are necessary to link to the source of the package and in order to look up changelogs.

The sourceUrl field supports template compilation, allowing you to dynamically construct URLs based on package information.

Setting the source URL for the dummy package
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"dummy\"],\n      \"sourceUrl\": \"https://github.com/org/dummy\"\n    }\n  ]\n}\n
Using templates to construct source URLs for OpenTofu providers
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"terraform-provider\"],\n      \"registryUrls\": [\"https://registry.opentofu.org\"],\n      \"sourceUrl\": \"https://github.com/{{replace '/' '/terraform-provider-' packageName}}\"\n    }\n  ]\n}\n

In the example above, a package name like hashicorp/aws will be transformed to https://github.com/hashicorp/terraform-provider-aws.

"},{"location":"configuration-options/#patch","title":"patch","text":"

Configuration to apply when an update type is patch.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object mergeable true env RENOVATE_PATCH

Add to this object if you wish to define rules that apply only to patch updates.

"},{"location":"configuration-options/#pin","title":"pin","text":"

Configuration to apply when an update type is pin.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"rebaseWhen\": \"behind-base-branch\",\n  \"groupName\": \"Pin Dependencies\",\n  \"groupSlug\": \"pin-dependencies\",\n  \"commitMessageAction\": \"Pin\",\n  \"group\": {\"commitMessageTopic\": \"dependencies\", \"commitMessageExtra\": \"\"}\n}\n
mergeable true env RENOVATE_PIN

Add to this object if you wish to define rules that apply only to PRs that pin dependencies.

"},{"location":"configuration-options/#pindigest","title":"pinDigest","text":"

Configuration to apply when pinning a digest (no change in tag/version).

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"groupName\": \"Pin Dependencies\",\n  \"groupSlug\": \"pin-dependencies\",\n  \"commitMessageAction\": \"Pin\",\n  \"group\": {\"commitMessageTopic\": \"dependencies\", \"commitMessageExtra\": \"\"}\n}\n
mergeable true env RENOVATE_PIN_DIGEST

Add to this object if you wish to define rules that apply only to PRs that pin digests.

"},{"location":"configuration-options/#pindigests","title":"pinDigests","text":"

Whether to add digests to Dockerfile source images.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default false cli --pin-digests env RENOVATE_PIN_DIGESTS

If enabled Renovate will pin Docker images or GitHub Actions by means of their SHA256 digest and not only by tag so that they are immutable.

"},{"location":"configuration-options/#platformautomerge","title":"platformAutomerge","text":"

Controls if platform-native auto-merge is used.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true supportedPlatforms azure, bitbucket-server, forgejo, gitea, github, gitlab cli --platform-automerge env RENOVATE_PLATFORM_AUTOMERGE

Note

If you use the default platformAutomerge=true then you should enable your Git hosting platform's capabilities to enforce test passing before PR merge. If you don't do this, the platform might merge Renovate PRs even if the repository's tests haven't started, are in still in progress, or possibly even when they have failed. On GitHub this is called \"Require status checks before merging\", which you can find in the \"Branch protection rules\" section of the settings for your repository. GitHub docs, about protected branches GitHub docs, require status checks before merging If you're using another platform, search their documentation for a similar feature.

Note

If you mark renovate/artifacts as a required status check in your branch protection rules, you must also set statusCheckWhen.artifactError to \"always\". The default \"failed\" only sets the check when artifact updates fail, so a required check rule would block every PR that has no artifact errors (the check would never appear). Setting it to \"always\" makes Renovate report green when there are no errors and red when there are, which is what branch protection requires.

If you have enabled automerge and set automergeType=pr in the Renovate config, then leaving platformAutomerge as true speeds up merging via the platform's native automerge functionality.

Where supported, platform-native automerge uses automergeStrategy to select the merge method.

On Bitbucket Server, GitHub and GitLab, Renovate re-enables the PR for platform-native automerge whenever it's rebased.

platformAutomerge will configure PRs to be merged after all (if any) branch policies have been met. This option is available for Azure, Bitbucket Server, Forgejo, Gitea, GitHub and GitLab. It falls back to Renovate-based automerge if the platform-native automerge is not available.

You can also fine-tune the behavior by setting packageRules if you want to use it selectively (e.g. per-package).

Note that the outcome of rebaseWhen=auto can differ when platformAutomerge=true. Normally when you set rebaseWhen=auto Renovate rebases any branch that's behind the base branch automatically, and some people rely on that. This behavior is no longer guaranteed when platformAutomerge is true because the platform might automerge a branch which is not up-to-date. For example, GitHub might automerge a Renovate branch even if it's behind the base branch at the time.

Please check platform specific docs for version requirements.

To learn how to use GitHub's Merge Queue feature with Renovate, read our GitHub Merge Queue docs.

"},{"location":"configuration-options/#platformcommit","title":"platformCommit","text":"

Use platform API to perform commits instead of using Git directly.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"auto\" allowedValues 
[\"auto\", \"disabled\", \"enabled\"]\n
supportedPlatforms github cli --platform-commit env RENOVATE_PLATFORM_COMMIT

Only use this option if you run Renovate as a GitHub App. It does not apply when you use a Personal Access Token as credential.

When platformCommit is enabled, Renovate will create commits with GitHub's API instead of using git directly. This way Renovate can use GitHub's Commit signing support for bots and other GitHub Apps feature.

Note

When using platform commits, GitHub determines the git author string to use and Renovate's own gitAuthor is ignored.

"},{"location":"configuration-options/#postupdateoptions","title":"postUpdateOptions","text":"

Enable post-update options to be run after package/artifact updating.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string allowedValues 
[\n  \"bundlerConservative\",\n  \"composerWithAll\",\n  \"composerNoMinimalChanges\",\n  \"dotnetWorkloadRestore\",\n  \"gomodMassage\",\n  \"gomodTidy\",\n  \"gomodTidy1.17\",\n  \"gomodTidyAll\",\n  \"gomodTidyE\",\n  \"gomodUpdateImportPaths\",\n  \"gomodSkipVendor\",\n  \"gomodVendor\",\n  \"goGenerate\",\n  \"helmUpdateSubChartArchives\",\n  \"kustomizeInflateHelmCharts\",\n  \"npmDedupe\",\n  \"npmInstallTwice\",\n  \"pnpmDedupe\",\n  \"yarnDedupeFewer\",\n  \"yarnDedupeHighest\"\n]\n
mergeable true default []"},{"location":"configuration-options/#bundlerconservative","title":"bundlerConservative","text":"

Enable conservative mode for bundler (Ruby dependencies). This will only update the immediate dependency in the lockfile instead of all subdependencies.

"},{"location":"configuration-options/#composernominimalchanges","title":"composerNoMinimalChanges","text":"

Run composer update with no --minimal-changes flag (does not affect lock file maintenance, which will never use --minimal-changes).

"},{"location":"configuration-options/#composerwithall","title":"composerWithAll","text":"

Run composer update with --with-all-dependencies flag instead of the default --with-dependencies.

"},{"location":"configuration-options/#dotnetworkloadrestore","title":"dotnetWorkloadRestore","text":"

Run dotnet workload restore before dotnet restore commands.

"},{"location":"configuration-options/#gogenerate","title":"goGenerate","text":"

Run go generate ./.... This will then commit any files which were added or modified by running go generate.

Note this will not install any other tools as part of the process. See Go Tool usage for how to incorporate these as part of your build process.

This runs after vendoring, if vendoring was required.

Note

In order for this option to function, the global configuration option allowedUnsafeExecutions must include goGenerate.

"},{"location":"configuration-options/#gomodmassage","title":"gomodMassage","text":"

Enable massaging replace directives before calling go commands.

"},{"location":"configuration-options/#gomodskipvendor","title":"gomodSkipVendor","text":"

Never run go mod vendor after Go module updates.

"},{"location":"configuration-options/#gomodtidy","title":"gomodTidy","text":"

Run go mod tidy after Go module updates. This is implicitly enabled for major module updates when gomodUpdateImportPaths is enabled.

"},{"location":"configuration-options/#gomodtidy117","title":"gomodTidy1.17","text":"

Run go mod tidy -compat=1.17 after Go module updates.

"},{"location":"configuration-options/#gomodtidyall","title":"gomodTidyAll","text":"

After running go mod tidy on the updated module, also run it on every other go.mod which references that module through a local replace directive, in dependency order. Use this in Go monorepos, where an update to a shared module must also reach the go.sum files of the modules which depend on it. Implies gomodTidy, and needs Go 1.20 or later. Avoid combining this with gomodMassage, which comments out the relative replace directives that this option follows.

"},{"location":"configuration-options/#gomodtidye","title":"gomodTidyE","text":"

Run go mod tidy -e after Go module updates.

"},{"location":"configuration-options/#gomodupdateimportpaths","title":"gomodUpdateImportPaths","text":"

Update source import paths on major module updates, using mod.

"},{"location":"configuration-options/#gomodvendor","title":"gomodVendor","text":"

Always run go mod vendor after Go module updates even if vendor files aren't detected.

"},{"location":"configuration-options/#helmupdatesubchartarchives","title":"helmUpdateSubChartArchives","text":"

Update subchart archives in the /charts folder.

"},{"location":"configuration-options/#kustomizeinflatehelmcharts","title":"kustomizeInflateHelmCharts","text":"

Inflate updated helm charts referenced in the kustomization.

"},{"location":"configuration-options/#npmdedupe","title":"npmDedupe","text":"

Run npm install with --prefer-dedupe for npm >= 7 or npm dedupe after package-lock.json update for npm <= 6.

"},{"location":"configuration-options/#npminstalltwice","title":"npmInstallTwice","text":"

Run npm install commands twice to work around bugs where npm generates invalid lock files if run only once.

During lock file maintenance, Renovate always runs npm install twice, even without this option, because regenerating a lock file from scratch is known to need a second pass.

"},{"location":"configuration-options/#pnpmdedupe","title":"pnpmDedupe","text":"

Run pnpm dedupe after pnpm-lock.yaml updates.

"},{"location":"configuration-options/#yarndedupefewer","title":"yarnDedupeFewer","text":"

Run yarn-deduplicate --strategy fewer after yarn.lock updates.

"},{"location":"configuration-options/#yarndedupehighest","title":"yarnDedupeHighest","text":"

Run yarn-deduplicate --strategy highest (yarn dedupe --strategy highest for Yarn >=2.2.0) after yarn.lock updates.

"},{"location":"configuration-options/#postupgradetasks","title":"postUpgradeTasks","text":"

Post-upgrade tasks that are executed before a commit is made by Renovate.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object default 
{\n  \"commands\": [],\n  \"fileFilters\": [],\n  \"executionMode\": \"update\",\n  \"installTools\": {}\n}\n
cli --post-upgrade-tasks env RENOVATE_POST_UPGRADE_TASKS

Post-upgrade tasks are commands that are executed by Renovate after a dependency has been updated but before the commit is created. The intention is to run any other command line tools that would modify existing files or generate new files when a dependency changes.

Post-upgrade tasks are blocked by default for security reasons, so the admin of Renovate needs to choose whether to allow specific commands or any commands to be run - it depends on how much they trust their users in repos.

Tip

In Mend-hosted Renovate apps, commands remain blocked by default, but depending on your plan, you have more control over this.

Each command must match at least one of the patterns defined in allowedCommands (a global-only configuration option) in order to be executed. If the list of allowed tasks is empty then no tasks will be executed.

e.g.

{\n  \"postUpgradeTasks\": {\n    \"commands\": [\"tslint --fix\"],\n    \"fileFilters\": [\"yarn.lock\", \"**/*.js\"],\n    \"executionMode\": \"update\"\n  }\n}\n

The postUpgradeTasks configuration consists of four fields:

"},{"location":"configuration-options/#postupgradetaskscommands","title":"postUpgradeTasks.commands","text":"

A list of post-upgrade commands that are executed before a commit is made by Renovate.

Name Value type array subType string parents postUpgradeTasks supportsTemplating true env RENOVATE_COMMANDS default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

A list of commands that are executed after Renovate has updated a dependency but before the commit is made.

You can use Handlebars templating in these commands. They will be compiled prior to the comparison against allowedCommands.

Note

Do not use git add in your commands to add new files to be tracked, add them by including them in your postUpgradeTasks.fileFilters instead.

"},{"location":"configuration-options/#postupgradetasksdatafiletemplate","title":"postUpgradeTasks.dataFileTemplate","text":"

A template to create post-upgrade command data file from.

Name Value type string parents postUpgradeTasks supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

A template to create data file from. The template uses the same format as commands. The data file is created as a temporary file and the path to the data file is stored in the RENOVATE_POST_UPGRADE_COMMAND_DATA_FILE environment variable avaliable to each post-upgrade command. The primary purpose of the data file is to store some update information in a file which would be consumed from a post-upgrade command. This is particularly useful if a post-upgrade command needs to have a long line of arguments. Example:

{\n  \"postUpgradeTasks\": {\n    \"commands\": [\n      \"my-script.py --data-file \\\"$RENOVATE_POST_UPGRADE_COMMAND_DATA_FILE\\\"\"\n    ],\n    \"dataFileTemplate\": \"[{{#each upgrades}}{\\\"depName\\\": \\\"{{{depName}}}\\\", \\\"currentValue\\\": \\\"{{{currentValue}}}\\\", \\\"newValue\\\": \\\"{{{newValue}}}\\\"}{{#unless @last}},{{\\/unless}}{{\\/each}}]\"\n  }\n}\n

Note

dataFileTemplate is ignored if there is no commands configured.

"},{"location":"configuration-options/#postupgradetasksexecutionmode","title":"postUpgradeTasks.executionMode","text":"

Controls when the post upgrade tasks run: on every update, or once per upgrade branch.

Name Value type string parents postUpgradeTasks allowedValues 
[\"update\", \"branch\"]\n
default \"update\" env RENOVATE_EXECUTION_MODE

Defaults to update, but can also be set to branch. This sets the level the postUpgradeTask runs on, if set to update the postUpgradeTask will be executed for every dependency on the branch. If set to branch the postUpgradeTask is executed for the whole branch.

"},{"location":"configuration-options/#postupgradetasksfilefilters","title":"postUpgradeTasks.fileFilters","text":"

Files that match the glob pattern will be committed after running a post-upgrade task.

Name Value type array subType string parents postUpgradeTasks default 
[\"**/*\"]\n
env RENOVATE_FILE_FILTERS

A list of glob-style matchers that determine which files will be included in the final commit made by Renovate. Dotfiles are included.

Optional field which defaults to any non-ignored file in the repo (**/* glob pattern). Specify a custom value for this if you wish to exclude certain files which are modified by your postUpgradeTasks and you don't want committed.

"},{"location":"configuration-options/#postupgradetasksinstalltools","title":"postUpgradeTasks.installTools","text":"

Install tools before executing commands

Name Value type object parents postUpgradeTasks mergeable false freeChoice true env RENOVATE_INSTALL_TOOLS

Whether to install any additional tools dynamically before executing the commands.

The possible tool names that are known by Containerbase are:

Note

When using binarySource=global, the installTools options do not take effect.

For example:

Adding a tool requirement
{\n  \"postUpgradeTasks\": {\n    \"commands\": [\"make generate\"],\n    \"installTools\": {\n      \"golang\": {}\n    }\n  }\n}\n
Utilising constraints for tool requirements
{\n  \"constraints\": {\n    \"node\": \"^18.0.0 || >=20.0.0\"\n  },\n  \"postUpgradeTasks\": {\n    \"commands\": [\"npm install\", \"npm run update-readme\"],\n    \"installTools\": {\n      \"node\": {}\n    }\n  }\n}\n

Note

The tool objects inside installTools currently do not expose any additional configurability.

"},{"location":"configuration-options/#postupgradetasksworkingdirtemplate","title":"postUpgradeTasks.workingDirTemplate","text":"

A template describing the working directory in which post-upgrade tasks should be executed.

Name Value type string parents postUpgradeTasks supportsTemplating true default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

A template describing the working directory in which the commands should be executed, relative to the repository root. If the template evaluates to a false value, then the command will be executed from the root of the repository. Example:

{\n  \"postUpgradeTasks\": {\n    \"commands\": [\"my-script.py\"],\n    \"workingDirTemplate\": \"{{{packageFileDir}}}\"\n  }\n}\n
"},{"location":"configuration-options/#prbodycolumns","title":"prBodyColumns","text":"

List of columns to use in PR bodies.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string default 
[\"Package\", \"Type\", \"Update\", \"Change\", \"Pending\"]\n
cli --pr-body-columns env RENOVATE_PR_BODY_COLUMNS

Use this array to provide a list of column names you wish to include in the PR tables.

Adding the package file name to the table
{\n  \"prBodyColumns\": [\n    \"Package\",\n    \"Update\",\n    \"Type\",\n    \"New value\",\n    \"Package file\",\n    \"References\"\n  ]\n}\n

Note

\"Package file\" is predefined in the default prBodyDefinitions object so does not require a definition before it can be used.

"},{"location":"configuration-options/#prbodydefinitions","title":"prBodyDefinitions","text":"

Table column definitions to use in PR tables.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object freeChoice true mergeable true default 
{\n  \"Package\": \"{{{depNameLinked}}}{{#if newName}}{{#unless (equals depName newName)}} \u2192 {{{newNameLinked}}}{{/unless}}{{/if}}\",\n  \"Type\": \"{{{depType}}}\",\n  \"Update\": \"{{{updateType}}}\",\n  \"Current value\": \"{{{currentValue}}}\",\n  \"New value\": \"{{{newValue}}}\",\n  \"Change\": \"`{{{displayFrom}}}` \u2192 `{{{displayTo}}}`\",\n  \"Pending\": \"{{{displayPending}}}\",\n  \"References\": \"{{{references}}}\",\n  \"Package file\": \"{{{packageFile}}}\",\n  \"Age\": \"{{#if newVersion}}![age](https://developer.mend.io/api/mc/badges/age/{{datasource}}/{{replace '/' '%2f' packageName}}/{{{newVersion}}}?slim=true){{/if}}\",\n  \"Adoption\": \"{{#if newVersion}}![adoption](https://developer.mend.io/api/mc/badges/adoption/{{datasource}}/{{replace '/' '%2f' packageName}}/{{{newVersion}}}?slim=true){{/if}}\",\n  \"Passing\": \"{{#if newVersion}}![passing](https://developer.mend.io/api/mc/badges/compatibility/{{datasource}}/{{replace '/' '%2f' packageName}}/{{{currentVersion}}}/{{{newVersion}}}?slim=true){{/if}}\",\n  \"Confidence\": \"{{#if newVersion}}![confidence](https://developer.mend.io/api/mc/badges/confidence/{{datasource}}/{{replace '/' '%2f' packageName}}/{{{currentVersion}}}/{{{newVersion}}}?slim=true){{/if}}\"\n}\n
cli --pr-body-definitions env RENOVATE_PR_BODY_DEFINITIONS

You can configure this object to either:

Modifying the default value for the Package column to put it inside a code block
{\n  \"prBodyDefinitions\": {\n    \"Package\": \"`{{{depName}}}`\"\n  }\n}\n
Adding a custom Sourcegraph column definition
{\n  \"prBodyDefinitions\": {\n    \"Sourcegraph\": \"[![code search for \\\"{{{depName}}}\\\"](https://sourcegraph.com/search/badge?q=repo:%5Egithub%5C.com/{{{repository}}}%24+case:yes+-file:package%28-lock%29%3F%5C.json+{{{depName}}}&label=matches)](https://sourcegraph.com/search?q=repo:%5Egithub%5C.com/{{{repository}}}%24+case:yes+-file:package%28-lock%29%3F%5C.json+{{{depName}}})\"\n  },\n  \"prBodyColumns\": [\n    \"Package\",\n    \"Update\",\n    \"New value\",\n    \"References\",\n    \"Sourcegraph\"\n  ]\n}\n

Tip

Columns must also be included in the prBodyColumns array in order to be used, so that's why it's included above in the example.

"},{"location":"configuration-options/#prbodyheadingdefinitions","title":"prBodyHeadingDefinitions","text":"

Table header definitions to use in PR tables.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object freeChoice true mergeable true default 
{\n  \"Age\": \"[Age](https://docs.renovatebot.com/merge-confidence/)\",\n  \"Adoption\": \"[Adoption](https://docs.renovatebot.com/merge-confidence/)\",\n  \"Passing\": \"[Passing](https://docs.renovatebot.com/merge-confidence/)\",\n  \"Confidence\": \"[Confidence](https://docs.renovatebot.com/merge-confidence/)\"\n}\n
cli --pr-body-heading-definitions env RENOVATE_PR_BODY_HEADING_DEFINITIONS

You can configure this object to modify the table headers present in the PR body. This can include Markdown or any other syntax that the platform supports.

Modifying the default value for the Package and Age table headers
{\n  \"prBodyHeadingDefinitions\": {\n    \"Package\": \"\ud83d\udce6 Package\",\n    \"Age\": \"[Age](https://docs.renovatebot.com/merge-confidence)\"\n  },\n  \"prBodyColumns\": [\"Package\", \"Age\"]\n}\n

Tip

Columns must also be included in the prBodyColumns array in order to be used, so that's why it's included above in the example.

Note

Templating is not supported for this option.

"},{"location":"configuration-options/#prbodynotes","title":"prBodyNotes","text":"

List of extra notes or templates to include in the Pull Request body.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string mergeable true supportsTemplating true cli --pr-body-notes env RENOVATE_PR_BODY_NOTES default []

This option supports Renovate's template syntax

See templates for available variables and helpers.

Use this field to add custom content inside PR bodies, including conditionally.

Adding an extra Warning to major updates
{\n  \"prBodyNotes\": [\"{{#if isMajor}}:warning: MAJOR MAJOR MAJOR :warning:{{/if}}\"]\n}\n
"},{"location":"configuration-options/#prbodytemplate","title":"prBodyTemplate","text":"

Pull Request body template. Controls which sections are rendered in the body of the pull request.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"{{{header}}}{{{table}}}{{{warnings}}}{{{notes}}}{{{changelogs}}}{{{configDescription}}}{{{controls}}}{{{footer}}}\" supportsTemplating true env RENOVATE_PR_BODY_TEMPLATE

This option supports Renovate's template syntax

See templates for available variables and helpers.

The available sections are:

"},{"location":"configuration-options/#prconcurrentlimit","title":"prConcurrentLimit","text":"

Limit to a maximum of x concurrent branches/PRs. 0 means no limit.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 10 cli --pr-concurrent-limit env RENOVATE_PR_CONCURRENT_LIMIT

This setting - if enabled - limits Renovate to a maximum of x concurrent PRs open at any time.

This limit is enforced on a per-repository basis.

Note

Renovate always creates security PRs, even if the concurrent PR limit is already reached. Security PRs have [SECURITY] in their PR title.

"},{"location":"configuration-options/#prcreation","title":"prCreation","text":"

When to create the PR for a branch.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"immediate\", \"not-pending\", \"status-success\", \"approval\"]\n
default \"immediate\" cli --pr-creation env RENOVATE_PR_CREATION

This setting tells Renovate when to create PRs:

When prCreation is set to immediate, you'll get a Pull Request and possible associated notification right away when a new update is available. You'll have to wait until the checks have been performed, before you can decide if you want to merge the PR.

When prCreation is set to not-pending, Renovate creates the PR only once all tests have passed or failed. When you get the PR notification, you can take action immediately, as you have the full test results. If there are no checks associated, Renovate will create the PR once prNotPendingHours have elapsed since the branch's latest commit (default: 25 hours).

not-pending can stall PR creation when there are no branch-level checks

A branch with no external status checks is reported as pending, so not-pending never sees checks \"complete\" and instead relies on the prNotPendingHours fallback. That fallback is measured from the branch's latest commit, not from when the branch was created, so anything that rewrites the branch (rebase, re-lock, etc.) restarts the timer. On repositories whose branches are rebased or re-locked more often than prNotPendingHours, PRs can be deferred indefinitely. This commonly happens when CI only runs on pull_request events, so bare Renovate branches carry no checks. If you rely on minimumReleaseAge/internalChecksFilter for the \"wait\" behavior, set internalChecksAsSuccess=true so the green internal stability check counts as success and the branch can go green without external checks, or use prCreation=immediate instead.

When prCreation is set to status-success, Renovate creates the PR only if all tests have passed. When a branch remains without PR due to a failing test: select the corresponding PR from the Dependency Dashboard, and push your fixes to the branch.

When prCreation is set to approval, Renovate creates the PR only when approved via the Dependency Dashboard. Renovate still creates the branch immediately.

Note

For all cases of non-immediate PR creation, Renovate doesn't run instantly once tests complete. Instead, Renovate create the PR on its next run after the relevant tests have completed, so there will be some delay.

Warning

If you set prCreation=approval you must not use dependencyDashboardApproval=true!

"},{"location":"configuration-options/#prfooter","title":"prFooter","text":"

Text added here will be placed last in the PR body, with a divider separator before it.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).\" supportsTemplating true cli --pr-footer env RENOVATE_PR_FOOTER

This option supports Renovate's template syntax

See templates for available variables and helpers.

"},{"location":"configuration-options/#prheader","title":"prHeader","text":"

Text added here will be placed first in the PR body.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true cli --pr-header env RENOVATE_PR_HEADER default null

This option supports Renovate's template syntax

See templates for available variables and helpers.

"},{"location":"configuration-options/#prhourlylimit","title":"prHourlyLimit","text":"

Rate limit PRs to maximum x created per hour. 0 means no limit.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 2 cli --pr-hourly-limit env RENOVATE_PR_HOURLY_LIMIT

This config option slows down the rate at which Renovate creates PRs.

Slowing Renovate down can be handy when you're onboarding a repository with a lot of dependencies. What may happen if you don't set a prHourlyLimit:

  1. Renovate creates an Onboarding PR
  2. You merge the onboarding PR to activate Renovate
  3. Renovate creates a \"Pin Dependencies\" PR (if needed)
  4. You merge the \"Pin Dependencies\" PR
  5. Renovate creates every single upgrade PR needed, which can be a lot

The above may cause:

To prevent these problems you can set prHourlyLimit to a value like 1 or 2. Renovate will only create that many PRs within each hourly period (:00 through :59). You still get all the PRs in a reasonable time, perhaps over a day or so. Now you can merge the PRs at a do-able rate, once the tests pass.

Tip

The prHourlyLimit setting does not limit the number of concurrently open PRs, only the rate at which PRs are created. The prHourlyLimit setting is enforced on a per-repository basis.

"},{"location":"configuration-options/#prnotpendinghours","title":"prNotPendingHours","text":"

Timeout in hours for when prCreation=not-pending.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer default 25 cli --pr-not-pending-hours env RENOVATE_PR_NOT_PENDING_HOURS

If you configure prCreation=not-pending, then Renovate will wait until tests are non-pending (all pass or at least one fails) before creating PRs. However there are cases where PRs may remain in pending state forever, e.g. absence of tests or status checks that are configure to pending indefinitely. This is why we configured an upper limit for how long we wait until creating a PR.

Note

If the option minimumReleaseAge is non-zero then Renovate disables the prNotPendingHours functionality.

"},{"location":"configuration-options/#prtitle","title":"prTitle","text":"

Pull Request title template. Inherits from commitMessage if null.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string supportsTemplating true env RENOVATE_PR_TITLE

This option supports Renovate's template syntax

See templates for available variables and helpers.

This feature has been deprecated

Direct editing of prTitle is now deprecated. Instead use config options like commitMessageAction, commitMessageExtra, and so on, as they will be passed through to prTitle.

The PR title is important for some of Renovate's matching algorithms (e.g. determining whether to recreate a PR or not) so ideally don't modify it much.

"},{"location":"configuration-options/#prtitlestrict","title":"prTitleStrict","text":"

Whether to bypass appending extra context to the Pull Request title.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false env RENOVATE_PR_TITLE_STRICT

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

There are certain scenarios where the default behavior appends extra context to the PR title.

These scenarios include if a baseBranch or if there is a grouped update and either separateMajorMinor or separateMinorPatch is true.

Using this option allows you to skip these default behaviors and use other templating methods to control the format of the PR title.

"},{"location":"configuration-options/#printconfig","title":"printConfig","text":"

If enabled, Renovate logs the fully resolved config for each repository, plus the fully resolved presets.

Name Value scopes repo type boolean default false cli --print-config env RENOVATE_PRINT_CONFIG

This option is useful for troubleshooting, particularly if using presets. e.g. run renovate foo/bar --print-config > config.log and the fully-resolved config will be included in the log file.

"},{"location":"configuration-options/#prunebranchafterautomerge","title":"pruneBranchAfterAutomerge","text":"

Set to true to enable branch pruning after automerging.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true cli --prune-branch-after-automerge env RENOVATE_PRUNE_BRANCH_AFTER_AUTOMERGE

By default Renovate deletes, or \"prunes\", the branch after automerging. Set pruneBranchAfterAutomerge to false to keep the branch after automerging.

"},{"location":"configuration-options/#prunestalebranches","title":"pruneStaleBranches","text":"

Set to false to disable pruning stale branches.

Name Value scopes repo type boolean default true cli --prune-stale-branches env RENOVATE_PRUNE_STALE_BRANCHES

By default, Renovate will \"prune\" any of its own branches/PRs which it thinks are no longer needed. Such branches are referred to as \"stale\", and may be the result of Open, Merged, or Closed/Ignored PRs. It usually doesn't know why they're there, instead it simply knows that it has no need for them.

If a branch appears stale but has been modified by a different git author, then Renovate won't delete the branch or autoclose any associated PR. Instead, it will update the title to append \" - abandoned\" plus add a comment noting that autoclosing is skipped. Read the Abandoned PRs docs to learn more.

If a branch appears stale and hasn't been modified, then:

You can configure pruneStaleBranches=false to disable deleting orphan branches and autoclosing PRs, but then you will be responsible for such branch/PR \"cleanup\" so it is not recommended.

"},{"location":"configuration-options/#rangestrategy","title":"rangeStrategy","text":"

Determines how to modify or update existing ranges.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string default \"auto\" allowedValues 
[\"auto\", \"pin\", \"bump\", \"replace\", \"widen\", \"update-lockfile\", \"in-range-only\"]\n

Behavior:

Renovate's \"auto\" strategy works like this for npm:

  1. Widen peerDependencies
  2. If an existing range already ends with an \"or\" operator like \"^1.0.0 || ^2.0.0\", then Renovate widens it into \"^1.0.0 || ^2.0.0 || ^3.0.0\"
  3. Otherwise, if the update is outside the existing range, Renovate replaces the range. So \"^2.0.0\" is replaced by \"^3.0.0\"
  4. Finally, if the update is in-range, Renovate will update the lockfile with the new exact version.

By default, Renovate assumes that if you are using ranges then it's because you want them to be wide/open. Renovate won't deliberately \"narrow\" any range by increasing the semver value inside.

For example, if your package.json specifies a value for left-pad of ^1.0.0 and the latest version on npmjs is 1.2.0, then Renovate won't change anything because 1.2.0 satisfies the range. If instead you'd prefer to be updated to ^1.2.0 in cases like this, then configure rangeStrategy to bump in your Renovate config.

This feature supports caret (^) and tilde (~) ranges only, like ^1.0.0 and ~1.0.0.

The in-range-only strategy may be useful if you want to leave the package file unchanged and only do update-lockfile within the existing range. The in-range-only strategy behaves like update-lockfile, but discards any updates where the new version of the dependency is not equal to the current version. We recommend you avoid using the in-range-only strategy unless you strictly need it. Using the in-range-only strategy may result in you being multiple releases behind without knowing it.

"},{"location":"configuration-options/#rebaselabel","title":"rebaseLabel","text":"

Label to request a rebase from Renovate.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"rebase\" cli --rebase-label env RENOVATE_REBASE_LABEL

On supported platforms it is possible to add a label to a PR to manually request Renovate to recreate/rebase it. By default this label is \"rebase\" but you can configure it to anything you want by changing this rebaseLabel field.

"},{"location":"configuration-options/#rebasewhen","title":"rebaseWhen","text":"

Controls when Renovate rebases an existing branch.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"auto\", \"never\", \"conflicted\", \"behind-base-branch\", \"automerging\"]\n
default \"auto\" cli --rebase-when env RENOVATE_REBASE_WHEN

Possible values and meanings:

rebaseWhen=conflicted is not recommended if you have enabled Renovate automerge, because:

It is also recommended to avoid rebaseWhen=never as it can result in conflicted branches with outdated PR descriptions and/or status checks.

Avoid setting rebaseWhen=never and then also setting prCreation=not-pending as this can prevent creation of PRs.

"},{"location":"configuration-options/#recreatewhen","title":"recreateWhen","text":"

Recreate PRs even if same ones were closed previously.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"auto\" allowedValues 
[\"auto\", \"always\", \"never\"]\n
cli --recreate-when env RENOVATE_RECREATE_WHEN

This feature used to be called recreateClosed.

By default, Renovate detects if it proposed an update to a project before, and will not propose the same update again. For example the Webpack 3.x case described in the separateMajorMinor documentation. You can use recreateWhen to customize this behavior down to a per-package level. For example we override it to always in the following cases where branch names and PR titles must be reused:

You can select which behavior you want from Renovate:

We recommend that you stick with the default setting for this option. Only change this setting if you really need to.

"},{"location":"configuration-options/#registryaliases","title":"registryAliases","text":"

Aliases for registries.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group mergeable true type object additionalProperties 
{\"type\": \"string\"}\n
supportedManagers ansible, argocd, bitbucket-pipelines, buildpacks, crossplane, crow, devcontainer, docker-compose, dockerfile, droneci, gitlabci, helm-requirements, helmfile, helmsman, helmv3, kubernetes, kustomize, maven, terraform, vendir, woodpecker cli --registry-aliases env RENOVATE_REGISTRY_ALIASES previouslyKnownAs 
[\"aliases\"]\n

You can use the registryAliases object to set registry aliases. Renovate applies all registryAliases objects, from top to bottom. The aliases support variables with default values (using the :- syntax) which can be useful for Docker Compose files.

This feature works with the following managers:

Setting generic aliases
{\n  \"registryAliases\": {\n    \"jfrogecosystem\": \"some.jfrog.mirror\",\n    \"jfrog.com\": \"some.jfrog.mirror\"\n  }\n}\n
Setting aliases for a specific Renovate manager only
{\n  \"gitlabci\": {\n    \"registryAliases\": {\n      \"$HARBOR_HOST/$HARBOR_PROJECT\": \"registry.example.com/proxy\",\n      \"$HARBOR_HOST/tools\": \"registry.example.com/tools\"\n    }\n  }\n}\n
Using variables with default values
{\n  \"registryAliases\": {\n    \"${CI_REGISTRY:-}\": \"my-registry.io\"\n  }\n}\n

Both image reference formats work:

The alias value works with or without a trailing slash.

If you are using a pull-through cache (for instance on Amazon Elastic Container Registry (ECR)):

Using a pull-through cache for public images
{\n  \"registryAliases\": {\n    \"12345612312.dkr.ecr.us-east-1.amazonaws.com/public-images-go-here/ghcr.io\": \"ghcr.io\",\n    \"12345612312.dkr.ecr.us-east-1.amazonaws.com/public-images-go-here/dockerhub\": \"docker.io\"\n  }\n}\n
"},{"location":"configuration-options/#registryurls","title":"registryUrls","text":"

List of URLs to try for dependency lookup. Package manager specific.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type array subType string default []

Usually Renovate is able to either (a) use the default registries for a datasource, or (b) automatically detect during the manager extract phase which custom registries are in use. In case there is a need to configure them manually, it can be done using this registryUrls field, typically using packageRules like so:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"registryUrls\": [\"https://docker.mycompany.domain\"]\n    }\n  ]\n}\n

The field supports multiple URLs but it is datasource-dependent on whether only the first is used or multiple.

In some situations managers can not derive which registry a given dependency comes from. In that case, managers skip it with skipReason: unknown-registry rather than look it up somewhere which may hold the wrong versions. When specifying registryUrls alongside a dependency with skipReason: unknown-registry, Renovate will use the configured registryUrls.

"},{"location":"configuration-options/#replacement","title":"replacement","text":"

Configuration to apply when replacing a dependency.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"branchTopic\": \"{{{depNameSanitized}}}-replacement\",\n  \"commitMessageAction\": \"Replace\",\n  \"commitMessageExtra\": \"with {{newName}} {{#if isMajor}}{{{prettyNewMajor}}}{{else}}{{#if isSingleVersion}}{{{prettyNewVersion}}}{{else}}{{{newValue}}}{{/if}}{{/if}}\",\n  \"prBodyNotes\": [\n    \"This is a special PR that replaces `{{{depName}}}` with the community suggested minimal stable replacement version.\"\n  ]\n}\n
mergeable true env RENOVATE_REPLACEMENT

Add to this object if you wish to define rules that apply only to PRs that replace dependencies.

"},{"location":"configuration-options/#replacementapproach","title":"replacementApproach","text":"

Select whether to perform a direct replacement or alias replacement.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"replace\", \"alias\"]\n
supportedManagers npm default \"replace\" cli --replacement-approach env RENOVATE_REPLACEMENT_APPROACH

For npm manager when replacementApproach=alias then instead of replacing \"foo\": \"1.2.3\" with \"@my/foo\": \"1.2.4\" we would instead replace it with \"foo\": \"npm:@my/foo@1.2.4\".

{\n  \"replacementApproach\": \"alias\"\n}\n
"},{"location":"configuration-options/#respectlatest","title":"respectLatest","text":"

Ignore versions newer than npm \"latest\" version.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default true cli --respect-latest env RENOVATE_RESPECT_LATEST

Similar to ignoreUnstable, this option controls whether to update to versions that are greater than the version tagged as latest in the repository. By default, renovate will update to a version greater than latest only if the current version is itself past latest.

Note

By default, respectLatest will be set to false for Maven results if a latest tag is found. This is because many Maven registries don't have a reliable latest tag - it just means whatever was last published. You need to override this to respectLatest=true in packageRules in order to use it.

"},{"location":"configuration-options/#reviewers","title":"reviewers","text":"

Requested reviewers for Pull Requests (either username or email address depending on the platform).

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --reviewers env RENOVATE_REVIEWERS default []

Must be valid usernames.

Required reviewers on Azure DevOps

To mark a reviewer as required on Azure DevOps, you must use the prefix required:.

For example: if the username or team name is bar then you would set the config option like this:

{\n  \"reviewers\": [\"required:bar\"]\n}\n

Required reviewers on Forgejo

If you're assigning a team to review on Forgejo, you must use the prefix team: and add the last part of the team name. Say the full team name on Forgejo is organization/foo, then you'd set the config option like this:

{\n  \"reviewers\": [\"team:foo\"]\n}\n

Required reviewers on GitHub

If you're assigning a team to review on GitHub, you must use the prefix team: and add the last part of the team name. Say the full team name on GitHub is @organization/foo, then you'd set the config option like this:

{\n  \"reviewers\": [\"team:foo\"]\n}\n

Please note that Reviewers are only added during creation of a PR, but are not modified afterwards.

Note

By default, Renovate will not assign reviewers and assignees to an automerge-enabled PR unless it fails status checks. By configuring assignAutomerge setting to true, Renovate will instead always assign reviewers and assignees for automerging PRs at time of creation.

"},{"location":"configuration-options/#reviewersfromcodeowners","title":"reviewersFromCodeOwners","text":"

Determine reviewers based on configured code owners and changes in PR.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --reviewers-from-code-owners env RENOVATE_REVIEWERS_FROM_CODE_OWNERS

If enabled Renovate tries to determine PR reviewers by matching rules defined in a CODEOWNERS file against the changes in the PR.

Read the docs for your platform for details on syntax and allowed file locations:

Please note that Reviewers are only added during creation of a PR, but are not modified afterwards.

"},{"location":"configuration-options/#reviewerssamplesize","title":"reviewersSampleSize","text":"

Take a random sample of given size from reviewers.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type integer cli --reviewers-sample-size env RENOVATE_REVIEWERS_SAMPLE_SIZE"},{"location":"configuration-options/#rollback","title":"rollback","text":"

Configuration to apply when rolling back a version.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type object default 
{\n  \"branchTopic\": \"{{{depNameSanitized}}}-rollback\",\n  \"commitMessageAction\": \"Roll back\",\n  \"semanticCommitType\": \"fix\"\n}\n
mergeable true env RENOVATE_ROLLBACK

Add to this object if you wish to define rules that apply only to PRs that roll back versions.

"},{"location":"configuration-options/#rollbackprs","title":"rollbackPrs","text":"

Create PRs to roll back versions if the current version is not found in the registry.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default false cli --rollback-prs env RENOVATE_ROLLBACK_PRS

There are times when a dependency version in use by a project gets removed from the registry. For some registries, existing releases or even whole packages can be removed or \"yanked\" at any time, while for some registries only very new or unused releases can be removed. Renovate's \"rollback\" feature exists to propose a downgrade to the next-highest release if the current release is no longer found in the registry.

Renovate does not create these rollback PRs by default, so this functionality needs to be opted-into. We recommend you do this selectively with packageRules and not globally.

"},{"location":"configuration-options/#schedule","title":"schedule","text":"

Limit branch creation to these times of day or week.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string cli --schedule default 
[\"at any time\"]\n

The schedule option allows you to define times of the day, week or month when you are willing to allow Renovate to create branches.

Setting a schedule does not itself cause or trigger Renovate to run. It's like putting a sign on your office which says \"DHL deliveries only accepted between 9-11am\". Such a sign won't cause DHL to come to your office only at 9-11am, instead it simply means that if they come at any other time of the day then they'll honor the sign and skip you. It also means that if they rarely attempt between 9-11am then you'll often get no deliveries in a day.

Similarly, if you set too restrictive of a Renovate schedule and the chance of Renovate running on your repo during those hours is low, then you might find your dependency updates regularly skipped. For this reason we recommend you allow a time window of at least 3-4 hours in any schedule, unless your instance of Renovate is expected to run more frequently than that.

Renovate supports the standard Cron syntax, as well as deprecated support for a subset of Later syntax. We recommend you always use Cron syntax, due to its superior testing and robustness. Config support questions are no longer accepted for Later syntax problems - you will be recommended to use Cron instead.

The default value for schedule is \"at any time\", which is functionally the same as declaring a null schedule or * * * * * with Cron. i.e. Renovate will create Pull Requests at any time of any day, as needed.

The easiest way to define a schedule is to use a preset if one of them fits your requirements. See Schedule presets for details and feel free to request a new one in the source repository if you think it would help others.

Here are some example schedules and their Cron equivalent:

English description Supported by Later? Cron syntax every weekend Yes * * * * 0,6 before 5:00am Yes * 0-4 * * * after 10pm and before 5am every weekday Yes * 22-23,0-4 * * 1-5 on friday and saturday Yes * * * * 5,6 every 3 months on the first day of the month Yes * * 1 */3 *

Note

For Cron schedules, you must use the * wildcard for the minutes value, as Renovate doesn't support minute granularity. And the cron schedule must have five comma separated parts.

One example might be that you don't want Renovate to run during your typical business hours, so that your build machines don't get clogged up testing package.json updates. You could then configure a schedule like this at the repository level:

{\n  \"description\": \"Schedule on weekdays at night (10 PM - 4 AM) and anytime on weekends\",\n  \"schedule\": [\"* 22-23,0-4 * * *\", \"* * * * 0,6\"]\n}\n

This would mean that Renovate can run for 7 hours each night, plus all the time on weekends. Note how the above example makes use of the \"OR\" logic of combining multiple schedules in the array.

Note

If both the day of the week and the day of the month are restricted in the schedule, then Renovate only runs when both the day of the month and day of the week match! For example: * * 1-7 * 4 means Renovate only runs on the first Thursday of the month.

It's common to use schedule in combination with timezone. You should configure updateNotScheduled=false if you want the schedule more strictly enforced so that updates to existing branches aren't pushed out of schedule. You can also configure automergeSchedule to limit the hours in which branches/PRs are automerged (if automerge is configured).

"},{"location":"configuration-options/#semanticcommitscope","title":"semanticCommitScope","text":"

Commit scope to use if Semantic Commits are enabled.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"deps\" nullable true supportsTemplating true cli --semantic-commit-scope env RENOVATE_SEMANTIC_COMMIT_SCOPE

This option supports Renovate's template syntax

See templates for available variables and helpers.

By default you will see Angular-style commit prefixes like \"chore(deps):\". If you wish to change it to something else like \"package\" then it will look like \"chore(package):\". You can also use parentDir or baseDir to namespace your commits for monorepos e.g. \"{{parentDir}}\".

"},{"location":"configuration-options/#semanticcommittype","title":"semanticCommitType","text":"

Commit type to use if Semantic Commits is enabled.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"chore\" supportsTemplating true cli --semantic-commit-type env RENOVATE_SEMANTIC_COMMIT_TYPE

This option supports Renovate's template syntax

See templates for available variables and helpers.

By default you will see Angular-style commit prefixes like \"chore(deps):\". If you wish to change it to something else like \"ci\" then it will look like \"ci(deps):\".

"},{"location":"configuration-options/#semanticcommits","title":"semanticCommits","text":"

Enable Semantic Commit prefixes for commits and PR titles.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string allowedValues 
[\"auto\", \"enabled\", \"disabled\"]\n
default \"auto\" cli --semantic-commits env RENOVATE_SEMANTIC_COMMITS

If you are using a semantic prefix for your commits, then you will want to enable this setting. Although it's configurable to a package-level, it makes most sense to configure it at a repository level. If configured to enabled, then the semanticCommitScope and semanticCommitType fields will be used for each commit message and PR title.

Renovate autodetects if your repository is already using semantic commits or not and follows suit, so you only need to configure this if you wish to override Renovate's autodetected setting.

"},{"location":"configuration-options/#separatemajorminor","title":"separateMajorMinor","text":"

If set to false, Renovate will upgrade dependencies to their latest release only. Renovate will not separate major or minor branches.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default true cli --separate-major-minor env RENOVATE_SEPARATE_MAJOR_MINOR

Renovate's default behavior is to create a separate branch/PR if both minor and major version updates exist (note that your choice of rangeStrategy value can influence which updates exist in the first place however). For example, if you were using Webpack 2.0.0 and versions 2.1.0 and 3.0.0 were both available, then Renovate would create two PRs so that you have the choice whether to apply the minor update to 2.x or the major update of 3.x. If you were to apply the minor update then Renovate would keep updating the 3.x branch for you as well, e.g. if Webpack 3.0.1 or 3.1.0 were released. If instead you applied the 3.0.0 update then Renovate would clean up the unneeded 2.x branch for you on the next run.

It is recommended that you leave this option to true, because of the polite way that Renovate handles this. For example, let's say in the above example that you decided you wouldn't update to Webpack 3 for a long time and don't want to build/test every time a new 3.x version arrives. In that case, simply close the \"Update Webpack to version 3.x\" PR and it won't be recreated again even if subsequent Webpack 3.x versions are released. You can continue with Webpack 2.x for as long as you want and get any updates/patches that are made for it. Then eventually when you do want to update to Webpack 3.x you can make that update to package.json yourself and commit it to the base branch once it's tested. After that, Renovate will resume providing you updates to 3.x again! i.e. if you close a major upgrade PR then it won't come back again, but once you make the major upgrade yourself then Renovate will resume providing you with minor or patch updates.

This option also has priority over package groups configured by packageRule. So Renovate will propose separate PRs for major and minor updates of packages even if they are grouped. If you want to enforce grouped package updates, you need to set this option to false within the packageRule.

"},{"location":"configuration-options/#separateminorpatch","title":"separateMinorPatch","text":"

If set to true, Renovate will separate minor and patch updates into separate branches.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default false cli --separate-minor-patch env RENOVATE_SEPARATE_MINOR_PATCH previouslyKnownAs 
[\"separatePatchReleases\"]\n

By default, Renovate groups patch (1.0.x) and minor (1.x.0) releases into a single PR. For example: you are running version 1.0.0 of a package, which has two updates:

By default, Renovate creates a single PR for the 1.1.0 version.

If you want Renovate to create separate PRs for patch and minor upgrades, set separateMinorPatch to true. Getting separate updates from Renovate can be handy when you want to, for example, automerge patch updates but manually merge minor updates.

"},{"location":"configuration-options/#separatemultiplemajor","title":"separateMultipleMajor","text":"

If set to true, PRs will be raised separately for each available major upgrade version.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default false cli --separate-multiple-major env RENOVATE_SEPARATE_MULTIPLE_MAJOR previouslyKnownAs 
[\"multipleMajorPrs\"]\n

Configure this to true if you wish to get one PR for every separate major version upgrade of a dependency. e.g. if you are on webpack@v1 currently then default behavior is a PR for upgrading to webpack@v3 and not for webpack@v2. If this setting is true then you would get one PR for webpack@v2 and one for webpack@v3.

"},{"location":"configuration-options/#separatemultipleminor","title":"separateMultipleMinor","text":"

If set to true, Renovate creates separate PRs for each minor stream.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default false cli --separate-multiple-minor env RENOVATE_SEPARATE_MULTIPLE_MINOR

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Enable this for dependencies when it is important to split updates into separate PRs per minor release stream (e.g. python).

For example, if you are on python@v3.9.0 currently, then by default Renovate creates a PR to upgrade you to the latest version such as python@v3.12.x. By default, Renovate skips versions in between, like python@v3.10.x.

But if you set separateMultipleMinor=true then you get separate PRs for each minor stream, like python@3.9.x, python@v3.10.x and python@v3.11.x, etc.

"},{"location":"configuration-options/#skipartifactsupdate","title":"skipArtifactsUpdate","text":"

Skip Renovate's automatic artifact updating.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default false cli --skip-artifacts-update env RENOVATE_SKIP_ARTIFACTS_UPDATE

Use this option when automatic artifact updating fails, is incorrect, or not needed.

This option was formerly known as updateLockFiles.

When this option is set, Renovate won't attempt to update artifacts such as lock files, so you will need to update them yourself, either manually or through secondary automation such as CI workflows.

Note

When this option is used in package rules, along with grouped upgrades, artifact updating will only be skipped if every upgrade in the grouped branch wants to skip it.

Warning

When artifact updates are skipped and the packageManager field in package.json is updated, the new version will not contain a hash. The hash is only applied when artifacts are updated. For example, a value of packageManager: \"yarn@3.0.0+sha224.deadbeef\" would be updated to just packageManager: \"yarn@3.1.0\" rather than packageManager: \"yarn@3.1.0+sha224.f0cacc1a\".

"},{"location":"configuration-options/#skipinstalls","title":"skipInstalls","text":"

Skip installing modules/dependencies if lock file updating is possible without a full install.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean supportedManagers npm cli --skip-installs env RENOVATE_SKIP_INSTALLS default null

By default, Renovate will use the most efficient approach to updating package files and lock files, which in most cases skips the need to perform a full module install. If this is set to false, then a full install of modules will be done. This is currently applicable to npm only, and only used in cases where bugs in npm result in incorrect lock files being updated.

"},{"location":"configuration-options/#statuschecknames","title":"statusCheckNames","text":"

Custom strings to use as status check names.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object mergeable true default 
{\n  \"artifactError\": \"renovate/artifacts\",\n  \"configValidation\": \"renovate/config-validation\",\n  \"mergeConfidence\": \"renovate/merge-confidence\",\n  \"minimumReleaseAge\": \"renovate/stability-days\"\n}\n
cli --status-check-names env RENOVATE_STATUS_CHECK_NAMES

Warning

For advanced use only! Use at your own risk!

You can customize the name/context of status checks that Renovate adds to commits/branches/PRs.

This option enables you to modify any existing status checks name/context, but adding new status checks this way is not supported. Setting the value to null or an empty string, effectively disables or skips that status check. This option is mergeable, which means you only have to specify the status checks that you want to modify.

Example of overriding status check strings
{\n  \"statusCheckNames\": {\n    \"minimumReleaseAge\": \"custom/stability-days\",\n    \"mergeConfidence\": \"custom/merge-confidence-level\"\n  }\n}\n
"},{"location":"configuration-options/#statuscheckwhen","title":"statusCheckWhen","text":"

Control when each Renovate status check is set on branches. Keys match statusCheckNames.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object mergeable true default 
{\n  \"artifactError\": \"failed\",\n  \"configValidation\": \"always\",\n  \"mergeConfidence\": \"always\",\n  \"minimumReleaseAge\": \"always\"\n}\n
cli --status-check-when env RENOVATE_STATUS_CHECK_WHEN

Warning

For advanced use only! Use at your own risk!

Control when each Renovate status check is set on branches. The keys match those available in statusCheckNames. This option is mergeable, so you only need to specify the checks you want to change.

Allowed values per key:

Default values:

Key Default Reasoning artifactError failed Legacy behavior \u2014 only reports artifact failures configValidation always Always reports validation pass/fail mergeConfidence always Always reports confidence level minimumReleaseAge always Always reports stability status

For example, to make renovate/artifacts a required check, set artifactError to \"always\" so it always reports green/red, allowing you to mark it as required in your branch protection rules. To skip a check entirely, set any key to \"never\" to suppress that status check. To only report failures for stability, set minimumReleaseAge to \"failed\" if you only care about the red/pending status.

Example: always set artifacts check, skip merge confidence
{\n  \"statusCheckWhen\": {\n    \"artifactError\": \"always\",\n    \"mergeConfidence\": \"never\"\n  }\n}\n
"},{"location":"configuration-options/#stopupdatinglabel","title":"stopUpdatingLabel","text":"

Label to make Renovate stop updating a PR.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string default \"stop-updating\" supportedPlatforms azure, forgejo, gerrit, gitea, github, gitlab cli --stop-updating-label env RENOVATE_STOP_UPDATING_LABEL

This feature only works on supported platforms, check the table above.

If you want Renovate to stop updating a PR, you can apply a label to the PR. By default, Renovate listens to the label: \"stop-updating\".

You can set your own label name with the \"stopUpdatingLabel\" field:

{\n  \"stopUpdatingLabel\": \"take-a-break-renovate\"\n}\n
"},{"location":"configuration-options/#suppressnotifications","title":"suppressNotifications","text":"

Options to suppress various types of warnings and other notifications.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type array subType string allowedValues 
[\n  \"artifactErrors\",\n  \"branchAutomergeFailure\",\n  \"configErrorIssue\",\n  \"dependencyLookupWarnings\",\n  \"lockFileErrors\",\n  \"missingCredentialsError\",\n  \"onboardingClose\",\n  \"prEditedNotification\",\n  \"prIgnoreNotification\"\n]\n
mergeable true default []

Use this field to suppress various types of warnings and other notifications from Renovate. For example:

{\n  \"suppressNotifications\": [\"prIgnoreNotification\"]\n}\n

The above config will suppress the comment which is added to a PR whenever you close a PR unmerged.

"},{"location":"configuration-options/#timezone","title":"timezone","text":"

Must conform to IANA Time Zone format.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type string cli --timezone env RENOVATE_TIMEZONE default null

We recommend that you only configure the timezone option if both of these are true:

Please see the above link for valid timezone names.

"},{"location":"configuration-options/#toolsettings","title":"toolSettings","text":"

Tool specific configuration. Global self-hosted configuration takes precedence.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object default 
{\"jvmMaxMemory\": 512, \"jvmMemory\": 512}\n
env RENOVATE_TOOL_SETTINGS

When Renovate updates a dependency and needs to invoke processes leveraging Java, for example Gradle for the gradle or the gradle-wrapper managers, the repository's Gradle Wrapper will be invoked, if present.

The JVM heap size for the Java invocations is 512m by default. This can be overridden using the following options.

This option can be used on the repository level and in the Renovate configuration using the following options.

Note

The JVM memory settings specified in the global self-hosted configuration set by the administrator in toolSettings.jvmMaxMemory limits the memory settings for all repositories. The default limit for all repositories is 512m.

Note

The JVM memory settings are considered for the gradle and gradle-wrapper manager.

"},{"location":"configuration-options/#toolsettingsjvmmaxmemory","title":"toolSettings.jvmMaxMemory","text":"

Maximum JVM memory in MB to use for updates that use a Java VM, like the Gradle Wrapper, defaults to 512. Repo configuration for this value will be ignored if it exceeds the global configuration for toolSettings.jvmMaxMemory

Name Value type integer parents toolSettings supportedManagers gradle-wrapper

Maximum heap size in MB for Java VMs. Defaults to 512 for both the repository level and self-hosted configuration.

To allow repositories to use more than 512m of heap during any invocations of the Gradle Wrapper, configure the jvmMaxMemory option in the toolSettings.jvmMaxMemory.

"},{"location":"configuration-options/#toolsettingsjvmmemory","title":"toolSettings.jvmMemory","text":"

Initial JVM memory in MB to use for updates that use a Java VM, like the Gradle Wrapper, defaults to jvmMaxMemory. Repo configuration for this value will be ignored if it exceeds the global configuration for toolSettings.jvmMaxMemory

Name Value type integer parents toolSettings supportedManagers gradle-wrapper

Initial heap size in MB for Java VMs. Must be less than or equal to jvmMaxMemory. Defaults to jvmMaxMemory.

"},{"location":"configuration-options/#toolsettingsnodemaxmemory","title":"toolSettings.nodeMaxMemory","text":"

Maximum memory in MiB for Node child processes invoked by Renovate. If unset, the Node process will automagically determine the memory limit to use. Repo configuration for this value will be ignored if it exceeds the global configuration for toolSettings.nodeMaxMemory

Name Value type integer parents toolSettings supportedManagers npm

Note

This does not apply to every Node process created by Renovate, only the managers noted above.

"},{"location":"configuration-options/#updateinternaldeps","title":"updateInternalDeps","text":"

Whether to update internal dep versions in a monorepo. Works on Yarn Workspaces.

Name Value scopes repo, manager type boolean default false supportedManagers npm cli --update-internal-deps env RENOVATE_UPDATE_INTERNAL_DEPS

Renovate defaults to skipping any internal package dependencies within monorepos. In such case dependency versions won't be updated by Renovate.

To opt in to letting Renovate update internal package versions normally, set this configuration option to true.

"},{"location":"configuration-options/#updatenotscheduled","title":"updateNotScheduled","text":"

Whether to update branches when not scheduled. Renovate will not create branches outside of the schedule.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type boolean default true cli --update-not-scheduled env RENOVATE_UPDATE_NOT_SCHEDULED

When schedules are in use, it generally means \"no updates\". However there are cases where updates might be desirable - e.g. if you have configured prCreation=not-pending, or you have rebaseWhen=behind-base-branch and the base branch is updated so you want Renovate PRs to be rebased.

This defaults to true, meaning that Renovate will perform certain \"desirable\" updates to existing PRs even when outside of schedule. If you wish to disable all updates outside of scheduled hours then configure this field to false.

"},{"location":"configuration-options/#updatepinneddependencies","title":"updatePinnedDependencies","text":"

Whether to update pinned (single version) dependencies or not.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type boolean default true cli --update-pinned-dependencies env RENOVATE_UPDATE_PINNED_DEPENDENCIES

By default, Renovate will try to update all detected dependencies, regardless of whether they are defined using pinned single versions (e.g. 1.2.3) or constraints/ranges (e.g. (^1.2.3). You can set this option to false if you wish to disable updating for pinned (single version) dependencies specifically.

"},{"location":"configuration-options/#usebasebranchconfig","title":"useBaseBranchConfig","text":"

Whether to read configuration from base branches instead of only the default branch.

Name Value scopes repo type string allowedValues 
[\"merge\", \"none\"]\n
default \"none\" cli --use-base-branch-config env RENOVATE_USE_BASE_BRANCH_CONFIG

By default, Renovate will read config file from the default branch only and will ignore any config files in base branches. You can configure useBaseBranchConfig=merge to instruct Renovate to merge the config from each base branch over the top of the config in the default branch.

The config file name in the base branch must be the same as in the default branch and cannot be package.json. This scenario may be useful for testing the config changes in base branches instantly.

"},{"location":"configuration-options/#userstrings","title":"userStrings","text":"

User-facing strings for the Renovate comment when a PR is closed.

Name Value scopes repo, packageRule, manager, updateType, vulnerabilityAlert, group type object freeChoice true default 
{\n  \"ignoreTopic\": \"Renovate Ignore Notification\",\n  \"ignoreMajor\": \"Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for *any* future `{{{newMajor}}}.x` releases. But if you manually upgrade to `{{{newMajor}}}.x` then Renovate will re-enable `minor` and `patch` updates automatically.\",\n  \"ignoreDigest\": \"Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the `{{{depName}}}` `{{{newDigestShort}}}` update again.\",\n  \"ignoreOther\": \"Because you closed this PR without merging, Renovate will ignore this update (`{{{newValue}}}`). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config.\",\n  \"artifactErrorWarning\": \"You probably do not want to merge this PR as-is.\"\n}\n
cli --user-strings env RENOVATE_USER_STRINGS

When a PR is closed, Renovate posts a comment to let users know that future updates will be ignored. If you want, you can change the text in the comment with the userStrings config option.

You can edit these user-facing strings:

For example:

{\n  \"userStrings\": {\n    \"artifactErrorWarning\": \"Custom text for artifact errors.\",\n    \"ignoreTopic\": \"Custom topic for PR comment\",\n    \"ignoreMajor\": \"Custom text for major upgrades.\",\n    \"ignoreDigest\": \"Custom text for digest upgrades.\",\n    \"ignoreOther\": \"Custom text for other upgrades.\"\n  }\n}\n
"},{"location":"configuration-options/#versioncompatibility","title":"versionCompatibility","text":"

A regex (re2) with named capture groups to show how version and compatibility are split from a raw version string.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string format regex default null

This option is used for advanced use cases where the version string embeds more data than just the version. It's typically used with docker and tags datasources.

Here are two examples:

Here is an example of solving these types of cases:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"ghcr.io/umami-software/umami\"],\n      \"versionCompatibility\": \"^(?<compatibility>.*)-(?<version>.*)$\",\n      \"versioning\": \"semver\"\n    },\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"node\"],\n      \"versionCompatibility\": \"^(?<version>[^-]+)(?<compatibility>-.*)?$\",\n      \"versioning\": \"node\"\n    }\n  ]\n}\n

This feature is most useful when the currentValue is a version and not a range/constraint.

This feature can be used in combination with extractVersion although that's likely only a rare edge case. When combined, extractVersion is applied to datasource results first, and then versionCompatibility. extractVersion should be used when the raw version string returned by the datasource contains extra details (such as a v prefix) when compared to the value/version used within the repository.

During the lookup phase, Renovate evaluates the versionCompatibility regex against the currentValue string. If there is a match, the version part is stored internally temporarily as compareValue and the compatibility part stored as currentCompatibility. Storing currentCompatibility allows Renovate to reuse this value later to filter for new versions with the same compatibility. Renovate applies this compatibility check to datasource lookup results by passing both the versionCompatibility and currentCompatibility strings to a filter.

For a new version to be allowed, it must:

At this point, Renovate's core lookup logic is comparing versions to versions, and ignoring compatibility strings like -jre8. Finally, once updates are decided, Renovate restores the compatibility part to the newValue result.

"},{"location":"configuration-options/#versioning","title":"versioning","text":"

Versioning to use for filtering and comparisons.

Name Value scopes repo, packageRule, manager, vulnerabilityAlert type string allowedValues 
[\n  \"apk\",\n  \"aws-eks-addon\",\n  \"aws-machine-image\",\n  \"azure-rest-api\",\n  \"bazel-module\",\n  \"cargo\",\n  \"composer\",\n  \"conan\",\n  \"conda\",\n  \"deb\",\n  \"debian\",\n  \"deno\",\n  \"devbox\",\n  \"docker\",\n  \"elm\",\n  \"exact\",\n  \"git\",\n  \"github-actions\",\n  \"glasskube\",\n  \"go-mod-directive\",\n  \"gomod\",\n  \"gradle\",\n  \"hashicorp\",\n  \"helm\",\n  \"hermit\",\n  \"hex\",\n  \"ivy\",\n  \"julia\",\n  \"kubernetes-api\",\n  \"lambda-node\",\n  \"loose\",\n  \"maven\",\n  \"nixpkgs\",\n  \"node\",\n  \"npm\",\n  \"nuget\",\n  \"paket\",\n  \"pep440\",\n  \"perl\",\n  \"poetry\",\n  \"pvp\",\n  \"python\",\n  \"redhat\",\n  \"regex\",\n  \"rez\",\n  \"rpm\",\n  \"ruby\",\n  \"rust-release-channel\",\n  \"same-major\",\n  \"semver\",\n  \"semver-coerced\",\n  \"semver-partial\",\n  \"swift\",\n  \"ubuntu\",\n  \"unity3d\",\n  \"unity3d-packages\",\n  \"vcpkg\"\n]\n
previouslyKnownAs 
[\"versionScheme\"]\n
default null

Usually, each language or package manager has a specific type of \"versioning\": JavaScript uses npm's SemVer implementation, Python uses pep440, etc.

Renovate also uses custom versioning, like \"docker\" to address the most common way people tag versions using Docker, and \"loose\" as a fallback that tries SemVer first. Otherwise Renovate does its best to sort and compare.

By exposing versioning to config, you can override the default versioning for a package manager if needed. We do not recommend overriding the default versioning, but there are some cases such as Docker or Gradle where versioning is not strictly defined and you may need to specify the versioning type per-package.

Renovate supports 4-part versions (1.2.3.4) in full for the NuGet package manager. Other managers can use the \"loose\" versioning fallback: the first 3 parts are used as the version, all trailing parts are used for alphanumeric sorting.

A key characteristic of the \"docker\" versioning is that it attempts to preserve the precision of the current version string. For example, if your current version has two parts (e.g., 5.6), Renovate will propose updates that also have two parts (e.g., 5.7), rather than a three-part SemVer equivalent (e.g., 5.7.0).

Example Use Case: \"Floating Patch Versions\" using 2 digits versioning

You may want to use a 2-part version like 5.6 to indicate the minor version while automatically receiving the latest patch updates (a \"floating patch\"). At the same time, you still want Renovate to create merge requests for minor or major updates like 5.7 or 6.2. The default semver versioning would update 5.6 to a 3-part version like 5.6.1, which would break the floating patch behavior.

In the below renovate.json extract example, Renovate will use the docker versioning for the .gitlab-ci.yml file, so you can pin the minor version while still receiving the latest patch updates.

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\".gitlab-ci.yml\"],\n      \"versioning\": \"docker\"\n    }\n  ]\n}\n

When using this strategy, make sure that the package you're referencing does support 2-part versions, e.g. that it has a version like 5.6 available in the registry in addition to 5.6.1 or 5.6.2.

"},{"location":"configuration-options/#vulnerabilityalerts","title":"vulnerabilityAlerts","text":"

Config to apply when a PR is needed due to a vulnerability in the existing package version.

Name Value scopes repo type object default 
{\n  \"groupName\": null,\n  \"schedule\": [],\n  \"dependencyDashboardApproval\": false,\n  \"minimumReleaseAge\": null,\n  \"rangeStrategy\": \"update-lockfile\",\n  \"commitMessageSuffix\": \"[SECURITY]\",\n  \"branchTopic\": \"{{{datasource}}}-{{{depNameSanitized}}}-vulnerability\",\n  \"prCreation\": \"immediate\",\n  \"vulnerabilityFixStrategy\": \"lowest\",\n  \"prConcurrentLimit\": 0\n}\n
mergeable true supportedPlatforms github

Renovate can read GitHub's Vulnerability Alerts to customize its Pull Requests. For this to work, you must enable the Dependency graph, and Dependabot alerts. Follow these steps:

  1. While logged in to GitHub, navigate to your repository
  2. Select the \"Settings\" tab
  3. Select \"Advanced Security\" in the sidebar
  4. Enable the \"Dependency graph\"
  5. Enable \"Dependabot alerts\"
  6. If you're running Renovate in app mode: make sure the app has read permissions for \"Dependabot alerts\". If you're the account administrator, browse to the app (for example the Mend Renovate App), select \"Configure\", and then scroll down to the \"Permissions\" section and make sure that read access to \"Dependabot alerts\" is mentioned

Once the above conditions are met, and you got one or more vulnerability alerts from GitHub for this repository, then Renovate tries to raise fix PRs.

You may use the vulnerabilityAlerts configuration object to customize vulnerability-fix PRs.

Setting a custom label and assignee
{\n  \"vulnerabilityAlerts\": {\n    \"labels\": [\"security\"],\n    \"automerge\": true,\n    \"assignees\": [\"@renovate-tests\"]\n  }\n}\n

Warning

There's a small chance that a wrong vulnerability alert results in a flapping/looping vulnerability fix. If you allow Renovate to automerge vulnerability fixes, please check if the automerged fix is correct.

Note

By default, when Renovate creates a vulnerabilityAlerts PR, it ignores settings like branchConcurrentLimit, commitHourlyLimit, prConcurrentLimit, prHourlyLimit, or schedule. This means that Renovate always tries to create a vulnerabilityAlerts PR. In short: vulnerability alerts \"skip the line\".

Note

Some managers disable certain dependencies by default, such as indirect Go modules or Gradle strictly constraints. Renovate still raises vulnerability-fix PRs for those dependencies, unless you disable them yourself with a packageRules entry that sets enabled=false.

If you get many alerts at once, for example when you onboard a repository which was not using Renovate before, then set prConcurrentLimit or branchConcurrentLimit inside the vulnerabilityAlerts object. Vulnerability fixes get their own budget, they do not take a share of the repository-wide one:

Allowing up to 5 vulnerability fix PRs on top of 5 regular PRs
{\n  \"prConcurrentLimit\": 5,\n  \"vulnerabilityAlerts\": {\n    \"prConcurrentLimit\": 5\n  }\n}\n

With the config above Renovate creates at most 10 open PRs: 5 for regular updates, plus 5 for vulnerability fixes. The default is 0, which means \"no limit\", so vulnerability alerts keep skipping the line until you set a limit yourself. You do not need to set branchConcurrentLimit as well, because its null default already means \"inherit prConcurrentLimit\". These limits also apply to updates that a packageRules entry marks with isVulnerabilityAlert=true.

Note

Only the concurrent limits can be set this way. Renovate always ignores commitHourlyLimit, prHourlyLimit, prCommitsPerRunLimit and schedule for vulnerability alerts, you can not override this.

To disable the vulnerability alerts feature, set enabled=false in a vulnerabilityAlerts config object, like this:

Disabling vulnerability alerts
{\n  \"vulnerabilityAlerts\": {\n    \"enabled\": false\n  }\n}\n

Note

If you want to raise only vulnerability fix PRs, you may use the security:only-security-updates preset.

"},{"location":"configuration-options/#vulnerabilityalertsvulnerabilityfixstrategy","title":"vulnerabilityAlerts.vulnerabilityFixStrategy","text":"

Strategy to use when fixing vulnerabilities. lowest will propose the earliest version with a fix, highest will always pick the latest version.

Name Value type string allowedValues 
[\"lowest\", \"highest\"]\n
default \"lowest\" parents vulnerabilityAlerts cli --vulnerability-fix-strategy env RENOVATE_VULNERABILITY_FIX_STRATEGY

When a vulnerability fix is available, Renovate will default to picking the lowest fixed version (vulnerabilityFixStrategy=lowest). For example, if the current version is 1.0.0, and a vulnerability is fixed in 1.1.0, while the latest version is 1.2.0, then Renovate will propose an update to 1.1.0 as the vulnerability fix.

If vulnerabilityFixStrategy=highest is configured then Renovate will use its normal strategy for picking upgrades, e.g. in the above example it will propose an update to 1.2.0 to fix the vulnerability.

Setting vulnerabilityFixStrategy to highest
{\n  \"vulnerabilityAlerts\": {\n    \"vulnerabilityFixStrategy\": \"highest\"\n  }\n}\n
"},{"location":"configuration-templates/","title":"Config Template Editing","text":"

This document describes how you can edit branch names, commit messages, PR titles and PR content.

"},{"location":"configuration-templates/#branch-name","title":"Branch Name","text":"

The branch name is very important for Renovate because it helps determine \"grouping\" of updates, and also makes it efficient when an existing PR needs to be updated when a newer version of a package is released. If you change the branchPrefix while you have ignored some upgrades (closed PR without merging), you might get a duplicate PR after the new branchPrefix setting is picked up by Renovate.

branchName default value is {{{branchPrefix}}}{{{additionalBranchPrefix}}}{{{branchTopic}}}.

The most common branch name you will see looks like this: renovate/react-18.x. In this example, the branchPrefix is the default renovate/, additionalBranchPrefix is empty, and branchTopic is react-18.x.

Most users will be happy with the default branchPrefix of renovate/, but you can change this if you don't like the default. Say you don't want the forward slashes, in that case you would use renovate- as your branchPrefix. The onboarding PR will always use renovate/configure.

additionalBranchPrefix is optional and by default is empty.

branchTopic depends on the package manager and upgrade type, so you will see a lot of variety. This is probably a setting you want to change yourself. Be careful, and consider creating a new \"config help\" post at the discussions tab in the Renovate repository to get help from the Renovate team with your config.

"},{"location":"configuration-templates/#commit-message","title":"Commit Message","text":"

Renovate uses one commit per branch. The commitMessage reflects the contents of the branch and is usually the same as the PR title.

commitMessage has a default value of {{{commitMessagePrefix}}} {{{commitMessageAction}}} {{{commitMessageTopic}}} {{{commitMessageExtra}}} {{{commitMessageSuffix}}}, with the intention that you only edit some of those subcomponents.

You usually don't need to edit commitMessagePrefix, this option is used by Renovate if it needs to add a prefix to conform to the Semantic Commit convention. Avoid editing the commit message, unless you know what you're doing.

commitMessageAction is usually one word, like 'Update', 'Pin', 'Refresh', etc. You're probably fine leaving this setting alone, though you can change it. e.g. if you prefer that Renovate uses the term 'Upgrade' instead of 'Update' then you could configure \"commitMessageAction\": \"Upgrade\".

commitMessageTopic is usually two to three words that show what is being updated. e.g. it might be dependency react or Docker image ubuntu. You may want to edit this. If you think your new commitMessageTopic is helpful for others, please open a PR.

commitMessageExtra refers to the version being updated to. e.g. to v18 for a major upgrade, or to v18.0.2 for a patch update. It can be empty in some cases, like if the action/topic doesn't change a package version, e.g. Pin Docker digests.

commitMessageSuffix defaults to empty but is currently used in two cases:

commitBody is used if you wish to add multi-line commit messages, such as for the Signed-off-by fields, or adding [skip-ci], etc. It is appended to the generated commitMessage, separated by a newline.

"},{"location":"configuration-templates/#pr-title","title":"PR Title","text":"

Because commit messages match with the PR title, the PR title template defaults to null and inherits/copies the value from commitMessage. If you have a requirement where prTitle should be different from commitMessage, then please raise a feature request for discussion.

"},{"location":"configuration-templates/#pr-body","title":"PR Body","text":"

You can change the PR body in the following ways:

"},{"location":"contributing-to-renovate/","title":"Contributing to Renovate","text":"

Thank you for thinking of contributing to Renovate! The docs/development/ directory of the renovatebot/renovate repository has all the developer-facing documentation.

"},{"location":"contributing-to-renovate/#i-want-to-write-code","title":"I want to write code","text":""},{"location":"contributing-to-renovate/#read-this-first","title":"Read this first","text":"
  1. Contributing guide
  2. Best practices
  3. Local Development or Remote Development
"},{"location":"contributing-to-renovate/#creatingediting-renovate-preset","title":"Creating/editing Renovate preset","text":"
  1. Creating/editing Renovate presets
"},{"location":"contributing-to-renovate/#adding-a-new-package-manager","title":"Adding a new package manager","text":"
  1. Adding a Package Manager
"},{"location":"contributing-to-renovate/#background-information","title":"Background information","text":"
  1. Design Decisions
  2. Zod schema guideline
  3. Branches and commits behavior
  4. Configuration
  5. Static Data
  6. How to bump Renovate to next NodeJS LTS release
"},{"location":"contributing-to-renovate/#i-want-to-write-documentation","title":"I want to write documentation","text":"

Read the Contributing guide, and the Renovate style guide.

"},{"location":"contributing-to-renovate/#i-want-to-triage-incoming-discussions","title":"I want to triage incoming discussions","text":"

Start by reading:

  1. Contributing guide
  2. Triage guide
  3. Issue labeling

You may need to direct a Renovate user to one of these pages:

  1. About minimal reproductions
  2. New package manager questionnaire
  3. Help Us Help You
"},{"location":"dependency-pinning/","title":"Should you Pin your JavaScript Dependencies?","text":"

Once you start using a tool/service like Renovate, probably the biggest decision you need to make is whether to \"pin\" your dependencies instead of using SemVer ranges. The answer is \"It's your choice\", but we can certainly make some generalizations/recommendations to help you.

If you don't want to read the in-depth discussion, you can skip ahead to our recommendations in the \"So what's best?\" section.

"},{"location":"dependency-pinning/#what-is-dependency-pinning","title":"What is Dependency Pinning?","text":"

To ensure we're all talking about the same thing, it's important to define exactly what we mean by dependency \"pinning\".

Historically, projects use SemVer ranges in their package.json. For instance, if you run npm install foobar you will see an entry like \"foobar\": \"^1.1.0\" added to your package.json. Verbosely, this means \"any foobar version greater than or equal to 1.1.0 but less than 2\". The project will automatically use 1.1.1 if it's released, or 1.2.0, or 1.2.1, etc - meaning you will get not only patch updates but also feature (minor) releases too.

Another alternative is ranges like \"foobar\": \"~1.1.0\" which means \"any foobar version greater than or equal to 1.1.0 but less than 1.2\". This narrows the range to only patch updates to the 1.1 range.

If instead you \"pin\" your dependencies rather than use ranges, it means you use exact entries like \"foobar\": \"1.1.0\" which means \"use only foobar version 1.1.0 and no other\".

"},{"location":"dependency-pinning/#why-use-ranges","title":"Why use ranges?","text":"

For projects of any type, the main reason to use ranges is so that you can \"automatically\" get updated releases - which may even include security fixes. By \"automatically\", we mean that any time you run npm install you will get the very latest version matching your SemVer - assuming you're not using a lock file, that is.

"},{"location":"dependency-pinning/#tilde-vs-caret","title":"Tilde vs Caret","text":"

If you're familiar with the theory of SemVer, you might think that you only need to use tilde ranges (e.g. \"~1.1.0\") to get bug fixes, rather than caret ranges (e.g. \"^1.1.0\"). This is true in theory but not in practice. The reality is that for most projects, fixes are not \"backported\" to previous minor releases, and minor releases themselves may include fixes. So for example release 1.2.0 may include one new feature and one fix, so if you stick with 1.1.0 then you will miss out on the fix as there will never be a 1.1.1 once 1.2.0 is already released. This is the reality of most open source packages.

"},{"location":"dependency-pinning/#ranges-for-libraries","title":"Ranges for Libraries","text":"

A second reason for using ranges applies to \"libraries\" that are published as npm packages with the intention that they are used/require()'d by other packages. In this case, it is usually a bad idea to pin all your dependencies because it will introduce an unnecessarily narrow range (one release!) and cause most users of your package to bloat their node_modules with duplicates.

For example, you might have pinned foobar to version 1.1.0 and another author pinned his/her foobar dependency to 1.2.2. Any user of both your packages will end up with npm trying to install two separate versions of foobar, which might not even work. Even if both projects use a service like Renovate to keep their pinned dependencies up to date with the very latest versions, it's still not a good idea - there will always be times when one package has updated/released before the other one and they will be out of sync. e.g. there might be a space of 30 minutes where your package specifies foobar 1.1.0 and the other one specifies 1.1.1 and your joint downstream users end up with a duplicate.

"},{"location":"dependency-pinning/#why-pin-dependencies","title":"Why pin dependencies?","text":"

You mainly pin versions for certainty, and visibility. When you have a pinned version of each dependency in your package.json, you know exactly which version of each dependency is installed at any time. This benefits when upgrading versions as well as when rolling back in case of problems.

Note

We'll cover lock files later, don't worry.

"},{"location":"dependency-pinning/#upgrading-pinned-versions","title":"Upgrading pinned versions","text":"

Let's say that a \"faulty\" version 1.2.0 of foobar is released and it breaks one of your tests.

If you were using default caret SemVer ranges, then your main branch is now \"broken\" because its package.json says that any version 1.x above 1.1.0 is acceptable, and npm will choose the latest (1.2.0). You would need to manually check and work out which dependency caused the failure (foobar may not have been the only dependency to have \"automatically\" upgraded since the last time your tests passed) and then you would need to pin the dependency yourself to stop npm installing 1.2.0.

Consider the same situation if instead you were pinning dependency versions. Your main branch would not be broken because it's pinned to foobar@1.1.0 - instead you'd have a Pull Request for upgrading to foobar@1.2.0 which would fail. You'd know not to merge it and can wait for foobar@1.2.1 or later when it's fixed. By pinning dependencies you know exactly what you're running and you know exactly what failed.

Now consider a similar theoretical scenario where foobar@1.2.0 is faulty but it is not caught by any of your automated tests. This is more common and more dangerous.

If you were using SemVer ranges then this new version of foobar will likely be deployed to production automatically one day, sometime after which you notice errors and realize you need to fix it. Like before, you need to manually work out which dependency caused it - assuming you guess correctly that it was a new dependency version at fault - and pin it manually by editing package.json one dependency at a time.

Alternatively, if you were instead pinning foobar then you would get a PR for foobar@1.2.0 which awaits your approval. So first of all, you can choose to read the changelogs and/or visually inspect the branch yourself before merging, hopefully saving you from pushing this faulty code to production.

If you did not catch the fault before merging, you are still better off with a pinned version. If you discover something wrong in production, you can easily \"roll back\" commits in your development environment until you find which rollback fixes the problem. Then you can simply revert that commit (reversing foobar@1.1.0 \u2192 foobar@1.2.0) and push that to main. When the next release of foobar comes out (e.g. 1.2.1) you will be prompted with a new PR and hopefully inspect it carefully this time before merge!

As you can see in the above, pinning dependencies makes your build more consistent and predictable as a developer.

"},{"location":"dependency-pinning/#downside-of-pinned-dependencies-upgrade-noise","title":"Downside of pinned dependencies - upgrade \"noise\"","text":"

The one major downside to your development workflow of pinning dependencies is the potential for increased \"noise\" in your repository. As mentioned above, you can expect to get Pull Requests whenever there is a new version of your dependencies available. Depending on how many repositories you maintain, and how many dependencies are in each, you may find this default approach to be overwhelming (e.g. waking up to 10 new Pull Requests each day).

"},{"location":"dependency-pinning/#reducing-the-noise-of-dependency-updates","title":"Reducing the \"noise\" of dependency updates","text":"

The increased volume of Pull Requests for upgrading dependencies may be considered by some to be undesirable \"noise\" in their day. To some extent this is simply a trade-off for having your dependencies pinned and predictable, but there are also ways you can reduce this noise while still gaining the majority of the benefits:

"},{"location":"dependency-pinning/#pull-request-automerging","title":"Pull Request automerging","text":"

There are some dependencies that either (a) don't have the potential to break something in production, or (b) are fully tested by your tests.

For example, it's very hard for eslint to break anything in production. If your build/tests pass, then you are fine. Consider enabling automerge for all lint packages to save yourself the work of manually approving the update each time. In this case you might wake up to 5/10 of your overnight Pull Requests having already merged themselves.

Another example of a good candidate for automerging might be a database driver like node-postgres (pg on npm), if you have 100% test coverage of your API. In that case if the pg package has a minor or patch update and passes all tests then you may as well merge it automatically if you were not going to do a manual inspection anyway.

"},{"location":"dependency-pinning/#branch-automerging","title":"Branch automerging","text":"

In the above suggestion of Pull Request automerging, you might still find it annoying if you get GitHub Notifications for every PR that is created and merged. In that case, you could set automergeType to branch, which means Renovate will:

With this approach, updates will be essentially \"silent\" - causing no notifications - but you will be able to see each commit on main of course.

"},{"location":"dependency-pinning/#scheduling","title":"Scheduling","text":"

Although it can feel satisfying to get updates \"immediately\" when they're available, the reality is that you usually don't need updates so frequently. And worse still, npm package versions that are less than 72 hours can be unpublished, which would really break your build if you've pinned to a version that no longer exists.

So to reduce the interruptions of automated dependency updates, consider putting Renovate on a schedule, such as:

To learn all about controlling Renovate's schedule, read the key concepts, scheduling docs.

"},{"location":"dependency-pinning/#grouping-related-packages","title":"Grouping related packages","text":"

Although it's good to isolate each dependency update for ease of troubleshooting, there are times when the extra noise isn't worth it, or when packages naturally belong together anyway (such as all babel packages). You can add a package rule in our Renovate configuration to group these together and you'll get one branch combined even if multiple packages have updates available.

"},{"location":"dependency-pinning/#pinning-dependencies-and-lock-files","title":"Pinning Dependencies and Lock Files","text":"

Since both yarn and npm@5 both support lock files, it's a common question to ask \"Why should I pin dependencies if I'm already using a lock file?\". It's a good question!

Lock files are a great companion to SemVer ranges or pinning dependencies, because these files lock (pin) deeper into your dependency tree than you see in package.json.

"},{"location":"dependency-pinning/#what-a-lock-file-will-do-for-you","title":"What a lock file will do for you","text":"

When kept in sync with its associated package.json, a lock file will further lock down the exact dependencies and sub-dependencies that your project uses, so that everyone running npm install or yarn install will install the exact same dependencies as the person or bot that last updated the lock file.

To reuse an earlier example, this means that you could have foobar@^1.1.0 in your package.json and be locked to 1.1.0 in your lock file, so that when the broken foobar@1.2.0 is released, nobody on the team installs it.

"},{"location":"dependency-pinning/#what-a-lock-file-doesnt-do-for-you","title":"What a lock file doesn't do for you","text":"

If a lock file gets out of sync with its package.json, it can no longer be guaranteed to lock anything, and the package.json will be the source of truth for installs.

The lock file has only delayed the inevitable problem, and provides much less visibility than package.json, because it's not designed to be human readable and is quite dense.

If the package.json has a range, and a new in-range version is released that would break the build, then essentially your package.json is in a state of \"broken\", even if the lock file is still holding things together.

The upside is that the lockfile will hold back foobar to 1.1.0 unless it's forced to upgrade, so the break is postponed. The downside is how you will discover the break eventually.

The easiest case is if for some reason you need to upgrade foobar, e.g. for a new feature it has, so you might run something like yarn upgrade foobar. Then you might either discover the break during your development or when you push your new development to CI for testing. In this case, hopefully you'll guess it's foobar that broke it and not your own code.

Alternatively, maybe someone thinks \"This lockfile is probably really out of date and might be missing some essential patches\" and decides to yarn upgrade the whole thing in one go. No doubt the diff will be full of green and red as many direct and indirect dependencies will have changed versions. Then it's pushed to CI for testing, fails, and you have to guess which of the changes caused it until you eventually narrow it down to foobar. This might require even manually looking through the lock file diffs line by line. Maybe dep blahblah also broke at the same time, to make it even harder.

By ceding control of direct dependency versions to the lock file, you have lost the ability to know when things are updated. You also may be missing out on really important patches you're not even aware of, because they're \"in range\" yet locked back to vulnerable or buggy versions in the lock file.

Reconsider the same scenario if foobar had instead been pinned to 1.1.0 in package.json. The (broken) upgrade to 1.2.0 would have been explicitly proposed to you via a Renovate PR, you would see the break, and know that the version is bad. Meanwhile you could be upgrading all the other essential fixes of other dependencies without worrying about foobar. You could even be running yarn upgrade regularly to be getting indirect package updates in the lockfile and seeing if everything still passes.

So the lock file does not solve the same SemVer problems that pinning solves - but it compliments it. For this reason our usual recommendation is using a lock file regardless of whether you pin dependencies or not, and pinning even if you have a lock file.

But you may also go ahead and configure however you want. Also, we're open to ideas for how to make lock file updates more \"visible\" too. e.g. are you interested in a Renovate feature where you get a lockfile-only PR any time a direct dependency gets an in-range update?

"},{"location":"dependency-pinning/#what-about-indirectsub-dependencies","title":"What about indirect/sub-dependencies?","text":"

A good argument made by @LinusU is:

Pinning will only protect you against breakage in a, in many cases, small percentage of your packages. If you for example have installed Express and pinned it, you will only protect yourself against a bad Express release, it will not help with the 30 dependencies that Express has.

Because of this, I personally think that pinning dependencies just creates a false sense of security, and that using a lock file is superior in every way.

It is true that pinning applies only to direct dependencies, and \"indirect\" dependencies typically count for a lot more in total in your lockfile than direct. e.g. those 30 ones that Express relies on.

Does pinning give you \"increased\" security? Undeniably. The question is not whether it does, but whether that increased security comes at a cost (e.g. \"noise\"). But Linus also points out that a false sense of security is a cost too.

Don't forget that there is some form of transitive trust too. You need to pick your direct dependencies carefully, and which versions of them you use. Hopefully in doing that you pick dependencies partly for how well they look after their own dependencies and versions (e.g. do they have good enough test coverage, do they use something like Renovate to keep updated, etc?). So the reality is that even if 90% of the entries in your lock file are indirect dependencies, those are ones you have somewhat \"delegated\" responsibility for to your dependencies. e.g. I'd hope that Express are even better at watching their dependencies for breaks than I am, to use the example above.

But certainly \"does it give a false sense of security\" is not a question we can really answer quantifiably.

"},{"location":"dependency-pinning/#so-whats-best","title":"So what's best?","text":"

We recommend:

  1. Any apps (web or Node.js) that aren't require()'d by other packages should pin all types of dependencies for greatest reliability/predictability
  2. Browser or dual browser/node.js libraries that are consumed/required()'d by others should keep using SemVer ranges for dependencies but can use pinned dependencies for devDependencies
  3. Node.js-only libraries can consider pinning all dependencies, because application size/duplicate dependencies are not as much a concern in Node.js compared to the browser. Of course, don't do that if your library is a micro one likely to be consumed in disk-sensitive environments
  4. Use a lock file

As noted earlier, when you pin dependencies then you will see an increase in the raw volume of dependency updates, compared to if you use ranges. If/when this starts bothering you, add Renovate rules to reduce the volume, such as scheduling updates, grouping them, or automerging \"safe\" ones.

"},{"location":"dependency-pinning/#references","title":"References","text":"

This is a \"living\" document and we plan to update it whenever we think of something new or someone makes a valid point we've missed or misunderstood.

Updated 2018-01-19 after excellent feedback on lockfiles by @LinusU

"},{"location":"docker-build-process/","title":"How does Renovate's Docker image get built?","text":"

The Renovate CLI is distributed for use in a few ways, one of which is as a pre-built container.

As part of this build process, there are two key variants of this:

"},{"location":"docker-build-process/#slim-image-default","title":"Slim image (default)","text":"

Renovate's \"slim\" image is recommended as the minimal set of installed tools on a given container to be able to run Renovate.

It uses binarySource=install to dynamically install tools as they're needed. This keeps the base container quite lightweight (hence \"slim\") but requires outbound network access at runtime.

It is possible to make the \"slim\" container even more lightweight by removing some of the tools and packages - for instance to reduce the attack surface, or reduce the size of the resulting image - but that is left as an exercise to the reader.

"},{"location":"docker-build-process/#full-image","title":"Full image","text":"

Renovate's \"full\" image is recommended for users who prefer to have most tools pre-installed, and not require any outbound access at runtime.

It uses binarySource=global which only uses tools that are installed in the image.

When using the \"full\" image, there are some tools and packages installed in the container that you may not be using. It is possible to remove these - for instance to reduce the attack surface, or reduce the size of the resulting image - but that is left as an exercise to the reader.

"},{"location":"docker-build-process/#build-process-flow","title":"Build process flow","text":"

Renovate leverages Containerbase, a project maintained by the same maintainers as the Renovate CLI project itself, which provides base images and utilities for managing dependencies.

This leads to a release process that requires multiple different container releases to result in the Renovate container image being updated.

The full flow can be seen below:

flowchart TD\n    Ubuntu               --> ContainerbaseUbuntu\n    ContainerbaseUbuntu  --> ContainerbaseBase\n    ContainerbaseBase    --> RenovatebotBaseImage\n    RenovatebotBaseImage --> RenovateSlim\n    RenovatebotBaseImage --> RenovateFull\n\n    Ubuntu[<code>docker.io/library/ubuntu</code>]\n    ContainerbaseUbuntu[<a href=\"https://github.com/containerbase/ubuntu\"><code>ghcr.io/containerbase/ubuntu</code></a>]\n    ContainerbaseBase[<a href=\"https://github.com/containerbase/base\"><code>ghcr.io/containerbase/base</code></a>]\n    RenovatebotBaseImage[<a href=\"https://github.com/renovatebot/base-image\"><code>ghcr.io/renovatebot/base-image</code></a>]\n    RenovateSlim[<code>ghcr.io/renovatebot/renovate</code><br><code>docker.io/renovate/renovate</code>]\n    RenovateFull[<code>ghcr.io/renovatebot/renovate:full</code><br><code>docker.io/renovate/renovate:full</code>]
"},{"location":"docker-build-process/#tool-support","title":"Tool support","text":""},{"location":"docker-build-process/#adding-new-tools","title":"Adding new tools","text":"

If you, as a user, are looking to extend the tool support that Renovate has, for instance to install it via constraints, then you will need to request a new tool. Once raised, you can then work through the \"how to add a new tool\" documentation.

This tool will have its support added in containerbase/base, to allow Containerbase's install-tool command-line tool to install the tool.

Once install-tool support is implemented, the update to ghcr.io/containerbase/base will need to bubble up to the Renovate \"slim\" and \"full\" images before the tool can be used.

"},{"location":"docker-build-process/#changing-default-tools","title":"Changing default tools","text":"

If you, as a user, are looking to provide a tool installed by default (in the \"slim\" or \"full\" images), you will need to first make sure that the tool is supported (and if not, add it).

To add it to the default images, the renovatebot/base-image image will need to be amended to add this tool.

Note

Installed-by-default-tools will generally only be allowed for the \"full\" image.

"},{"location":"docker-build-process/#building-the-docker-image-locally","title":"Building the Docker image locally","text":"

Renovate's Docker image can be built locally like so:

pnpm build\npnpm build:docker\n# or to customize the build\nenv OWNER=jamietanna pnpm build:docker build --platform linux/amd64 --version 0.0.0-local\n
"},{"location":"docker/","title":"Docker","text":"

Renovate supports upgrading dependencies in various types of Docker definition files:

"},{"location":"docker/#how-it-works","title":"How It Works","text":"
  1. Renovate searches in each repository for any files matching each manager's configured managerFilePatterns
  2. Matching files are parsed, Renovate checks if the file(s) has any Docker image references (e.g. FROM lines in a Dockerfile)
  3. If the image tag in use \"looks\" like a version (e.g. myimage:1, myimage:1.1, myimage:1.1.0, myimage:1-onbuild) then Renovate checks the Docker registry for upgrades (e.g. from myimage:1.1.0 to myimage:1.2.0)
"},{"location":"docker/#preservation-of-version-precision","title":"Preservation of Version Precision","text":"

By default, Renovate preserves the precision level specified in the Docker images. For example, if the existing image is pinned at myimage:1.1 then Renovate only proposes upgrades to myimage:1.2 or myimage:1.3. This means that you will not get upgrades to a more specific versions like myimage:1.2.0 or myimage:1.3.0. Renovate does not yet support \"pinning\" an imprecise version to a precise version, e.g. from myimage:1.2 to myimage:1.2.0, but it's a feature we'd like to work on one day.

"},{"location":"docker/#version-compatibility","title":"Version compatibility","text":"

Although suffixes in SemVer indicate pre-releases (e.g. v1.2.0-alpha.2), in Docker they typically indicate compatibility, e.g. 1.2.0-alpine. By default Renovate assumes suffixes indicate compatibility, for this reason Renovate will not change any suffixes. Renovate will update 1.2.0-alpine to 1.2.1-alpine but never updates to 1.2.1 or 1.2.1-stretch as that would change the suffix.

If this behavior does not suit a particular package you have, Renovate allows you to customize the versioning scheme it uses. For example, you have a Docker image foo/bar that sticks to SemVer versioning. This means that you need to tell Renovate that suffixes indicate pre-release versions, and not compatibility.

You could then use this packageRules array, to tell Renovate to use semver versioning for the foo/bar package:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"foo/bar\"],\n      \"versioning\": \"semver\"\n    }\n  ]\n}\n

Another example is the official python image, which follows pep440 versioning.

Telling Renovate to use the pep440 versioning scheme
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"python\"],\n      \"versioning\": \"pep440\"\n    }\n  ]\n}\n

If traditional versioning doesn't work, try Renovate's built-in loose versioning. Renovate will perform a best-effort sort of the versions, regardless of whether they have letters or digits.

If both the traditional versioning, and the loose versioning do not give the results you want, try the regex versioning. This approach uses regex capture group syntax to specify which part of the version string is major, minor, patch, pre-release, or compatibility. See the docs for versioning for documentation and examples of regex versioning in action.

"},{"location":"docker/#digest-pinning","title":"Digest Pinning","text":"

We recommend that you pin your Docker images to an exact digest. By pinning to a digest you make your Docker builds immutable, every time you do a pull you get the same content.

If you work with dependencies in the JavaScript/npm ecosystem, you may be used to exact versions being immutable. For example, if you set a version like 2.0.1, you and your colleagues always get the exact same \"code\".

Docker's tags are not immutable versions, even if tags look like a version. You probably expect myimage:1 and myimage:1.2 to change over time, but you might incorrectly assume that myimage:1.2.0 never changes. Although it probably shouldn't, the reality is that any Docker image tag can change content, and potentially break.

By replacing Docker tags with Docker digests as the image's primary identifier you'll get immutable builds. Working with strings like FROM node@sha256:d938c1761e3afbae9242848ffbb95b9cc1cb0a24d889f8bd955204d347a7266e is hard. Luckily Renovate can update the digests for you.

When pinning a digest, Renovate retains the Docker tag in the FROM line for readability, like this: FROM node:14.15.1@sha256:d938c1761e3afbae9242848ffbb95b9cc1cb0a24d889f8bd955204d347a7266e.

"},{"location":"docker/#digest-updating","title":"Digest Updating","text":"

If you follow our advice to replace a tag like node:14 with a pinned digest like node:14@sha256:d938c1761e3afbae9242848ffbb95b9cc1cb0a24d889f8bd955204d347a7266e, you will get Renovate PRs whenever the node:14 image is updated on Docker Hub.

Previously this update would have been \"invisible\" to you - one day you pull code that represents node:14.15.0 and the next day you pull code that represents node:14.15.1. But you can never be sure, especially as Docker caches. Maybe some of your colleagues, or worse still your build machine, are stuck on an older version with a security vulnerability.

By pinning to a digest instead, you will get these updates via Pull Requests, or even committed directly to your repository if you enable branch automerge for convenience. This makes sure everyone on your team uses the latest versions.

"},{"location":"docker/#version-upgrading","title":"Version Upgrading","text":"

Renovate also supports upgrading versions in Docker tags, so from myimage:1.2.0 to myimage:1.2.1, or from myimage:1.2 to myimage:1.3. If a tag looks like a version, Renovate will upgrade it like a version.

We recommend you use the major.minor.patch tagging scheme, so change myimage:1 to myimage:1.1.1 first. This way you can see the changes in Renovate PRs. You can see the difference between a PR that upgrades myimage from 1.1.1 to 1.1.2 and a PR that changes the contents of the version you already use (1.1.1).

By default, Renovate will upgrade major, minor and patch versions. If you do not want major updates: add the preset docker:disableMajor to the extends array in your renovate.json file.

Renovate has some Docker-specific intelligence when it comes to versions. For example:

"},{"location":"docker/#ubuntu-codenames","title":"Ubuntu codenames","text":"

Renovate understands Ubuntu release code names and will offer upgrades to the latest LTS release.

You must only use the first term of the code name in lowercase. So use noble for the Noble Numbat release.

For example, Renovate will offer to upgrade the following Dockerfile layer:

- FROM ubuntu:jammy\n+ FROM ubuntu:noble\n
"},{"location":"docker/#debian-codenames","title":"Debian codenames","text":"

Renovate understands Debian release code names and rolling updates schedule and will offer upgrades to the latest stable release. For example from debian:bullseye to debian:bookworm.

Renovate also supports dated container image versions for Debian, such as debian:bookworm-20230816 or debian:bullseye-20220101.2. These are commonly used in Debian Docker images to pin to specific snapshots.

The Debian codename must be in lowercase.

For example, Renovate will offer to upgrade the following Dockerfile layer:

- FROM debian:bullseye\n+ FROM debian:bookworm\n

Or for dated versions:

- FROM debian:bookworm-20230816\n+ FROM debian:bookworm-20230901\n
"},{"location":"docker/#configuringdisabling","title":"Configuring/Disabling","text":"

If you wish to make changes that apply to all Docker managers, then add them to the docker config object. This is not foolproof, because some managers like circleci and ansible support multiple datasources that do not inherit from the docker config object.

If you wish to override Docker settings for one particular type of manager, use that manager's config object instead. For example, to disable digest updates for Docker Compose only but leave them for other managers like Dockerfile, you would use this:

{\n  \"docker-compose\": {\n    \"digest\": {\n      \"enabled\": false\n    }\n  }\n}\n

The following configuration options are applicable to Docker:

"},{"location":"docker/#disable-all-docker-renovation","title":"Disable all Docker Renovation","text":"

Add \"docker:disable\" to your extends array.

"},{"location":"docker/#disable-renovate-for-only-certain-dockerfiles","title":"Disable Renovate for only certain Dockerfiles","text":"

Add all paths to ignore into the ignorePaths configuration field. e.g.

{\n  \"extends\": [\"config:recommended\"],\n  \"ignorePaths\": [\"docker/old-files/\"]\n}\n
"},{"location":"docker/#disable-docker-major-updates","title":"Disable Docker major updates","text":"

Add \"docker:disableMajor\" to your extends array.

"},{"location":"docker/#disable-digest-pinning","title":"Disable digest pinning","text":"

Add \"default:pinDigestsDisabled\" to your extends array.

Note

This preset only sets the global default for the digest pinning flag to false. If you have configured package rules that set pinDigests to true, those will still apply. This is also the case if you use the docker:pinDigests preset, which adds a package rule that sets pinDigests to true for all packages from the docker datasource.

If you want to disable the docker:pinDigests preset (e.g. if you want to use config:best-practices but not have digest pinning enabled), ignore the preset like this:

{\n  \"extends\": [\"config:best-practices\"],\n  \"ignorePresets\": [\"docker:pinDigests\"]\n}\n
"},{"location":"docker/#automerge-digest-updates","title":"Automerge digest updates","text":"

Add \"default:automergeDigest\" to your extends array. If you want Renovate to commit directly to your base branch without opening a PR first, add \"default:automergeBranchPush\" to the extends array.

"},{"location":"docker/#registry-authentication","title":"Registry authentication","text":"

There are many different registries, and many ways to authenticate to those registries. We will explain how to authenticate for the most common registries.

"},{"location":"docker/#docker-hub","title":"Docker Hub","text":"

Here is an example of configuring a Docker username/password for Docker Hub in config.js. The Docker Hub password is stored in a process environment variable.

config.js
module.exports = {\n  hostRules: [\n    {\n      hostType: 'docker',\n      matchHost: 'docker.io',\n      username: '<your-username>',\n      password: process.env.DOCKER_HUB_PASSWORD,\n    },\n  ],\n};\n

You can add more host rules, read the hostRules documentation for more information.

"},{"location":"docker/#self-hosted-docker-registry","title":"Self-hosted Docker registry","text":"

Say you host some Docker images yourself, and use a password to access your self-hosted Docker images. In addition to self-hosting, you also pull images from Docker Hub, without a password. In this example you would configure a specific Docker host like this:

module.exports = {\n  hostRules: [\n    {\n      hostType: 'docker',\n      matchHost: 'your.host.io',\n      username: '<your-username>',\n      password: process.env.SELF_HOSTED_DOCKER_IMAGES_PASSWORD,\n    },\n  ],\n};\n
"},{"location":"docker/#aws-ecr-amazon-web-services-elastic-container-registry","title":"AWS ECR (Amazon Web Services Elastic Container Registry)","text":""},{"location":"docker/#using-access-key-id-secret","title":"Using access key id & secret","text":"

Renovate can authenticate with AWS ECR using AWS access key id & secret as the username & password, for example:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"docker\",\n      \"matchHost\": \"12345612312.dkr.ecr.us-east-1.amazonaws.com\",\n      \"username\": \"AKIAABCDEFGHIJKLMNOPQ\",\n      \"encrypted\": {\n        \"password\": \"w...A\"\n      }\n    }\n  ]\n}\n
"},{"location":"docker/#using-get-login-password","title":"Using get-login-password","text":"

Renovate can also authenticate with AWS ECR using the output from the aws ecr get-login-password command as outlined in the AWS documentation. To make use of this authentication mechanism, specify the username as AWS:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"docker\",\n      \"matchHost\": \"12345612312.dkr.ecr.us-east-1.amazonaws.com\",\n      \"username\": \"AWS\",\n      \"encrypted\": {\n        \"password\": \"w...A\"\n      }\n    }\n  ]\n}\n
"},{"location":"docker/#google-container-registry-google-artifact-registry","title":"Google Container Registry / Google Artifact Registry","text":""},{"location":"docker/#using-workload-identity","title":"Using Workload Identity","text":"

To let Renovate authenticate with Workload Identity, you must:

"},{"location":"docker/#with-application-default-credentials-self-hosted-only","title":"With Application Default Credentials (self-hosted only)","text":"

To let Renovate authenticate with ADC, you must:

Renovate will get the credentials with the google-auth-library.

"},{"location":"docker/#with-short-lived-access-token-github-actions-self-hosted-only","title":"With short-lived access token / GitHub Actions (self-hosted only)","text":"Example for Workload Identity plus Renovate host rules
- name: authenticate to google cloud\n  id: auth\n  uses: google-github-actions/auth@v3.0.0\n  with:\n    token_format: 'access_token'\n    workload_identity_provider: ${{ env.WORKLOAD_IDENTITY_PROVIDER }}\n    service_account: ${{ env.SERVICE_ACCOUNT }}\n\n- name: renovate\n  uses: renovatebot/github-action@v46.3.10\n  env:\n    RENOVATE_HOST_RULES: |\n      [\n        {\n          matchHost: \"us-central1-docker.pkg.dev\",\n          hostType: \"docker\",\n          username: \"oauth2accesstoken\",\n          password: \"${{ steps.auth.outputs.access_token }}\"\n        }\n      ]\n  with:\n    token: ${{ secrets.RENOVATE_TOKEN }}\n    configurationFile: .github/renovate.json5\n

You can find a full GitHub Workflow example on the renovatebot/github-action repository.

"},{"location":"docker/#using-long-lived-service-account-credentials","title":"Using long-lived service account credentials","text":"

To access the Google Container Registry (deprecated) or the Google Artifact Registry, use the JSON service account with Basic authentication, and use the:

To avoid JSON-in-JSON wrapping, which can cause problems, encode the JSON service account beforehand.

Google Container Registry does not natively support _json_key_base64 and a base64 encoded service account. Google Artifact Registry supports _json_key_base64 and a base64 encoded service account natively. If all your dependencies are on the Google Artifact Registry, you can base64 encode and use the service account directly:

  1. Download your JSON service account and store it on your machine. Make sure that the service account has read (and only read) permissions to your artifacts
  2. Base64 encode the service account credentials by running cat service-account.json | base64

  3. Add the encoded service account to your configuration file

    1. If you want to add it to your self-hosted configuration file:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-docker.pkg.dev\",\n      \"username\": \"_json_key_base64\",\n      \"password\": \"<base64 service account>\"\n    }\n  ]\n}\n```\n

    2. If you want to add it to your repository Renovate configuration file, encrypt it and then add it:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-docker.pkg.dev\",\n      \"username\": \"_json_key_base64\",\n      \"encrypted\": {\n        \"password\": \"<encrypted base64 service account>\"\n      }\n    }\n  ]\n}\n```\n

If you have dependencies on Google Container Registry (and Artifact Registry) you need to use _json_key and a slightly different encoding:

  1. Download your JSON service account and store it on your machine. Make sure that the service account has read (and only read) permissions to your artifacts

  2. Open the file and prefix the content with _json_key:. The file should look like this:

    _json_key:{\n  \"type\": \"service_account\",\n  \"project_id\": \"sample-project\",\n  \"private_key_id\": \"5786ff7e615522b932a2a37b4a6f9645c4316dbd\",\n  \"private_key\": \"-----BEGIN PRIVATE KEY-----\\nMIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQDaOkxZut9uDUHV\\n...\\n/PWs0Wa2z5+IawMD7nO63+b6\\n-----END PRIVATE KEY-----\\n\",\n  \"client_email\": \"renovate-lookup@sample-project.iam.gserviceaccount.com\",\n  \"client_id\": \"115429165445403928973\",\n  \"auth_uri\": \"https://accounts.google.com/o/oauth2/auth\",\n  \"token_uri\": \"https://oauth2.googleapis.com/token\",\n  \"auth_provider_x509_cert_url\": \"https://www.googleapis.com/oauth2/v1/certs\",\n  \"client_x509_cert_url\": \"https://www.googleapis.com/robot/v1/metadata/x509/renovate-lookup%40sample-project.iam.gserviceaccount.com\"\n}\n

  3. Base64 encode the prefixed service account credentials by running cat prefixed-service-account.json | base64

  4. Add the prefixed and encoded service account to your configuration file

    1. If you want to add it to your self-hosted configuration file:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-docker.pkg.dev\",\n      \"authType\": \"Basic\",\n      \"token\": \"<base64 prefixed service account>\"\n    }\n  ]\n}\n```\n

    2. If you want to add it to your repository Renovate configuration file, encrypt it and then add it:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-docker.pkg.dev\",\n      \"authType\": \"Basic\",\n      \"encrypted\": {\n        \"token\": \"<encrypted base64 prefixed service account>\"\n      }\n    }\n  ]\n}\n```\n
"},{"location":"docker/#using-short-lived-access-token-gitlab-ci-google-cloud","title":"Using short-lived access token / Gitlab CI / Google Cloud","text":"

For this example, assume that you want to:

"},{"location":"docker/#accessing-the-google-container-registry","title":"Accessing the Google Container Registry","text":"

Accessing the GCR uses Bearer token based authentication.

First, install the Google Cloud SDK. Then get the token by running: gcloud auth print-access-token.

"},{"location":"docker/#short-lived-gcr-bearer-tokens","title":"Short-lived GCR Bearer tokens","text":"

The GCR Bearer token expires after 60 minutes. This means you can not re-use the token in a later build.

Instead, before Renovate starts in the GCR context, you must:

  1. Fetch the Google access token
  2. Inject the token into the hostRules configuration

The following text explains one way to fetch the token, and inject it into Renovate.

"},{"location":"docker/#basic-approach","title":"Basic approach","text":"

The basic approach is:

  1. Create a custom image: fetch the GCR token, and inject the token into Renovate's config.js file
  2. Then run Renovate as one of the stages of your project
"},{"location":"docker/#independent-runs","title":"Independent runs","text":"

To make the run independent of any user, use a Project Access Token. Give the Project Access Token these scopes:

Then use the Project Access Token as the RENOVATE_TOKEN variable for GitLab CI. For more (gitlab-ci.yml) configuration examples, see the renovate-runner repository on GitLab.

"},{"location":"docker/#create-a-custom-image","title":"Create a custom image","text":"

To access the token, you need a custom Renovate Docker image. Make sure to install the Google Cloud SDK into the custom image, as you need the gcloud auth print-access-token command later.

For example:

FROM renovate/renovate:44.133.0\n# Include the \"Docker tip\" which you can find here https://cloud.google.com/sdk/docs/install\n# under \"Installation\" for \"Debian/Ubuntu\"\nRUN ...\n
"},{"location":"docker/#accessing-the-google-container-registry-gcr","title":"Accessing the Google Container Registry (GCR)","text":"

Renovate needs the current Google Access Token to access the Google Container Registry (GCR). Here's an example of how to set that up:

hostRules: [\n  {\n    matchHost: 'eu.gcr.io',\n    token: 'MyReallySecretTokenThatExpiresAfter60Minutes',\n  },\n];\n

One way to give Renovate the short-lived Google Access Token is to:

  1. Write a script that generates a config.js file, with the token, in your gitlab-ci.yml file
  2. Run the config.js creation script just before you start Renovate

For example:

script:\n  - 'echo \"module.exports = { hostRules: [ { matchHost: ''eu.gcr.io'', token: ''\"$(gcloud auth print-access-token)\"'' } ] };\" > config.js'\n  - renovate $RENOVATE_EXTRA_FLAGS\n
"},{"location":"environment-variable-handling/","title":"Environment Variable Handling","text":""},{"location":"environment-variable-handling/#for-renovate","title":"For Renovate","text":"

Renovate itself can be configured through a number of environment variables that correspond with global self-hosted configuration options, as well as some repository configuration options. These environment variables have the prefix with RENOVATE_.

Renovate also has some \"experimental\" variables that can be used with self-hosted deployments.

It is also possible to use the following configuration options to control Renovate's environment variables:

"},{"location":"environment-variable-handling/#with-child-processes","title":"With child processes","text":"

For security reasons, Renovate does not expose all environment variables to child processes. Instead, Renovate will use an allowlist of environment variables which it passes to any processes it calls.

This is an intentional decision to protect against two key attack vectors:

By limiting the environment variables provided to child processes, we can reduce the risk of a malicious actor from receiving access to potentially sensitive information, such as authentication tokens.

By default, Renovate will always pass the following environment variables to child processes:

Additionally, Renovate will always set the following environment variables to these exact values:

Note

Some managers pass additional environment variables where necessary. For example, Renovate will convert Host Rules to the respective environment variables when calling npm, pnpm and yarn, including setting GIT_CONFIG_ environment variables. This is not currently documented in full - you will need to review Renovate's code to see the full list.

As a self-hosted administrator, you can make it possible to specify other environment variables that repository owners can set, using:

With these option(s) configured, users will be able to set these environment variable(s) in their repository configuration using env, as well as referencing them in any fields that support templating.

"},{"location":"environment-variable-handling/#using-environment-variables-for-secrets","title":"Using environment variables for secrets","text":"

Where possible, Renovate will try and redact secrets in its log messages, and the log output from any child processes. This relies on knowing whether the value is a secret for instance those configured through secrets or in hostRules.

If specifying an environment variable - through the above - with a value that isn't known to Renovate as a secret, this may lead to the secret being unknowingly exposed in the logs.

"},{"location":"environment-variable-handling/#precedence","title":"Precedence","text":"

When determining which environment variables Renovate should pass to a child process, Renovate merges with the following precedence order:

flowchart TD\n    extraEnv[\"<strong><code>extraEnv</code></strong><br/><small>Manager-defined defaults/hints string value = default, null = inherit key only</small>\"]\n    parentEnv[\"<strong><code>parentEnv</code></strong><br/><small>process.env filtered to basicEnvVars<sup>1</sup> + string keys from extraEnv</small>\"]\n    globalConfigEnv[\"<strong><code>globalConfigEnv</code></strong><br/><small><code>customEnvVariables</code> set by self-hosted admin at startup</small>\"]\n    userConfiguredEnv[\"<strong><code>userConfiguredEnv</code></strong><br/><small><code>env</code> config in Renovate config file</small>\"]\n    forcedEnv[\"<strong><code>forcedEnv</code></strong><br/><small>Hardcoded per exec-call by Renovate internals</small>\"]\n    childProcess[\"<strong>Child Process</strong>\"]\n    exposeAllEnv[\"<strong><code>exposeAllEnv = true</code></strong><br/><small>Bypasses all layering, passes entire <code>process.env</code></small>\"]\n    processEnvConfig[\"<strong><code>processEnv</code></strong><br/><small></small>\"]\n    processEnv[\"<strong><code>process.env</code></strong><br/><small>The original process' <code>process.env</code> and <code>processEnv</code></small>\"]\n    allowedEnv[\"<strong><code>allowedEnv</code></strong><br/><small>Admin-controlled allowlist gates which environment variables repo owners may set</small>\"]\n\n    extraEnv -->|\"overridden by\"| parentEnv\n    parentEnv -->|\"overridden by\"| globalConfigEnv\n    globalConfigEnv -->|\"overridden by\"| userConfiguredEnv\n    userConfiguredEnv -->|\"overridden by\"| forcedEnv\n    forcedEnv --> childProcess\n\n    exposeAllEnv -.->|\"short-circuits to\"| childProcess\n    processEnvConfig -.->|\"merged into\"| processEnv\n    processEnv -.->|\"filtered with <code>basicEnvVars</code>\"| parentEnv\n    allowedEnv -.->|\"restricts\"| userConfiguredEnv\n

1: the list of environment variables noted above that are always passed to child processes

"},{"location":"environment-variable-handling/#templating","title":"Templating","text":"

Allowlisted environment variables can be referenced in templates. See templates and environment variables for more details.

"},{"location":"faq/","title":"Frequently Asked Questions (FAQ)","text":""},{"location":"faq/#what-is-the-default-behavior","title":"What is the default behavior?","text":"

Renovate will:

"},{"location":"faq/#which-renovate-versions-are-officially-supported","title":"Which Renovate versions are officially supported?","text":"

Only the latest version of Renovate is supported by the Renovate maintainers. The Renovate team only fixes bugs in an older version if:

If you're using the Mend Renovate App, you don't need to do anything, as the Renovate maintainers update it regularly. If you're self hosting Renovate, use the latest release if possible.

"},{"location":"faq/#renovate-core-features-not-supported-on-all-platforms","title":"Renovate core features not supported on all platforms","text":"Feature Platforms which lack feature Dependency Dashboard Bitbucket, Bitbucket Server, Gerrit, SCM-Manager The Mend Renovate App Bitbucket Server, Forgejo, Gitea, SCM-Manager"},{"location":"faq/#major-platform-features-not-supported-by-renovate","title":"Major platform features not supported by Renovate","text":"

Some major platform features are not supported at all by Renovate.

Feature name Platform See Renovate issue(s) Jira issues Bitbucket #20568 Jira issues Bitbucket Server #3796 Configurable merge strategy and message Only Bitbucket, Forgejo and Gitea for now #10867 #10869 #10870"},{"location":"faq/#what-is-this-main-branch-i-see-in-the-documentation","title":"What is this main branch I see in the documentation?","text":"

When you create a new repository with Git, Git creates a base branch for you. The default branch name that Git uses is master (this will be changed to main later).

The Git-hosting ecosystem decided to use main instead of master. When you create a new repository on say GitHub or GitLab, you'll get a main branch as your base branch.

We replaced master with main in our documentation where possible.

A branch name has no special meaning within the Git program, it's only a name. The base branch could be called trunk or mainline or prod, and Git would work just as well.

"},{"location":"faq/#what-if-i-need-to","title":"What if I need to .. ?","text":""},{"location":"faq/#troubleshoot-renovate","title":"Troubleshoot Renovate","text":"

If you have problems with Renovate, or want to know where Renovate keeps the logging output then read our troubleshooting documentation.

"},{"location":"faq/#tell-renovate-to-ask-for-approval-before-creating-a-pull-request","title":"Tell Renovate to ask for approval before creating a Pull Request","text":"

By default, Renovate creates a pull request right away whenever there's an update. But maybe you want Renovate to ask for your approval before it creates a pull request. Use the \"Dependency Dashboard approval\" workflow to get updates for certain packages - or certain types of updates - only after you give approval via the Dependency Dashboard.

The basic idea is that you create a new packageRules entry and describe what kind of package, or type of updates you want to approve beforehand.

Manually approve all major npm package manager updates
{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"major\"],\n      \"matchManagers\": [\"npm\"],\n      \"dependencyDashboardApproval\": true\n    }\n  ]\n}\n
Manually approve all major Jest updates
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"jest\"],\n      \"matchUpdateTypes\": [\"major\"],\n      \"dependencyDashboardApproval\": true\n    }\n  ]\n}\n

You may even configure Renovate to ask for approval for all updates. The dependencyDashboardApproval config option is outside of a packageRules array, and so applies to all updates:

{\n  \"dependencyDashboardApproval\": true\n}\n

Read our documentation on the dependencyDashboardApproval config option.

"},{"location":"faq/#use-an-alternative-branch-as-my-pull-request-target","title":"Use an alternative branch as my Pull Request target","text":"

Say your repository's default branch is main but you want Renovate to use the next branch as its PR target. You can configure the PR target branch via the baseBranchPatterns option.

Add this line to the renovate.json file that's in the default branch (main in this example).

{\n  \"baseBranchPatterns\": [\"next\"]\n}\n

You can set more than one PR target branch in the baseBranchPatterns array.

"},{"location":"faq/#support-private-npm-modules","title":"Support private npm modules","text":"

See the dedicated Private npm module support page.

"},{"location":"faq/#control-renovates-schedule","title":"Control Renovate's schedule","text":"

To learn about controlling Renovate schedule, read the key concepts, scheduling docs.

"},{"location":"faq/#disable-renovate-for-certain-dependency-types","title":"Disable Renovate for certain dependency types","text":"

Define a packageRules entry which has the dependency type(s) in matchDepTypes and \"enabled\": false.

"},{"location":"faq/#use-a-single-branchpr-for-all-dependency-upgrades","title":"Use a single branch/PR for all dependency upgrades","text":"

Add a configuration for configuration option groupName set to value \"all\", at the top level of your renovate.json or package.json.

"},{"location":"faq/#use-separate-branches-per-dependency-but-not-one-per-major-release","title":"Use separate branches per dependency, but not one per major release","text":"

Set configuration option separateMajorMinor to false.

"},{"location":"faq/#keep-using-semver-ranges-instead-of-pinning-dependencies","title":"Keep using SemVer ranges, instead of pinning dependencies","text":"

Set configuration option rangeStrategy to \"replace\".

"},{"location":"faq/#keep-lock-files-including-sub-dependencies-up-to-date-even-when-packagejson-hasnt-changed","title":"Keep lock files (including sub-dependencies) up-to-date, even when package.json hasn't changed","text":"

By default, if you enable lock-file maintenance, Renovate will update the lockfile [\"before 4am on monday\"]. If you want to update the lock file more often, set the schedule field inside the lockFileMaintenance object.

"},{"location":"faq/#wait-until-tests-have-passed-before-creating-the-pr","title":"Wait until tests have passed before creating the PR","text":"

Set the configuration option prCreation to \"status-success\". Branches with failing tests will remain in Git and get updated if needed. Renovate will only create a PR once the tests pass.

"},{"location":"faq/#wait-until-tests-have-passed-before-creating-a-pr-but-create-the-pr-even-if-they-fail","title":"Wait until tests have passed before creating a PR, but create the PR even if they fail","text":"

Set the configuration option prCreation to \"not-pending\".

"},{"location":"faq/#assign-prs-to-specific-users","title":"Assign PRs to specific user(s)","text":"

Set the configuration option assignees to an array of usernames.

"},{"location":"faq/#add-labels-to-prs","title":"Add labels to PRs","text":"

Set the configuration option labels to an array of labels to use.

"},{"location":"faq/#apply-a-rule-but-only-to-package-abc","title":"Apply a rule, but only to package abc?","text":"
  1. Add a packageRules array to your configuration
  2. Create one object inside this array
  3. Set field matchPackageNames to value [\"abc\"]
  4. Add the configuration option to the same object

e.g.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"abc\"],\n      \"assignees\": [\"importantreviewer\"]\n    }\n  ]\n}\n
"},{"location":"faq/#apply-a-rule-but-only-for-packages-starting-with-abc","title":"Apply a rule, but only for packages starting with abc","text":"

Do the same as above, but instead of an exact match, use a glob prefix:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": \"abc**\",\n      \"assignees\": [\"importantreviewer\"]\n    }\n  ]\n}\n

For more examples, see String Pattern Matching, example glob patterns.

"},{"location":"faq/#group-all-packages-starting-with-abc-together-in-one-pr","title":"Group all packages starting with abc together in one PR","text":"

As above, but apply a groupName:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": \"abc**\",\n      \"groupName\": \"abc packages\"\n    }\n  ]\n}\n
"},{"location":"faq/#change-the-default-values-for-branch-name-commit-message-pr-title-or-pr-description","title":"Change the default values for branch name, commit message, PR title or PR description","text":"

You can use the branchName, commitMessage, prTitle or prBody configuration options to change the defaults for those settings.

"},{"location":"faq/#automatically-merge-passing-pull-requests","title":"Automatically merge passing Pull Requests","text":"

Set the configuration option automerge to true. Nest it inside a patch or minor object if you only want to automerge certain types of updates.

"},{"location":"faq/#separate-patch-releases-from-minor-releases","title":"Separate patch releases from minor releases","text":""},{"location":"faq/#renovates-default-behavior-for-majorminor-releases","title":"Renovate's default behavior for major/minor releases","text":"

By default, Renovate separates major and minor releases. Patch releases are treated as \"minor\". Here's an example:

Say you're using version 0.8.0 of the foo package. The foo maintainers release the following versions:

Renovate creates the following PRs:

Renovate groups the patch and minor versions into one PR. This means you only get a PR for the minor version, 0.9.0.

You can override this default behavior. To learn more read the section below.

"},{"location":"faq/#overriding-the-default-behavior-for-majorminor-releases","title":"Overriding the default behavior for major/minor releases","text":"

You can see in the example above that Renovate won't normally create a PR for the foo patch release.

You can tell Renovate to create a separate PR for the patch release by setting separateMinorPatch to true.

In both cases, Renovate will open 3 PRs:

Usually you don't want more PRs though. It can be nice to get patch PRs when you're using automerge:

This means you barely notice Renovate during the week, while you still get the benefits of patch level updates.

"},{"location":"faq/#whats-the-difference-between-depname-and-packagename","title":"What's the difference between depName and packageName?","text":"

Renovate uses two important config options to define a dependency's name: depName and packageName.

The depName is the short \"pretty name\" of the dependency. This is the user-facing name for the dependency. By default, Renovate uses the depName:

The packageName is the full exact name. Renovate uses the packageName to find the dependency in the package registry.

Often depName and packageName are the same, but not always.

Renovate uses the \"pretty\" depName in branch names and PR titles/content, because the depName is easier to read than the packageName.

For instance, given the following Gradle plugin:

plugins {\n    id(\"com.gradle.develocity\").version(\"3.18.1\")\n}\n

Renovate will give the dependency these properties:

Again, often the depName and packageName are equal. The names Renovate uses for the depName and packageName depend on the package manager (and package ecosystem naming conventions). For instance, depName and packageName may be different when you proxy Docker images.

"},{"location":"gitlab-bot-security/","title":"Security considerations when running Renovate against GitLab.com","text":"

Make sure you understand GitLab's security model before you run Renovate against GitLab, whether through the Mend-hosted app or a self-hosted deployment.

Warning

If you have any doubts or concerns about this content that could affect other users, please follow our Security Policy and report them confidentially.

"},{"location":"gitlab-bot-security/#mend-hosted-renovate","title":"Mend-hosted Renovate","text":"

In July 2026, Mend relaunched its hosted Renovate app for GitLab.com. You can set it up by following these instructions when logging into the Mend Developer Platform.

Tip

The GitLab user who onboards an organization becomes the account used to create commit statuses, issues, and MRs. Mend recommends creating a dedicated user solely for the integration with the Mend Developer Platform, and completing the rest of the installation as that dedicated user, rather than using a personal account.

The previous Mend-hosted Renovate for GitLab.com ran inside GitLab CI, using CI_JOB_TOKEN credentials, which we found too risky to run as a shared service and retired. Although GitLab has improved this since we retired the previous hosted app, we have since relaunched the app using an OAuth app, which avoids those risks.

"},{"location":"gitlab-bot-security/#security-model","title":"Security model","text":""},{"location":"gitlab-bot-security/#running-in-gitlab-ci","title":"Running in GitLab CI","text":"

GitLab's CI job-token permission model (the token was called CI_BUILD_TOKEN until it was renamed CI_JOB_TOKEN in GitLab 9.0) was overhauled in GitLab 8.12 (2016-09), so jobs now run with the permissions of the user account which triggered the pipeline. The token was originally limited to read-only permissions and a small set of API endpoints, but its write scope has grown significantly since: it can now push to its own project's repository, push cross-project to allowlisted projects, publish to the Package Registry, and more. Historically, any pipeline triggered by a user account thus had permissions to:

This is why we retired the original Mend-hosted GitLab app: a pipeline run for one customer, under a shared bot account, could read or write to any other project that account had access to.

GitLab introduced a CI/CD job token allowlist in GitLab 15.9 (2023-02): a job token from one project can no longer authenticate against another project's API just because the triggering user has access to both. The target project must explicitly add the source project, or group, to its allowlist first, and the triggering user must still have their own permission to perform the action. As of GitLab 18.0 (2025-05), this allowlist is enabled and enforced for every project on GitLab.com, including projects created before the allowlist existed, and can't be disabled there. If you administer a GitLab Self-Managed or Dedicated instance, note that admins can still disable this instance-wide setting even on GitLab 18.0+, so confirm it's actually enforced rather than switched off.

Even with the allowlist enabled, public and internal projects still expose some resources, such as artifacts, the container/package registry, releases, and repository contents, to a job token from any project, allowlisted or not. So the advice below still applies regardless of allowlist status.

If you run Renovate yourself inside your own GitLab CI pipelines, you should still only commit to a project you trust completely, since a malicious project could steal repository data, publish fake releases, or spam releases within its allowlisted scope. You should also remember that when accounts are invited into projects or groups on GitLab, acceptance happens automatically. If you are running a shared self-hosted Renovate service, we recommend you:

"},{"location":"gitlab-bot-security/#running-as-an-oauth-app","title":"Running as an OAuth app","text":"

An alternative to running with a shared user's personal access token is to run using per-installation OAuth tokens: users explicitly authorize an OAuth app to act on specific groups or projects they choose, rather than a shared bot account being invited, and auto-accepted, into projects without its own consent.

This is the model the relaunched Mend-hosted GitLab app uses. It avoids the \"single shared bot identity reachable from every onboarded customer\" failure mode described above, since each authorization is scoped to the projects or groups an admin actually selects, and commits/Merge Requests are attributable to that authorization rather than one global bot account. We considered Project and Group Access Tokens as an alternative, but both remain gated behind paid tiers on gitlab.com, which would have excluded free-plan users from the service.

One limitation to be aware of: GitLab's OAuth scopes (api, read_repository, write_repository, and so on) are granted at the level of the authorizing user, not restricted to specific projects by GitLab itself. The resulting token is therefore as capable as the authorizing user's own GitLab account, not limited to the group(s) selected during onboarding, by any GitLab-enforced boundary, unlike a Project Access Token, which GitLab itself would restrict to a single project. GitLab does support project/group-scoped access for fine-grained personal access tokens, but not yet for OAuth application tokens.

"},{"location":"gitlab-bot-security/#acknowledgments","title":"Acknowledgments","text":"

Thank you to Nejc Habjan for bringing this security challenge to our attention, and also to his colleagues at Siemens for their help researching the risks. Thanks also to the GitLab security team for being responsive to our questions.

"},{"location":"golang/","title":"Automated Dependency Updates for Go Modules","text":"

Renovate supports upgrading dependencies in go.mod files and associated go.sum checksums.

If you're self-hosting Renovate, you may use these environment variables:

To learn what these variables do, read the Go Modules Reference about theGOPROXY protocol.

"},{"location":"golang/#how-it-works","title":"How It Works","text":"
  1. Renovate searches in each repository for any go.mod files
  2. Renovate extracts existing dependencies from require statements
  3. Renovate resolves the dependency's source repository and checks for SemVer tags if found. Otherwise commits and v0.0.0-.... syntax will be used
  4. If Renovate finds an update, Renovate will update go.mod to the new value
  5. Renovate runs go get to update the go.sum files (you can configure which directories are included using the goGetDirs option)
  6. If the user has enabled the option gomodUpdateImportPaths in the postUpdateOptions array, then Renovate uses mod to update import paths on major updates, which can update any Go source file
  7. If the user has any of the available gomodTidy options (e.g. gomodTidy1.17) in the postUpdateOptions, then Renovate runs go mod tidy with the respective options (multiple options are allowed).
  8. go mod vendor is run if vendored modules are detected
  9. A PR will be created with go.mod,go.sum, and any updated vendored files updated in the one commit
  10. If the source repository has either a \"changelog\" file or uses GitHub releases, then Release Notes for each version will be embedded in the generated PR
"},{"location":"golang/#enabling-go-modules-updating","title":"Enabling Go Modules Updating","text":"

Renovate updates Go Modules by default. To install Renovate itself, either enable the Renovate App on GitHub, or check out Renovate OSS for self-hosted.

"},{"location":"golang/#technical-details","title":"Technical Details","text":""},{"location":"golang/#replace-massaging","title":"Replace massaging","text":"

Renovate can massage replace statements it finds prior to running go commands, and then massage them back afterwards. This capability was added - and originally default behavior - because relative replace statements outside of the current repo will not work when Renovate clones the repo locally.

On the other hand, this massaging of replace statements may lead to unexpected results, especially because go mod tidy may not fully tidy the go.sum if it is missing the replace directives in go.mod. It has therefore been disabled by default.

To enable this replace massaging behavior, add gomodMassage to your postUpdateOptions array.

"},{"location":"golang/#module-tidying","title":"Module Tidying","text":"

Go Modules tidying is not enabled by default, and is opt-in via the postUpdateOptions config option. The reason for this is that a go mod tidy command may make changes to go.mod and go.sum that are completely unrelated to the updated module(s) in the PR, and so may be confusing to some users.

"},{"location":"golang/#monorepo-tidying-for-local-replace-directives","title":"Monorepo tidying for local replace directives","text":"

In Go monorepos it is common for one module to depend on another in the same repo via a local replace directive, for example:

// api/go.mod\nreplace example.com/shared => ../shared\n

When Renovate updates the shared module, running go mod tidy only in that module leaves the dependent go.sum files stale. Add gomodTidyAll to postUpdateOptions to also tidy every go.mod which transitively depends on the updated module, in dependency order. The gomodTidy1.17 and gomodTidyE flags apply to those commands as well. gomodTidyAll implies gomodTidy, so you only need to set one of them. Renovate runs these commands with go -C, so this option needs Go 1.20 or later.

Avoid combining gomodTidyAll with gomodMassage. Massaging comments out the relative replace directives that gomodTidyAll follows, so the two options work against each other. Massaging only rewrites the go.mod of the updated module, and Go ignores replace directives outside the main module, so the tidy commands for the dependent modules still behave correctly. But if the updated module itself uses a relative replace, then massaging removes that directive and go mod tidy fails for that module.

"},{"location":"golang/#module-vendoring","title":"Module Vendoring","text":"

Vendoring of Go Modules is done automatically if vendor/modules.txt is present. Renovate will commit all files changed within the vendor/ folder.

Note

Renovate does not support vendoring major upgrades of Go modules. Follow issue #21010.

"},{"location":"golang/#go-binary-version","title":"Go binary version","text":"

By default, Renovate will keep up with the latest version of the go binary.

You can force Renovate to use a specific version of Go by setting a constraint.

Getting Renovate to use the latest patch version of the 1.23 Go binary
{\n  \"constraints\": {\n    \"go\": \"1.23\"\n  }\n}\n

We do not support patch level versions for the minimum go version. This means you cannot use go 1.23.3, but you can use go 1.23 as a constraint.

"},{"location":"golang/#custom-registry-support-and-authentication","title":"Custom registry support, and authentication","text":"

This example shows how you can use a hostRules configuration to configure Renovate for use with a custom private Go module source using Git to pull the modules when updating go.sum and vendored modules. All token hostRules with a hostType (e.g. github, gitlab, bitbucket, ... ) and host rules without a hostType are setup for authentication.

module.exports = {\n  hostRules: [\n    {\n      matchHost: 'github.enterprise.com',\n      token: process.env.GO_GITHUB_TOKEN,\n      hostType: 'github',\n    },\n    {\n      matchHost: 'someGitHost.enterprise.com',\n      token: process.env.GO_GIT_TOKEN,\n    },\n  ],\n};\n
"},{"location":"golang/#private-go-modules-hosted-on-gitlab","title":"Private Go modules hosted on GitLab","text":"

For private GitLab projects, Renovate must authenticate the ?go-get=1 requests it uses to resolve the source repository of a module. Add a host rule with hostType set to go that uses username and password:

module.exports = {\n  hostRules: [\n    {\n      matchHost: 'gitlab.company.com',\n      hostType: 'go',\n      username: 'renovate-bot',\n      password: process.env.GITLAB_PAT,\n    },\n  ],\n};\n

The password must be a personal access token with the read_api scope. The username can be any non-empty string when the password is a personal access token.

Warning

Use username and password in the go host rule, not token. GitLab only supports Basic authentication for ?go-get=1 requests, and a token results in a Bearer authorization header.

If you do not run Renovate with GitLab as its platform, you also need a host rule with hostType set to gitlab to authenticate the GitLab tags API.

Without the go host rule, GitLab responds to the unauthenticated ?go-get=1 request with a truncated go-import path, so Renovate resolves the wrong repository. Lookups then fail with a 404 response for a tags URL with a truncated project path, for example: https://gitlab.company.com/api/v4/projects/group%2Fsubgroup/repository/tags?per_page=100.

"},{"location":"golang/#private-go-modules-served-by-a-module-proxy","title":"Private Go modules served by a module proxy","text":"

Some Go modules are not served from version control, but instead through a module proxy.

For instance, when interacting with a private Buf Schema Registry (BSR), the Go toolchain is pointed to a module proxy on the BSR, which allows serving the module directly, instead of retrieving it from source control.

They advertise this with a go-import meta tag that uses mod instead of git, for example:

<meta\n  name=\"go-import\"\n  content=\"bsr.example.com/gen/go mod https://bsr.example.com/gen/go\"\n/>\n

When Renovate looks up a module directly, it follows the mod proxy URL, as the go command does.

Renovate looks up a module directly when GOPROXY is set to direct, or the module matches GONOPROXY or GOPRIVATE.

For a private registry, set GOPRIVATE (or GONOPROXY) to the registry's host so that the module is not sent to the public proxy:

GOPRIVATE=bsr.example.com\n

Renovate uses the host rule with hostType set to go to authenticate both the ?go-get=1 request and the requests to the mod proxy:

module.exports = {\n  hostRules: [\n    {\n      matchHost: 'bsr.example.com',\n      hostType: 'go',\n      token: process.env.BSR_TOKEN,\n    },\n  ],\n};\n
"},{"location":"golang/#deriving-go-environment-variables-from-host-rules","title":"Deriving Go environment variables from host rules","text":"

If you're self-hosting Renovate, you can set goEnvFromHostRules to true to have Renovate derive GOPROXY, GONOPROXY and GONOSUMDB from your host rules. Renovate uses the derived values to look up modules and to run go, so you don't have to configure the same hosts twice.

Renovate only derives a value if you have not set the environment variable yourself. If you set GOPRIVATE, Renovate does not derive GONOPROXY, and derives GONOSUMDB as your GOPRIVATE value followed by the go-proxy hosts.

For example, with a private proxy and a GitHub organization whose modules may be private:

module.exports = {\n  goEnvFromHostRules: true,\n  hostRules: [\n    {\n      matchHost: 'bsr.example.com',\n      hostType: 'go-proxy',\n      username: process.env.BSR_USERNAME,\n      password: process.env.BSR_TOKEN,\n    },\n    {\n      matchHost: 'https://github.com/my-org',\n      hostType: 'go',\n      token: process.env.GITHUB_TOKEN,\n    },\n  ],\n};\n

Renovate uses:

GOPROXY=https://bsr.example.com,https://proxy.golang.org,direct\nGONOPROXY=github.com/my-org\nGONOSUMDB=bsr.example.com,github.com/my-org\n

Modules under github.com/my-org are fetched directly from GitHub with the token, and skip both proxies and the public checksum database. Other modules go through bsr.example.com, then the public proxy.

You can also mark private modules with GOPRIVATE instead of go host rules, for example in the repository config's env:

{\n  \"env\": {\n    \"GOPRIVATE\": \"github.com/my-org\"\n  }\n}\n

With the same go-proxy rule for bsr.example.com, Renovate uses:

GOPROXY=https://bsr.example.com,https://proxy.golang.org,direct\nGOPRIVATE=github.com/my-org\nGONOSUMDB=github.com/my-org,bsr.example.com\n

GOPROXY is still derived from the go-proxy rule, and go uses GOPRIVATE in place of GONOPROXY.

If you only want to use your own proxy, without the public proxy, set GOPROXY yourself.

"},{"location":"java/","title":"Java Dependency Updates","text":"

Renovate can update Gradle, Maven, and Ant dependencies. This includes libraries and plugins as well as the Gradle Wrapper.

"},{"location":"java/#lts-releases","title":"LTS releases","text":"

The config:recommended preset includes the workarounds:javaLTSVersions preset. The workaround limits Renovate to upgrade to LTS versions of the Java runtime only.

If you want Renovate to offer all major Java updates then add workarounds:javaLTSVersions to the ignorePreset array:

{\n  \"extends\": [\"config:recommended\"],\n  \"ignorePresets\": [\"workarounds:javaLTSVersions\"]\n}\n
"},{"location":"java/#gradle","title":"Gradle","text":"

Renovate detects versions that are specified in a string 'group:artifact:version' and those specified in a map (group:groupName, name:ArtifactName, version:Version).

"},{"location":"java/#gradle-file-support","title":"Gradle File Support","text":"

Renovate can update:

Renovate does not support:

"},{"location":"java/#gradle-plugin-support","title":"Gradle Plugin Support","text":"

Renovate can also update Gradle plugins. It supports the id(<pluginId>) syntax as well as the kotlin(<kotlinPluginId>) shortcut for id(org.jetbrains.kotlin.<kotlinPluginId>).

For specifying packageRules it is important to know how depName and packageName are defined for a Gradle plugin:

This is a direct consequence of the Plugin Marker Artifact naming convention.

"},{"location":"java/#gradle-wrapper","title":"Gradle Wrapper","text":"

Renovate can update the Gradle Wrapper of a project.

This includes the source declaration inside the gradle/wrapper/gradle-wrapper.properties as well as accompanied files such as gradlew, gradlew.bat, and gradle/wrapper/gradle-wrapper.jar.

"},{"location":"java/#how-it-works","title":"How It Works","text":"

Renovate extracts the Gradle Wrapper version used from the distributionUrl inside the gradle-wrapper.properties. Once the version is determined, Renovate will look for newer versions from the gradle-version datasource. Renovate will then invoke the Gradle Wrapper to update itself, as recommended by Gradle.

For the extraction to work, the distributionUrl must point to a file of type .zip, which includes the version in its name, and defines one of the official distribution types (bin, all).

"},{"location":"java/#support-for-mirrors-and-custom-distributions","title":"Support for mirrors and custom distributions","text":"

As Renovate takes the distributionUrl defined inside the gradle-wrapper.properties as basis for its update, source declarations other than to the official Gradle Wrapper are supported.

This can be used for hosting the official distributions with a proxy server, an offline mirror or even providing a custom distribution of the Gradle Wrapper, e.g. to provide a company-wide base configuration for all Gradle projects.

But the gradle-version datasource is used to determine available versions. In case the available versions at the defined source differ from those available from Gradle or the default datasource cannot be reached, e.g. due to network restrictions, the datasource may be reconfigured via a packageRule:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"gradle-version\"],\n      \"registryUrls\": [\n        \"https://domain.tld/repository/custom-gradle-wrapper/versions.json\"\n      ]\n    }\n  ]\n}\n
"},{"location":"java/#maven","title":"Maven","text":"

Renovate can update dependency versions found in Maven pom.xml files.

"},{"location":"java/#maven-file-support","title":"Maven File Support","text":"

Renovate will search repositories for all pom.xml files and processes them independently.

Renovate will also parse settings.xml files in the following locations:

Any repository URLs found within will be added as registryUrls to extracted dependencies.

"},{"location":"java/#custom-registry-support-and-authentication","title":"Custom registry support, and authentication","text":"

The manager for Gradle makes use of the maven datasource. Renovate can be configured to access more repositories and access repositories authenticated.

This example shows how you can use a config.js file to configure Renovate for use with Artifactory. We're using environment variables to pass the Artifactory username and password to Renovate.

config.js
module.exports = {\n  hostRules: [\n    {\n      hostType: 'maven',\n      matchHost: 'https://artifactory.yourcompany.com/',\n      username: process.env.ARTIFACTORY_USERNAME,\n      password: process.env.ARTIFACTORY_PASSWORD,\n    },\n  ],\n};\n

You can overwrite the repositories to use for version lookup through configuration.

module.exports = {\n  packageRules: [\n    {\n      matchDatasources: ['maven'],\n      registryUrls: ['https://repo-a.tld/repo', 'https://repo-b.tld/repo'],\n    },\n  ],\n};\n
"},{"location":"java/#google-artifact-registry","title":"Google Artifact Registry","text":"

There are multiple ways to configure Renovate to access Artifact Registry.

"},{"location":"java/#using-application-default-credentials-workload-identity-self-hosted-only","title":"Using Application Default Credentials / Workload Identity (Self-Hosted only)","text":"

Configure ADC or Workload Identity as normal and don't provide a username, password or token. Renovate will automatically retrieve the credentials using the google-auth-library.

"},{"location":"java/#using-long-lived-service-account-credentials","title":"Using long-lived service account credentials","text":"

To access the Google Artifact Registry, use the JSON service account with Basic authentication, and use the:

To avoid JSON-in-JSON wrapping, which can cause problems, encode the JSON service account beforehand.

  1. Download your JSON service account and store it on your machine. Make sure that the service account has read (and only read) permissions to your artifacts
  2. Base64 encode the service account credentials by running cat service-account.json | base64

  3. Add the encoded service account to your configuration file

    1. If you want to add it to your self-hosted configuration file:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-maven.pkg.dev\",\n      \"username\": \"_json_key_base64\",\n      \"password\": \"<base64 service account>\"\n    }\n  ]\n}\n```\n

    2. If you want to add it to your repository Renovate configuration file, encrypt it and then add it:

      ```json\n{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"europe-maven.pkg.dev\",\n      \"username\": \"_json_key_base64\",\n      \"encrypted\": {\n        \"password\": \"<encrypted base64 service account>\"\n      }\n    }\n  ]\n}\n```\n

  4. Add the following to the packageRules in your repository Renovate configuration file:

    {\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"maven\", \"gradle\"],\n      \"registryUrls\": [\n        \"https://europe-maven.pkg.dev/<my-gcp-project>/<my-repository>\"\n      ]\n    }\n  ]\n}\n
"},{"location":"javascript/","title":"JavaScript","text":"

Renovate supports upgrading JavaScript dependencies specified in package.json files.

npm, yarn, pnpm and bun are all supported.

"},{"location":"json-schema/","title":"JSON Schema","text":"

Renovate provides JSON Schemas which can provide autocomplete, documentation and validation in your editor. Consult your editor's documentation for how to configure this functionality.

When Renovate creates an onboarding PR, it will automagically add the JSON Schema definition, like so:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  // ...\n}\n

As well as the renovate-schema.json, which covers repository configuration, Renovate also provides configuration for other types of configuration.

The following JSON Schemas are available for use:

See below for more details on each of them.

"},{"location":"json-schema/#repository-configuration-renovate-schemajson","title":"Repository configuration (renovate-schema.json)","text":"

docs.renovatebot.com/renovate-schema.json covers any repository configuration options and is likely to be used in:

"},{"location":"json-schema/#repository-inherited-configuration-renovate-inherited-schemajson","title":"Repository + inherited configuration (renovate-inherited-schema.json)","text":"

docs.renovatebot.com/renovate-inherited-schema.json covers any repository configuration options, and any inherited config options.

It is only likely to be used if you create an org-inherited-config.json (or override the filename with inheritConfigFileName) in your shared config repo.

"},{"location":"json-schema/#global-self-hosted-configuration-renovate-global-schemajson","title":"Global self-hosted configuration (renovate-global-schema.json)","text":"

docs.renovatebot.com/renovate-global-schema.json covers any global self-hosted configuration, and is likely to be used in:

"},{"location":"json-schema/#usage-with-configjs","title":"Usage with config.js","text":"

Unfortunately - at time of writing - Language Server Protocol (LSP) servers do no yet provide a way to use a JSON Schema to provide type hints in a JavaScript file.

"},{"location":"json-schema/#limitations","title":"Limitations","text":"

The JSON Schema is autogenerated from the configuration options that Renovate holds.

While we aim to provide relevant options, documentation and validation rules where possible, there may be times where there is a gap in the schema.

Additionally, some of Renovate's concepts cannot be validated through JSON Schema, as they require more complex checks that only happen in Renovate's codebase.

Using the JSON Schema is recommended for early feedback (in your editor, or for your agent) but it is recommended to look at the documentation around validating your config, for instance using renovate-config-validator, which will provide a more robust and accurate validation process.

"},{"location":"json-schema/#previous-majors","title":"Previous majors","text":"

The Renovate documentation site tracks the current release version of Renovate.

If you are using the current major version of Renovate, but not the most up-to-date version of Renovate, you may find that the JSON Schema describes a configuration option you do not yet have access to.

If you're using a previous major version of Renovate, there will likely be many differences between what you have available in your version of Renovate.

With this in mind, when Renovate releases a major version, we store an archive of the JSON Schema for the previous major version in Schema Store.

Note

Previous major versions are only available since Renovate 39 (2025-04-29).

For instance, if you are running Renovate 41, you will be able to use i.e. www.schemastore.org/renovate-41.json for your JSON Schema.

"},{"location":"known-limitations/","title":"Known limitations","text":"

Learn about the limitations of Renovate.

"},{"location":"known-limitations/#introduction","title":"Introduction","text":"

Renovate, like any computer program has limitations. Sometimes these are functionality limitations - perhaps something is impossible or too complex to do, or we simply haven't implemented it yet. At other times it may be a \"performance\" limitation, because jobs neither start nor complete instantly, even if the user may start with that expectation.

This document tries to list out the most commonly seen limitations and describe whether they're permanent and if there's any plans to improving the situation.

"},{"location":"known-limitations/#timeschedule-based-limitations","title":"Time/schedule based limitations","text":"

When a user configures a schedule in their repo config, they may think that this schedule \"controls\" when Renovate runs. In actuality, Renovate may be running frequently, but skipping updates to the repo if the configured schedule is not met. Additionally, the Renovate admin may have put Renovate on its own schedule, or the job queue may be too long, so Renovate doesn't even get a chance to run on your repository during a certain scheduled time window.

For scheduled action to take place, both these need to happen:

"},{"location":"known-limitations/#the-mend-renovate-app-and-scheduled-jobs","title":"The Mend Renovate app and scheduled jobs","text":"

The Mend Renovate App checks each active repository roughly every three hours, if no activity has been seen before then (merged PRs, etc).

For this reason, you should set your schedule window to at least three or four hours. This makes it likely that Renovate checks your repository at least once during the schedule.

"},{"location":"known-limitations/#automerge-limitations","title":"Automerge limitations","text":"

The limitation to only merge one branch per run is because Renovate's dependency and branch state is based on what was present in the base branch at the start of the run. If a branch is merged into the base branch during Renovate's run - including by other users - it means that remaining Renovate branches may have Git conflicts. It also means that Renovate's knowledge about dependencies in the base branch is now invalid and other branches may need changing as a result of the merge.

The limitation to only automerge branches which are up-to-date is a decision due to this example:

"},{"location":"language-constraints-and-upgrading/","title":"Language constraints and upgrading","text":""},{"location":"language-constraints-and-upgrading/#package-releases-have-language-constraints","title":"Package releases have language constraints","text":"

Many ecosystems have the concept where each release of a package has its own language \"constraint\". For example, a npm package may support Node.js 18 and 20 in its v1 releases and Node.js 20 and 22 from v2.0.0 onwards.

In an ideal scenario:

"},{"location":"language-constraints-and-upgrading/#restricting-upgrades-to-compatible-releases","title":"Restricting upgrades to compatible releases","text":"

By default Renovate does not apply language constraints to upgrades. This means Renovate will propose \"any\" stable upgrade. Renovate will not check if the language version you're using actually supports that upgrade. In certain ecosystems, changes to language constraints are made with a major release, and are documented in the release notes. So Renovate's default behavior may be okay in those ecosystems. For other ecosystems Renovate's default behavior may seem wrong.

As a Renovate user, you can opt into strict compatibility filtering by setting constraintsFiltering=strict. Before you set constraintsFiltering=strict, you should:

Please keep reading to learn more.

"},{"location":"language-constraints-and-upgrading/#language-constraint-updating","title":"Language constraint updating","text":"

The first challenge is that Renovate may not yet support the ability to update your language constraints in an automated manner, and even when it does, users may not understand how many updates are depending on it.

For example: a Node.js project has set its engines field to \"node\": \"^18.0.0 || ^20.0.0\".

Should Renovate skip Node.js v21 because it is a non-LTS release? When Node.js v22 releases, should Renovate add it to your engines, or wait until v22 becomes the LTS version? When Node.js v18 is EOL, should Renovate drop it from the engines field?

Renovate can not guess what users want. Users have strong and different opinions on what Renovate should do for each example listed above.

Also, even if Renovate guesses right or adds advanced capabilities to allow this to be configurable: users might still wait on any of these \"major\" upgrades for months. If a project waits to create or merge the update to drop Node.js v18 from engines, then they can not upgrade to any new versions of library dependencies. Those library dependencies may have dropped support for Node.js v18 already.

"},{"location":"language-constraints-and-upgrading/#strict-filtering-limitations","title":"Strict filtering limitations","text":"

Let's go back to the Node.js project which has its engines field set to \"node\": \"^18.0.0 || ^20.0.0\".

Now also consider a library which sets its engines field to \"node\": \"^18.12.0 || ^20.9.0\" because the library only supports \"LTS releases\" of Node.js. Strictly speaking, this library is not compatible with the project above, because the project has wider requirements for their Node versions. This means Renovate holds back any upgrades for it. Should Renovate somehow \"think\" and assume that this narrower engines support is actually OK? What if the project already used a current version of this library \"in a way that's not officially supported\"?

A second problem is that if:

Then the user may not know that many dependencies are out of date, because Renovate is not creating PRs. For example: a project may have 10 dependencies, and 8 of those have updates. But all 8 dependencies need the project to update its language constraints first. The project administrator thinks they are up to date, because Renovate is not creating PRs, but 80% of their dependencies are outdated.

In short, users who set constraintsFiltering=strict often do not understand how strict that setting is and how many releases it will filter out.

"},{"location":"language-constraints-and-upgrading/#transitive-constraint-limitations","title":"Transitive constraint limitations","text":"

Often a library sets language constraints (like the engines examples above), and then depend on libraries with narrower constraints, like \"node\": \"^20.0.0\". In cases like these, Renovate \"trusts\" the declaration of the library and may create a update, even with strict constraints filtering.

For some package managers, like npm, this incompatibility will not be detected or warned about (even during lock file generation), but this may not be a problem for your application. Other package managers, like Poetry, may detect and warn about incompatible language constraints during lock file generation, which Renovate reports as an \"Artifacts update error\".

"},{"location":"language-constraints-and-upgrading/#applying-constraints-through-config","title":"Applying constraints through config","text":"

You can set language constraints in the Renovate config. For example:

Renovate config with Node.js constraints
{\n  \"constraints\": {\n    \"node\": \"^18.0.0 || >=20.0.0\"\n  }\n}\n

You may need to set constraints in the Renovate config when:

Renovate will not create \"update\" PRs to update any of these versions once they become outdated, so you must update those by hand. For this reason, setting constraints manually in the Renovate config is undesirable. We prefer to fix problems in Renovate itself, instead of you setting constraints.

"},{"location":"language-constraints-and-upgrading/#future-work","title":"Future Work","text":"

Please start, or join, a GitHub Discussion if you are interested in this topic. Subtopics include:

"},{"location":"logo-brand-guidelines/","title":"Logo and brand guidelines","text":"

This page explains how you may use the Renovate name, logo and branding.

"},{"location":"logo-brand-guidelines/#do-not-pretend-to-be-the-real-renovate-app","title":"Do not pretend to be the real Renovate app","text":"

Avoid using our name, logo, or branding in a way that causes people to think you are the real Renovate app on a public platform. For example: do not call your self-hosted version something like @realrenovatebot on GitHub.

"},{"location":"logo-brand-guidelines/#do-not-pretend-to-be-a-renovate-developer","title":"Do not pretend to be a Renovate developer","text":"

Avoid using our name, logo, or branding in a way that causes people to think you are a developer of Renovate.

"},{"location":"logo-brand-guidelines/#allowed-uses-of-the-renovate-name","title":"Allowed uses of the Renovate name","text":"

You are allowed to use the Renovate name:

"},{"location":"logo-brand-guidelines/#allowed-uses-of-the-renovate-logo","title":"Allowed uses of the Renovate logo","text":"

You are allowed to use our logo as:

"},{"location":"logo-brand-guidelines/#allowed-uses-of-the-renovate-branding","title":"Allowed uses of the Renovate branding","text":"

Do not use our banner images.

"},{"location":"logo-brand-guidelines/#we-keep-the-rights-to-our-logo-name-and-branding","title":"We keep the rights to our logo, name, and branding","text":"

You may only use our logo, name and branding as described in this guideline. We keep the rights to our logo, name and branding.

"},{"location":"merge-confidence/","title":"Merge Confidence","text":"

Look at the Merge Confidence badges before merging to:

Merge Confidence finds and flags undeclared breaking releases. It analyzes test and release adoption data from the Mend Renovate App users.

"},{"location":"merge-confidence/#pull-request-badges","title":"Pull request badges","text":"

Merge Confidence adds the following badges to your pull requests:

"},{"location":"merge-confidence/#supported-platforms","title":"Supported platforms","text":"

Merge Confidence badges for pull requests are available on any supported platform or Renovate distribution, including Mend Remediate.

"},{"location":"merge-confidence/#supported-languages","title":"Supported languages","text":"

Renovate will show Merge Confidence badges for these languages:

Language Datasource Golang go JavaScript npm Java maven Python pypi .NET nuget PHP packagist Ruby rubygems

We plan to support more languages soon.

"},{"location":"merge-confidence/#enabling-and-disabling","title":"Enabling and disabling","text":"

If you use the Mend Renovate App then the badges are enabled automatically.

If you're self-hosting Renovate, you can enable the badges by adding the mergeConfidence:all-badges preset to the extends array in your Renovate config:

{\n  \"extends\": [\"mergeConfidence:all-badges\"]\n}\n

Note

The mergeConfidence:age-confidence-badges preset can be used to only show the Age and Confidence badges.

If you want to disable the badges in the Mend Renovate App, add the mergeConfidence:all-badges preset to the ignorePresets array in your config:

{\n  \"ignorePresets\": [\"mergeConfidence:all-badges\"]\n}\n
"},{"location":"merge-confidence/#confidence-levels-and-their-meaning","title":"Confidence levels and their meaning","text":"

Merge Confidence uses the following confidence levels:

"},{"location":"merge-confidence/#how-it-works","title":"How it works","text":"

The Mend Renovate App created millions of pull requests on github.com to help developers update their dependencies since 2017. We bundle and analyze metrics such as package Age, package Adoption, and Passing tests. This way we can find packages that have undeclared breaking changes.

"},{"location":"merge-confidence/#algorithm","title":"Algorithm","text":"

The algorithm that decides on the values is private and is not something we plan to share. Similar to a search engine's algorithm, we plan to adjust and improve it over time, for example by using historical data to set a baseline confidence level for packages.

"},{"location":"merge-confidence/#data","title":"Data","text":"

We plan to expose much more of the data via a companion website, such as number of users of a package and popular repositories which already updated to the version in question.

"},{"location":"merge-confidence/#merge-confidence-workflows","title":"Merge Confidence Workflows","text":"

If you are a paying Mend customer, or you are an Open Source project who has access to Mend Renovate Community (OSS) Cloud, you will have access to Merge Confidence Workflows.

This makes it possible to introduce more intelligent workflows, such as \"only raise a PR once the update is in High confidence\" or \"automerge Very High confidence updates\".

"},{"location":"merge-confidence/#explanations","title":"Explanations","text":""},{"location":"merge-confidence/#package-ranking","title":"Package ranking","text":"

npm packages less than three days old can be unpublished, which can result in a service impact if you have updated to a package that gets unpublished. This is why npm packages can only get the High Confidence badge when they are at least three days old.

"},{"location":"merge-confidence/#percentage-values-weighting","title":"Percentage values weighting","text":"

The percentages for Adoption and Passing are weighted towards Organizations, private repositories, and projects with high test reliability. This means those values aren't raw percentages.

"},{"location":"merge-confidence/#questions-and-feedback","title":"Questions and feedback","text":"

If you have any feedback about Merge Confidence, please add it to our feedback megathread.

"},{"location":"node/","title":"Node.js Versions","text":"

Renovate can upgrade the Node.js runtime used by your project. This way you're using the latest bug fixes, performance improvements, security mitigations, etc.

"},{"location":"node/#lts-codenames","title":"LTS codenames","text":"

Renovate understands codenames for Node.js LTS releases and will offer upgrades for them (e.g. from fermium to gallium) as long as the node versioning scheme is being used.

"},{"location":"node/#file-support","title":"File Support","text":"

Renovate can manage the Node.js version in the following files:

"},{"location":"node/#package-manager-versions","title":"Package manager versions","text":"

Renovate can manage the package manager version in the following fields in package.json:

"},{"location":"node/#configuring-which-version-of-npm-renovate-uses","title":"Configuring which version of npm Renovate uses","text":"

When binarySource=install, such as in the Mend Renovate App, Renovate will choose and install an npm version dynamically.

To control which version or constraint is installed, you should use the engines.npm property in your package.json file. Renovate will then use that version constraint for npm when it creates a pull request.

For example, if you want to use at least npm 8.1.0 and also allow newer versions of npm in the 8.x range, you would put this in your package.json file:

package.json
{\n  \"engines\": {\n    \"npm\": \"^8.1.0\"\n  }\n}\n

Alternatively, the npm version can also be configured via the constraints option.

"},{"location":"noise-reduction/","title":"Noise Reduction","text":"

Generally, the first reaction people have to automated dependency updates like Renovate is \"oh great/feel the power of automation\". The next reaction a few days or weeks later is often \"this is getting overwhelming\". Indeed, if you leave Renovate on its default settings of raising a PR every single time any dependency receives any update.. you will get a lot of PRs and related notifications. This document will give you some ideas of how to reduce the amount of \"noise\" in your repository and the Pros/Cons of each approach.

Of course, please keep in mind that people's definitions of \"noise\" may differ. For some people, it's noisy only if they get a notification or email from GitHub. For others, too many commits in their base branch may be \"noise\". In other words, your mileage may vary. If you have any ideas on this topic, please contact the author by starting a new discussion on the Renovate repository.

"},{"location":"noise-reduction/#package-grouping","title":"Package Grouping","text":"

To reduce noise, you can reduce the number of updates in total, and a good way to do that is via intelligent grouping of related packages.

As an example, our default \":app\" and \":library\" presets include the rule \"group:monorepos\", which means that \"sibling\" packages from known monorepos will always be grouped into the same branch/PR by renovate. For example, all @angular/* packages that are updated at the same time will be raised in a \"Renovate angular monorepo packages\" PR. And every package in the React monorepo will be grouped together in a React monorepo PR too.

You may wish to take this further, for example you might want to group together all packages related to eslint, even if they come from separate repositories/authors. In that case you might create a config like this:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"groupName\": \"eslint\"\n    }\n  ]\n}\n

By setting matchPackageNames to /eslint/, it means that any package with eslint anywhere in its name will be grouped into a renovate/eslint branch and related PR.

"},{"location":"noise-reduction/#be-smart-about-grouping-dependencies","title":"Be smart about grouping dependencies","text":"

Grouping dependencies may help you, but can also cause problems. Sometimes you're better off getting a single PR per dependency!

Grouping dependencies versus single PRs:

"},{"location":"noise-reduction/#scheduling-renovate","title":"Scheduling Renovate","text":"

For a high level overview of scheduling when Renovate runs, read the key concepts, scheduling docs.

On its own, the Renovate CLI tool runs once and then exits. Hence, it only runs as often as its administrator sets it to (e.g. via cron).

For the Mend Renovate App, it currently runs continuously using a job queue that gets refreshed hourly for Enterprise users, and every 4 hours for Community users, or when you make relevant commits to your repository. You can expect to get PRs at any time of the day, e.g. soon after versions are published to npm.

Receiving PRs at any hour can increase the feeling of being \"overwhelmed\" by updates and possibly interrupt your flow during working hours, so many Renovate users also consider reducing Renovate's schedule to be outside their normal working hours, for example weeknights and weekends. This is achievable by configuring schedule in your Renovate config and optionally timezone (Renovate's default time zone is UTC, so you may find it easier to write schedules if you override timezone to your local one).

Another example of adjusting schedules to fit with your workflow might be if your company performs releases every Monday. In that case, you might schedule Renovate to run every Tuesday after midnight to pick up new dependency updates that you can test over the following week before the next release.

Caution: You need to make sure you leave yourself and Renovate enough time in a week to actually get all your updating and merging done. There are multiple reasons why Renovate may need to \"recreate\" PRs after you merge another:

  1. Conflict with package.json (sometimes)
  2. Conflict with lock files (often)
  3. If you have configured Renovate or GitHub that PRs must always be kept up-to-date with the base branch

Any of the above reasons can lead to a Renovate branch being considered \"stale\" and then Renovate needs to rebase it off the base branch before you can test and merge again, and Renovate won't do this until it's back in schedule.

"},{"location":"noise-reduction/#selective-scheduling","title":"Selective scheduling","text":"

Don't think that you need to apply blanket rules to scheduling. Remember that Renovate's configuration is highly flexible so you can configure automerge anywhere from globally (entire repo) right down to a package/upgrade type level. You could even configure a nonsensical rule like: \"patch updates of jquery are for Mondays only\".

Remember our example of grouping all eslint packages? If you think about it, updates to eslint rules don't exactly need to be applied in real time! You don't want to get too far behind, so how about we update eslint packages only once a month?

Update ESLint packages once a month
{\n  \"packageRules\": [\n    {\n      \"description\": \"Schedule updates on first day of each month\",\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"groupName\": \"eslint\",\n      \"schedule\": [\"* * 1 * *\"]\n    }\n  ]\n}\n

Or perhaps at least weekly:

Update ESLint packages weekly
{\n  \"packageRules\": [\n    {\n      \"description\": \"Schedule updates on Monday mornings(before 4 AM)\",\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"groupName\": \"eslint\",\n      \"schedule\": [\"* 0-3 * * 1\"]\n    }\n  ]\n}\n

If you're wondering what is supported and not, under the hood, the schedule is parsed using @breejs/later using the later.parse.text(scheduleString) API. Read the parser documentation at breejs.github.io/later/parsers.html#text. Renovate does not support scheduled minutes or \"at an exact time\" granularity. Granularity must be at least one hour.

"},{"location":"noise-reduction/#automerging","title":"Automerging","text":"

Automerging is a Renovate feature that can save you a lot of time/noise directly, while also benefiting grouping and scheduling. In short: it means that Renovate can merge PRs or even branches itself if they pass your tests.

We recommend that you enable automerge for any type of dependency update where you would select Merge anyway. We all know that there are some types of updates that we (nearly) always verify manually before merging, and plenty of others that we don't bother looking at unless tests fail. Every time you select Merge on a Renovate PR without manually testing it, you should consider if you can enable automerge and save yourself the time in future.

Automerge works particularly well for devDependencies and for production dependencies that have great test coverage.

For example, if you have jest or mocha as a dependency, and it has an upgrade with passing tests: automerge them! If you have a linter like eslint or tslint and its update passes: automerge them! If you have an API with 100% test coverage and express is updated: automerge it!

"},{"location":"noise-reduction/#branch-automerging","title":"Branch automerging","text":"

Those of you familiar with GitHub might note that even if you automerge PRs, you are still going to get notifications (noise) anyway - one when the PR is created and another when it is merged. For this reason we recommend you consider setting automergeType=branch which will mean:

The result is that passing updates are essentially \"silent\" - the only sign of them are the commits to your base branch.

"},{"location":"noise-reduction/#automerging-and-scheduling","title":"Automerging and scheduling","text":"

Automerging is particularly beneficial if you have configured a schedule, because Renovate on its own may be able to automerge the majority of your updates. And this is especially so if your repository needs rebasing, e.g. because you use lock files. e.g. let's say you have dependencies abc and xyz with upgrades, and you use a yarn.lock file.

This is a lot better than you waking up to two PRs and then having to deal with conflicts yourself after you merge the first one.

Remember our running eslint example? Let's automerge it if all the linting updates pass:

Automerge ESLint packages
{\n  \"packageRules\": [\n    {\n      \"description\": \"Schedule updates on Monday mornings(before 4 AM)\",\n      \"matchPackageNames\": [\"/eslint/\"],\n      \"groupName\": \"eslint\",\n      \"schedule\": [\"* 0-3 * * 1\"],\n      \"automerge\": true,\n      \"automergeType\": \"branch\"\n    }\n  ]\n}\n

Have you come up with a rule that would help others? How about a PR to our presets? For example the above rule could be named \":automergeEslintWeekly\" in schedule.ts.

"},{"location":"noise-reduction/#lock-file-considerations","title":"Lock file considerations","text":"

Using lock files greatly increases the chance that merging one PR will result in a second PR becoming conflicted with the base branch. The table below highlights different noise reduction strategies and their effect on pull request and potential lock file conflicts:

Action Effect on pull requests Chance of lock file conflicts Group dependencies together Decreases separate PRs Decreases Automerge dependencies Decreases concurrent PRs Decreases Decrease scheduled time for Renovate Increases concurrent PRs Increases"},{"location":"noise-reduction/#the-future-of-noise-reduction","title":"The Future of Noise Reduction","text":"

First of all, if you ever have any ideas about how to make Renovate less noisy, please raise or comment on issues in the main repository. Our philosophy is:

  1. Nearly everyone should use Renovate-like dependency update automation
  2. Over time, you should \"see\" Renovate less and less

One of our hopes with preset configs is that a set of \"sensible\" configs can be maintained by the community that combine grouping, scheduling and automerging to reduce the amount of noise in repositories with little downside or increased risk. Such lists could be maintained and used somewhat like Adblock lists - kept up to date by maintainers but for the majority of users they are simply trusted/automatic/invisible.

"},{"location":"nuget/","title":"NuGet","text":"

Renovate can upgrade dependencies in these files:

"},{"location":"nuget/#version-support","title":"Version Support","text":"

Renovate only works with SDK-style .csproj, .fsproj or .vbproj files. By default, this includes:

To convert your .NET Framework .csproj, .fsproj or .vbproj files into an SDK-style project, follow the steps in this guide.

"},{"location":"nuget/#how-it-works","title":"How it works","text":"
  1. Renovate searches in each repository for any files with a .csproj, .fsproj, .sqlproj, or .vbproj extension
  2. Existing dependencies are extracted from <PackageReference> and <PackageVersion> tags, and MSBuild SDK versions from <Sdk>, <Import Sdk>, and <Project Sdk=\"name/version\"> elements
  3. Renovate looks up the latest version on nuget.org (or an alternative feed if configured) to see if any upgrades are available

  4. If the source package includes a GitHub URL as its source, and has either:

    then release notes for each version are embedded in the generated PR

If your project file references a packages.config file, no dependencies will be extracted. Find out here how to migrate from packages.config to PackageReference.

"},{"location":"nuget/#alternate-feeds","title":"Alternate feeds","text":"

By default Renovate performs all lookups on https://api.nuget.org/v3/index.json, but you can set alternative NuGet feeds. You can set alternative feeds:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"nuget\"],\n      \"registryUrls\": [\n        \"https://api.nuget.org/v3/index.json\",\n        \"https://example1.com/nuget/\",\n        \"https://example2.com/nuget/v3/index.json\"\n      ]\n    }\n  ]\n}\n

In the example above we've set three NuGet feeds. The package resolving process uses the merge strategy to handle the three feeds. All feeds are checked for dependency updates, and duplicate updates are merged into a single dependency update.

Note

Some alternative feeds (e.g. Artifactory) do not implement the full set of required NuGet resources for the V3 API. If the PackageBaseAddress resource does not exist, Renovate falls back to using the projectUrl from the dependency's catalog entry as the sourceUrl for the dependency, affecting changelog detection.

"},{"location":"nuget/#protocol-versions","title":"Protocol versions","text":"

NuGet supports two protocol versions, v2 and v3. The NuGet client and server must use the same version. When Renovate acts as the client, it can use the v2 and v3 protocols.

By default, Renovate uses the v2 protocol. If the configured feed URL ends with index.json, Renovate uses the v3 protocol. So Renovate behaves like the official NuGet client.

"},{"location":"nuget/#v3-feed-url-not-ending-with-indexjson","title":"v3 feed URL not ending with index.json","text":"

If a v3 feed URL does not end with index.json, you must specify the version explicitly.

You may need this workaround when you use the JFrog Artifactory.

"},{"location":"nuget/#authenticated-feeds","title":"Authenticated feeds","text":"

Credentials for authenticated/private feeds can be given via host rules in the configuration options (file or command line parameter).

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"nuget\",\n      \"matchHost\": \"http://example1.com/nuget\",\n      \"username\": \"root\",\n      \"password\": \"p4$$w0rd\"\n    }\n  ]\n}\n

If you use Azure DevOps:

Note

Only Basic HTTP authentication (via username and password) is supported. For Azure DevOps: use a PAT with read permissions on Packaging. The username of the PAT must match the username of the user of the PAT. The generated nuget.config forces the basic authentication, which cannot be overridden externally!

"},{"location":"nuget/#ignoring-package-files-when-using-presets","title":"Ignoring package files when using presets","text":"

Because nuget manager has a dedicated ignorePaths entry in the :ignoreModulesAndTests preset, if you're using any presets that extend it (like config:recommended), you need to put your ignorePaths inside the nuget section for it to be merged. For example:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"extends\": [\"config:recommended\"],\n  \"nuget\": {\n    \"ignorePaths\": [\"IgnoreThisPackage/**\"]\n  }\n}\n

Otherwise, all nuget.ignorePaths values in :ignoreModulesAndTests will override values you put inside ignorePaths at the top-level config.

"},{"location":"nuget/#future-work","title":"Future work","text":"

We welcome contributions or feature requests to support more patterns or use cases.

"},{"location":"opentelemetry/","title":"OpenTelemetry and Renovate","text":"

This feature is flagged as experimental

Experimental features might be changed at any time. Renovate's OpenTelemetry support is stable enough to use in production, but there may be changes that rename attributes or fix bugs in a way that could be breaking to users, even in non-major version updates.

Renovate supports the OpenTelemetry monitoring and observability standard.

OpenTelemetry has three types of observability data it supports within the OpenTelemetry Protocol (OTLP):

Note

While the OpenTelemetry Protocol (OTLP) support traces, metrics, and logs, Renovate only supports traces, and some metrics. This means Renovate does not support other observability data like: stats on caching, error events, number of found updates, and so on.

"},{"location":"opentelemetry/#examples","title":"Examples","text":"

An example for setting up a local OpenTelemetry test setup with Docker can be found on OpenTelemetry examples page.

"},{"location":"opentelemetry/#usage","title":"Usage","text":"

To activate the instrumentation, you must set the OTEL_EXPORTER_OTLP_ENDPOINT environment variable. This variable controls the endpoint for the telemetry data. Once this endpoint is set, you can use all environment variables listed in the OpenTelemetry specification. You can also set the following environment variables:

The following resource detectors are used:

You can disable all cloud detectors by setting the RENOVATE_USE_CLOUD_METADATA_SERVICES environment variable to false. Then only the EnvDetector will be used.

Additionally you can use OTEL_NODE_RESOURCE_DETECTORS environment variable to control which resource detectors are used. The default values is all, which means all of the above detectors are used. Set it to none to disable all detectors, or a comma-separated list of the following values to specify which detectors to use:

"},{"location":"opentelemetry/#opentelemetry-exporter-protocol","title":"OpenTelemetry exporter protocol","text":"

Renovate supports sending traces via OTLP/gRPC (via @opentelemetry/exporter-trace-otlp-grpc), OTLP/HTTP with protobuf encoding (via @opentelemetry/exporter-trace-otlp-proto), or OTLP/HTTP with JSON encoding (via @opentelemetry/exporter-trace-otlp-http).

Set the OTEL_EXPORTER_OTLP_PROTOCOL (or the signal-specific OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, which takes precedence) environment variable to one of grpc, http/protobuf, or http/json to choose the protocol.

If neither variable is set, Renovate defaults to http/json

"},{"location":"opentelemetry/#file-exporter","title":"File exporter","text":"

The OpenTelemetry data can also be exported into a newline-delimited JSON (NDJSON) file, in OTLP JSON format.

This is configured using the RENOVATE_TRACING_FILE_EXPORTER_PATH environment variable.

You can then ingest this data into other tools, for instance:

Exporting the JSONL OTLP file to a local OpenTelemetry traces API
# bash-specific syntax\nwhile IFS= read -r line || [ -n \"$line\" ]; do\n  curl -s -X POST http://localhost:4318/v1/traces \\\n    -H 'Content-Type: application/json' \\\n    --data-binary @- <<< \"$line\"\ndone < /tmp/traces.jsonl\n
"},{"location":"opentelemetry/#supported-otlp-data","title":"Supported OTLP data","text":""},{"location":"opentelemetry/#traces","title":"Traces","text":"

Renovate provides instrumentation through traces for (non-exhaustively):

As well as following OpenTelemetry's semantic conventions where possible, Renovate defines several Custom Attributes, which can be found in lib/instrumentation/types.ts.

"},{"location":"opentelemetry/#metrics","title":"Metrics","text":"

Renovate does not currently support metrics in an OTLP format.

However, as seen in the OpenTelemetry examples page, it is possible to use the spanmetrics connector to automagically generate metrics from the tracing support Renovate has.

"},{"location":"opentelemetry/#logs","title":"Logs","text":"

Renovate does not currently support logging in an OTLP format.

"},{"location":"opentelemetry/#debugging","title":"Debugging","text":"

To help you debug, you can print the telemetry to the console. Use the environment variable RENOVATE_TRACING_CONSOLE_EXPORTER.

You can also set OTEL_LOG_LEVEL to control the log level of OpenTelemetry's internal diagnostics, which can be helpful for debugging.

"},{"location":"opentelemetry/#help-wanted","title":"Help wanted","text":"

We're continually looking to improve Renovate's instrumentation, and are aware there may be gaps in instrumentation.

As with the rest of Renovate, any additional contributions are very welcome!

You can see our current planned TODO list using the core:instrumentation label.

"},{"location":"php/","title":"Automated Dependency Updates for PHP Composer Dependencies","text":"

Renovate can upgrade dependencies in PHP's composer.json and composer.lock files.

"},{"location":"php/#how-it-works","title":"How It Works","text":"
  1. Renovate searches in each repository for any composer.json files
  2. Existing dependencies are extracted from the relevant sections of the JSON
  3. Renovate resolves the dependency on Packagist (or elsewhere if configured), and filter for SemVer versions
  4. A PR is created with composer.json and composer.lock updated in the same commit
  5. If the source repository has either a \"changelog\" file or uses GitHub releases, then Release Notes for each version will be embedded in the generated PR
"},{"location":"php/#enabling","title":"Enabling","text":"

Either install the Renovate App on GitHub, or check out Renovate OSS for self-hosted.

"},{"location":"php/#private-packages","title":"Private packages","text":"

If you are using a privately hosted Composer package you can pass the credentials via the hostRules configuration.

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"some.vendor.com\",\n      \"hostType\": \"packagist\",\n      \"username\": \"<your-username>\",\n      \"password\": \"<your-password>\"\n    },\n    {\n      \"matchHost\": \"bearer-auth.for.vendor.com\",\n      \"hostType\": \"packagist\",\n      \"token\": \"abcdef0123456789\"\n    }\n  ]\n}\n

This host rule is best added to the self-hosted config.js config so that it is not visible to users of the repository. If you are using the Mend Renovate App then you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it.

Go to https://app.renovatebot.com/encrypt, paste in the secret string you wish to encrypt, select Encrypt, then copy the encrypted result. You may encrypt your password only, but you can encrypt your username as well.

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"some.vendor.com\",\n      \"hostType\": \"packagist\",\n      \"encrypted\": {\n        \"username\": \"<your-encrypted-username>\",\n        \"password\": \"<your-encrypted-password>\"\n      }\n    },\n    {\n      \"matchHost\": \"bearer-auth.for.vendor.com\",\n      \"hostType\": \"packagist\",\n      \"encrypted\": {\n        \"token\": \"<your-encrypted-token>\"\n      }\n    }\n  ]\n}\n
"},{"location":"php/#update-all-dependencies","title":"Update all dependencies","text":"

By default, Renovate will invoke composer update with the --with-dependencies flag. Add composerWithAll to your postUpdateOptions array to use the --with-all-dependencies flag instead.

"},{"location":"presets-abandonments/","title":"Abandonment Presets","text":""},{"location":"presets-abandonments/#abandonmentsrecommended","title":"abandonments:recommended","text":"

Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.

{\n  \"packageRules\": [\n    {\n      \"abandonmentThreshold\": \"1 year\",\n      \"matchPackageNames\": [\n        \"*\"\n      ]\n    },\n    {\n      \"abandonmentThreshold\": null,\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@types/*\"\n      ]\n    },\n    {\n      \"abandonmentThreshold\": \"5 years\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"eslint-plugin-no-only-tests\"\n      ]\n    },\n    {\n      \"abandonmentThreshold\": \"6 years\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"lodash\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-config/","title":"Full Config Presets","text":""},{"location":"presets-config/#configbest-practices","title":"config:best-practices","text":"

Preset with best practices from the Renovate maintainers. Recommended for advanced users, who want to follow our best practices.

{\n  \"extends\": [\n    \"config:recommended\", // (1)!\n    \"docker:pinDigests\", // (2)!\n    \"helpers:pinGitHubActionDigests\", // (3)!\n    \":configMigration\", // (4)!\n    \":pinDevDependencies\", // (5)!\n    \"abandonments:recommended\", // (6)!\n    \"security:minimumReleaseAgeNpm\", // (7)!\n    \":maintainLockFilesWeekly\" // (8)!\n  ]\n}\n
  1. config:recommended: Recommended configuration for most users. It does not matter what programming language you use.
  2. docker:pinDigests: Pin Docker digests.
  3. helpers:pinGitHubActionDigests: Pin github-action digests.
  4. :configMigration: Enable Renovate configuration migration PRs when needed.
  5. :pinDevDependencies: Pin dependency versions for development dependencies.
  6. abandonments:recommended: Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
  7. security:minimumReleaseAgeNpm: Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
  8. :maintainLockFilesWeekly: Run lock file maintenance (updates) early Monday mornings.
"},{"location":"presets-config/#configjs-app","title":"config:js-app","text":"

Default configuration for webapps.

{\n  \"extends\": [\n    \"config:recommended\", // (1)!\n    \":pinAllExceptPeerDependencies\" // (2)!\n  ]\n}\n
  1. config:recommended: Recommended configuration for most users. It does not matter what programming language you use.
  2. :pinAllExceptPeerDependencies: Pin all dependency versions except peerDependencies.
"},{"location":"presets-config/#configjs-lib","title":"config:js-lib","text":"

Default configuration for libraries.

{\n  \"extends\": [\n    \"config:recommended\", // (1)!\n    \":pinOnlyDevDependencies\" // (2)!\n  ]\n}\n
  1. config:recommended: Recommended configuration for most users. It does not matter what programming language you use.
  2. :pinOnlyDevDependencies: Pin dependency versions for development dependencies and retain SemVer ranges for others.
"},{"location":"presets-config/#configrecommended","title":"config:recommended","text":"

Recommended configuration for most users. It does not matter what programming language you use.

{\n  \"extends\": [\n    \":dependencyDashboard\", // (1)!\n    \":semanticPrefixFixDepsChoreOthers\", // (2)!\n    \":ignoreModulesAndTests\", // (3)!\n    \"group:monorepos\", // (4)!\n    \"group:recommended\", // (5)!\n    \"mergeConfidence:age-confidence-badges\", // (6)!\n    \"replacements:all\", // (7)!\n    \"workarounds:all\", // (8)!\n    \"security:php2shell\", // (9)!\n    \"helpers:forgejoDigestChangelogs\", // (10)!\n    \"helpers:giteaDigestChangelogs\", // (11)!\n    \"helpers:githubDigestChangelogs\", // (12)!\n    \"helpers:gitlabDigestChangelogs\", // (13)!\n    \"helpers:goXPackagesChangelogLink\", // (14)!\n    \"helpers:goXPackagesNameLink\", // (15)!\n    \"helpers:renovateChangelog\" // (16)!\n  ]\n}\n
  1. :dependencyDashboard: Enable Renovate Dependency Dashboard creation.
  2. :semanticPrefixFixDepsChoreOthers: Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  3. :ignoreModulesAndTests: Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
  4. group:monorepos: Group known monorepo packages together.
  5. group:recommended: Use curated list of recommended non-monorepo package groupings.
  6. mergeConfidence:age-confidence-badges: Show only the Age and Confidence Merge Confidence badges for pull requests.
  7. replacements:all: Apply crowd-sourced package replacement rules.
  8. workarounds:all: Apply crowd-sourced workarounds for known problems with packages.
  9. security:php2shell: Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.
  10. helpers:forgejoDigestChangelogs: Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  11. helpers:giteaDigestChangelogs: Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  12. helpers:githubDigestChangelogs: Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  13. helpers:gitlabDigestChangelogs: Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  14. helpers:goXPackagesChangelogLink: Correctly link to the source code for golang.org/x packages
  15. helpers:goXPackagesNameLink: Link to pkg.go.dev/... for golang.org/x packages' title
  16. helpers:renovateChangelog: Provide a link to octochangelog's improved breakdown for Renovate's changelogs
"},{"location":"presets-config/#configsemverallmonthly","title":"config:semverAllMonthly","text":"

Preserve SemVer ranges and update everything together once a month. (excluding replacements and lockfile maintenance)

{\n  \"extends\": [\n    \":preserveSemverRanges\", // (1)!\n    \"group:all\", // (2)!\n    \"schedule:monthly\", // (3)!\n    \":maintainLockFilesMonthly\" // (4)!\n  ],\n  \"lockFileMaintenance\": {\n    \"commitMessageAction\": \"Update\"\n  },\n  \"separateMajorMinor\": false\n}\n
  1. :preserveSemverRanges: Preserve (but continue to upgrade) any existing SemVer ranges.
  2. group:all: Group all updates together.
  3. schedule:monthly: Schedule once a month on the first day of the month before 4 AM.
  4. :maintainLockFilesMonthly: Run lock file maintenance (updates) on the first day of each month.
"},{"location":"presets-config/#configsemverallweekly","title":"config:semverAllWeekly","text":"

Preserve SemVer ranges and update everything together once a week (excluding replacements and lockfile maintenance).

{\n  \"extends\": [\n    \":preserveSemverRanges\", // (1)!\n    \"group:all\", // (2)!\n    \"schedule:weekly\", // (3)!\n    \":maintainLockFilesWeekly\" // (4)!\n  ],\n  \"lockFileMaintenance\": {\n    \"commitMessageAction\": \"Update\"\n  },\n  \"separateMajorMinor\": false\n}\n
  1. :preserveSemverRanges: Preserve (but continue to upgrade) any existing SemVer ranges.
  2. group:all: Group all updates together.
  3. schedule:weekly: Schedule weekly.
  4. :maintainLockFilesWeekly: Run lock file maintenance (updates) early Monday mornings.
"},{"location":"presets-customManagers/","title":"CustomManager Presets","text":""},{"location":"presets-customManagers/#custommanagersazurepipelinesversions","title":"customManagers:azurePipelinesVersions","text":"

Update _VERSION environment variables in Azure Pipelines files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/.azuredevops/**/*.{yml,yaml}\",\n        \"azure*pipeline*.{yml,yaml}\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (?:lookupName|packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s+[A-Za-z0-9_]+?_VERSION\\\\s*:\\\\s*[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersbiomeversions","title":"customManagers:biomeVersions","text":"

Update $schema version in biome.json configuration files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"datasourceTemplate\": \"npm\",\n      \"depNameTemplate\": \"@biomejs/biome\",\n      \"fileFormat\": \"json\",\n      \"managerFilePatterns\": [\n        \"**/biome.{json,jsonc}\"\n      ],\n      \"matchStrings\": [\n        \"{\\\"currentValue\\\": $split($.\\\"$schema\\\",(\\\"/\\\"))[-2]}\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersbitbucketpipelinesversions","title":"customManagers:bitbucketPipelinesVersions","text":"

Update _VERSION variables in Bitbucket Pipelines

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/*-pipelines.yml\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (lookupName|packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s+.*\\\\s+[A-Za-z0-9_]+?_VERSION[ =:]\\\\s?[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersdockerfileversions","title":"customManagers:dockerfileVersions","text":"

Update _VERSION variables in Dockerfiles.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/[Dd]ockerfile*\",\n        \"**/[Cc]ontainerfile*\",\n        \"**/*.[Dd]ockerfile*\",\n        \"**/*.[Cc]ontainerfile*\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (lookupName|packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s(?:ENV|ARG)\\\\s+[A-Za-z0-9_]+?_VERSION[ =][\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersgithubactionsversions","title":"customManagers:githubActionsVersions","text":"

Update _VERSION environment variables in GitHub Action files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"/(^|/)(workflow-templates|\\\\.(?:github|gitea|forgejo)/(?:workflows|actions))/.+\\\\.ya?ml$/\",\n        \"/(^|/)action\\\\.ya?ml$/\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (?:lookupName|packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s+[A-Za-z0-9_]+?_VERSION\\\\s*:\\\\s*[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersgitlabpipelineversions","title":"customManagers:gitlabPipelineVersions","text":"

Update _VERSION environment variables in GitLab pipeline file.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/*.gitlab-ci.{yml,yaml}\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (?:packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s+[A-Za-z0-9_]+?_VERSION\\\\s*:\\\\s*[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagershelmchartyamlappversions","title":"customManagers:helmChartYamlAppVersions","text":"

Update appVersion value in Helm chart Chart.yaml.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"docker\",\n      \"managerFilePatterns\": [\n        \"**/Chart.yaml\"\n      ],\n      \"matchStrings\": [\n        \"#\\\\s*renovate: image=(?<depName>.*?)\\\\s+appVersion:\\\\s*[\\\"']?(?<currentValue>[\\\\w+\\\\.\\\\-]*)\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersmakefileversions","title":"customManagers:makefileVersions","text":"

Update _VERSION variables in Makefiles.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/[Mm]akefile\",\n        \"**/GNUMakefile\",\n        \"**/*.mk\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-zA-Z0-9-._]+?) depName=(?<depName>[^\\\\s]+?)(?: (?:packageName)=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s+[A-Za-z0-9_]+?_VERSION\\\\s*:*\\\\??=\\\\s*[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersmavenpropertyversions","title":"customManagers:mavenPropertyVersions","text":"

Update *.version properties in pom.xml files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"{{#if datasource}}{{{datasource}}}{{else}}maven{{/if}}\",\n      \"managerFilePatterns\": [\n        \"**/pom.xml\"\n      ],\n      \"matchStrings\": [\n        \"<!--\\\\s?renovate:( datasource=(?<datasource>[a-zA-Z0-9-._]+?))? depName=(?<depName>[^\\\\s]+?)(?: packageName=(?<packageName>[^\\\\s]+?))?(?: versioning=(?<versioning>[^\\\\s]+?))?(?: extractVersion=(?<extractVersion>[^\\\\s]+?))?\\\\s+-->\\\\s+<.+\\\\.version>(?<currentValue>.+)<\\\\/.+\\\\.version>\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{/if}}\"\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagerstfvarsversions","title":"customManagers:tfvarsVersions","text":"

Update *_version variables in .tfvars files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"**/*.tfvars\"\n      ],\n      \"matchStrings\": [\n        \"#\\\\s*renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?(?: extractVersion=(?<extractVersion>.*?))?(?: registryUrl=(?<registryUrl>[^\\\\s]+?))?\\\\s.*?_version\\\\s*=\\\\s*\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{/if}}\"\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagerstsconfignodeversions","title":"customManagers:tsconfigNodeVersions","text":"

Update @tsconfig/node extends in tsconfig.json and jsconfig.json files.

{\n  \"customManagers\": [\n    {\n      \"autoReplaceStringTemplate\": \"\\\"@tsconfig/node{{{major}}}/tsconfig.json\\\"\",\n      \"currentValueTemplate\": \"{{{major}}}\",\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"npm\",\n      \"managerFilePatterns\": [\n        \"**/{j,t}sconfig.json\",\n        \"**/{j,t}sconfig.*.json\"\n      ],\n      \"matchStrings\": [\n        \"\\\"(?<depName>@tsconfig/node(?<major>\\\\d+))/tsconfig\\\\.json\\\"\"\n      ]\n    },\n    {\n      \"autoReplaceStringTemplate\": \"\\\"@tsconfig/node{{{major}}}\\\"\",\n      \"currentValueTemplate\": \"{{{major}}}\",\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"npm\",\n      \"managerFilePatterns\": [\n        \"**/{j,t}sconfig.json\",\n        \"**/{j,t}sconfig.*.json\"\n      ],\n      \"matchStrings\": [\n        \"\\\"(?<depName>@tsconfig/node(?<major>\\\\d+))\\\"\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-customManagers/#custommanagersvaleversions","title":"customManagers:valeVersions","text":"

Update Vale package versions in .vale.ini configuration files.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"github-releases\",\n      \"managerFilePatterns\": [\n        \"/(^|/)\\\\.vale\\\\.ini$/\"\n      ],\n      \"matchStrings\": [\n        \"https://github\\\\.com/(?<packageName>[^/]+/[^/]+)/releases/download/(?<currentValue>[^/]+)/\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/","title":"Default Presets","text":""},{"location":"presets-default/#approvemajorupdates","title":":approveMajorUpdates","text":"

Require Dependency Dashboard approval for major updates.

{\n  \"packageRules\": [\n    {\n      \"dependencyDashboardApproval\": true,\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#assignandreviewarg0","title":":assignAndReview(<arg0>)","text":"

Set arg0 as assignee and reviewer of PRs.

{\n  \"extends\": [\n    \":assignee(arg0)\", // (1)!\n    \":reviewer(arg0)\" // (2)!\n  ]\n}\n
  1. :assignee(arg0): Assign PRs to arg0.
  2. :reviewer(arg0): Add arg0 as reviewer for PRs.
"},{"location":"presets-default/#assigneearg0","title":":assignee(<arg0>)","text":"

Assign PRs to arg0.

{\n  \"assignees\": [\n    \"arg0\"\n  ]\n}\n
"},{"location":"presets-default/#automergeall","title":":automergeAll","text":"

Automerge all upgrades (including major) if they pass tests.

{\n  \"automerge\": true\n}\n
"},{"location":"presets-default/#automergebranch","title":":automergeBranch","text":"

If automerging, push the new commit directly to the base branch (no PR).

{\n  \"automergeType\": \"branch\"\n}\n
"},{"location":"presets-default/#automergedigest","title":":automergeDigest","text":"

Automerge digest upgrades if they pass tests.

{\n  \"digest\": {\n    \"automerge\": true\n  }\n}\n
"},{"location":"presets-default/#automergedisabled","title":":automergeDisabled","text":"

Disable automerging feature - wait for humans to merge all PRs.

{\n  \"automerge\": false\n}\n
"},{"location":"presets-default/#automergelinters","title":":automergeLinters","text":"

Update lint packages automatically if tests pass.

{\n  \"packageRules\": [\n    {\n      \"automerge\": true,\n      \"extends\": [\n        \"packages:linters\" // (1)!\n      ]\n    }\n  ]\n}\n
  1. packages:linters: All lint-related packages.
"},{"location":"presets-default/#automergemajor","title":":automergeMajor","text":"

Automerge all upgrades (including major) if they pass tests.

{\n  \"automerge\": true\n}\n
"},{"location":"presets-default/#automergeminor","title":":automergeMinor","text":"

Automerge patch and minor upgrades if they pass tests.

{\n  \"lockFileMaintenance\": {\n    \"automerge\": true\n  },\n  \"minor\": {\n    \"automerge\": true\n  },\n  \"patch\": {\n    \"automerge\": true\n  },\n  \"pin\": {\n    \"automerge\": true\n  }\n}\n
"},{"location":"presets-default/#automergepatch","title":":automergePatch","text":"

Automerge patch upgrades if they pass tests.

{\n  \"lockFileMaintenance\": {\n    \"automerge\": true\n  },\n  \"patch\": {\n    \"automerge\": true\n  },\n  \"pin\": {\n    \"automerge\": true\n  },\n  \"separateMinorPatch\": true\n}\n
"},{"location":"presets-default/#automergepr","title":":automergePr","text":"

Raise a PR first before any automerging.

{\n  \"automergeType\": \"pr\"\n}\n
"},{"location":"presets-default/#automergerequireallstatuschecks","title":":automergeRequireAllStatusChecks","text":"

Require all status checks to pass before any automerging.

{\n  \"ignoreTests\": false\n}\n
"},{"location":"presets-default/#automergestablenonmajor","title":":automergeStableNonMajor","text":"

Automerge non-major upgrades for semver stable packages if they pass tests.

{\n  \"packageRules\": [\n    {\n      \"automerge\": true,\n      \"matchCurrentVersion\": \"!/^0/\",\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#automergetesters","title":":automergeTesters","text":"

Update testing packages automatically if tests pass.

{\n  \"packageRules\": [\n    {\n      \"automerge\": true,\n      \"extends\": [\n        \"packages:test\" // (1)!\n      ]\n    }\n  ]\n}\n
  1. packages:test: Test packages.
"},{"location":"presets-default/#automergetypes","title":":automergeTypes","text":"

Update @types/* packages automatically if tests pass.

{\n  \"packageRules\": [\n    {\n      \"automerge\": true,\n      \"matchPackageNames\": [\n        \"@types/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#combinepatchminorreleases","title":":combinePatchMinorReleases","text":"

Do not separate patch and minor upgrades into separate PRs for the same dependency.

{\n  \"separateMinorPatch\": false\n}\n
"},{"location":"presets-default/#configmigration","title":":configMigration","text":"

Enable Renovate configuration migration PRs when needed.

{\n  \"configMigration\": true\n}\n
"},{"location":"presets-default/#dependencydashboard","title":":dependencyDashboard","text":"

Enable Renovate Dependency Dashboard creation.

{\n  \"dependencyDashboard\": true\n}\n
"},{"location":"presets-default/#dependencydashboardapproval","title":":dependencyDashboardApproval","text":"

Enable Renovate Dependency Dashboard approval workflow.

{\n  \"dependencyDashboardApproval\": true\n}\n
"},{"location":"presets-default/#disabledependencydashboard","title":":disableDependencyDashboard","text":"

Disable Renovate Dependency Dashboard creation.

{\n  \"dependencyDashboard\": false\n}\n
"},{"location":"presets-default/#disabledevdependencies","title":":disableDevDependencies","text":"

Do not update development dependencies.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDepTypes\": [\n        \"devDependencies\",\n        \"dev-dependencies\",\n        \"dev\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#disabledigestupdates","title":":disableDigestUpdates","text":"

Disable digest and Git hash updates.

{\n  \"digest\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"presets-default/#disabledomainarg0","title":":disableDomain(<arg0>)","text":"

Disable requests to a particular domain.

{\n  \"hostRules\": [\n    {\n      \"enabled\": false,\n      \"matchHost\": \"arg0\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#disablehostarg0","title":":disableHost(<arg0>)","text":"

Disable requests to a particular host.

{\n  \"hostRules\": [\n    {\n      \"enabled\": false,\n      \"matchHost\": \"https://arg0\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#disablemajorupdates","title":":disableMajorUpdates","text":"

Disable major updates.

{\n  \"major\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"presets-default/#disablepeerdependencies","title":":disablePeerDependencies","text":"

Do not update peerDependencies versions/ranges.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDepTypes\": [\n        \"peerDependencies\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#disableprcontrols","title":":disablePrControls","text":"

Remove the checkbox controls from PRs.

{\n  \"prBodyTemplate\": \"{{{header}}}{{{table}}}{{{notes}}}{{{changelogs}}}{{{configDescription}}}{{{footer}}}\"\n}\n
"},{"location":"presets-default/#disableratelimiting","title":":disableRateLimiting","text":"

Remove hourly and concurrent rate limits.

{\n  \"commitHourlyLimit\": 0,\n  \"prConcurrentLimit\": 0,\n  \"prHourlyLimit\": 0\n}\n
"},{"location":"presets-default/#disablerenovate","title":":disableRenovate","text":"

Disable Renovate.

{\n  \"enabled\": false\n}\n
"},{"location":"presets-default/#disablevulnerabilityalerts","title":":disableVulnerabilityAlerts","text":"

Disable vulnerability alerts completely.

{\n  \"vulnerabilityAlerts\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"presets-default/#docker","title":":docker","text":"

Keep Dockerfile FROM sources updated.

{\n  \"docker-compose\": {\n    \"enabled\": true\n  },\n  \"dockerfile\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#donotpinpackagearg0","title":":doNotPinPackage(<arg0>)","text":"

Disable version pinning for arg0.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\n        \"arg0\"\n      ],\n      \"rangeStrategy\": \"replace\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#enableprecommit","title":":enablePreCommit","text":"

Enable the pre-commit manager.

{\n  \"pre-commit\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#enablerenovate","title":":enableRenovate","text":"

Enable Renovate.

{\n  \"enabled\": true\n}\n
"},{"location":"presets-default/#enablevulnerabilityalerts","title":":enableVulnerabilityAlerts","text":"

Raise PR when vulnerability alerts are detected.

{\n  \"vulnerabilityAlerts\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#enablevulnerabilityalertswithadditionallabelarg0","title":":enableVulnerabilityAlertsWithAdditionalLabel(<arg0>)","text":"

Raise PR when vulnerability alerts are detected with label arg0, in addition to any existing list of PR labels.

{\n  \"vulnerabilityAlerts\": {\n    \"addLabels\": [\n      \"arg0\"\n    ],\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#enablevulnerabilityalertswithlabelarg0","title":":enableVulnerabilityAlertsWithLabel(<arg0>)","text":"

Raise PR when vulnerability alerts are detected with label arg0, replacing any existing list of PR labels.

{\n  \"vulnerabilityAlerts\": {\n    \"enabled\": true,\n    \"labels\": [\n      \"arg0\"\n    ]\n  }\n}\n
"},{"location":"presets-default/#followtagarg0-arg1","title":":followTag(<arg0>, <arg1>)","text":"

For package arg0, strictly follow release tag arg1.

{\n  \"packageRules\": [\n    {\n      \"followTag\": \"arg1\",\n      \"matchPackageNames\": [\n        \"arg0\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-default/#githubcomtokenarg0","title":":githubComToken(<arg0>)","text":"

Use provided token for github.com lookups. Do not configure this if you are already running on github.com.

{\n  \"hostRules\": [\n    {\n      \"encrypted\": {\n        \"token\": \"arg0\"\n      },\n      \"hostType\": \"github\",\n      \"matchHost\": \"github.com\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#gitsignoff","title":":gitSignOff","text":"

Append Signed-off-by: to signoff Git commits.

{\n  \"commitTrailers\": [\n    \"Signed-off-by: {{{gitAuthor}}}\"\n  ]\n}\n
"},{"location":"presets-default/#gomod","title":":gomod","text":"

Enable Go modules support.

{\n  \"gomod\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#grouparg0-arg1","title":":group(<arg0>, <arg1>)","text":"

Group arg1 packages into same branch/PR.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"arg0\"\n      ],\n      \"groupName\": \"arg1\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#ignoremodulesandtests","title":":ignoreModulesAndTests","text":"

Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.

{\n  \"ignorePaths\": [\n    \"**/node_modules/**\",\n    \"**/bower_components/**\",\n    \"**/vendor/**\",\n    \"**/examples/**\",\n    \"**/__tests__/**\",\n    \"**/test/**\",\n    \"**/tests/**\",\n    \"**/__fixtures__/**\"\n  ],\n  \"nuget\": {\n    \"ignorePaths\": [\n      \"**/node_modules/**\",\n      \"**/bower_components/**\",\n      \"**/vendor/**\",\n      \"**/examples/**\",\n      \"**/__fixtures__/**\"\n    ]\n  }\n}\n
"},{"location":"presets-default/#ignoreunstable","title":":ignoreUnstable","text":"

Upgrade to unstable versions only if the existing version is unstable.

{\n  \"ignoreUnstable\": true\n}\n
"},{"location":"presets-default/#includenodemodules","title":":includeNodeModules","text":"

Include package.json files found within node_modules folders or bower_components.

{\n  \"ignorePaths\": []\n}\n
"},{"location":"presets-default/#labelarg0","title":":label(<arg0>)","text":"

Apply label arg0 to PRs.

{\n  \"labels\": [\n    \"arg0\"\n  ]\n}\n
"},{"location":"presets-default/#labelsarg0-arg1","title":":labels(<arg0>, <arg1>)","text":"

Apply labels arg0 and arg1 to PRs.

{\n  \"labels\": [\n    \"arg0\",\n    \"arg1\"\n  ]\n}\n
"},{"location":"presets-default/#maintainlockfilesdisabled","title":":maintainLockFilesDisabled","text":"

Update existing lock files only when package.json is modified.

{\n  \"lockFileMaintenance\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"presets-default/#maintainlockfilesmonthly","title":":maintainLockFilesMonthly","text":"

Run lock file maintenance (updates) on the first day of each month.

{\n  \"lockFileMaintenance\": {\n    \"enabled\": true,\n    \"extends\": [\n      \"schedule:monthly\" // (1)!\n    ]\n  }\n}\n
  1. schedule:monthly: Schedule once a month on the first day of the month before 4 AM.
"},{"location":"presets-default/#maintainlockfilesweekly","title":":maintainLockFilesWeekly","text":"

Run lock file maintenance (updates) early Monday mornings.

{\n  \"lockFileMaintenance\": {\n    \"enabled\": true,\n    \"extends\": [\n      \"schedule:weekly\" // (1)!\n    ]\n  }\n}\n
  1. schedule:weekly: Schedule weekly.
"},{"location":"presets-default/#meteor","title":":meteor","text":"

Keep Meteor Npm.depends packages updated.

{\n  \"meteor\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#nounscheduledupdates","title":":noUnscheduledUpdates","text":"

Only update branches when scheduled.

{\n  \"updateNotScheduled\": false\n}\n
"},{"location":"presets-default/#npm","title":":npm","text":"

Keep package.json npm dependencies updated.

{\n  \"npm\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-default/#pathsemanticcommittypearg0-arg1","title":":pathSemanticCommitType(<arg0>, <arg1>)","text":"

Use semanticCommitType arg1 for all package files matching path arg0.

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\n        \"arg0\"\n      ],\n      \"semanticCommitType\": \"arg1\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#pinallexceptpeerdependencies","title":":pinAllExceptPeerDependencies","text":"

Pin all dependency versions except peerDependencies.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"rangeStrategy\": \"pin\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"engines\",\n        \"peerDependencies\"\n      ],\n      \"rangeStrategy\": \"auto\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#pindependencies","title":":pinDependencies","text":"

Pin dependency versions where depType=dependencies. Usually applies only to non-dev dependencies in package.json.

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\n        \"dependencies\"\n      ],\n      \"rangeStrategy\": \"pin\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#pindevdependencies","title":":pinDevDependencies","text":"

Pin dependency versions for development dependencies.

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\n        \"devDependencies\",\n        \"dev-dependencies\",\n        \"dev\"\n      ],\n      \"rangeStrategy\": \"pin\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#pindigestsdisabled","title":":pinDigestsDisabled","text":"

Disable pinning of dependency digests.

Note: This preset does not revert the digest pinning set from within the packageRules, when set at root level or via extends). See Docker - Disable digest pinning for more details.

{\n  \"pinDigests\": false\n}\n
"},{"location":"presets-default/#pinonlydevdependencies","title":":pinOnlyDevDependencies","text":"

Pin dependency versions for development dependencies and retain SemVer ranges for others.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"rangeStrategy\": \"replace\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"devDependencies\",\n        \"dev-dependencies\",\n        \"dev\"\n      ],\n      \"rangeStrategy\": \"pin\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"peerDependencies\"\n      ],\n      \"rangeStrategy\": \"widen\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#pinskipci","title":":pinSkipCi","text":"

Add [skip ci] to commit message body whenever pinning.

{\n  \"pin\": {\n    \"commitBody\": \"[skip ci]\"\n  }\n}\n
"},{"location":"presets-default/#pinversions","title":":pinVersions","text":"

Use version pinning (maintain a single version only and not SemVer ranges).

{\n  \"rangeStrategy\": \"pin\"\n}\n
"},{"location":"presets-default/#prconcurrentlimit10","title":":prConcurrentLimit10","text":"

Limit to maximum 10 open PRs at any time.

{\n  \"prConcurrentLimit\": 10\n}\n
"},{"location":"presets-default/#prconcurrentlimit20","title":":prConcurrentLimit20","text":"

Limit to maximum 20 open PRs at any time.

{\n  \"prConcurrentLimit\": 20\n}\n
"},{"location":"presets-default/#prconcurrentlimitnone","title":":prConcurrentLimitNone","text":"

Remove limit for open PRs at any time.

{\n  \"prConcurrentLimit\": 0\n}\n
"},{"location":"presets-default/#preservesemverranges","title":":preserveSemverRanges","text":"

Preserve (but continue to upgrade) any existing SemVer ranges.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"rangeStrategy\": \"replace\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#prhourlylimit1","title":":prHourlyLimit1","text":"

Rate limit PR creation to a maximum of one per hour.

{\n  \"prHourlyLimit\": 1\n}\n
"},{"location":"presets-default/#prhourlylimit2","title":":prHourlyLimit2","text":"

Rate limit PR creation to a maximum of two per hour.

{\n  \"prHourlyLimit\": 2\n}\n
"},{"location":"presets-default/#prhourlylimit4","title":":prHourlyLimit4","text":"

Rate limit PR creation to a maximum of four per hour.

{\n  \"prHourlyLimit\": 4\n}\n
"},{"location":"presets-default/#prhourlylimitnone","title":":prHourlyLimitNone","text":"

Removes rate limit for PR creation per hour.

{\n  \"prHourlyLimit\": 0\n}\n
"},{"location":"presets-default/#primmediately","title":":prImmediately","text":"

Raise PRs immediately (after branch is created).

{\n  \"prCreation\": \"immediate\"\n}\n
"},{"location":"presets-default/#prnotpending","title":":prNotPending","text":"

Wait for branch tests to pass or fail before creating the PR.

{\n  \"prCreation\": \"not-pending\"\n}\n
"},{"location":"presets-default/#rebasestaleprs","title":":rebaseStalePrs","text":"

Rebase existing PRs any time the base branch has been updated.

{\n  \"rebaseWhen\": \"behind-base-branch\"\n}\n
"},{"location":"presets-default/#renovateprefix","title":":renovatePrefix","text":"

Add the renovate/ prefix to all branch names.

{\n  \"branchPrefix\": \"renovate/\"\n}\n
"},{"location":"presets-default/#respectlatest","title":":respectLatest","text":"

Upgrade versions up to the \"latest\" tag in the npm registry.

{\n  \"respectLatest\": true\n}\n
"},{"location":"presets-default/#reviewerarg0","title":":reviewer(<arg0>)","text":"

Add arg0 as reviewer for PRs.

{\n  \"reviewers\": [\n    \"arg0\"\n  ]\n}\n
"},{"location":"presets-default/#semanticcommits","title":":semanticCommits","text":"

Use semantic prefixes for commit messages and PR titles.

{\n  \"semanticCommits\": \"enabled\"\n}\n
"},{"location":"presets-default/#semanticcommitscopearg0","title":":semanticCommitScope(<arg0>)","text":"

Use semantic commit scope arg0 for all commits and PR titles.

{\n  \"semanticCommitScope\": \"arg0\"\n}\n
"},{"location":"presets-default/#semanticcommitscopedisabled","title":":semanticCommitScopeDisabled","text":"

Disable semantic commit scope for all commits and PR titles.

{\n  \"semanticCommitScope\": null\n}\n
"},{"location":"presets-default/#semanticcommitsdisabled","title":":semanticCommitsDisabled","text":"

Disable semantic prefixes for commit messages and PR titles.

{\n  \"semanticCommits\": \"disabled\"\n}\n
"},{"location":"presets-default/#semanticcommittypearg0","title":":semanticCommitType(<arg0>)","text":"

Use arg0 as semantic commit type for commit messages and PR titles.

{\n  \"semanticCommitType\": \"arg0\"\n}\n
"},{"location":"presets-default/#semanticcommittypeallarg0","title":":semanticCommitTypeAll(<arg0>)","text":"

If Renovate detects semantic commits, it will use semantic commit type arg0 for all commits.

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\n        \"**/*\"\n      ],\n      \"semanticCommitType\": \"arg0\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#semanticprefixchorearg0","title":":semanticPrefixChore(<arg0>)","text":"

Use chore as semantic commit type for commit messages and PR titles.

{\n  \"extends\": [\n    \":semanticCommitType(chore)\" // (1)!\n  ]\n}\n
  1. :semanticCommitType(chore): Use arg0 as semantic commit type for commit messages and PR titles.
"},{"location":"presets-default/#semanticprefixfixarg0","title":":semanticPrefixFix(<arg0>)","text":"

Use fix as semantic commit type for commit messages and PR titles.

{\n  \"extends\": [\n    \":semanticCommitType(fix)\" // (1)!\n  ]\n}\n
  1. :semanticCommitType(fix): Use arg0 as semantic commit type for commit messages and PR titles.
"},{"location":"presets-default/#semanticprefixfixdepschoreothers","title":":semanticPrefixFixDepsChoreOthers","text":"

Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"semanticCommitType\": \"chore\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"dependencies\",\n        \"require\"\n      ],\n      \"semanticCommitType\": \"fix\"\n    },\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchDepTypes\": [\n        \"compile\",\n        \"provided\",\n        \"runtime\",\n        \"system\",\n        \"import\",\n        \"parent\"\n      ],\n      \"semanticCommitType\": \"fix\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"project.dependencies\",\n        \"project.optional-dependencies\"\n      ],\n      \"matchManagers\": [\n        \"pep621\",\n        \"poetry\"\n      ],\n      \"semanticCommitType\": \"fix\"\n    },\n    {\n      \"matchDepTypes\": [\n        \"dependencies\",\n        \"extras\"\n      ],\n      \"matchManagers\": [\n        \"poetry\"\n      ],\n      \"semanticCommitType\": \"fix\"\n    },\n    {\n      \"matchJsonata\": [\n        \"isLockfileUpdate = true\"\n      ],\n      \"semanticCommitType\": \"chore\"\n    }\n  ]\n}\n
"},{"location":"presets-default/#separatemajorreleases","title":":separateMajorReleases","text":"

Separate major versions of dependencies into individual branches/PRs.

{\n  \"separateMajorMinor\": true\n}\n
"},{"location":"presets-default/#separatemultiplemajorreleases","title":":separateMultipleMajorReleases","text":"

Separate each major version of dependencies into individual branches/PRs.

{\n  \"separateMajorMinor\": true,\n  \"separateMultipleMajor\": true\n}\n
"},{"location":"presets-default/#separatemultipleminorreleases","title":":separateMultipleMinorReleases","text":"

Separate each minor version of dependencies into individual branches/PRs.

{\n  \"separateMultipleMinor\": true\n}\n
"},{"location":"presets-default/#separatepatchreleases","title":":separatePatchReleases","text":"

Separate patch and minor releases of dependencies into separate PRs.

{\n  \"separateMinorPatch\": true\n}\n
"},{"location":"presets-default/#skipartifactsupdate","title":":skipArtifactsUpdate","text":"

Skips artifact updates.

{\n  \"skipArtifactsUpdate\": true\n}\n
"},{"location":"presets-default/#skipstatuschecks","title":":skipStatusChecks","text":"

Skip status checks and automerge right away.

{\n  \"ignoreTests\": true\n}\n
"},{"location":"presets-default/#timezonearg0","title":":timezone(<arg0>)","text":"

Evaluate schedules according to timezone arg0.

{\n  \"timezone\": \"arg0\"\n}\n
"},{"location":"presets-default/#updatenotscheduled","title":":updateNotScheduled","text":"

Keep existing branches updated even when not scheduled.

{\n  \"updateNotScheduled\": true\n}\n
"},{"location":"presets-default/#widenpeerdependencies","title":":widenPeerDependencies","text":"

Always widen peerDependencies SemVer ranges when updating, instead of replacing.

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\n        \"peerDependencies\"\n      ],\n      \"rangeStrategy\": \"widen\"\n    }\n  ]\n}\n
"},{"location":"presets-docker/","title":"Docker Presets","text":""},{"location":"presets-docker/#dockerdisable","title":"docker:disable","text":"

Disable Docker updates.

{\n  \"circleci\": {\n    \"enabled\": false\n  },\n  \"docker-compose\": {\n    \"enabled\": false\n  },\n  \"dockerfile\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"presets-docker/#dockerdisablemajor","title":"docker:disableMajor","text":"

Disable Docker major updates.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-docker/#dockerenablemajor","title":"docker:enableMajor","text":"

Enable Docker major updates.

{\n  \"packageRules\": [\n    {\n      \"enabled\": true,\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-docker/#dockerpindigests","title":"docker:pinDigests","text":"

Pin Docker digests.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"pinDigests\": true\n    },\n    {\n      \"matchManagers\": [\n        \"argocd\",\n        \"devcontainer\",\n        \"helmv3\",\n        \"pyenv\"\n      ],\n      \"pinDigests\": false\n    }\n  ]\n}\n
"},{"location":"presets-global/","title":"Global Presets","text":""},{"location":"presets-global/#globalsafeenv","title":"global:safeEnv","text":"

Hopefully safe environment variables to allow users to configure.

{\n  \"allowedEnv\": [\n    \"BUN_CONFIG_MAX_HTTP_REQUESTS\",\n    \"GO*\",\n    \"GRADLE_OPTS\",\n    \"RUSTC_BOOTSTRAP\",\n    \"PNPM_WORKERS\",\n    \"PNPM_MAX_WORKERS\"\n  ]\n}\n
"},{"location":"presets-group/","title":"Group Presets","text":""},{"location":"presets-group/#groupall","title":"group:all","text":"

Group all updates together.

{\n  \"groupName\": \"all dependencies\",\n  \"groupSlug\": \"all\",\n  \"packageRules\": [\n    {\n      \"groupName\": \"all dependencies\",\n      \"groupSlug\": \"all\",\n      \"matchPackageNames\": [\n        \"*\"\n      ]\n    }\n  ],\n  \"separateMajorMinor\": false\n}\n
"},{"location":"presets-group/#groupallapollographql","title":"group:allApollographql","text":"

Group all packages published by Apollo GraphQL together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:apollographql\" // (1)!\n      ],\n      \"groupName\": \"Apollo GraphQL packages\"\n    }\n  ]\n}\n
  1. packages:apollographql: All packages published by Apollo GraphQL.
"},{"location":"presets-group/#groupalldigest","title":"group:allDigest","text":"

Group all digest updates together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"all digest updates\",\n      \"groupSlug\": \"all-digest\",\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupallnonmajor","title":"group:allNonMajor","text":"

Group all minor and patch updates together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"all non-major dependencies\",\n      \"groupSlug\": \"all-minor-patch\",\n      \"matchPackageNames\": [\n        \"*\"\n      ],\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupapiplatform","title":"group:apiPlatform","text":"

Group PHP API Platform packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"api-platform packages\",\n      \"groupSlug\": \"api-platform\",\n      \"matchDatasources\": [\n        \"packagist\"\n      ],\n      \"matchPackageNames\": [\n        \"api-platform/*\",\n        \"!api-platform/admin-meta\",\n        \"!api-platform/admin-pack\",\n        \"!api-platform/api-pack\",\n        \"!api-platform/api-platform\",\n        \"!api-platform/parameter-validator\",\n        \"!api-platform/postman-collection-generator\",\n        \"!api-platform/schema-generator\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupatlaskit","title":"group:atlaskit","text":"

Group all Atlassian @atlaskit packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:atlaskit\" // (1)!\n      ],\n      \"groupName\": \"Atlassian Atlaskit packages\"\n    }\n  ]\n}\n
  1. packages:atlaskit: All @atlaskit packages published by Atlassian.
"},{"location":"presets-group/#groupboto","title":"group:boto","text":"

Group all Boto packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"boto\",\n      \"matchDatasources\": [\n        \"pypi\"\n      ],\n      \"matchPackageNames\": [\n        \"boto3\",\n        \"botocore\",\n        \"s3transfer\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupcodemirror","title":"group:codemirror","text":"

Group CodeMirror packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"CodeMirror\",\n      \"matchPackageNames\": [\n        \"@codemirror/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupdefinitelytyped","title":"group:definitelyTyped","text":"

Group all @types packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"definitelyTyped\",\n      \"matchPackageNames\": [\n        \"@types/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupdotnetcore","title":"group:dotNetCore","text":"

.NET Core Docker containers.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \".NET Core Docker containers\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"mcr.microsoft.com/dotnet/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupdrupal-core","title":"group:drupal-core","text":"

Group Drupal core updates.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Drupal core\",\n      \"matchPackageNames\": [\n        \"drupal/core\",\n        \"drupal/core-*\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupflyway","title":"group:flyway","text":"

Group Java Flyway packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"flyway\",\n      \"matchPackageNames\": [\n        \"org.flywaydb:*\",\n        \"org.flywaydb.flyway:*\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupfortawesome","title":"group:fortawesome","text":"

Group all packages by Font Awesome together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Font Awesome\",\n      \"matchPackageNames\": [\n        \"@fortawesome/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupfusionjs","title":"group:fusionjs","text":"

Group Fusion.js packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Fusion.js packages\",\n      \"matchPackageNames\": [\n        \"fusion-cli\",\n        \"fusion-core\",\n        \"fusion-test-utils\",\n        \"fusion-tokens\",\n        \"fusion-plugin-**\",\n        \"fusion-react**\",\n        \"fusion-apollo**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupgithubartifactactions","title":"group:githubArtifactActions","text":"

Group download-artifact and upload-artifact major updates together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"GitHub Artifact Actions\",\n      \"matchManagers\": [\n        \"github-actions\"\n      ],\n      \"matchPackageNames\": [\n        \"actions/download-artifact\",\n        \"actions/upload-artifact\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupglimmer","title":"group:glimmer","text":"

Group Glimmer.js packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Glimmer.js packages\",\n      \"groupSlug\": \"glimmer\",\n      \"matchPackageNames\": [\n        \"@glimmer/component\",\n        \"@glimmer/tracking\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupgoogleapis","title":"group:googleapis","text":"

Group googleapis packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:googleapis\" // (1)!\n      ],\n      \"groupName\": \"googleapis packages\"\n    }\n  ]\n}\n
  1. packages:googleapis: All googleapis packages.
"},{"location":"presets-group/#groupgoopenapi","title":"group:goOpenapi","text":"

Group go-openapi packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"go-openapi packages\",\n      \"groupSlug\": \"go-openapi\",\n      \"matchDatasources\": [\n        \"go\"\n      ],\n      \"matchPackageNames\": [\n        \"github.com/go-openapi/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupgradle","title":"group:gradle","text":"

Group anything that looks like Gradle together so that it's updated together.

{\n  \"packageRules\": [\n    {\n      \"commitMessageTopic\": \"Gradle\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"gradle-version\"\n      ],\n      \"matchPackageNames\": [\n        \"/(?:^|/)gradle$/\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouphibernatecommons","title":"group:hibernateCommons","text":"

Group Java Hibernate Commons packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"hibernate commons\",\n      \"matchPackageNames\": [\n        \"org.hibernate.common:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouphibernatecore","title":"group:hibernateCore","text":"

Group Java Hibernate Core packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"hibernate core\",\n      \"matchPackageNames\": [\n        \"org.hibernate:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouphibernateogm","title":"group:hibernateOgm","text":"

Group Java Hibernate OGM packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"hibernate ogm\",\n      \"matchPackageNames\": [\n        \"org.hibernate.ogm:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouphibernatevalidator","title":"group:hibernateValidator","text":"

Group Java Hibernate Validator packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"hibernate validator\",\n      \"matchPackageNames\": [\n        \"org.hibernate.validator:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupilluminate","title":"group:illuminate","text":"

Group PHP Illuminate packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"illuminate packages\",\n      \"groupSlug\": \"illuminate\",\n      \"matchPackageNames\": [\n        \"illuminate/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupjava","title":"group:java","text":"

Group Java runtime versions together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Java\",\n      \"matchDatasources\": [\n        \"java-version\"\n      ],\n      \"matchPackageNames\": [\n        \"java\",\n        \"java-jdk\",\n        \"java-jre\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupjekyllecosystem","title":"group:jekyllEcosystem","text":"

Group Jekyll and related Ruby packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"jekyll ecosystem packages\",\n      \"matchSourceUrls\": [\n        \"https://github.com/jekyll/**\",\n        \"https://github.com/github/pages-gem**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupjestplustsjest","title":"group:jestPlusTSJest","text":"

Add ts-jest major update to Jest monorepo.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"jest monorepo\",\n      \"matchSourceUrls\": [\n        \"https://github.com/kulshekhar/ts-jest\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupjestplustypes","title":"group:jestPlusTypes","text":"

Add @types/jest update to Jest monorepo.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"jest monorepo\",\n      \"matchPackageNames\": [\n        \"@types/jest\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupjstest","title":"group:jsTest","text":"

Group JS test packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:jsTest\" // (1)!\n      ],\n      \"groupName\": \"JS test packages\"\n    }\n  ]\n}\n
  1. packages:jsTest: JavaScript test packages.
"},{"location":"presets-group/#groupjstestnonmajor","title":"group:jsTestNonMajor","text":"

Group non-major JS test package updates together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:jsTest\" // (1)!\n      ],\n      \"groupName\": \"JS test packages\",\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
  1. packages:jsTest: JavaScript test packages.
"},{"location":"presets-group/#groupjsunittest","title":"group:jsUnitTest","text":"

Group JavaScript unit test packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:jsUnitTest\" // (1)!\n      ],\n      \"groupName\": \"JS unit test packages\"\n    }\n  ]\n}\n
  1. packages:jsUnitTest: Unit test packages for JavaScript.
"},{"location":"presets-group/#groupjsunittestnonmajor","title":"group:jsUnitTestNonMajor","text":"

Group JavaScipt unit test packages together for non-major updates.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:jsUnitTest\" // (1)!\n      ],\n      \"groupName\": \"JS unit test packages\",\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
  1. packages:jsUnitTest: Unit test packages for JavaScript.
"},{"location":"presets-group/#groupjwtframework","title":"group:jwtFramework","text":"

Group JWT Framework packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"JWT Framework packages\",\n      \"matchDatasources\": [\n        \"packagist\"\n      ],\n      \"matchPackageNames\": [\n        \"web-token/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouplinters","title":"group:linters","text":"

Group various lint packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:linters\" // (1)!\n      ],\n      \"groupName\": \"linters\"\n    }\n  ]\n}\n
  1. packages:linters: All lint-related packages.
"},{"location":"presets-group/#groupmicrometer","title":"group:micrometer","text":"

Group Micrometer packages together, e.g. 'io.micrometer:micrometer-core'.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"micrometer\",\n      \"matchPackageNames\": [\n        \"io.micrometer:micrometer-**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupnodejs","title":"group:nodeJs","text":"

Group anything that looks like Node.js together so that it's updated together.

{\n  \"packageRules\": [\n    {\n      \"commitMessageTopic\": \"Node.js\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"node-version\"\n      ],\n      \"matchPackageNames\": [\n        \"/(?:^|/)node$/\",\n        \"!calico/node\",\n        \"!docker.io/calico/node\",\n        \"!ghcr.io/devcontainers/features/node\",\n        \"!kindest/node\",\n        \"!docker.io/kindest/node\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupnodejswithtypes","title":"group:nodeJsWithTypes","text":"

Group Node.js runtime updates together with @types/node.

{\n  \"extends\": [\n    \"group:nodeJs\" // (1)!\n  ],\n  \"packageRules\": [\n    {\n      \"groupName\": \"Node.js\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"node-version\"\n      ],\n      \"matchPackageNames\": [\n        \"/(?:^|/)node$/\",\n        \"!calico/node\",\n        \"!docker.io/calico/node\",\n        \"!ghcr.io/devcontainers/features/node\",\n        \"!kindest/node\",\n        \"!docker.io/kindest/node\"\n      ]\n    },\n    {\n      \"groupName\": \"Node.js\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@types/node\"\n      ]\n    }\n  ]\n}\n
  1. group:nodeJs: Group anything that looks like Node.js together so that it's updated together.
"},{"location":"presets-group/#groupphpstan","title":"group:phpstan","text":"

Group PHPStan packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"PHPStan packages\",\n      \"matchDatasources\": [\n        \"packagist\"\n      ],\n      \"matchPackageNames\": [\n        \"phpstan/phpstan\",\n        \"//phpstan-/\",\n        \"//larastan/\",\n        \"phpstan/extension-installer\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouppnpm","title":"group:pnpm","text":"

Group pnpm packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"pnpm packages\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"pnpm\",\n        \"ghcr.io/pnpm/pnpm\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouppolymer","title":"group:polymer","text":"

Group all @polymer packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"polymer packages\",\n      \"matchPackageNames\": [\n        \"@polymer/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouppostcss","title":"group:postcss","text":"

Group PostCSS packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:postcss\" // (1)!\n      ],\n      \"groupName\": \"postcss packages\"\n    }\n  ]\n}\n
  1. packages:postcss: All PostCSS packages.
"},{"location":"presets-group/#groupprimer","title":"group:primer","text":"

Group all @primer packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Primer packages\",\n      \"groupSlug\": \"primer\",\n      \"matchPackageNames\": [\n        \"@primer/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouppulumi","title":"group:pulumi","text":"

Group Pulumi packages together.

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group Pulumi Node.JS packages together.\",\n      \"groupName\": \"Pulumi\",\n      \"groupSlug\": \"pulumi-node\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@pulumi/**\"\n      ]\n    },\n    {\n      \"description\": \"Group Pulumi Python packages together.\",\n      \"groupName\": \"Pulumi\",\n      \"groupSlug\": \"pulumi-python\",\n      \"matchDatasources\": [\n        \"pypi\"\n      ],\n      \"matchPackageNames\": [\n        \"pulumi-**\"\n      ]\n    },\n    {\n      \"description\": \"Group Pulumi Go packages together.\",\n      \"groupName\": \"Pulumi\",\n      \"groupSlug\": \"pulumi-go\",\n      \"matchDatasources\": [\n        \"go\"\n      ],\n      \"matchPackageNames\": [\n        \"github.com/pulumi/**\"\n      ]\n    },\n    {\n      \"description\": \"Group Pulumi Java packages together.\",\n      \"groupName\": \"Pulumi\",\n      \"groupSlug\": \"pulumi-java\",\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"com.pulumi**\"\n      ]\n    },\n    {\n      \"description\": \"Group Pulumi .NET packages together.\",\n      \"groupName\": \"Pulumi\",\n      \"groupSlug\": \"pulumi-dotnet\",\n      \"matchDatasources\": [\n        \"nuget\"\n      ],\n      \"matchPackageNames\": [\n        \"Pulumi**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouppuppeteer","title":"group:puppeteer","text":"

Group Puppeteer packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Puppeteer\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"puppeteer\",\n        \"puppeteer-core\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupreact","title":"group:react","text":"

Group React and corresponding @types packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"react monorepo\",\n      \"matchPackageNames\": [\n        \"@types/react\",\n        \"@types/react-dom\",\n        \"@types/react-is\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouprecommended","title":"group:recommended","text":"

Use curated list of recommended non-monorepo package groupings.

{\n  \"extends\": [\n    \"group:nodeJs\", // (1)!\n    \"group:allApollographql\", // (2)!\n    \"group:apiPlatform\", // (3)!\n    \"group:boto\", // (4)!\n    \"group:codemirror\", // (5)!\n    \"group:flyway\", // (6)!\n    \"group:fortawesome\", // (7)!\n    \"group:fusionjs\", // (8)!\n    \"group:githubArtifactActions\", // (9)!\n    \"group:glimmer\", // (10)!\n    \"group:goOpenapi\", // (11)!\n    \"group:gradle\", // (12)!\n    \"group:hibernateCore\", // (13)!\n    \"group:hibernateValidator\", // (14)!\n    \"group:hibernateOgm\", // (15)!\n    \"group:hibernateCommons\", // (16)!\n    \"group:illuminate\", // (17)!\n    \"group:java\", // (18)!\n    \"group:jekyllEcosystem\", // (19)!\n    \"group:jestPlusTSJest\", // (20)!\n    \"group:jestPlusTypes\", // (21)!\n    \"group:jwtFramework\", // (22)!\n    \"group:micrometer\", // (23)!\n    \"group:phpstan\", // (24)!\n    \"group:polymer\", // (25)!\n    \"group:puppeteer\", // (26)!\n    \"group:react\", // (27)!\n    \"group:remark\", // (28)!\n    \"group:resilience4j\", // (29)!\n    \"group:rubyOnRails\", // (30)!\n    \"group:rubyOmniauth\", // (31)!\n    \"group:socketio\", // (32)!\n    \"group:springAmqp\", // (33)!\n    \"group:springAndroid\", // (34)!\n    \"group:springBatch\", // (35)!\n    \"group:springBoot\", // (36)!\n    \"group:springCloud\", // (37)!\n    \"group:springCore\", // (38)!\n    \"group:springData\", // (39)!\n    \"group:springHateoas\", // (40)!\n    \"group:springIntegration\", // (41)!\n    \"group:springKafka\", // (42)!\n    \"group:springLdap\", // (43)!\n    \"group:springMobile\", // (44)!\n    \"group:springOsgi\", // (45)!\n    \"group:springRestDocs\", // (46)!\n    \"group:springRoo\", // (47)!\n    \"group:springScala\", // (48)!\n    \"group:springSecurity\", // (49)!\n    \"group:springSession\", // (50)!\n    \"group:springShell\", // (51)!\n    \"group:springSocial\", // (52)!\n    \"group:springStatemachine\", // (53)!\n    \"group:springWebflow\", // (54)!\n    \"group:springWs\", // (55)!\n    \"group:symfony\" // (56)!\n  ]\n}\n
  1. group:nodeJs: Group anything that looks like Node.js together so that it's updated together.
  2. group:allApollographql: Group all packages published by Apollo GraphQL together.
  3. group:apiPlatform: Group PHP API Platform packages together.
  4. group:boto: Group all Boto packages together.
  5. group:codemirror: Group CodeMirror packages together.
  6. group:flyway: Group Java Flyway packages.
  7. group:fortawesome: Group all packages by Font Awesome together.
  8. group:fusionjs: Group Fusion.js packages together.
  9. group:githubArtifactActions: Group download-artifact and upload-artifact major updates together.
  10. group:glimmer: Group Glimmer.js packages together.
  11. group:goOpenapi: Group go-openapi packages together.
  12. group:gradle: Group anything that looks like Gradle together so that it's updated together.
  13. group:hibernateCore: Group Java Hibernate Core packages.
  14. group:hibernateValidator: Group Java Hibernate Validator packages.
  15. group:hibernateOgm: Group Java Hibernate OGM packages.
  16. group:hibernateCommons: Group Java Hibernate Commons packages.
  17. group:illuminate: Group PHP Illuminate packages together.
  18. group:java: Group Java runtime versions together.
  19. group:jekyllEcosystem: Group Jekyll and related Ruby packages together.
  20. group:jestPlusTSJest: Add ts-jest major update to Jest monorepo.
  21. group:jestPlusTypes: Add @types/jest update to Jest monorepo.
  22. group:jwtFramework: Group JWT Framework packages together.
  23. group:micrometer: Group Micrometer packages together, e.g. 'io.micrometer:micrometer-core'.
  24. group:phpstan: Group PHPStan packages together.
  25. group:polymer: Group all @polymer packages together.
  26. group:puppeteer: Group Puppeteer packages together.
  27. group:react: Group React and corresponding @types packages together.
  28. group:remark: Group remark packages together.
  29. group:resilience4j: Group Java Resilience4j packages.
  30. group:rubyOnRails: Group Ruby on Rails packages together.
  31. group:rubyOmniauth: Group OmniAuth packages together.
  32. group:socketio: Group socket.io packages.
  33. group:springAmqp: Group Java Spring AMQP packages.
  34. group:springAndroid: Group Java Spring Android packages.
  35. group:springBatch: Group Java Spring Batch packages.
  36. group:springBoot: Group Java Spring Boot packages.
  37. group:springCloud: Group Java Spring Cloud packages.
  38. group:springCore: Group Java Spring Core packages.
  39. group:springData: Group Java Spring Data packages.
  40. group:springHateoas: Group Java Spring HATEOAS packages.
  41. group:springIntegration: Group Java Spring Integration packages.
  42. group:springKafka: Group Java Spring Kafka packages.
  43. group:springLdap: Group Java Spring LDAP packages.
  44. group:springMobile: Group Java Spring Mobile packages.
  45. group:springOsgi: Group Java Spring OSGi packages.
  46. group:springRestDocs: Group Java Spring REST Docs packages.
  47. group:springRoo: Group Java Spring Roo packages.
  48. group:springScala: Group Java Spring Scala packages.
  49. group:springSecurity: Group Java Spring Security packages.
  50. group:springSession: Group Java Spring Session packages.
  51. group:springShell: Group Java Spring Shell packages.
  52. group:springSocial: Group Java Spring Social packages.
  53. group:springStatemachine: Group Java Spring Statemachine packages.
  54. group:springWebflow: Group Java Spring WebFlow packages.
  55. group:springWs: Group Java Spring WS packages.
  56. group:symfony: Group PHP Symfony packages together.
"},{"location":"presets-group/#groupremark","title":"group:remark","text":"

Group remark packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"remark\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchSourceUrls\": [\n        \"https://github.com/remarkjs/**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupresilience4j","title":"group:resilience4j","text":"

Group Java Resilience4j packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"resilience4j\",\n      \"matchPackageNames\": [\n        \"io.github.resilience4j:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouprubyomniauth","title":"group:rubyOmniauth","text":"

Group OmniAuth packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"omniauth packages\",\n      \"matchDatasources\": [\n        \"rubygems\"\n      ],\n      \"matchPackageNames\": [\n        \"omniauth**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouprubyonrails","title":"group:rubyOnRails","text":"

Group Ruby on Rails packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"Ruby on Rails packages\",\n      \"matchDatasources\": [\n        \"rubygems\"\n      ],\n      \"matchPackageNames\": [\n        \"actioncable\",\n        \"actionmailbox\",\n        \"actionmailer\",\n        \"actionpack\",\n        \"actiontext\",\n        \"actionview\",\n        \"activejob\",\n        \"activemodel\",\n        \"activerecord\",\n        \"activestorage\",\n        \"activesupport\",\n        \"railties\",\n        \"rails\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupsocketio","title":"group:socketio","text":"

Group socket.io packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"socket.io packages\",\n      \"matchPackageNames\": [\n        \"socket.io**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringamqp","title":"group:springAmqp","text":"

Group Java Spring AMQP packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring amqp\",\n      \"matchPackageNames\": [\n        \"org.springframework.amqp:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringandroid","title":"group:springAndroid","text":"

Group Java Spring Android packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring android\",\n      \"matchPackageNames\": [\n        \"org.springframework.android:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringbatch","title":"group:springBatch","text":"

Group Java Spring Batch packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring batch\",\n      \"matchPackageNames\": [\n        \"org.springframework.batch:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringboot","title":"group:springBoot","text":"

Group Java Spring Boot packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring boot\",\n      \"matchDepNames\": [\n        \"org.springframework.boot\"\n      ]\n    },\n    {\n      \"groupName\": \"spring boot\",\n      \"matchPackageNames\": [\n        \"org.springframework.boot:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringcloud","title":"group:springCloud","text":"

Group Java Spring Cloud packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring cloud\",\n      \"matchPackageNames\": [\n        \"org.springframework.cloud:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringcore","title":"group:springCore","text":"

Group Java Spring Core packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring core\",\n      \"matchPackageNames\": [\n        \"org.springframework:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringdata","title":"group:springData","text":"

Group Java Spring Data packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring data\",\n      \"matchPackageNames\": [\n        \"org.springframework.data:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringhateoas","title":"group:springHateoas","text":"

Group Java Spring HATEOAS packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring hateoas\",\n      \"matchPackageNames\": [\n        \"org.springframework.hateoas:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringintegration","title":"group:springIntegration","text":"

Group Java Spring Integration packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring integration\",\n      \"matchPackageNames\": [\n        \"org.springframework.integration:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringkafka","title":"group:springKafka","text":"

Group Java Spring Kafka packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring kafka\",\n      \"matchPackageNames\": [\n        \"org.springframework.kafka:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringldap","title":"group:springLdap","text":"

Group Java Spring LDAP packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring ldap\",\n      \"matchPackageNames\": [\n        \"org.springframework.ldap:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringmobile","title":"group:springMobile","text":"

Group Java Spring Mobile packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring mobile\",\n      \"matchPackageNames\": [\n        \"org.springframework.mobile:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringosgi","title":"group:springOsgi","text":"

Group Java Spring OSGi packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring osgi\",\n      \"matchPackageNames\": [\n        \"org.springframework.osgi:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringrestdocs","title":"group:springRestDocs","text":"

Group Java Spring REST Docs packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring restdocs\",\n      \"matchPackageNames\": [\n        \"org.springframework.restdocs:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringroo","title":"group:springRoo","text":"

Group Java Spring Roo packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring roo\",\n      \"matchPackageNames\": [\n        \"org.springframework.roo:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringscala","title":"group:springScala","text":"

Group Java Spring Scala packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring scala\",\n      \"matchPackageNames\": [\n        \"org.springframework.scala:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringsecurity","title":"group:springSecurity","text":"

Group Java Spring Security packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring security\",\n      \"matchPackageNames\": [\n        \"org.springframework.security:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringsession","title":"group:springSession","text":"

Group Java Spring Session packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring session\",\n      \"matchPackageNames\": [\n        \"org.springframework.session:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringshell","title":"group:springShell","text":"

Group Java Spring Shell packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring shell\",\n      \"matchPackageNames\": [\n        \"org.springframework.shell:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringsocial","title":"group:springSocial","text":"

Group Java Spring Social packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring social\",\n      \"matchPackageNames\": [\n        \"org.springframework.social:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringstatemachine","title":"group:springStatemachine","text":"

Group Java Spring Statemachine packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring statemachine\",\n      \"matchPackageNames\": [\n        \"org.springframework.statemachine:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringwebflow","title":"group:springWebflow","text":"

Group Java Spring WebFlow packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring webflow\",\n      \"matchPackageNames\": [\n        \"org.springframework.webflow:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupspringws","title":"group:springWs","text":"

Group Java Spring WS packages.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"spring ws\",\n      \"matchPackageNames\": [\n        \"org.springframework.ws:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#groupstylelint","title":"group:stylelint","text":"

Group stylelint packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:stylelint\" // (1)!\n      ],\n      \"groupName\": \"stylelint packages\",\n      \"groupSlug\": \"stylelint\",\n      \"separateMajorMinor\": false\n    }\n  ]\n}\n
  1. packages:stylelint: All Stylelint packages.
"},{"location":"presets-group/#groupsymfony","title":"group:symfony","text":"

Group PHP Symfony packages together.

{\n  \"packageRules\": [\n    {\n      \"groupName\": \"symfony packages\",\n      \"groupSlug\": \"symfony\",\n      \"matchDatasources\": [\n        \"packagist\"\n      ],\n      \"matchPackageNames\": [\n        \"symfony/*\",\n        \"!symfony/*contracts\",\n        \"!symfony/*pack\",\n        \"!symfony/flex\",\n        \"!symfony/maker-bundle\",\n        \"!symfony/monolog-bundle\",\n        \"!symfony/panther\",\n        \"!symfony/polyfill*\",\n        \"!symfony/proxy-manager-bridge\",\n        \"!symfony/security-guard\",\n        \"!symfony/stimulus-bundle\",\n        \"!symfony/templating\",\n        \"!symfony/thanks\",\n        \"!symfony/ux*\",\n        \"!symfony/webpack-encore-bundle\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-group/#grouptest","title":"group:test","text":"

Group all test packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:test\" // (1)!\n      ],\n      \"groupName\": \"test packages\"\n    }\n  ]\n}\n
  1. packages:test: Test packages.
"},{"location":"presets-group/#grouptestnonmajor","title":"group:testNonMajor","text":"

Group all non-major test package updates together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:test\" // (1)!\n      ],\n      \"groupName\": \"test packages\",\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
  1. packages:test: Test packages.
"},{"location":"presets-group/#groupunittest","title":"group:unitTest","text":"

Group all unit test packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:unitTest\" // (1)!\n      ],\n      \"groupName\": \"unit test packages\"\n    }\n  ]\n}\n
  1. packages:unitTest: All unit test packages.
"},{"location":"presets-group/#groupunittestnonmajor","title":"group:unitTestNonMajor","text":"

Group all unit test packages together for non-major updates.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:unitTest\" // (1)!\n      ],\n      \"groupName\": \"unit test packages\",\n      \"matchUpdateTypes\": [\n        \"minor\",\n        \"patch\"\n      ]\n    }\n  ]\n}\n
  1. packages:unitTest: All unit test packages.
"},{"location":"presets-group/#groupvite","title":"group:vite","text":"

Group all Vite related packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:vite\" // (1)!\n      ],\n      \"groupName\": \"Vite packages\"\n    }\n  ]\n}\n
  1. packages:vite: All Vite related packages
"},{"location":"presets-group/#groupviteplus","title":"group:vitePlus","text":"

Group all Vite+ related packages together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"packages:vitePlus\" // (1)!\n      ],\n      \"groupName\": \"Vite+ packages\"\n    }\n  ]\n}\n
  1. packages:vitePlus: All Vite+ related packages
"},{"location":"presets-group/#groupaccountsmonorepo","title":"group:accountsMonorepo","text":"

Group packages from accounts monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:accounts\" // (1)!\n      ],\n      \"groupName\": \"accounts monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:accounts: accounts monorepo
"},{"location":"presets-group/#groupacotmonorepo","title":"group:acotMonorepo","text":"

Group packages from acot monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:acot\" // (1)!\n      ],\n      \"groupName\": \"acot monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:acot: acot monorepo
"},{"location":"presets-group/#groupag-gridmonorepo","title":"group:ag-gridMonorepo","text":"

Group packages from ag-grid monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ag-grid\" // (1)!\n      ],\n      \"groupName\": \"ag-grid monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ag-grid: ag-grid monorepo
"},{"location":"presets-group/#groupalgolia-instantsearchmonorepo","title":"group:algolia-instantsearchMonorepo","text":"

Group packages from algolia-instantsearch monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:algolia-instantsearch\" // (1)!\n      ],\n      \"groupName\": \"algolia-instantsearch monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:algolia-instantsearch: algolia-instantsearch monorepo
"},{"location":"presets-group/#groupalgolia-react-instantsearchmonorepo","title":"group:algolia-react-instantsearchMonorepo","text":"

Group packages from algolia-react-instantsearch monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:algolia-react-instantsearch\" // (1)!\n      ],\n      \"groupName\": \"algolia-react-instantsearch monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:algolia-react-instantsearch: algolia-react-instantsearch monorepo
"},{"location":"presets-group/#groupalgoliasearch-autocompletemonorepo","title":"group:algoliasearch-autocompleteMonorepo","text":"

Group packages from algoliasearch-autocomplete monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:algoliasearch-autocomplete\" // (1)!\n      ],\n      \"groupName\": \"algoliasearch-autocomplete monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:algoliasearch-autocomplete: algoliasearch-autocomplete monorepo
"},{"location":"presets-group/#groupalgoliasearch-client-javascriptmonorepo","title":"group:algoliasearch-client-javascriptMonorepo","text":"

Group packages from algoliasearch-client-javascript monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:algoliasearch-client-javascript\" // (1)!\n      ],\n      \"groupName\": \"algoliasearch-client-javascript monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:algoliasearch-client-javascript: algoliasearch-client-javascript monorepo
"},{"location":"presets-group/#groupanalogmonorepo","title":"group:analogMonorepo","text":"

Group packages from analog monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:analog\" // (1)!\n      ],\n      \"groupName\": \"analog monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:analog: analog monorepo
"},{"location":"presets-group/#groupangularmonorepo","title":"group:angularMonorepo","text":"

Group packages from angular monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angular\" // (1)!\n      ],\n      \"groupName\": \"angular monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angular: angular monorepo
"},{"location":"presets-group/#groupangular-climonorepo","title":"group:angular-cliMonorepo","text":"

Group packages from angular-cli monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angular-cli\" // (1)!\n      ],\n      \"groupName\": \"angular-cli monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angular-cli: angular-cli monorepo
"},{"location":"presets-group/#groupangular-eslintmonorepo","title":"group:angular-eslintMonorepo","text":"

Group packages from angular-eslint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angular-eslint\" // (1)!\n      ],\n      \"groupName\": \"angular-eslint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angular-eslint: angular-eslint monorepo
"},{"location":"presets-group/#groupangularfiremonorepo","title":"group:angularfireMonorepo","text":"

Group packages from angularfire monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angularfire\" // (1)!\n      ],\n      \"groupName\": \"angularfire monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angularfire: angularfire monorepo
"},{"location":"presets-group/#groupangularjsmonorepo","title":"group:angularjsMonorepo","text":"

Group packages from angularjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angularjs\" // (1)!\n      ],\n      \"groupName\": \"angularjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angularjs: angularjs monorepo
"},{"location":"presets-group/#groupapache-lucenemonorepo","title":"group:apache-luceneMonorepo","text":"

Group packages from apache-lucene monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:apache-lucene\" // (1)!\n      ],\n      \"groupName\": \"apache-lucene monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:apache-lucene: apache-lucene monorepo
"},{"location":"presets-group/#groupapollo-servermonorepo","title":"group:apollo-serverMonorepo","text":"

Group packages from apollo-server monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:apollo-server\" // (1)!\n      ],\n      \"groupName\": \"apollo-server monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:apollo-server: apollo-server monorepo
"},{"location":"presets-group/#groupapolloclientmonorepo","title":"group:apolloclientMonorepo","text":"

Group packages from apolloclient monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:apolloclient\" // (1)!\n      ],\n      \"groupName\": \"apolloclient monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:apolloclient: apolloclient monorepo
"},{"location":"presets-group/#groupappiummonorepo","title":"group:appiumMonorepo","text":"

Group packages from appium monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:appium\" // (1)!\n      ],\n      \"groupName\": \"appium monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:appium: appium monorepo
"},{"location":"presets-group/#groupapplicationinsights-dotnetmonorepo","title":"group:applicationinsights-dotnetMonorepo","text":"

Group packages from applicationinsights-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:applicationinsights-dotnet\" // (1)!\n      ],\n      \"groupName\": \"applicationinsights-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:applicationinsights-dotnet: applicationinsights-dotnet monorepo
"},{"location":"presets-group/#grouparcusbackground-jobsmonorepo","title":"group:arcus.background-jobsMonorepo","text":"

Group packages from arcus.background-jobs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.background-jobs\" // (1)!\n      ],\n      \"groupName\": \"arcus.background-jobs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.background-jobs: arcus.background-jobs monorepo
"},{"location":"presets-group/#grouparcusevent-gridmonorepo","title":"group:arcus.event-gridMonorepo","text":"

Group packages from arcus.event-grid monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.event-grid\" // (1)!\n      ],\n      \"groupName\": \"arcus.event-grid monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.event-grid: arcus.event-grid monorepo
"},{"location":"presets-group/#grouparcusmessagingmonorepo","title":"group:arcus.messagingMonorepo","text":"

Group packages from arcus.messaging monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.messaging\" // (1)!\n      ],\n      \"groupName\": \"arcus.messaging monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.messaging: arcus.messaging monorepo
"},{"location":"presets-group/#grouparcusobservabilitymonorepo","title":"group:arcus.observabilityMonorepo","text":"

Group packages from arcus.observability monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.observability\" // (1)!\n      ],\n      \"groupName\": \"arcus.observability monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.observability: arcus.observability monorepo
"},{"location":"presets-group/#grouparcussecuritymonorepo","title":"group:arcus.securityMonorepo","text":"

Group packages from arcus.security monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.security\" // (1)!\n      ],\n      \"groupName\": \"arcus.security monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.security: arcus.security monorepo
"},{"location":"presets-group/#grouparcuswebapimonorepo","title":"group:arcus.webapiMonorepo","text":"

Group packages from arcus.webapi monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arcus.webapi\" // (1)!\n      ],\n      \"groupName\": \"arcus.webapi monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arcus.webapi: arcus.webapi monorepo
"},{"location":"presets-group/#grouparrow-ktmonorepo","title":"group:arrow-ktMonorepo","text":"

Group packages from arrow-kt monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arrow-kt\" // (1)!\n      ],\n      \"groupName\": \"arrow-kt monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arrow-kt: arrow-kt monorepo
"},{"location":"presets-group/#grouparrow-rsmonorepo","title":"group:arrow-rsMonorepo","text":"

Group packages from arrow-rs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:arrow-rs\" // (1)!\n      ],\n      \"groupName\": \"arrow-rs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:arrow-rs: arrow-rs monorepo
"},{"location":"presets-group/#groupaspiremonorepo","title":"group:aspireMonorepo","text":"

Group packages from aspire monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspire\" // (1)!\n      ],\n      \"groupName\": \"aspire monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspire: aspire monorepo
"},{"location":"presets-group/#groupaspnet-aspnetwebstackmonorepo","title":"group:aspnet aspnetwebstackMonorepo","text":"

Group packages from aspnet aspnetwebstack monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspnet aspnetwebstack\" // (1)!\n      ],\n      \"groupName\": \"aspnet aspnetwebstack monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspnet aspnetwebstack: aspnet aspnetwebstack monorepo
"},{"location":"presets-group/#groupaspnet-extensionsmonorepo","title":"group:aspnet extensionsMonorepo","text":"

Group packages from aspnet extensions monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspnet extensions\" // (1)!\n      ],\n      \"groupName\": \"aspnet extensions monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspnet extensions: aspnet extensions monorepo
"},{"location":"presets-group/#groupaspnet-api-versioningmonorepo","title":"group:aspnet-api-versioningMonorepo","text":"

Group packages from aspnet-api-versioning monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspnet-api-versioning\" // (1)!\n      ],\n      \"groupName\": \"aspnet-api-versioning monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspnet-api-versioning: aspnet-api-versioning monorepo
"},{"location":"presets-group/#groupaspnet-health-checksmonorepo","title":"group:aspnet-health-checksMonorepo","text":"

Group packages from aspnet-health-checks monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspnet-health-checks\" // (1)!\n      ],\n      \"groupName\": \"aspnet-health-checks monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspnet-health-checks: aspnet-health-checks monorepo
"},{"location":"presets-group/#groupaspnet-security-oauth-providersmonorepo","title":"group:aspnet-security-oauth-providersMonorepo","text":"

Group packages from aspnet-security-oauth-providers monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aspnet-security-oauth-providers\" // (1)!\n      ],\n      \"groupName\": \"aspnet-security-oauth-providers monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aspnet-security-oauth-providers: aspnet-security-oauth-providers monorepo
"},{"location":"presets-group/#groupastromonorepo","title":"group:astroMonorepo","text":"

Group packages from astro monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:astro\" // (1)!\n      ],\n      \"groupName\": \"astro monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:astro: astro monorepo
"},{"location":"presets-group/#groupautomonorepo","title":"group:autoMonorepo","text":"

Group packages from auto monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:auto\" // (1)!\n      ],\n      \"groupName\": \"auto monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:auto: auto monorepo
"},{"location":"presets-group/#groupautofixturemonorepo","title":"group:autofixtureMonorepo","text":"

Group packages from autofixture monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:autofixture\" // (1)!\n      ],\n      \"groupName\": \"autofixture monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:autofixture: autofixture monorepo
"},{"location":"presets-group/#groupautomapper-dotnetmonorepo","title":"group:automapper-dotnetMonorepo","text":"

Group packages from automapper-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:automapper-dotnet\" // (1)!\n      ],\n      \"groupName\": \"automapper-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:automapper-dotnet: automapper-dotnet monorepo
"},{"location":"presets-group/#groupavaloniamonorepo","title":"group:avaloniaMonorepo","text":"

Group packages from avalonia monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:avalonia\" // (1)!\n      ],\n      \"groupName\": \"avalonia monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:avalonia: avalonia monorepo
"},{"location":"presets-group/#groupaws-cdkmonorepo","title":"group:aws-cdkMonorepo","text":"

Group packages from aws-cdk monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-cdk\" // (1)!\n      ],\n      \"groupName\": \"aws-cdk monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-cdk: aws-cdk monorepo
"},{"location":"presets-group/#groupaws-lambda-dotnetmonorepo","title":"group:aws-lambda-dotnetMonorepo","text":"

Group packages from aws-lambda-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-lambda-dotnet\" // (1)!\n      ],\n      \"groupName\": \"aws-lambda-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-lambda-dotnet: aws-lambda-dotnet monorepo
"},{"location":"presets-group/#groupaws-lambda-powertools-typescriptmonorepo","title":"group:aws-lambda-powertools-typescriptMonorepo","text":"

Group packages from aws-lambda-powertools-typescript monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-lambda-powertools-typescript\" // (1)!\n      ],\n      \"groupName\": \"aws-lambda-powertools-typescript monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-lambda-powertools-typescript: aws-lambda-powertools-typescript monorepo
"},{"location":"presets-group/#groupaws-sdk-client-mockmonorepo","title":"group:aws-sdk-client-mockMonorepo","text":"

Group packages from aws-sdk-client-mock monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-client-mock\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-client-mock monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-client-mock: aws-sdk-client-mock monorepo
"},{"location":"presets-group/#groupaws-sdk-gomonorepo","title":"group:aws-sdk-goMonorepo","text":"

Group packages from aws-sdk-go monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-go\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-go monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-go: aws-sdk-go monorepo
"},{"location":"presets-group/#groupaws-sdk-go-v2monorepo","title":"group:aws-sdk-go-v2Monorepo","text":"

Group packages from aws-sdk-go-v2 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-go-v2\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-go-v2 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-go-v2: aws-sdk-go-v2 monorepo
"},{"location":"presets-group/#groupaws-sdk-js-v3monorepo","title":"group:aws-sdk-js-v3Monorepo","text":"

Group packages from aws-sdk-js-v3 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-js-v3\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-js-v3 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-js-v3: aws-sdk-js-v3 monorepo
"},{"location":"presets-group/#groupaws-sdk-netmonorepo","title":"group:aws-sdk-netMonorepo","text":"

Group packages from aws-sdk-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-net\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-net: aws-sdk-net monorepo
"},{"location":"presets-group/#groupaws-sdk-rustmonorepo","title":"group:aws-sdk-rustMonorepo","text":"

Group packages from aws-sdk-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-sdk-rust\" // (1)!\n      ],\n      \"groupName\": \"aws-sdk-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-sdk-rust: aws-sdk-rust monorepo
"},{"location":"presets-group/#groupawsappsyncmonorepo","title":"group:awsappsyncMonorepo","text":"

Group packages from awsappsync monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:awsappsync\" // (1)!\n      ],\n      \"groupName\": \"awsappsync monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:awsappsync: awsappsync monorepo
"},{"location":"presets-group/#groupaxummonorepo","title":"group:axumMonorepo","text":"

Group packages from axum monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:axum\" // (1)!\n      ],\n      \"groupName\": \"axum monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:axum: axum monorepo
"},{"location":"presets-group/#groupazure-azure-libraries-for-netmonorepo","title":"group:azure azure-libraries-for-netMonorepo","text":"

Group packages from azure azure-libraries-for-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure azure-libraries-for-net\" // (1)!\n      ],\n      \"groupName\": \"azure azure-libraries-for-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure azure-libraries-for-net: azure azure-libraries-for-net monorepo
"},{"location":"presets-group/#groupazure-azure-sdk-for-netmonorepo","title":"group:azure azure-sdk-for-netMonorepo","text":"

Group packages from azure azure-sdk-for-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure azure-sdk-for-net\" // (1)!\n      ],\n      \"groupName\": \"azure azure-sdk-for-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure azure-sdk-for-net: azure azure-sdk-for-net monorepo
"},{"location":"presets-group/#groupazure-azure-storage-netmonorepo","title":"group:azure azure-storage-netMonorepo","text":"

Group packages from azure azure-storage-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure azure-storage-net\" // (1)!\n      ],\n      \"groupName\": \"azure azure-storage-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure azure-storage-net: azure azure-storage-net monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-androidmonorepo","title":"group:azure-ad-microsoft-authentication-library-for-androidMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-android monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-android\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-android monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-android: azure-ad-microsoft-authentication-library-for-android monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-dotnetmonorepo","title":"group:azure-ad-microsoft-authentication-library-for-dotnetMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-dotnet\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-dotnet: azure-ad-microsoft-authentication-library-for-dotnet monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-gomonorepo","title":"group:azure-ad-microsoft-authentication-library-for-goMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-go monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-go\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-go monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-go: azure-ad-microsoft-authentication-library-for-go monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-javamonorepo","title":"group:azure-ad-microsoft-authentication-library-for-javaMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-java monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-java\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-java monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-java: azure-ad-microsoft-authentication-library-for-java monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-jsmonorepo","title":"group:azure-ad-microsoft-authentication-library-for-jsMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-js\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-js: azure-ad-microsoft-authentication-library-for-js monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-objcmonorepo","title":"group:azure-ad-microsoft-authentication-library-for-objcMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-objc monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-objc\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-objc monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-objc: azure-ad-microsoft-authentication-library-for-objc monorepo
"},{"location":"presets-group/#groupazure-ad-microsoft-authentication-library-for-pythonmonorepo","title":"group:azure-ad-microsoft-authentication-library-for-pythonMonorepo","text":"

Group packages from azure-ad-microsoft-authentication-library-for-python monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-ad-microsoft-authentication-library-for-python\" // (1)!\n      ],\n      \"groupName\": \"azure-ad-microsoft-authentication-library-for-python monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-ad-microsoft-authentication-library-for-python: azure-ad-microsoft-authentication-library-for-python monorepo
"},{"location":"presets-group/#groupazure-functions-dotnet-workermonorepo","title":"group:azure-functions-dotnet-workerMonorepo","text":"

Group packages from azure-functions-dotnet-worker monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-functions-dotnet-worker\" // (1)!\n      ],\n      \"groupName\": \"azure-functions-dotnet-worker monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-functions-dotnet-worker: azure-functions-dotnet-worker monorepo
"},{"location":"presets-group/#groupazure-sdk-for-androidmonorepo","title":"group:azure-sdk-for-androidMonorepo","text":"

Group packages from azure-sdk-for-android monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-android\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-android monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-android: azure-sdk-for-android monorepo
"},{"location":"presets-group/#groupazure-sdk-for-cmonorepo","title":"group:azure-sdk-for-cMonorepo","text":"

Group packages from azure-sdk-for-c monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-c\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-c monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-c: azure-sdk-for-c monorepo
"},{"location":"presets-group/#groupazure-sdk-for-cppmonorepo","title":"group:azure-sdk-for-cppMonorepo","text":"

Group packages from azure-sdk-for-cpp monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-cpp\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-cpp monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-cpp: azure-sdk-for-cpp monorepo
"},{"location":"presets-group/#groupazure-sdk-for-gomonorepo","title":"group:azure-sdk-for-goMonorepo","text":"

Group packages from azure-sdk-for-go monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-go\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-go monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-go: azure-sdk-for-go monorepo
"},{"location":"presets-group/#groupazure-sdk-for-iosmonorepo","title":"group:azure-sdk-for-iosMonorepo","text":"

Group packages from azure-sdk-for-ios monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-ios\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-ios monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-ios: azure-sdk-for-ios monorepo
"},{"location":"presets-group/#groupazure-sdk-for-javamonorepo","title":"group:azure-sdk-for-javaMonorepo","text":"

Group packages from azure-sdk-for-java monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-java\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-java monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-java: azure-sdk-for-java monorepo
"},{"location":"presets-group/#groupazure-sdk-for-jsmonorepo","title":"group:azure-sdk-for-jsMonorepo","text":"

Group packages from azure-sdk-for-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-js\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-js: azure-sdk-for-js monorepo
"},{"location":"presets-group/#groupazure-sdk-for-pythonmonorepo","title":"group:azure-sdk-for-pythonMonorepo","text":"

Group packages from azure-sdk-for-python monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-python\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-python monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-python: azure-sdk-for-python monorepo
"},{"location":"presets-group/#groupazure-sdk-for-rustmonorepo","title":"group:azure-sdk-for-rustMonorepo","text":"

Group packages from azure-sdk-for-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:azure-sdk-for-rust\" // (1)!\n      ],\n      \"groupName\": \"azure-sdk-for-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:azure-sdk-for-rust: azure-sdk-for-rust monorepo
"},{"location":"presets-group/#groupbabelmonorepo","title":"group:babelMonorepo","text":"

Group packages from babel monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:babel\" // (1)!\n      ],\n      \"groupName\": \"babel monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:babel: babel monorepo
"},{"location":"presets-group/#groupbackstagemonorepo","title":"group:backstageMonorepo","text":"

Group packages from backstage monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:backstage\" // (1)!\n      ],\n      \"groupName\": \"backstage monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:backstage: backstage monorepo
"},{"location":"presets-group/#groupbasetmonorepo","title":"group:basetMonorepo","text":"

Group packages from baset monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:baset\" // (1)!\n      ],\n      \"groupName\": \"baset monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:baset: baset monorepo
"},{"location":"presets-group/#groupbetter-authmonorepo","title":"group:better-authMonorepo","text":"

Group packages from better-auth monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:better-auth\" // (1)!\n      ],\n      \"groupName\": \"better-auth monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:better-auth: better-auth monorepo
"},{"location":"presets-group/#groupbravemonorepo","title":"group:braveMonorepo","text":"

Group packages from brave monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:brave\" // (1)!\n      ],\n      \"groupName\": \"brave monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:brave: brave monorepo
"},{"location":"presets-group/#groupbugsnag-jsmonorepo","title":"group:bugsnag-jsMonorepo","text":"

Group packages from bugsnag-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:bugsnag-js\" // (1)!\n      ],\n      \"groupName\": \"bugsnag-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:bugsnag-js: bugsnag-js monorepo
"},{"location":"presets-group/#groupbull-boardmonorepo","title":"group:bull-boardMonorepo","text":"

Group packages from bull-board monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:bull-board\" // (1)!\n      ],\n      \"groupName\": \"bull-board monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:bull-board: bull-board monorepo
"},{"location":"presets-group/#groupcakemonorepo","title":"group:cakeMonorepo","text":"

Group packages from cake monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:cake\" // (1)!\n      ],\n      \"groupName\": \"cake monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:cake: cake monorepo
"},{"location":"presets-group/#groupcake-issuesmonorepo","title":"group:cake-issuesMonorepo","text":"

Group packages from cake-issues monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:cake-issues\" // (1)!\n      ],\n      \"groupName\": \"cake-issues monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:cake-issues: cake-issues monorepo
"},{"location":"presets-group/#groupcapacitormonorepo","title":"group:capacitorMonorepo","text":"

Group packages from capacitor monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:capacitor\" // (1)!\n      ],\n      \"groupName\": \"capacitor monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:capacitor: capacitor monorepo
"},{"location":"presets-group/#groupcedarmonorepo","title":"group:cedarMonorepo","text":"

Group packages from cedar monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:cedar\" // (1)!\n      ],\n      \"groupName\": \"cedar monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:cedar: cedar monorepo
"},{"location":"presets-group/#groupchakra-uimonorepo","title":"group:chakra-uiMonorepo","text":"

Group packages from chakra-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:chakra-ui\" // (1)!\n      ],\n      \"groupName\": \"chakra-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:chakra-ui: chakra-ui monorepo
"},{"location":"presets-group/#groupchromelymonorepo","title":"group:chromelyMonorepo","text":"

Group packages from chromely monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:chromely\" // (1)!\n      ],\n      \"groupName\": \"chromely monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:chromely: chromely monorepo
"},{"location":"presets-group/#groupcitation-jsmonorepo","title":"group:citation-jsMonorepo","text":"

Group packages from citation-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:citation-js\" // (1)!\n      ],\n      \"groupName\": \"citation-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:citation-js: citation-js monorepo
"},{"location":"presets-group/#groupckeditormonorepo","title":"group:ckeditorMonorepo","text":"

Group packages from ckeditor monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ckeditor\" // (1)!\n      ],\n      \"groupName\": \"ckeditor monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ckeditor: ckeditor monorepo
"},{"location":"presets-group/#groupclaritymonorepo","title":"group:clarityMonorepo","text":"

Group packages from clarity monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:clarity\" // (1)!\n      ],\n      \"groupName\": \"clarity monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:clarity: clarity monorepo
"},{"location":"presets-group/#groupclearscriptmonorepo","title":"group:clearscriptMonorepo","text":"

Group packages from clearscript monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:clearscript\" // (1)!\n      ],\n      \"groupName\": \"clearscript monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:clearscript: clearscript monorepo
"},{"location":"presets-group/#groupcommitlintmonorepo","title":"group:commitlintMonorepo","text":"

Group packages from commitlint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:commitlint\" // (1)!\n      ],\n      \"groupName\": \"commitlint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:commitlint: commitlint monorepo
"},{"location":"presets-group/#groupconfectmonorepo","title":"group:confectMonorepo","text":"

Group packages from confect monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:confect\" // (1)!\n      ],\n      \"groupName\": \"confect monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:confect: confect monorepo
"},{"location":"presets-group/#groupconformmonorepo","title":"group:conformMonorepo","text":"

Group packages from conform monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:conform\" // (1)!\n      ],\n      \"groupName\": \"conform monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:conform: conform monorepo
"},{"location":"presets-group/#groupcontentful-rich-textmonorepo","title":"group:contentful-rich-textMonorepo","text":"

Group packages from contentful-rich-text monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:contentful-rich-text\" // (1)!\n      ],\n      \"groupName\": \"contentful-rich-text monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:contentful-rich-text: contentful-rich-text monorepo
"},{"location":"presets-group/#groupconvexmonorepo","title":"group:convexMonorepo","text":"

Group packages from convex monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:convex\" // (1)!\n      ],\n      \"groupName\": \"convex monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:convex: convex monorepo
"},{"location":"presets-group/#groupcspellmonorepo","title":"group:cspellMonorepo","text":"

Group packages from cspell monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:cspell\" // (1)!\n      ],\n      \"groupName\": \"cspell monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:cspell: cspell monorepo
"},{"location":"presets-group/#groupdatadog-browser-sdkmonorepo","title":"group:datadog-browser-sdkMonorepo","text":"

Group packages from datadog-browser-sdk monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datadog-browser-sdk\" // (1)!\n      ],\n      \"groupName\": \"datadog-browser-sdk monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datadog-browser-sdk: datadog-browser-sdk monorepo
"},{"location":"presets-group/#groupdatafusionmonorepo","title":"group:datafusionMonorepo","text":"

Group packages from datafusion monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datafusion\" // (1)!\n      ],\n      \"groupName\": \"datafusion monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datafusion: datafusion monorepo
"},{"location":"presets-group/#groupdatatables-netmonorepo","title":"group:datatables-netMonorepo","text":"

Group packages from datatables-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net\" // (1)!\n      ],\n      \"groupName\": \"datatables-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net: datatables-net monorepo
"},{"location":"presets-group/#groupdatatables-net-autofillmonorepo","title":"group:datatables-net-autofillMonorepo","text":"

Group packages from datatables-net-autofill monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-autofill\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-autofill monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-autofill: datatables-net-autofill monorepo
"},{"location":"presets-group/#groupdatatables-net-buttonsmonorepo","title":"group:datatables-net-buttonsMonorepo","text":"

Group packages from datatables-net-buttons monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-buttons\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-buttons monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-buttons: datatables-net-buttons monorepo
"},{"location":"presets-group/#groupdatatables-net-colreordermonorepo","title":"group:datatables-net-colreorderMonorepo","text":"

Group packages from datatables-net-colreorder monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-colreorder\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-colreorder monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-colreorder: datatables-net-colreorder monorepo
"},{"location":"presets-group/#groupdatatables-net-fixedcolumnsmonorepo","title":"group:datatables-net-fixedcolumnsMonorepo","text":"

Group packages from datatables-net-fixedcolumns monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-fixedcolumns\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-fixedcolumns monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-fixedcolumns: datatables-net-fixedcolumns monorepo
"},{"location":"presets-group/#groupdatatables-net-fixedheadermonorepo","title":"group:datatables-net-fixedheaderMonorepo","text":"

Group packages from datatables-net-fixedheader monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-fixedheader\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-fixedheader monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-fixedheader: datatables-net-fixedheader monorepo
"},{"location":"presets-group/#groupdatatables-net-keytablemonorepo","title":"group:datatables-net-keytableMonorepo","text":"

Group packages from datatables-net-keytable monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-keytable\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-keytable monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-keytable: datatables-net-keytable monorepo
"},{"location":"presets-group/#groupdatatables-net-responsivemonorepo","title":"group:datatables-net-responsiveMonorepo","text":"

Group packages from datatables-net-responsive monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-responsive\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-responsive monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-responsive: datatables-net-responsive monorepo
"},{"location":"presets-group/#groupdatatables-net-rowgroupmonorepo","title":"group:datatables-net-rowgroupMonorepo","text":"

Group packages from datatables-net-rowgroup monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-rowgroup\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-rowgroup monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-rowgroup: datatables-net-rowgroup monorepo
"},{"location":"presets-group/#groupdatatables-net-rowreordermonorepo","title":"group:datatables-net-rowreorderMonorepo","text":"

Group packages from datatables-net-rowreorder monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-rowreorder\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-rowreorder monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-rowreorder: datatables-net-rowreorder monorepo
"},{"location":"presets-group/#groupdatatables-net-scrollermonorepo","title":"group:datatables-net-scrollerMonorepo","text":"

Group packages from datatables-net-scroller monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-scroller\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-scroller monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-scroller: datatables-net-scroller monorepo
"},{"location":"presets-group/#groupdatatables-net-searchbuildermonorepo","title":"group:datatables-net-searchbuilderMonorepo","text":"

Group packages from datatables-net-searchbuilder monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-searchbuilder\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-searchbuilder monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-searchbuilder: datatables-net-searchbuilder monorepo
"},{"location":"presets-group/#groupdatatables-net-searchpanesmonorepo","title":"group:datatables-net-searchpanesMonorepo","text":"

Group packages from datatables-net-searchpanes monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-searchpanes\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-searchpanes monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-searchpanes: datatables-net-searchpanes monorepo
"},{"location":"presets-group/#groupdatatables-net-selectmonorepo","title":"group:datatables-net-selectMonorepo","text":"

Group packages from datatables-net-select monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-select\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-select monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-select: datatables-net-select monorepo
"},{"location":"presets-group/#groupdatatables-net-staterestoremonorepo","title":"group:datatables-net-staterestoreMonorepo","text":"

Group packages from datatables-net-staterestore monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:datatables-net-staterestore\" // (1)!\n      ],\n      \"groupName\": \"datatables-net-staterestore monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:datatables-net-staterestore: datatables-net-staterestore monorepo
"},{"location":"presets-group/#groupdate-iomonorepo","title":"group:date-ioMonorepo","text":"

Group packages from date-io monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:date-io\" // (1)!\n      ],\n      \"groupName\": \"date-io monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:date-io: date-io monorepo
"},{"location":"presets-group/#groupdeck-glmonorepo","title":"group:deck-glMonorepo","text":"

Group packages from deck-gl monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:deck-gl\" // (1)!\n      ],\n      \"groupName\": \"deck-gl monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:deck-gl: deck-gl monorepo
"},{"location":"presets-group/#groupdenomonorepo","title":"group:denoMonorepo","text":"

Group packages from deno monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:deno\" // (1)!\n      ],\n      \"groupName\": \"deno monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:deno: deno monorepo
"},{"location":"presets-group/#groupdevextreme-reactivemonorepo","title":"group:devextreme-reactiveMonorepo","text":"

Group packages from devextreme-reactive monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:devextreme-reactive\" // (1)!\n      ],\n      \"groupName\": \"devextreme-reactive monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:devextreme-reactive: devextreme-reactive monorepo
"},{"location":"presets-group/#groupdnd-kitmonorepo","title":"group:dnd-kitMonorepo","text":"

Group packages from dnd-kit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dnd-kit\" // (1)!\n      ],\n      \"groupName\": \"dnd-kit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dnd-kit: dnd-kit monorepo
"},{"location":"presets-group/#groupdocusaurusmonorepo","title":"group:docusaurusMonorepo","text":"

Group packages from docusaurus monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:docusaurus\" // (1)!\n      ],\n      \"groupName\": \"docusaurus monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:docusaurus: docusaurus monorepo
"},{"location":"presets-group/#groupdot-swashbucklemonorepo","title":"group:dot-swashbuckleMonorepo","text":"

Group packages from dot-swashbuckle monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dot-swashbuckle\" // (1)!\n      ],\n      \"groupName\": \"dot-swashbuckle monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dot-swashbuckle: dot-swashbuckle monorepo
"},{"location":"presets-group/#groupdotnetmonorepo","title":"group:dotnetMonorepo","text":"

Group packages from dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dotnet\" // (1)!\n      ],\n      \"groupName\": \"dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dotnet: dotnet monorepo
"},{"location":"presets-group/#groupdotnet-azure-ad-identitymodel-extensionsmonorepo","title":"group:dotnet-azure-ad-identitymodel-extensionsMonorepo","text":"

Group packages from dotnet-azure-ad-identitymodel-extensions monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dotnet-azure-ad-identitymodel-extensions\" // (1)!\n      ],\n      \"groupName\": \"dotnet-azure-ad-identitymodel-extensions monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dotnet-azure-ad-identitymodel-extensions: dotnet-azure-ad-identitymodel-extensions monorepo
"},{"location":"presets-group/#groupdotnet-azure-ad-microsoft-identity-webmonorepo","title":"group:dotnet-azure-ad-microsoft-identity-webMonorepo","text":"

Group packages from dotnet-azure-ad-microsoft-identity-web monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dotnet-azure-ad-microsoft-identity-web\" // (1)!\n      ],\n      \"groupName\": \"dotnet-azure-ad-microsoft-identity-web monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dotnet-azure-ad-microsoft-identity-web: dotnet-azure-ad-microsoft-identity-web monorepo
"},{"location":"presets-group/#groupdotnet-wcfmonorepo","title":"group:dotnet-wcfMonorepo","text":"

Group packages from dotnet-wcf monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dotnet-wcf\" // (1)!\n      ],\n      \"groupName\": \"dotnet-wcf monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dotnet-wcf: dotnet-wcf monorepo
"},{"location":"presets-group/#groupdotnetcore-capmonorepo","title":"group:dotnetcore-capMonorepo","text":"

Group packages from dotnetcore-cap monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dotnetcore-cap\" // (1)!\n      ],\n      \"groupName\": \"dotnetcore-cap monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dotnetcore-cap: dotnetcore-cap monorepo
"},{"location":"presets-group/#groupdropwizardmonorepo","title":"group:dropwizardMonorepo","text":"

Group packages from dropwizard monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:dropwizard\" // (1)!\n      ],\n      \"groupName\": \"dropwizard monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:dropwizard: dropwizard monorepo
"},{"location":"presets-group/#groupduende-identityservermonorepo","title":"group:duende-identityserverMonorepo","text":"

Group packages from duende-identityserver monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:duende-identityserver\" // (1)!\n      ],\n      \"groupName\": \"duende-identityserver monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:duende-identityserver: duende-identityserver monorepo
"},{"location":"presets-group/#groupeffectmonorepo","title":"group:effectMonorepo","text":"

Group packages from effect monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:effect\" // (1)!\n      ],\n      \"groupName\": \"effect monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:effect: effect monorepo
"},{"location":"presets-group/#groupelastic-apm-agent-rum-jsmonorepo","title":"group:elastic-apm-agent-rum-jsMonorepo","text":"

Group packages from elastic-apm-agent-rum-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:elastic-apm-agent-rum-js\" // (1)!\n      ],\n      \"groupName\": \"elastic-apm-agent-rum-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:elastic-apm-agent-rum-js: elastic-apm-agent-rum-js monorepo
"},{"location":"presets-group/#groupelastic-ecs-dotnetmonorepo","title":"group:elastic-ecs-dotnetMonorepo","text":"

Group packages from elastic-ecs-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:elastic-ecs-dotnet\" // (1)!\n      ],\n      \"groupName\": \"elastic-ecs-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:elastic-ecs-dotnet: elastic-ecs-dotnet monorepo
"},{"location":"presets-group/#groupelectron-forgemonorepo","title":"group:electron-forgeMonorepo","text":"

Group packages from electron-forge monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:electron-forge\" // (1)!\n      ],\n      \"groupName\": \"electron-forge monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:electron-forge: electron-forge monorepo
"},{"location":"presets-group/#groupember-decoratorsmonorepo","title":"group:ember-decoratorsMonorepo","text":"

Group packages from ember-decorators monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ember-decorators\" // (1)!\n      ],\n      \"groupName\": \"ember-decorators monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ember-decorators: ember-decorators monorepo
"},{"location":"presets-group/#groupembla-carouselmonorepo","title":"group:embla-carouselMonorepo","text":"

Group packages from embla-carousel monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:embla-carousel\" // (1)!\n      ],\n      \"groupName\": \"embla-carousel monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:embla-carousel: embla-carousel monorepo
"},{"location":"presets-group/#groupemojibasemonorepo","title":"group:emojibaseMonorepo","text":"

Group packages from emojibase monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:emojibase\" // (1)!\n      ],\n      \"groupName\": \"emojibase monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:emojibase: emojibase monorepo
"},{"location":"presets-group/#groupemotionmonorepo","title":"group:emotionMonorepo","text":"

Group packages from emotion monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:emotion\" // (1)!\n      ],\n      \"groupName\": \"emotion monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:emotion: emotion monorepo
"},{"location":"presets-group/#groupenumeratummonorepo","title":"group:enumeratumMonorepo","text":"

Group packages from enumeratum monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:enumeratum\" // (1)!\n      ],\n      \"groupName\": \"enumeratum monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:enumeratum: enumeratum monorepo
"},{"location":"presets-group/#groupenvelopmonorepo","title":"group:envelopMonorepo","text":"

Group packages from envelop monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:envelop\" // (1)!\n      ],\n      \"groupName\": \"envelop monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:envelop: envelop monorepo
"},{"location":"presets-group/#grouperror-pronemonorepo","title":"group:error-proneMonorepo","text":"

Group packages from error-prone monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:error-prone\" // (1)!\n      ],\n      \"groupName\": \"error-prone monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:error-prone: error-prone monorepo
"},{"location":"presets-group/#grouperror-prone-supportmonorepo","title":"group:error-prone-supportMonorepo","text":"

Group packages from error-prone-support monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:error-prone-support\" // (1)!\n      ],\n      \"groupName\": \"error-prone-support monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:error-prone-support: error-prone-support monorepo
"},{"location":"presets-group/#groupeslintmonorepo","title":"group:eslintMonorepo","text":"

Group packages from eslint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:eslint\" // (1)!\n      ],\n      \"groupName\": \"eslint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:eslint: eslint monorepo
"},{"location":"presets-group/#groupeslint-config-globexmonorepo","title":"group:eslint-config-globexMonorepo","text":"

Group packages from eslint-config-globex monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:eslint-config-globex\" // (1)!\n      ],\n      \"groupName\": \"eslint-config-globex monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:eslint-config-globex: eslint-config-globex monorepo
"},{"location":"presets-group/#groupeslint-stylisticmonorepo","title":"group:eslint-stylisticMonorepo","text":"

Group packages from eslint-stylistic monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:eslint-stylistic\" // (1)!\n      ],\n      \"groupName\": \"eslint-stylistic monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:eslint-stylistic: eslint-stylistic monorepo
"},{"location":"presets-group/#groupexpomonorepo","title":"group:expoMonorepo","text":"

Group packages from expo monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:expo\" // (1)!\n      ],\n      \"groupName\": \"expo monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:expo: expo monorepo
"},{"location":"presets-group/#groupfabric-chaincode-nodemonorepo","title":"group:fabric-chaincode-nodeMonorepo","text":"

Group packages from fabric-chaincode-node monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fabric-chaincode-node\" // (1)!\n      ],\n      \"groupName\": \"fabric-chaincode-node monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fabric-chaincode-node: fabric-chaincode-node monorepo
"},{"location":"presets-group/#groupfabric8-kubernetes-clientmonorepo","title":"group:fabric8-kubernetes-clientMonorepo","text":"

Group packages from fabric8-kubernetes-client monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fabric8-kubernetes-client\" // (1)!\n      ],\n      \"groupName\": \"fabric8-kubernetes-client monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fabric8-kubernetes-client: fabric8-kubernetes-client monorepo
"},{"location":"presets-group/#groupfaro-web-sdkmonorepo","title":"group:faro-web-sdkMonorepo","text":"

Group packages from faro-web-sdk monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:faro-web-sdk\" // (1)!\n      ],\n      \"groupName\": \"faro-web-sdk monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:faro-web-sdk: faro-web-sdk monorepo
"},{"location":"presets-group/#groupfastendpointsmonorepo","title":"group:fastendpointsMonorepo","text":"

Group packages from fastendpoints monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fastendpoints\" // (1)!\n      ],\n      \"groupName\": \"fastendpoints monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fastendpoints: fastendpoints monorepo
"},{"location":"presets-group/#groupfeathersmonorepo","title":"group:feathersMonorepo","text":"

Group packages from feathers monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:feathers\" // (1)!\n      ],\n      \"groupName\": \"feathers monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:feathers: feathers monorepo
"},{"location":"presets-group/#groupfeaturemanagement-dotnetmonorepo","title":"group:featuremanagement-dotnetMonorepo","text":"

Group packages from featuremanagement-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:featuremanagement-dotnet\" // (1)!\n      ],\n      \"groupName\": \"featuremanagement-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:featuremanagement-dotnet: featuremanagement-dotnet monorepo
"},{"location":"presets-group/#groupfeignmonorepo","title":"group:feignMonorepo","text":"

Group packages from feign monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:feign\" // (1)!\n      ],\n      \"groupName\": \"feign monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:feign: feign monorepo
"},{"location":"presets-group/#groupfelamonorepo","title":"group:felaMonorepo","text":"

Group packages from fela monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fela\" // (1)!\n      ],\n      \"groupName\": \"fela monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fela: fela monorepo
"},{"location":"presets-group/#groupfimbullintermonorepo","title":"group:fimbullinterMonorepo","text":"

Group packages from fimbullinter monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fimbullinter\" // (1)!\n      ],\n      \"groupName\": \"fimbullinter monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fimbullinter: fimbullinter monorepo
"},{"location":"presets-group/#groupflippermonorepo","title":"group:flipperMonorepo","text":"

Group packages from flipper monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:flipper\" // (1)!\n      ],\n      \"groupName\": \"flipper monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:flipper: flipper monorepo
"},{"location":"presets-group/#groupflopflipmonorepo","title":"group:flopflipMonorepo","text":"

Group packages from flopflip monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:flopflip\" // (1)!\n      ],\n      \"groupName\": \"flopflip monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:flopflip: flopflip monorepo
"},{"location":"presets-group/#groupfluemonorepo","title":"group:flueMonorepo","text":"

Group packages from flue monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:flue\" // (1)!\n      ],\n      \"groupName\": \"flue monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:flue: flue monorepo
"},{"location":"presets-group/#groupfontsourcemonorepo","title":"group:fontsourceMonorepo","text":"

Group packages from fontsource monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fontsource\" // (1)!\n      ],\n      \"groupName\": \"fontsource monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fontsource: fontsource monorepo
"},{"location":"presets-group/#groupformatjsmonorepo","title":"group:formatjsMonorepo","text":"

Group packages from formatjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:formatjs\" // (1)!\n      ],\n      \"groupName\": \"formatjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:formatjs: formatjs monorepo
"},{"location":"presets-group/#groupframework7monorepo","title":"group:framework7Monorepo","text":"

Group packages from framework7 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:framework7\" // (1)!\n      ],\n      \"groupName\": \"framework7 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:framework7: framework7 monorepo
"},{"location":"presets-group/#groupfunogrammonorepo","title":"group:funogramMonorepo","text":"

Group packages from funogram monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:funogram\" // (1)!\n      ],\n      \"groupName\": \"funogram monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:funogram: funogram monorepo
"},{"location":"presets-group/#groupfusioncachemonorepo","title":"group:fusioncacheMonorepo","text":"

Group packages from fusioncache monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fusioncache\" // (1)!\n      ],\n      \"groupName\": \"fusioncache monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fusioncache: fusioncache monorepo
"},{"location":"presets-group/#groupgatsbymonorepo","title":"group:gatsbyMonorepo","text":"

Group packages from gatsby monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:gatsby\" // (1)!\n      ],\n      \"groupName\": \"gatsby monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:gatsby: gatsby monorepo
"},{"location":"presets-group/#groupgitbeakermonorepo","title":"group:gitbeakerMonorepo","text":"

Group packages from gitbeaker monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:gitbeaker\" // (1)!\n      ],\n      \"groupName\": \"gitbeaker monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:gitbeaker: gitbeaker monorepo
"},{"location":"presets-group/#groupgithub-workflows-ktmonorepo","title":"group:github-workflows-ktMonorepo","text":"

Group packages from github-workflows-kt monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:github-workflows-kt\" // (1)!\n      ],\n      \"groupName\": \"github-workflows-kt monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:github-workflows-kt: github-workflows-kt monorepo
"},{"location":"presets-group/#groupgo-cloudmonorepo","title":"group:go-cloudMonorepo","text":"

Group packages from go-cloud monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:go-cloud\" // (1)!\n      ],\n      \"groupName\": \"go-cloud monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:go-cloud: go-cloud monorepo
"},{"location":"presets-group/#groupgomockmonorepo","title":"group:gomockMonorepo","text":"

Group packages from gomock monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:gomock\" // (1)!\n      ],\n      \"groupName\": \"gomock monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:gomock: gomock monorepo
"},{"location":"presets-group/#groupgoogle-api-dotnet-clientmonorepo","title":"group:google-api-dotnet-clientMonorepo","text":"

Group packages from google-api-dotnet-client monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:google-api-dotnet-client\" // (1)!\n      ],\n      \"groupName\": \"google-api-dotnet-client monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:google-api-dotnet-client: google-api-dotnet-client monorepo
"},{"location":"presets-group/#groupgoogle-cloud-rustmonorepo","title":"group:google-cloud-rustMonorepo","text":"

Group packages from google-cloud-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:google-cloud-rust\" // (1)!\n      ],\n      \"groupName\": \"google-cloud-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:google-cloud-rust: google-cloud-rust monorepo
"},{"location":"presets-group/#groupgrafanamonorepo","title":"group:grafanaMonorepo","text":"

Group packages from grafana monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:grafana\" // (1)!\n      ],\n      \"groupName\": \"grafana monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:grafana: grafana monorepo
"},{"location":"presets-group/#groupgraphiqlmonorepo","title":"group:graphiqlMonorepo","text":"

Group packages from graphiql monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphiql\" // (1)!\n      ],\n      \"groupName\": \"graphiql monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphiql: graphiql monorepo
"},{"location":"presets-group/#groupgraphql-hive-gatewaymonorepo","title":"group:graphql-hive-gatewayMonorepo","text":"

Group packages from graphql-hive-gateway monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-hive-gateway\" // (1)!\n      ],\n      \"groupName\": \"graphql-hive-gateway monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-hive-gateway: graphql-hive-gateway monorepo
"},{"location":"presets-group/#groupgraphql-meshmonorepo","title":"group:graphql-meshMonorepo","text":"

Group packages from graphql-mesh monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-mesh\" // (1)!\n      ],\n      \"groupName\": \"graphql-mesh monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-mesh: graphql-mesh monorepo
"},{"location":"presets-group/#groupgraphql-modulesmonorepo","title":"group:graphql-modulesMonorepo","text":"

Group packages from graphql-modules monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-modules\" // (1)!\n      ],\n      \"groupName\": \"graphql-modules monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-modules: graphql-modules monorepo
"},{"location":"presets-group/#groupgraphql-platformmonorepo","title":"group:graphql-platformMonorepo","text":"

Group packages from graphql-platform monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-platform\" // (1)!\n      ],\n      \"groupName\": \"graphql-platform monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-platform: graphql-platform monorepo
"},{"location":"presets-group/#groupgraphql-toolsmonorepo","title":"group:graphql-toolsMonorepo","text":"

Group packages from graphql-tools monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-tools\" // (1)!\n      ],\n      \"groupName\": \"graphql-tools monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-tools: graphql-tools monorepo
"},{"location":"presets-group/#groupgraphql-yogamonorepo","title":"group:graphql-yogaMonorepo","text":"

Group packages from graphql-yoga monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphql-yoga\" // (1)!\n      ],\n      \"groupName\": \"graphql-yoga monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphql-yoga: graphql-yoga monorepo
"},{"location":"presets-group/#groupgraphqlcodegeneratormonorepo","title":"group:graphqlcodegeneratorMonorepo","text":"

Group packages from graphqlcodegenerator monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:graphqlcodegenerator\" // (1)!\n      ],\n      \"groupName\": \"graphqlcodegenerator monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:graphqlcodegenerator: graphqlcodegenerator monorepo
"},{"location":"presets-group/#groupgreenmailmonorepo","title":"group:greenmailMonorepo","text":"

Group packages from greenmail monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:greenmail\" // (1)!\n      ],\n      \"groupName\": \"greenmail monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:greenmail: greenmail monorepo
"},{"location":"presets-group/#groupgroovymonorepo","title":"group:groovyMonorepo","text":"

Group packages from groovy monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:groovy\" // (1)!\n      ],\n      \"groupName\": \"groovy monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:groovy: groovy monorepo
"},{"location":"presets-group/#groupgrpc-dotnetmonorepo","title":"group:grpc-dotnetMonorepo","text":"

Group packages from grpc-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:grpc-dotnet\" // (1)!\n      ],\n      \"groupName\": \"grpc-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:grpc-dotnet: grpc-dotnet monorepo
"},{"location":"presets-group/#groupgrpc-javamonorepo","title":"group:grpc-javaMonorepo","text":"

Group packages from grpc-java monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:grpc-java\" // (1)!\n      ],\n      \"groupName\": \"grpc-java monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:grpc-java: grpc-java monorepo
"},{"location":"presets-group/#groupgstreamer-rustmonorepo","title":"group:gstreamer-rustMonorepo","text":"

Group packages from gstreamer-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:gstreamer-rust\" // (1)!\n      ],\n      \"groupName\": \"gstreamer-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:gstreamer-rust: gstreamer-rust monorepo
"},{"location":"presets-group/#groupguavamonorepo","title":"group:guavaMonorepo","text":"

Group packages from guava monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:guava\" // (1)!\n      ],\n      \"groupName\": \"guava monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:guava: guava monorepo
"},{"location":"presets-group/#grouphangfiremonorepo","title":"group:hangfireMonorepo","text":"

Group packages from hangfire monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hangfire\" // (1)!\n      ],\n      \"groupName\": \"hangfire monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hangfire: hangfire monorepo
"},{"location":"presets-group/#grouphappy-dommonorepo","title":"group:happy-domMonorepo","text":"

Group packages from happy-dom monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:happy-dom\" // (1)!\n      ],\n      \"groupName\": \"happy-dom monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:happy-dom: happy-dom monorepo
"},{"location":"presets-group/#grouphibernate-modelsmonorepo","title":"group:hibernate-modelsMonorepo","text":"

Group packages from hibernate-models monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hibernate-models\" // (1)!\n      ],\n      \"groupName\": \"hibernate-models monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hibernate-models: hibernate-models monorepo
"},{"location":"presets-group/#grouphibernate-ormmonorepo","title":"group:hibernate-ormMonorepo","text":"

Group packages from hibernate-orm monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hibernate-orm\" // (1)!\n      ],\n      \"groupName\": \"hibernate-orm monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hibernate-orm: hibernate-orm monorepo
"},{"location":"presets-group/#grouphibernate-searchmonorepo","title":"group:hibernate-searchMonorepo","text":"

Group packages from hibernate-search monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hibernate-search\" // (1)!\n      ],\n      \"groupName\": \"hibernate-search monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hibernate-search: hibernate-search monorepo
"},{"location":"presets-group/#grouphibernate-toolsmonorepo","title":"group:hibernate-toolsMonorepo","text":"

Group packages from hibernate-tools monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hibernate-tools\" // (1)!\n      ],\n      \"groupName\": \"hibernate-tools monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hibernate-tools: hibernate-tools monorepo
"},{"location":"presets-group/#grouphickory-dnsmonorepo","title":"group:hickory-dnsMonorepo","text":"

Group packages from hickory-dns monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hickory-dns\" // (1)!\n      ],\n      \"groupName\": \"hickory-dns monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hickory-dns: hickory-dns monorepo
"},{"location":"presets-group/#grouphocuspocusmonorepo","title":"group:hocuspocusMonorepo","text":"

Group packages from hocuspocus monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hocuspocus\" // (1)!\n      ],\n      \"groupName\": \"hocuspocus monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hocuspocus: hocuspocus monorepo
"},{"location":"presets-group/#grouphtml-eslintmonorepo","title":"group:html-eslintMonorepo","text":"

Group packages from html-eslint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:html-eslint\" // (1)!\n      ],\n      \"groupName\": \"html-eslint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:html-eslint: html-eslint monorepo
"},{"location":"presets-group/#grouphumanizermonorepo","title":"group:humanizerMonorepo","text":"

Group packages from humanizer monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:humanizer\" // (1)!\n      ],\n      \"groupName\": \"humanizer monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:humanizer: humanizer monorepo
"},{"location":"presets-group/#groupimmichmonorepo","title":"group:immichMonorepo","text":"

Group packages from immich monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:immich\" // (1)!\n      ],\n      \"groupName\": \"immich monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:immich: immich monorepo
"},{"location":"presets-group/#groupinfrastructure-uimonorepo","title":"group:infrastructure-uiMonorepo","text":"

Group packages from infrastructure-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:infrastructure-ui\" // (1)!\n      ],\n      \"groupName\": \"infrastructure-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:infrastructure-ui: infrastructure-ui monorepo
"},{"location":"presets-group/#groupionic-nativemonorepo","title":"group:ionic-nativeMonorepo","text":"

Group packages from ionic-native monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ionic-native\" // (1)!\n      ],\n      \"groupName\": \"ionic-native monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ionic-native: ionic-native monorepo
"},{"location":"presets-group/#groupistanbuljsmonorepo","title":"group:istanbuljsMonorepo","text":"

Group packages from istanbuljs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:istanbuljs\" // (1)!\n      ],\n      \"groupName\": \"istanbuljs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:istanbuljs: istanbuljs monorepo
"},{"location":"presets-group/#groupistiomonorepo","title":"group:istioMonorepo","text":"

Group packages from istio monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:istio\" // (1)!\n      ],\n      \"groupName\": \"istio monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:istio: istio monorepo
"},{"location":"presets-group/#groupjacksonmonorepo","title":"group:jacksonMonorepo","text":"

Group packages from jackson monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jackson\" // (1)!\n      ],\n      \"groupName\": \"jackson monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jackson: jackson monorepo
"},{"location":"presets-group/#groupjasminemonorepo","title":"group:jasmineMonorepo","text":"

Group packages from jasmine monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jasmine\" // (1)!\n      ],\n      \"groupName\": \"jasmine monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jasmine: jasmine monorepo
"},{"location":"presets-group/#groupjavafxmonorepo","title":"group:javafxMonorepo","text":"

Group packages from javafx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:javafx\" // (1)!\n      ],\n      \"groupName\": \"javafx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:javafx: javafx monorepo
"},{"location":"presets-group/#groupjavahamcrestmonorepo","title":"group:javahamcrestMonorepo","text":"

Group packages from javahamcrest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:javahamcrest\" // (1)!\n      ],\n      \"groupName\": \"javahamcrest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:javahamcrest: javahamcrest monorepo
"},{"location":"presets-group/#groupjavascriptengineswitchermonorepo","title":"group:javascriptengineswitcherMonorepo","text":"

Group packages from javascriptengineswitcher monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:javascriptengineswitcher\" // (1)!\n      ],\n      \"groupName\": \"javascriptengineswitcher monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:javascriptengineswitcher: javascriptengineswitcher monorepo
"},{"location":"presets-group/#groupjaxb-rimonorepo","title":"group:jaxb-riMonorepo","text":"

Group packages from jaxb-ri monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jaxb-ri\" // (1)!\n      ],\n      \"groupName\": \"jaxb-ri monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jaxb-ri: jaxb-ri monorepo
"},{"location":"presets-group/#groupjerseymonorepo","title":"group:jerseyMonorepo","text":"

Group packages from jersey monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jersey\" // (1)!\n      ],\n      \"groupName\": \"jersey monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jersey: jersey monorepo
"},{"location":"presets-group/#groupjestmonorepo","title":"group:jestMonorepo","text":"

Group packages from jest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jest\" // (1)!\n      ],\n      \"groupName\": \"jest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jest: jest monorepo
"},{"location":"presets-group/#groupjettymonorepo","title":"group:jettyMonorepo","text":"

Group packages from jetty monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jetty\" // (1)!\n      ],\n      \"groupName\": \"jetty monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jetty: jetty monorepo
"},{"location":"presets-group/#groupjnamonorepo","title":"group:jnaMonorepo","text":"

Group packages from jna monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jna\" // (1)!\n      ],\n      \"groupName\": \"jna monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jna: jna monorepo
"},{"location":"presets-group/#groupjson-smart-v2monorepo","title":"group:json-smart-v2Monorepo","text":"

Group packages from json-smart-v2 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:json-smart-v2\" // (1)!\n      ],\n      \"groupName\": \"json-smart-v2 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:json-smart-v2: json-smart-v2 monorepo
"},{"location":"presets-group/#groupjsonformsmonorepo","title":"group:jsonformsMonorepo","text":"

Group packages from jsonforms monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jsonforms\" // (1)!\n      ],\n      \"groupName\": \"jsonforms monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jsonforms: jsonforms monorepo
"},{"location":"presets-group/#groupjsplumbmonorepo","title":"group:jsplumbMonorepo","text":"

Group packages from jsplumb monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:jsplumb\" // (1)!\n      ],\n      \"groupName\": \"jsplumb monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:jsplumb: jsplumb monorepo
"},{"location":"presets-group/#groupjuniormonorepo","title":"group:juniorMonorepo","text":"

Group packages from junior monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:junior\" // (1)!\n      ],\n      \"groupName\": \"junior monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:junior: junior monorepo
"},{"location":"presets-group/#groupjunit-frameworkmonorepo","title":"group:junit-frameworkMonorepo","text":"

Group packages from junit-framework monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:junit-framework\" // (1)!\n      ],\n      \"groupName\": \"junit-framework monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:junit-framework: junit-framework monorepo
"},{"location":"presets-group/#groupkernelmemorymonorepo","title":"group:kernelmemoryMonorepo","text":"

Group packages from kernelmemory monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kernelmemory\" // (1)!\n      ],\n      \"groupName\": \"kernelmemory monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kernelmemory: kernelmemory monorepo
"},{"location":"presets-group/#groupkiotamonorepo","title":"group:kiotaMonorepo","text":"

Group packages from kiota monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kiota\" // (1)!\n      ],\n      \"groupName\": \"kiota monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kiota: kiota monorepo
"},{"location":"presets-group/#groupkotlinmonorepo","title":"group:kotlinMonorepo","text":"

Group packages from kotlin monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kotlin\" // (1)!\n      ],\n      \"groupName\": \"kotlin monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kotlin: kotlin monorepo
"},{"location":"presets-group/#groupkotlinx-coroutinesmonorepo","title":"group:kotlinx-coroutinesMonorepo","text":"

Group packages from kotlinx-coroutines monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kotlinx-coroutines\" // (1)!\n      ],\n      \"groupName\": \"kotlinx-coroutines monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kotlinx-coroutines: kotlinx-coroutines monorepo
"},{"location":"presets-group/#groupkrokimonorepo","title":"group:krokiMonorepo","text":"

Group packages from kroki monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kroki\" // (1)!\n      ],\n      \"groupName\": \"kroki monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kroki: kroki monorepo
"},{"location":"presets-group/#groupkspmonorepo","title":"group:kspMonorepo","text":"

Group packages from ksp monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ksp\" // (1)!\n      ],\n      \"groupName\": \"ksp monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ksp: ksp monorepo
"},{"location":"presets-group/#groupktormonorepo","title":"group:ktorMonorepo","text":"

Group packages from ktor monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ktor\" // (1)!\n      ],\n      \"groupName\": \"ktor monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ktor: ktor monorepo
"},{"location":"presets-group/#groupkubbmonorepo","title":"group:kubbMonorepo","text":"

Group packages from kubb monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kubb\" // (1)!\n      ],\n      \"groupName\": \"kubb monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kubb: kubb monorepo
"},{"location":"presets-group/#groupkubernetesmonorepo","title":"group:kubernetesMonorepo","text":"

Group packages from kubernetes monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:kubernetes\" // (1)!\n      ],\n      \"groupName\": \"kubernetes monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:kubernetes: kubernetes monorepo
"},{"location":"presets-group/#grouplamarmonorepo","title":"group:lamarMonorepo","text":"

Group packages from lamar monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lamar\" // (1)!\n      ],\n      \"groupName\": \"lamar monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lamar: lamar monorepo
"},{"location":"presets-group/#grouplangchain4jmonorepo","title":"group:langchain4jMonorepo","text":"

Group packages from langchain4j monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:langchain4j\" // (1)!\n      ],\n      \"groupName\": \"langchain4j monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:langchain4j: langchain4j monorepo
"},{"location":"presets-group/#grouplernamonorepo","title":"group:lernaMonorepo","text":"

Group packages from lerna monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lerna\" // (1)!\n      ],\n      \"groupName\": \"lerna monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lerna: lerna monorepo
"},{"location":"presets-group/#grouplerna-litemonorepo","title":"group:lerna-liteMonorepo","text":"

Group packages from lerna-lite monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lerna-lite\" // (1)!\n      ],\n      \"groupName\": \"lerna-lite monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lerna-lite: lerna-lite monorepo
"},{"location":"presets-group/#grouplexicalmonorepo","title":"group:lexicalMonorepo","text":"

Group packages from lexical monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lexical\" // (1)!\n      ],\n      \"groupName\": \"lexical monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lexical: lexical monorepo
"},{"location":"presets-group/#grouplinguijsmonorepo","title":"group:linguijsMonorepo","text":"

Group packages from linguijs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:linguijs\" // (1)!\n      ],\n      \"groupName\": \"linguijs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:linguijs: linguijs monorepo
"},{"location":"presets-group/#grouplinkifyjsmonorepo","title":"group:linkifyjsMonorepo","text":"

Group packages from linkifyjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:linkifyjs\" // (1)!\n      ],\n      \"groupName\": \"linkifyjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:linkifyjs: linkifyjs monorepo
"},{"location":"presets-group/#grouplog4j2monorepo","title":"group:log4j2Monorepo","text":"

Group packages from log4j2 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:log4j2\" // (1)!\n      ],\n      \"groupName\": \"log4j2 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:log4j2: log4j2 monorepo
"},{"location":"presets-group/#grouplogbackmonorepo","title":"group:logbackMonorepo","text":"

Group packages from logback monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:logback\" // (1)!\n      ],\n      \"groupName\": \"logback monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:logback: logback monorepo
"},{"location":"presets-group/#grouplogtapemonorepo","title":"group:logtapeMonorepo","text":"

Group packages from logtape monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:logtape\" // (1)!\n      ],\n      \"groupName\": \"logtape monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:logtape: logtape monorepo
"},{"location":"presets-group/#grouploopbackmonorepo","title":"group:loopbackMonorepo","text":"

Group packages from loopback monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:loopback\" // (1)!\n      ],\n      \"groupName\": \"loopback monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:loopback: loopback monorepo
"},{"location":"presets-group/#grouplrnwebcomponentsmonorepo","title":"group:lrnwebcomponentsMonorepo","text":"

Group packages from lrnwebcomponents monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lrnwebcomponents\" // (1)!\n      ],\n      \"groupName\": \"lrnwebcomponents monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lrnwebcomponents: lrnwebcomponents monorepo
"},{"location":"presets-group/#grouplucidemonorepo","title":"group:lucideMonorepo","text":"

Group packages from lucide monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lucide\" // (1)!\n      ],\n      \"groupName\": \"lucide monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lucide: lucide monorepo
"},{"location":"presets-group/#groupmailingmonorepo","title":"group:mailingMonorepo","text":"

Group packages from mailing monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mailing\" // (1)!\n      ],\n      \"groupName\": \"mailing monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mailing: mailing monorepo
"},{"location":"presets-group/#groupmantinemonorepo","title":"group:mantineMonorepo","text":"

Group packages from mantine monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mantine\" // (1)!\n      ],\n      \"groupName\": \"mantine monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mantine: mantine monorepo
"},{"location":"presets-group/#groupmapstructmonorepo","title":"group:mapstructMonorepo","text":"

Group packages from mapstruct monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mapstruct\" // (1)!\n      ],\n      \"groupName\": \"mapstruct monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mapstruct: mapstruct monorepo
"},{"location":"presets-group/#groupmartenmonorepo","title":"group:martenMonorepo","text":"

Group packages from marten monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:marten\" // (1)!\n      ],\n      \"groupName\": \"marten monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:marten: marten monorepo
"},{"location":"presets-group/#groupmasstransitmonorepo","title":"group:masstransitMonorepo","text":"

Group packages from masstransit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:masstransit\" // (1)!\n      ],\n      \"groupName\": \"masstransit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:masstransit: masstransit monorepo
"},{"location":"presets-group/#groupmaterial-components-webmonorepo","title":"group:material-components-webMonorepo","text":"

Group packages from material-components-web monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:material-components-web\" // (1)!\n      ],\n      \"groupName\": \"material-components-web monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:material-components-web: material-components-web monorepo
"},{"location":"presets-group/#groupmaterial-uimonorepo","title":"group:material-uiMonorepo","text":"

Group packages from material-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:material-ui\" // (1)!\n      ],\n      \"groupName\": \"material-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:material-ui: material-ui monorepo
"},{"location":"presets-group/#groupmdc-reactmonorepo","title":"group:mdc-reactMonorepo","text":"

Group packages from mdc-react monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mdc-react\" // (1)!\n      ],\n      \"groupName\": \"mdc-react monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mdc-react: mdc-react monorepo
"},{"location":"presets-group/#groupmdxmonorepo","title":"group:mdxMonorepo","text":"

Group packages from mdx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mdx\" // (1)!\n      ],\n      \"groupName\": \"mdx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mdx: mdx monorepo
"},{"location":"presets-group/#groupmiddy-jsmonorepo","title":"group:middy-jsMonorepo","text":"

Group packages from middy-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:middy-js\" // (1)!\n      ],\n      \"groupName\": \"middy-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:middy-js: middy-js monorepo
"},{"location":"presets-group/#groupmikro-ormmonorepo","title":"group:mikro-ormMonorepo","text":"

Group packages from mikro-orm monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mikro-orm\" // (1)!\n      ],\n      \"groupName\": \"mikro-orm monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mikro-orm: mikro-orm monorepo
"},{"location":"presets-group/#groupml-dotnetmonorepo","title":"group:ml-dotnetMonorepo","text":"

Group packages from ml-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ml-dotnet\" // (1)!\n      ],\n      \"groupName\": \"ml-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ml-dotnet: ml-dotnet monorepo
"},{"location":"presets-group/#groupmockitomonorepo","title":"group:mockitoMonorepo","text":"

Group packages from mockito monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mockito\" // (1)!\n      ],\n      \"groupName\": \"mockito monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mockito: mockito monorepo
"},{"location":"presets-group/#groupmongo-csharp-drivermonorepo","title":"group:mongo-csharp-driverMonorepo","text":"

Group packages from mongo-csharp-driver monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mongo-csharp-driver\" // (1)!\n      ],\n      \"groupName\": \"mongo-csharp-driver monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mongo-csharp-driver: mongo-csharp-driver monorepo
"},{"location":"presets-group/#groupmongo-java-drivermonorepo","title":"group:mongo-java-driverMonorepo","text":"

Group packages from mongo-java-driver monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mongo-java-driver\" // (1)!\n      ],\n      \"groupName\": \"mongo-java-driver monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mongo-java-driver: mongo-java-driver monorepo
"},{"location":"presets-group/#groupmstestmonorepo","title":"group:mstestMonorepo","text":"

Group packages from mstest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mstest\" // (1)!\n      ],\n      \"groupName\": \"mstest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mstest: mstest monorepo
"},{"location":"presets-group/#groupmutation-testing-elementsmonorepo","title":"group:mutation-testing-elementsMonorepo","text":"

Group packages from mutation-testing-elements monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:mutation-testing-elements\" // (1)!\n      ],\n      \"groupName\": \"mutation-testing-elements monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:mutation-testing-elements: mutation-testing-elements monorepo
"},{"location":"presets-group/#groupnestmonorepo","title":"group:nestMonorepo","text":"

Group packages from nest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nest\" // (1)!\n      ],\n      \"groupName\": \"nest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nest: nest monorepo
"},{"location":"presets-group/#groupnest-graphqlmonorepo","title":"group:nest-graphqlMonorepo","text":"

Group packages from nest-graphql monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nest-graphql\" // (1)!\n      ],\n      \"groupName\": \"nest-graphql monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nest-graphql: nest-graphql monorepo
"},{"location":"presets-group/#groupnettymonorepo","title":"group:nettyMonorepo","text":"

Group packages from netty monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:netty\" // (1)!\n      ],\n      \"groupName\": \"netty monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:netty: netty monorepo
"},{"location":"presets-group/#groupneutrinomonorepo","title":"group:neutrinoMonorepo","text":"

Group packages from neutrino monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:neutrino\" // (1)!\n      ],\n      \"groupName\": \"neutrino monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:neutrino: neutrino monorepo
"},{"location":"presets-group/#groupnexpectmonorepo","title":"group:nexpectMonorepo","text":"

Group packages from nexpect monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nexpect\" // (1)!\n      ],\n      \"groupName\": \"nexpect monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nexpect: nexpect monorepo
"},{"location":"presets-group/#groupnextjsmonorepo","title":"group:nextjsMonorepo","text":"

Group packages from nextjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nextjs\" // (1)!\n      ],\n      \"groupName\": \"nextjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nextjs: nextjs monorepo
"},{"location":"presets-group/#groupnextramonorepo","title":"group:nextraMonorepo","text":"

Group packages from nextra monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nextra\" // (1)!\n      ],\n      \"groupName\": \"nextra monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nextra: nextra monorepo
"},{"location":"presets-group/#groupngx-cookie-servicemonorepo","title":"group:ngx-cookie-serviceMonorepo","text":"

Group packages from ngx-cookie-service monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ngx-cookie-service\" // (1)!\n      ],\n      \"groupName\": \"ngx-cookie-service monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ngx-cookie-service: ngx-cookie-service monorepo
"},{"location":"presets-group/#groupngx-formlymonorepo","title":"group:ngx-formlyMonorepo","text":"

Group packages from ngx-formly monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ngx-formly\" // (1)!\n      ],\n      \"groupName\": \"ngx-formly monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ngx-formly: ngx-formly monorepo
"},{"location":"presets-group/#groupngxs-storemonorepo","title":"group:ngxs-storeMonorepo","text":"

Group packages from ngxs-store monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ngxs-store\" // (1)!\n      ],\n      \"groupName\": \"ngxs-store monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ngxs-store: ngxs-store monorepo
"},{"location":"presets-group/#groupnivomonorepo","title":"group:nivoMonorepo","text":"

Group packages from nivo monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nivo\" // (1)!\n      ],\n      \"groupName\": \"nivo monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nivo: nivo monorepo
"},{"location":"presets-group/#groupnjson-schemamonorepo","title":"group:njson-schemaMonorepo","text":"

Group packages from njson-schema monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:njson-schema\" // (1)!\n      ],\n      \"groupName\": \"njson-schema monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:njson-schema: njson-schema monorepo
"},{"location":"presets-group/#groupnswagmonorepo","title":"group:nswagMonorepo","text":"

Group packages from nswag monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nswag\" // (1)!\n      ],\n      \"groupName\": \"nswag monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nswag: nswag monorepo
"},{"location":"presets-group/#groupnugetmonorepo","title":"group:nugetMonorepo","text":"

Group packages from nuget monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nuget\" // (1)!\n      ],\n      \"groupName\": \"nuget monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nuget: nuget monorepo
"},{"location":"presets-group/#groupnuke-buildmonorepo","title":"group:nuke-buildMonorepo","text":"

Group packages from nuke-build monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nuke-build\" // (1)!\n      ],\n      \"groupName\": \"nuke-build monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nuke-build: nuke-build monorepo
"},{"location":"presets-group/#groupnuxtjsmonorepo","title":"group:nuxtjsMonorepo","text":"

Group packages from nuxtjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nuxtjs\" // (1)!\n      ],\n      \"groupName\": \"nuxtjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nuxtjs: nuxtjs monorepo
"},{"location":"presets-group/#groupokhttpmonorepo","title":"group:okhttpMonorepo","text":"

Group packages from okhttp monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:okhttp\" // (1)!\n      ],\n      \"groupName\": \"okhttp monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:okhttp: okhttp monorepo
"},{"location":"presets-group/#groupopenapi-dotnetmonorepo","title":"group:openapi-dotnetMonorepo","text":"

Group packages from openapi-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:openapi-dotnet\" // (1)!\n      ],\n      \"groupName\": \"openapi-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:openapi-dotnet: openapi-dotnet monorepo
"},{"location":"presets-group/#groupopencostmonorepo","title":"group:opencostMonorepo","text":"

Group packages from opencost monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opencost\" // (1)!\n      ],\n      \"groupName\": \"opencost monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opencost: opencost monorepo
"},{"location":"presets-group/#groupopeniddictmonorepo","title":"group:openiddictMonorepo","text":"

Group packages from openiddict monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:openiddict\" // (1)!\n      ],\n      \"groupName\": \"openiddict monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:openiddict: openiddict monorepo
"},{"location":"presets-group/#groupopentelemetry-dotnetmonorepo","title":"group:opentelemetry-dotnetMonorepo","text":"

Group packages from opentelemetry-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-dotnet\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-dotnet: opentelemetry-dotnet monorepo
"},{"location":"presets-group/#groupopentelemetry-dotnet-contribmonorepo","title":"group:opentelemetry-dotnet-contribMonorepo","text":"

Group packages from opentelemetry-dotnet-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-dotnet-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-dotnet-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-dotnet-contrib: opentelemetry-dotnet-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-erlangmonorepo","title":"group:opentelemetry-erlangMonorepo","text":"

Group packages from opentelemetry-erlang monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-erlang\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-erlang monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-erlang: opentelemetry-erlang monorepo
"},{"location":"presets-group/#groupopentelemetry-erlang-contribmonorepo","title":"group:opentelemetry-erlang-contribMonorepo","text":"

Group packages from opentelemetry-erlang-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-erlang-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-erlang-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-erlang-contrib: opentelemetry-erlang-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-gomonorepo","title":"group:opentelemetry-goMonorepo","text":"

Group packages from opentelemetry-go monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-go\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-go monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-go: opentelemetry-go monorepo
"},{"location":"presets-group/#groupopentelemetry-go-contribmonorepo","title":"group:opentelemetry-go-contribMonorepo","text":"

Group packages from opentelemetry-go-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-go-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-go-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-go-contrib: opentelemetry-go-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-javamonorepo","title":"group:opentelemetry-javaMonorepo","text":"

Group packages from opentelemetry-java monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-java\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-java monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-java: opentelemetry-java monorepo
"},{"location":"presets-group/#groupopentelemetry-java-contribmonorepo","title":"group:opentelemetry-java-contribMonorepo","text":"

Group packages from opentelemetry-java-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-java-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-java-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-java-contrib: opentelemetry-java-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-jsmonorepo","title":"group:opentelemetry-jsMonorepo","text":"

Group packages from opentelemetry-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-js\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-js: opentelemetry-js monorepo
"},{"location":"presets-group/#groupopentelemetry-js-contribmonorepo","title":"group:opentelemetry-js-contribMonorepo","text":"

Group packages from opentelemetry-js-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-js-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-js-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-js-contrib: opentelemetry-js-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-phpmonorepo","title":"group:opentelemetry-phpMonorepo","text":"

Group packages from opentelemetry-php monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-php\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-php monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-php: opentelemetry-php monorepo
"},{"location":"presets-group/#groupopentelemetry-php-contribmonorepo","title":"group:opentelemetry-php-contribMonorepo","text":"

Group packages from opentelemetry-php-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-php-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-php-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-php-contrib: opentelemetry-php-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-pythonmonorepo","title":"group:opentelemetry-pythonMonorepo","text":"

Group packages from opentelemetry-python monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-python\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-python monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-python: opentelemetry-python monorepo
"},{"location":"presets-group/#groupopentelemetry-python-contribmonorepo","title":"group:opentelemetry-python-contribMonorepo","text":"

Group packages from opentelemetry-python-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-python-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-python-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-python-contrib: opentelemetry-python-contrib monorepo
"},{"location":"presets-group/#groupopentelemetry-rustmonorepo","title":"group:opentelemetry-rustMonorepo","text":"

Group packages from opentelemetry-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-rust\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-rust: opentelemetry-rust monorepo
"},{"location":"presets-group/#groupopentelemetry-rust-contribmonorepo","title":"group:opentelemetry-rust-contribMonorepo","text":"

Group packages from opentelemetry-rust-contrib monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:opentelemetry-rust-contrib\" // (1)!\n      ],\n      \"groupName\": \"opentelemetry-rust-contrib monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:opentelemetry-rust-contrib: opentelemetry-rust-contrib monorepo
"},{"location":"presets-group/#grouporleansmonorepo","title":"group:orleansMonorepo","text":"

Group packages from orleans monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:orleans\" // (1)!\n      ],\n      \"groupName\": \"orleans monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:orleans: orleans monorepo
"},{"location":"presets-group/#grouporpcmonorepo","title":"group:orpcMonorepo","text":"

Group packages from orpc monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:orpc\" // (1)!\n      ],\n      \"groupName\": \"orpc monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:orpc: orpc monorepo
"},{"location":"presets-group/#grouppanda-cssmonorepo","title":"group:panda-cssMonorepo","text":"

Group packages from panda-css monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:panda-css\" // (1)!\n      ],\n      \"groupName\": \"panda-css monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:panda-css: panda-css monorepo
"},{"location":"presets-group/#groupparcelmonorepo","title":"group:parcelMonorepo","text":"

Group packages from parcel monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:parcel\" // (1)!\n      ],\n      \"groupName\": \"parcel monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:parcel: parcel monorepo
"},{"location":"presets-group/#grouppayloadcmsmonorepo","title":"group:payloadcmsMonorepo","text":"

Group packages from payloadcms monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:payloadcms\" // (1)!\n      ],\n      \"groupName\": \"payloadcms monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:payloadcms: payloadcms monorepo
"},{"location":"presets-group/#grouppdfmemonorepo","title":"group:pdfmeMonorepo","text":"

Group packages from pdfme monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pdfme\" // (1)!\n      ],\n      \"groupName\": \"pdfme monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pdfme: pdfme monorepo
"},{"location":"presets-group/#grouppercy-climonorepo","title":"group:percy-cliMonorepo","text":"

Group packages from percy-cli monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:percy-cli\" // (1)!\n      ],\n      \"groupName\": \"percy-cli monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:percy-cli: percy-cli monorepo
"},{"location":"presets-group/#grouppicassojsmonorepo","title":"group:picassojsMonorepo","text":"

Group packages from picassojs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:picassojs\" // (1)!\n      ],\n      \"groupName\": \"picassojs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:picassojs: picassojs monorepo
"},{"location":"presets-group/#grouppixijsmonorepo","title":"group:pixijsMonorepo","text":"

Group packages from pixijs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pixijs\" // (1)!\n      ],\n      \"groupName\": \"pixijs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pixijs: pixijs monorepo
"},{"location":"presets-group/#groupplaywrightmonorepo","title":"group:playwrightMonorepo","text":"

Group packages from playwright monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:playwright\" // (1)!\n      ],\n      \"groupName\": \"playwright monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:playwright: playwright monorepo
"},{"location":"presets-group/#groupplaywright-dotnetmonorepo","title":"group:playwright-dotnetMonorepo","text":"

Group packages from playwright-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:playwright-dotnet\" // (1)!\n      ],\n      \"groupName\": \"playwright-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:playwright-dotnet: playwright-dotnet monorepo
"},{"location":"presets-group/#grouppnpcoremonorepo","title":"group:pnpcoreMonorepo","text":"

Group packages from pnpcore monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pnpcore\" // (1)!\n      ],\n      \"groupName\": \"pnpcore monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pnpcore: pnpcore monorepo
"},{"location":"presets-group/#grouppnpjsmonorepo","title":"group:pnpjsMonorepo","text":"

Group packages from pnpjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pnpjs\" // (1)!\n      ],\n      \"groupName\": \"pnpjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pnpjs: pnpjs monorepo
"},{"location":"presets-group/#grouppollymonorepo","title":"group:pollyMonorepo","text":"

Group packages from polly monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:polly\" // (1)!\n      ],\n      \"groupName\": \"polly monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:polly: polly monorepo
"},{"location":"presets-group/#grouppollyjsmonorepo","title":"group:pollyjsMonorepo","text":"

Group packages from pollyjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pollyjs\" // (1)!\n      ],\n      \"groupName\": \"pollyjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pollyjs: pollyjs monorepo
"},{"location":"presets-group/#grouppothosmonorepo","title":"group:pothosMonorepo","text":"

Group packages from pothos monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pothos\" // (1)!\n      ],\n      \"groupName\": \"pothos monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pothos: pothos monorepo
"},{"location":"presets-group/#grouppouchdbmonorepo","title":"group:pouchdbMonorepo","text":"

Group packages from pouchdb monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:pouchdb\" // (1)!\n      ],\n      \"groupName\": \"pouchdb monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:pouchdb: pouchdb monorepo
"},{"location":"presets-group/#grouppowermockmonorepo","title":"group:powermockMonorepo","text":"

Group packages from powermock monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:powermock\" // (1)!\n      ],\n      \"groupName\": \"powermock monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:powermock: powermock monorepo
"},{"location":"presets-group/#groupprismamonorepo","title":"group:prismaMonorepo","text":"

Group packages from prisma monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:prisma\" // (1)!\n      ],\n      \"groupName\": \"prisma monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:prisma: prisma monorepo
"},{"location":"presets-group/#groupprometheus-netmonorepo","title":"group:prometheus-netMonorepo","text":"

Group packages from prometheus-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:prometheus-net\" // (1)!\n      ],\n      \"groupName\": \"prometheus-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:prometheus-net: prometheus-net monorepo
"},{"location":"presets-group/#grouppromstermonorepo","title":"group:promsterMonorepo","text":"

Group packages from promster monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:promster\" // (1)!\n      ],\n      \"groupName\": \"promster monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:promster: promster monorepo
"},{"location":"presets-group/#groupprotobufmonorepo","title":"group:protobufMonorepo","text":"

Group packages from protobuf monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:protobuf\" // (1)!\n      ],\n      \"groupName\": \"protobuf monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:protobuf: protobuf monorepo
"},{"location":"presets-group/#groupquartznetmonorepo","title":"group:quartznetMonorepo","text":"

Group packages from quartznet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:quartznet\" // (1)!\n      ],\n      \"groupName\": \"quartznet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:quartznet: quartznet monorepo
"},{"location":"presets-group/#groupradix-ui-primitivesmonorepo","title":"group:radix-ui-primitivesMonorepo","text":"

Group packages from radix-ui-primitives monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:radix-ui-primitives\" // (1)!\n      ],\n      \"groupName\": \"radix-ui-primitives monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:radix-ui-primitives: radix-ui-primitives monorepo
"},{"location":"presets-group/#groupreach-uimonorepo","title":"group:reach-uiMonorepo","text":"

Group packages from reach-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:reach-ui\" // (1)!\n      ],\n      \"groupName\": \"reach-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:reach-ui: reach-ui monorepo
"},{"location":"presets-group/#groupreactmonorepo","title":"group:reactMonorepo","text":"

Group packages from react monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react\" // (1)!\n      ],\n      \"groupName\": \"react monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react: react monorepo
"},{"location":"presets-group/#groupreact-adminmonorepo","title":"group:react-adminMonorepo","text":"

Group packages from react-admin monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-admin\" // (1)!\n      ],\n      \"groupName\": \"react-admin monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-admin: react-admin monorepo
"},{"location":"presets-group/#groupreact-apollomonorepo","title":"group:react-apolloMonorepo","text":"

Group packages from react-apollo monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-apollo\" // (1)!\n      ],\n      \"groupName\": \"react-apollo monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-apollo: react-apollo monorepo
"},{"location":"presets-group/#groupreact-dndmonorepo","title":"group:react-dndMonorepo","text":"

Group packages from react-dnd monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-dnd\" // (1)!\n      ],\n      \"groupName\": \"react-dnd monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-dnd: react-dnd monorepo
"},{"location":"presets-group/#groupreact-emailmonorepo","title":"group:react-emailMonorepo","text":"

Group packages from react-email monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-email\" // (1)!\n      ],\n      \"groupName\": \"react-email monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-email: react-email monorepo
"},{"location":"presets-group/#groupreact-navigationmonorepo","title":"group:react-navigationMonorepo","text":"

Group packages from react-navigation monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-navigation\" // (1)!\n      ],\n      \"groupName\": \"react-navigation monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-navigation: react-navigation monorepo
"},{"location":"presets-group/#groupreact-pagemonorepo","title":"group:react-pageMonorepo","text":"

Group packages from react-page monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-page\" // (1)!\n      ],\n      \"groupName\": \"react-page monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-page: react-page monorepo
"},{"location":"presets-group/#groupreact-railsmonorepo","title":"group:react-railsMonorepo","text":"

Group packages from react-rails monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-rails\" // (1)!\n      ],\n      \"groupName\": \"react-rails monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-rails: react-rails monorepo
"},{"location":"presets-group/#groupreact-routermonorepo","title":"group:react-routerMonorepo","text":"

Group packages from react-router monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-router\" // (1)!\n      ],\n      \"groupName\": \"react-router monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-router: react-router monorepo
"},{"location":"presets-group/#groupreact-spectrummonorepo","title":"group:react-spectrumMonorepo","text":"

Group packages from react-spectrum monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-spectrum\" // (1)!\n      ],\n      \"groupName\": \"react-spectrum monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-spectrum: react-spectrum monorepo
"},{"location":"presets-group/#groupreact-springmonorepo","title":"group:react-springMonorepo","text":"

Group packages from react-spring monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:react-spring\" // (1)!\n      ],\n      \"groupName\": \"react-spring monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:react-spring: react-spring monorepo
"},{"location":"presets-group/#groupreactivestack-cookiesmonorepo","title":"group:reactivestack-cookiesMonorepo","text":"

Group packages from reactivestack-cookies monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:reactivestack-cookies\" // (1)!\n      ],\n      \"groupName\": \"reactivestack-cookies monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:reactivestack-cookies: reactivestack-cookies monorepo
"},{"location":"presets-group/#groupreakitmonorepo","title":"group:reakitMonorepo","text":"

Group packages from reakit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:reakit\" // (1)!\n      ],\n      \"groupName\": \"reakit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:reakit: reakit monorepo
"},{"location":"presets-group/#groupredwoodmonorepo","title":"group:redwoodMonorepo","text":"

Group packages from redwood monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:redwood\" // (1)!\n      ],\n      \"groupName\": \"redwood monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:redwood: redwood monorepo
"},{"location":"presets-group/#grouprefitmonorepo","title":"group:refitMonorepo","text":"

Group packages from refit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:refit\" // (1)!\n      ],\n      \"groupName\": \"refit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:refit: refit monorepo
"},{"location":"presets-group/#groupreg-suitmonorepo","title":"group:reg-suitMonorepo","text":"

Group packages from reg-suit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:reg-suit\" // (1)!\n      ],\n      \"groupName\": \"reg-suit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:reg-suit: reg-suit monorepo
"},{"location":"presets-group/#groupremarkmonorepo","title":"group:remarkMonorepo","text":"

Group packages from remark monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:remark\" // (1)!\n      ],\n      \"groupName\": \"remark monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:remark: remark monorepo
"},{"location":"presets-group/#groupremixmonorepo","title":"group:remixMonorepo","text":"

Group packages from remix monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:remix\" // (1)!\n      ],\n      \"groupName\": \"remix monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:remix: remix monorepo
"},{"location":"presets-group/#groupretrofitmonorepo","title":"group:retrofitMonorepo","text":"

Group packages from retrofit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:retrofit\" // (1)!\n      ],\n      \"groupName\": \"retrofit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:retrofit: retrofit monorepo
"},{"location":"presets-group/#grouprivermonorepo","title":"group:riverMonorepo","text":"

Group packages from river monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:river\" // (1)!\n      ],\n      \"groupName\": \"river monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:river: river monorepo
"},{"location":"presets-group/#grouprjsfmonorepo","title":"group:rjsfMonorepo","text":"

Group packages from rjsf monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:rjsf\" // (1)!\n      ],\n      \"groupName\": \"rjsf monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:rjsf: rjsf monorepo
"},{"location":"presets-group/#grouprouter5monorepo","title":"group:router5Monorepo","text":"

Group packages from router5 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:router5\" // (1)!\n      ],\n      \"groupName\": \"router5 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:router5: router5 monorepo
"},{"location":"presets-group/#grouprspackmonorepo","title":"group:rspackMonorepo","text":"

Group packages from rspack monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:rspack\" // (1)!\n      ],\n      \"groupName\": \"rspack monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:rspack: rspack monorepo
"},{"location":"presets-group/#groupruby-on-railsmonorepo","title":"group:ruby-on-railsMonorepo","text":"

Group packages from ruby-on-rails monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ruby-on-rails\" // (1)!\n      ],\n      \"groupName\": \"ruby-on-rails monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ruby-on-rails: ruby-on-rails monorepo
"},{"location":"presets-group/#grouprust-analyzermonorepo","title":"group:rust-analyzerMonorepo","text":"

Group packages from rust-analyzer monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:rust-analyzer\" // (1)!\n      ],\n      \"groupName\": \"rust-analyzer monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:rust-analyzer: rust-analyzer monorepo
"},{"location":"presets-group/#grouprust-futuresmonorepo","title":"group:rust-futuresMonorepo","text":"

Group packages from rust-futures monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:rust-futures\" // (1)!\n      ],\n      \"groupName\": \"rust-futures monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:rust-futures: rust-futures monorepo
"},{"location":"presets-group/#grouprust-wasm-bindgenmonorepo","title":"group:rust-wasm-bindgenMonorepo","text":"

Group packages from rust-wasm-bindgen monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:rust-wasm-bindgen\" // (1)!\n      ],\n      \"groupName\": \"rust-wasm-bindgen monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:rust-wasm-bindgen: rust-wasm-bindgen monorepo
"},{"location":"presets-group/#groupsanitymonorepo","title":"group:sanityMonorepo","text":"

Group packages from sanity monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sanity\" // (1)!\n      ],\n      \"groupName\": \"sanity monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sanity: sanity monorepo
"},{"location":"presets-group/#groupscaffdogmonorepo","title":"group:scaffdogMonorepo","text":"

Group packages from scaffdog monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:scaffdog\" // (1)!\n      ],\n      \"groupName\": \"scaffdog monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:scaffdog: scaffdog monorepo
"},{"location":"presets-group/#groupscalarmonorepo","title":"group:scalarMonorepo","text":"

Group packages from scalar monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:scalar\" // (1)!\n      ],\n      \"groupName\": \"scalar monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:scalar: scalar monorepo
"},{"location":"presets-group/#groupsea-ormmonorepo","title":"group:sea-ormMonorepo","text":"

Group packages from sea-orm monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sea-orm\" // (1)!\n      ],\n      \"groupName\": \"sea-orm monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sea-orm: sea-orm monorepo
"},{"location":"presets-group/#groupsecretlintmonorepo","title":"group:secretlintMonorepo","text":"

Group packages from secretlint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:secretlint\" // (1)!\n      ],\n      \"groupName\": \"secretlint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:secretlint: secretlint monorepo
"},{"location":"presets-group/#groupsendgrid-nodejsmonorepo","title":"group:sendgrid-nodejsMonorepo","text":"

Group packages from sendgrid-nodejs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sendgrid-nodejs\" // (1)!\n      ],\n      \"groupName\": \"sendgrid-nodejs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sendgrid-nodejs: sendgrid-nodejs monorepo
"},{"location":"presets-group/#groupsentry-dotnetmonorepo","title":"group:sentry-dotnetMonorepo","text":"

Group packages from sentry-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sentry-dotnet\" // (1)!\n      ],\n      \"groupName\": \"sentry-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sentry-dotnet: sentry-dotnet monorepo
"},{"location":"presets-group/#groupsentry-javascriptmonorepo","title":"group:sentry-javascriptMonorepo","text":"

Group packages from sentry-javascript monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sentry-javascript\" // (1)!\n      ],\n      \"groupName\": \"sentry-javascript monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sentry-javascript: sentry-javascript monorepo
"},{"location":"presets-group/#groupsentry-rubymonorepo","title":"group:sentry-rubyMonorepo","text":"

Group packages from sentry-ruby monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sentry-ruby\" // (1)!\n      ],\n      \"groupName\": \"sentry-ruby monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sentry-ruby: sentry-ruby monorepo
"},{"location":"presets-group/#groupsentry-rustmonorepo","title":"group:sentry-rustMonorepo","text":"

Group packages from sentry-rust monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sentry-rust\" // (1)!\n      ],\n      \"groupName\": \"sentry-rust monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sentry-rust: sentry-rust monorepo
"},{"location":"presets-group/#groupserdemonorepo","title":"group:serdeMonorepo","text":"

Group packages from serde monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:serde\" // (1)!\n      ],\n      \"groupName\": \"serde monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:serde: serde monorepo
"},{"location":"presets-group/#groupserenity-jsmonorepo","title":"group:serenity-jsMonorepo","text":"

Group packages from serenity-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:serenity-js\" // (1)!\n      ],\n      \"groupName\": \"serenity-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:serenity-js: serenity-js monorepo
"},{"location":"presets-group/#groupserilog-uimonorepo","title":"group:serilog-uiMonorepo","text":"

Group packages from serilog-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:serilog-ui\" // (1)!\n      ],\n      \"groupName\": \"serilog-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:serilog-ui: serilog-ui monorepo
"},{"location":"presets-group/#groupservicestackmonorepo","title":"group:servicestackMonorepo","text":"

Group packages from servicestack monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:servicestack\" // (1)!\n      ],\n      \"groupName\": \"servicestack monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:servicestack: servicestack monorepo
"},{"location":"presets-group/#groupserwistmonorepo","title":"group:serwistMonorepo","text":"

Group packages from serwist monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:serwist\" // (1)!\n      ],\n      \"groupName\": \"serwist monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:serwist: serwist monorepo
"},{"location":"presets-group/#groupshedlockmonorepo","title":"group:shedlockMonorepo","text":"

Group packages from shedlock monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:shedlock\" // (1)!\n      ],\n      \"groupName\": \"shedlock monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:shedlock: shedlock monorepo
"},{"location":"presets-group/#groupshikimonorepo","title":"group:shikiMonorepo","text":"

Group packages from shiki monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:shiki\" // (1)!\n      ],\n      \"groupName\": \"shiki monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:shiki: shiki monorepo
"},{"location":"presets-group/#groupshopify-app-bridgemonorepo","title":"group:shopify-app-bridgeMonorepo","text":"

Group packages from shopify-app-bridge monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:shopify-app-bridge\" // (1)!\n      ],\n      \"groupName\": \"shopify-app-bridge monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:shopify-app-bridge: shopify-app-bridge monorepo
"},{"location":"presets-group/#groupsitecore-jssmonorepo","title":"group:sitecore-jssMonorepo","text":"

Group packages from sitecore-jss monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:sitecore-jss\" // (1)!\n      ],\n      \"groupName\": \"sitecore-jss monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:sitecore-jss: sitecore-jss monorepo
"},{"location":"presets-group/#groupsize-limitmonorepo","title":"group:size-limitMonorepo","text":"

Group packages from size-limit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:size-limit\" // (1)!\n      ],\n      \"groupName\": \"size-limit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:size-limit: size-limit monorepo
"},{"location":"presets-group/#groupskiasharpmonorepo","title":"group:skiasharpMonorepo","text":"

Group packages from skiasharp monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:skiasharp\" // (1)!\n      ],\n      \"groupName\": \"skiasharp monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:skiasharp: skiasharp monorepo
"},{"location":"presets-group/#groupslack-netmonorepo","title":"group:slack-netMonorepo","text":"

Group packages from slack-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:slack-net\" // (1)!\n      ],\n      \"groupName\": \"slack-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:slack-net: slack-net monorepo
"},{"location":"presets-group/#groupslf4jmonorepo","title":"group:slf4jMonorepo","text":"

Group packages from slf4j monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:slf4j\" // (1)!\n      ],\n      \"groupName\": \"slf4j monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:slf4j: slf4j monorepo
"},{"location":"presets-group/#groupslim-message-busmonorepo","title":"group:slim-message-busMonorepo","text":"

Group packages from slim-message-bus monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:slim-message-bus\" // (1)!\n      ],\n      \"groupName\": \"slim-message-bus monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:slim-message-bus: slim-message-bus monorepo
"},{"location":"presets-group/#groupspectre-consolemonorepo","title":"group:spectre-consoleMonorepo","text":"

Group packages from spectre-console monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:spectre-console\" // (1)!\n      ],\n      \"groupName\": \"spectre-console monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:spectre-console: spectre-console monorepo
"},{"location":"presets-group/#groupspectre-console-climonorepo","title":"group:spectre-console-cliMonorepo","text":"

Group packages from spectre-console-cli monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:spectre-console-cli\" // (1)!\n      ],\n      \"groupName\": \"spectre-console-cli monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:spectre-console-cli: spectre-console-cli monorepo
"},{"location":"presets-group/#groupspringfoxmonorepo","title":"group:springfoxMonorepo","text":"

Group packages from springfox monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:springfox\" // (1)!\n      ],\n      \"groupName\": \"springfox monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:springfox: springfox monorepo
"},{"location":"presets-group/#groupstack-exchange-redis-extensionsmonorepo","title":"group:stack-exchange-redis-extensionsMonorepo","text":"

Group packages from stack-exchange-redis-extensions monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:stack-exchange-redis-extensions\" // (1)!\n      ],\n      \"groupName\": \"stack-exchange-redis-extensions monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:stack-exchange-redis-extensions: stack-exchange-redis-extensions monorepo
"},{"location":"presets-group/#groupstatsig-js-clientmonorepo","title":"group:statsig-js-clientMonorepo","text":"

Group packages from statsig-js-client monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:statsig-js-client\" // (1)!\n      ],\n      \"groupName\": \"statsig-js-client monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:statsig-js-client: statsig-js-client monorepo
"},{"location":"presets-group/#groupsteeltoemonorepo","title":"group:steeltoeMonorepo","text":"

Group packages from steeltoe monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:steeltoe\" // (1)!\n      ],\n      \"groupName\": \"steeltoe monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:steeltoe: steeltoe monorepo
"},{"location":"presets-group/#groupstorybookmonorepo","title":"group:storybookMonorepo","text":"

Group packages from storybook monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:storybook\" // (1)!\n      ],\n      \"groupName\": \"storybook monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:storybook: storybook monorepo
"},{"location":"presets-group/#groupstorybook-react-nativemonorepo","title":"group:storybook-react-nativeMonorepo","text":"

Group packages from storybook-react-native monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:storybook-react-native\" // (1)!\n      ],\n      \"groupName\": \"storybook-react-native monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:storybook-react-native: storybook-react-native monorepo
"},{"location":"presets-group/#groupstrapimonorepo","title":"group:strapiMonorepo","text":"

Group packages from strapi monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:strapi\" // (1)!\n      ],\n      \"groupName\": \"strapi monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:strapi: strapi monorepo
"},{"location":"presets-group/#groupstrummonorepo","title":"group:strumMonorepo","text":"

Group packages from strum monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:strum\" // (1)!\n      ],\n      \"groupName\": \"strum monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:strum: strum monorepo
"},{"location":"presets-group/#groupstryker-jsmonorepo","title":"group:stryker-jsMonorepo","text":"

Group packages from stryker-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:stryker-js\" // (1)!\n      ],\n      \"groupName\": \"stryker-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:stryker-js: stryker-js monorepo
"},{"location":"presets-group/#groupstylex-swcmonorepo","title":"group:stylex-swcMonorepo","text":"

Group packages from stylex-swc monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:stylex-swc\" // (1)!\n      ],\n      \"groupName\": \"stylex-swc monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:stylex-swc: stylex-swc monorepo
"},{"location":"presets-group/#groupsurveyjsmonorepo","title":"group:surveyjsMonorepo","text":"

Group packages from surveyjs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:surveyjs\" // (1)!\n      ],\n      \"groupName\": \"surveyjs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:surveyjs: surveyjs monorepo
"},{"location":"presets-group/#groupswashbuckle-aspnetcoremonorepo","title":"group:swashbuckle-aspnetcoreMonorepo","text":"

Group packages from swashbuckle-aspnetcore monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:swashbuckle-aspnetcore\" // (1)!\n      ],\n      \"groupName\": \"swashbuckle-aspnetcore monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:swashbuckle-aspnetcore: swashbuckle-aspnetcore monorepo
"},{"location":"presets-group/#groupsystemioabstractionsmonorepo","title":"group:system.io.abstractionsMonorepo","text":"

Group packages from system.io.abstractions monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:system.io.abstractions\" // (1)!\n      ],\n      \"groupName\": \"system.io.abstractions monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:system.io.abstractions: system.io.abstractions monorepo
"},{"location":"presets-group/#grouptaiga-uimonorepo","title":"group:taiga-uiMonorepo","text":"

Group packages from taiga-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:taiga-ui\" // (1)!\n      ],\n      \"groupName\": \"taiga-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:taiga-ui: taiga-ui monorepo
"},{"location":"presets-group/#grouptailwindcssmonorepo","title":"group:tailwindcssMonorepo","text":"

Group packages from tailwindcss monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tailwindcss\" // (1)!\n      ],\n      \"groupName\": \"tailwindcss monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tailwindcss: tailwindcss monorepo
"},{"location":"presets-group/#grouptamaguimonorepo","title":"group:tamaguiMonorepo","text":"

Group packages from tamagui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tamagui\" // (1)!\n      ],\n      \"groupName\": \"tamagui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tamagui: tamagui monorepo
"},{"location":"presets-group/#grouptanstack-formmonorepo","title":"group:tanstack-formMonorepo","text":"

Group packages from tanstack-form monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tanstack-form\" // (1)!\n      ],\n      \"groupName\": \"tanstack-form monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tanstack-form: tanstack-form monorepo
"},{"location":"presets-group/#grouptanstack-querymonorepo","title":"group:tanstack-queryMonorepo","text":"

Group packages from tanstack-query monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tanstack-query\" // (1)!\n      ],\n      \"groupName\": \"tanstack-query monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tanstack-query: tanstack-query monorepo
"},{"location":"presets-group/#grouptanstack-routermonorepo","title":"group:tanstack-routerMonorepo","text":"

Group packages from tanstack-router monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tanstack-router\" // (1)!\n      ],\n      \"groupName\": \"tanstack-router monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tanstack-router: tanstack-router monorepo
"},{"location":"presets-group/#grouptanstack-tablemonorepo","title":"group:tanstack-tableMonorepo","text":"

Group packages from tanstack-table monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tanstack-table\" // (1)!\n      ],\n      \"groupName\": \"tanstack-table monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tanstack-table: tanstack-table monorepo
"},{"location":"presets-group/#grouptanstack-virtualmonorepo","title":"group:tanstack-virtualMonorepo","text":"

Group packages from tanstack-virtual monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tanstack-virtual\" // (1)!\n      ],\n      \"groupName\": \"tanstack-virtual monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tanstack-virtual: tanstack-virtual monorepo
"},{"location":"presets-group/#grouptaurimonorepo","title":"group:tauriMonorepo","text":"

Group packages from tauri monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tauri\" // (1)!\n      ],\n      \"groupName\": \"tauri monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tauri: tauri monorepo
"},{"location":"presets-group/#grouptelus-tdsmonorepo","title":"group:telus-tdsMonorepo","text":"

Group packages from telus-tds monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:telus-tds\" // (1)!\n      ],\n      \"groupName\": \"telus-tds monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:telus-tds: telus-tds monorepo
"},{"location":"presets-group/#grouptelus-tds-coremonorepo","title":"group:telus-tds-coreMonorepo","text":"

Group packages from telus-tds-core monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:telus-tds-core\" // (1)!\n      ],\n      \"groupName\": \"telus-tds-core monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:telus-tds-core: telus-tds-core monorepo
"},{"location":"presets-group/#grouptemporalio-tsmonorepo","title":"group:temporalio-tsMonorepo","text":"

Group packages from temporalio-ts monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:temporalio-ts\" // (1)!\n      ],\n      \"groupName\": \"temporalio-ts monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:temporalio-ts: temporalio-ts monorepo
"},{"location":"presets-group/#groupterraformmonorepo","title":"group:terraformMonorepo","text":"

Group packages from terraform monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:terraform\" // (1)!\n      ],\n      \"groupName\": \"terraform monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:terraform: terraform monorepo
"},{"location":"presets-group/#grouptestcontainers-dotnetmonorepo","title":"group:testcontainers-dotnetMonorepo","text":"

Group packages from testcontainers-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:testcontainers-dotnet\" // (1)!\n      ],\n      \"groupName\": \"testcontainers-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:testcontainers-dotnet: testcontainers-dotnet monorepo
"},{"location":"presets-group/#grouptestcontainers-gomonorepo","title":"group:testcontainers-goMonorepo","text":"

Group packages from testcontainers-go monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:testcontainers-go\" // (1)!\n      ],\n      \"groupName\": \"testcontainers-go monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:testcontainers-go: testcontainers-go monorepo
"},{"location":"presets-group/#grouptestcontainers-javamonorepo","title":"group:testcontainers-javaMonorepo","text":"

Group packages from testcontainers-java monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:testcontainers-java\" // (1)!\n      ],\n      \"groupName\": \"testcontainers-java monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:testcontainers-java: testcontainers-java monorepo
"},{"location":"presets-group/#grouptestcontainers-nodemonorepo","title":"group:testcontainers-nodeMonorepo","text":"

Group packages from testcontainers-node monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:testcontainers-node\" // (1)!\n      ],\n      \"groupName\": \"testcontainers-node monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:testcontainers-node: testcontainers-node monorepo
"},{"location":"presets-group/#grouptheme-uimonorepo","title":"group:theme-uiMonorepo","text":"

Group packages from theme-ui monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:theme-ui\" // (1)!\n      ],\n      \"groupName\": \"theme-ui monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:theme-ui: theme-ui monorepo
"},{"location":"presets-group/#grouptikamonorepo","title":"group:tikaMonorepo","text":"

Group packages from tika monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tika\" // (1)!\n      ],\n      \"groupName\": \"tika monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tika: tika monorepo
"},{"location":"presets-group/#grouptimvirmonorepo","title":"group:timvirMonorepo","text":"

Group packages from timvir monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:timvir\" // (1)!\n      ],\n      \"groupName\": \"timvir monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:timvir: timvir monorepo
"},{"location":"presets-group/#grouptiptapmonorepo","title":"group:tiptapMonorepo","text":"

Group packages from tiptap monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tiptap\" // (1)!\n      ],\n      \"groupName\": \"tiptap monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tiptap: tiptap monorepo
"},{"location":"presets-group/#grouptokio-prostmonorepo","title":"group:tokio-prostMonorepo","text":"

Group packages from tokio-prost monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tokio-prost\" // (1)!\n      ],\n      \"groupName\": \"tokio-prost monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tokio-prost: tokio-prost monorepo
"},{"location":"presets-group/#grouptokio-tracingmonorepo","title":"group:tokio-tracingMonorepo","text":"

Group packages from tokio-tracing monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tokio-tracing\" // (1)!\n      ],\n      \"groupName\": \"tokio-tracing monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tokio-tracing: tokio-tracing monorepo
"},{"location":"presets-group/#grouptomcatmonorepo","title":"group:tomcatMonorepo","text":"

Group packages from tomcat monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tomcat\" // (1)!\n      ],\n      \"groupName\": \"tomcat monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tomcat: tomcat monorepo
"},{"location":"presets-group/#grouptonicmonorepo","title":"group:tonicMonorepo","text":"

Group packages from tonic monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tonic\" // (1)!\n      ],\n      \"groupName\": \"tonic monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tonic: tonic monorepo
"},{"location":"presets-group/#grouptreatmonorepo","title":"group:treatMonorepo","text":"

Group packages from treat monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:treat\" // (1)!\n      ],\n      \"groupName\": \"treat monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:treat: treat monorepo
"},{"location":"presets-group/#grouptrpcmonorepo","title":"group:trpcMonorepo","text":"

Group packages from trpc monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:trpc\" // (1)!\n      ],\n      \"groupName\": \"trpc monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:trpc: trpc monorepo
"},{"location":"presets-group/#grouptrust-dnsmonorepo","title":"group:trust-dnsMonorepo","text":"

Group packages from trust-dns monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:trust-dns\" // (1)!\n      ],\n      \"groupName\": \"trust-dns monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:trust-dns: trust-dns monorepo
"},{"location":"presets-group/#grouptsoamonorepo","title":"group:tsoaMonorepo","text":"

Group packages from tsoa monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tsoa\" // (1)!\n      ],\n      \"groupName\": \"tsoa monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tsoa: tsoa monorepo
"},{"location":"presets-group/#grouptunitmonorepo","title":"group:tunitMonorepo","text":"

Group packages from tunit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:tunit\" // (1)!\n      ],\n      \"groupName\": \"tunit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:tunit: tunit monorepo
"},{"location":"presets-group/#groupturbomonorepo","title":"group:turboMonorepo","text":"

Group packages from turbo monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:turbo\" // (1)!\n      ],\n      \"groupName\": \"turbo monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:turbo: turbo monorepo
"},{"location":"presets-group/#groupturfmonorepo","title":"group:turfMonorepo","text":"

Group packages from turf monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:turf\" // (1)!\n      ],\n      \"groupName\": \"turf monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:turf: turf monorepo
"},{"location":"presets-group/#grouptyped-signalrmonorepo","title":"group:typed-signalrMonorepo","text":"

Group packages from typed-signalr monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:typed-signalr\" // (1)!\n      ],\n      \"groupName\": \"typed-signalr monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:typed-signalr: typed-signalr monorepo
"},{"location":"presets-group/#grouptypefacesmonorepo","title":"group:typefacesMonorepo","text":"

Group packages from typefaces monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:typefaces\" // (1)!\n      ],\n      \"groupName\": \"typefaces monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:typefaces: typefaces monorepo
"},{"location":"presets-group/#grouptypescript-eslintmonorepo","title":"group:typescript-eslintMonorepo","text":"

Group packages from typescript-eslint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:typescript-eslint\" // (1)!\n      ],\n      \"groupName\": \"typescript-eslint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:typescript-eslint: typescript-eslint monorepo
"},{"location":"presets-group/#grouptypography-jsmonorepo","title":"group:typography-jsMonorepo","text":"

Group packages from typography-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:typography-js\" // (1)!\n      ],\n      \"groupName\": \"typography-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:typography-js: typography-js monorepo
"},{"location":"presets-group/#groupui5-webcomponentsmonorepo","title":"group:ui5-webcomponentsMonorepo","text":"

Group packages from ui5-webcomponents monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ui5-webcomponents\" // (1)!\n      ],\n      \"groupName\": \"ui5-webcomponents monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ui5-webcomponents: ui5-webcomponents monorepo
"},{"location":"presets-group/#groupunheadmonorepo","title":"group:unheadMonorepo","text":"

Group packages from unhead monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:unhead\" // (1)!\n      ],\n      \"groupName\": \"unhead monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:unhead: unhead monorepo
"},{"location":"presets-group/#groupunocssmonorepo","title":"group:unocssMonorepo","text":"

Group packages from unocss monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:unocss\" // (1)!\n      ],\n      \"groupName\": \"unocss monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:unocss: unocss monorepo
"},{"location":"presets-group/#groupuppymonorepo","title":"group:uppyMonorepo","text":"

Group packages from uppy monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:uppy\" // (1)!\n      ],\n      \"groupName\": \"uppy monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:uppy: uppy monorepo
"},{"location":"presets-group/#grouputoipamonorepo","title":"group:utoipaMonorepo","text":"

Group packages from utoipa monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:utoipa\" // (1)!\n      ],\n      \"groupName\": \"utoipa monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:utoipa: utoipa monorepo
"},{"location":"presets-group/#groupvaadin-hillamonorepo","title":"group:vaadin-hillaMonorepo","text":"

Group packages from vaadin-hilla monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vaadin-hilla\" // (1)!\n      ],\n      \"groupName\": \"vaadin-hilla monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vaadin-hilla: vaadin-hilla monorepo
"},{"location":"presets-group/#groupvaadinwebcomponentsmonorepo","title":"group:vaadinWebComponentsMonorepo","text":"

Group packages from vaadinWebComponents monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vaadinWebComponents\" // (1)!\n      ],\n      \"groupName\": \"vaadinWebComponents monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vaadinWebComponents: vaadinWebComponents monorepo
"},{"location":"presets-group/#groupvanilla-extractmonorepo","title":"group:vanilla-extractMonorepo","text":"

Group packages from vanilla-extract monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vanilla-extract\" // (1)!\n      ],\n      \"groupName\": \"vanilla-extract monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vanilla-extract: vanilla-extract monorepo
"},{"location":"presets-group/#groupvisxmonorepo","title":"group:visxMonorepo","text":"

Group packages from visx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:visx\" // (1)!\n      ],\n      \"groupName\": \"visx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:visx: visx monorepo
"},{"location":"presets-group/#groupvite-plusmonorepo","title":"group:vite-plusMonorepo","text":"

Group packages from vite-plus monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vite-plus\" // (1)!\n      ],\n      \"groupName\": \"vite-plus monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vite-plus: vite-plus monorepo
"},{"location":"presets-group/#groupvitestmonorepo","title":"group:vitestMonorepo","text":"

Group packages from vitest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vitest\" // (1)!\n      ],\n      \"groupName\": \"vitest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vitest: vitest monorepo
"},{"location":"presets-group/#groupvstestmonorepo","title":"group:vstestMonorepo","text":"

Group packages from vstest monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vstest\" // (1)!\n      ],\n      \"groupName\": \"vstest monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vstest: vstest monorepo
"},{"location":"presets-group/#groupvuemonorepo","title":"group:vueMonorepo","text":"

Group packages from vue monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vue\" // (1)!\n      ],\n      \"groupName\": \"vue monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vue: vue monorepo
"},{"location":"presets-group/#groupvue-climonorepo","title":"group:vue-cliMonorepo","text":"

Group packages from vue-cli monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vue-cli\" // (1)!\n      ],\n      \"groupName\": \"vue-cli monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vue-cli: vue-cli monorepo
"},{"location":"presets-group/#groupvue-language-toolsmonorepo","title":"group:vue-language-toolsMonorepo","text":"

Group packages from vue-language-tools monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vue-language-tools\" // (1)!\n      ],\n      \"groupName\": \"vue-language-tools monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vue-language-tools: vue-language-tools monorepo
"},{"location":"presets-group/#groupvuepressmonorepo","title":"group:vuepressMonorepo","text":"

Group packages from vuepress monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vuepress\" // (1)!\n      ],\n      \"groupName\": \"vuepress monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vuepress: vuepress monorepo
"},{"location":"presets-group/#groupvueusemonorepo","title":"group:vueuseMonorepo","text":"

Group packages from vueuse monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:vueuse\" // (1)!\n      ],\n      \"groupName\": \"vueuse monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:vueuse: vueuse monorepo
"},{"location":"presets-group/#groupweaselmonorepo","title":"group:weaselMonorepo","text":"

Group packages from weasel monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:weasel\" // (1)!\n      ],\n      \"groupName\": \"weasel monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:weasel: weasel monorepo
"},{"location":"presets-group/#groupweb3-reactmonorepo","title":"group:web3-reactMonorepo","text":"

Group packages from web3-react monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:web3-react\" // (1)!\n      ],\n      \"groupName\": \"web3-react monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:web3-react: web3-react monorepo
"},{"location":"presets-group/#groupwebdriveriomonorepo","title":"group:webdriverioMonorepo","text":"

Group packages from webdriverio monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:webdriverio\" // (1)!\n      ],\n      \"groupName\": \"webdriverio monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:webdriverio: webdriverio monorepo
"},{"location":"presets-group/#groupwolverinemonorepo","title":"group:wolverineMonorepo","text":"

Group packages from wolverine monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:wolverine\" // (1)!\n      ],\n      \"groupName\": \"wolverine monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:wolverine: wolverine monorepo
"},{"location":"presets-group/#groupworkboxmonorepo","title":"group:workboxMonorepo","text":"

Group packages from workbox monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:workbox\" // (1)!\n      ],\n      \"groupName\": \"workbox monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:workbox: workbox monorepo
"},{"location":"presets-group/#groupwyw-in-jsmonorepo","title":"group:wyw-in-jsMonorepo","text":"

Group packages from wyw-in-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:wyw-in-js\" // (1)!\n      ],\n      \"groupName\": \"wyw-in-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:wyw-in-js: wyw-in-js monorepo
"},{"location":"presets-group/#groupxstatemonorepo","title":"group:xstateMonorepo","text":"

Group packages from xstate monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:xstate\" // (1)!\n      ],\n      \"groupName\": \"xstate monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:xstate: xstate monorepo
"},{"location":"presets-group/#groupxtermmonorepo","title":"group:xtermMonorepo","text":"

Group packages from xterm monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:xterm\" // (1)!\n      ],\n      \"groupName\": \"xterm monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:xterm: xterm monorepo
"},{"location":"presets-group/#groupxunit-dotnetmonorepo","title":"group:xunit-dotnetMonorepo","text":"

Group packages from xunit-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:xunit-dotnet\" // (1)!\n      ],\n      \"groupName\": \"xunit-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:xunit-dotnet: xunit-dotnet monorepo
"},{"location":"presets-group/#groupyamldotnetmonorepo","title":"group:yamldotnetMonorepo","text":"

Group packages from yamldotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:yamldotnet\" // (1)!\n      ],\n      \"groupName\": \"yamldotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:yamldotnet: yamldotnet monorepo
"},{"location":"presets-group/#groupyarnmonorepo","title":"group:yarnMonorepo","text":"

Group packages from yarn monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:yarn\" // (1)!\n      ],\n      \"groupName\": \"yarn monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:yarn: yarn monorepo
"},{"location":"presets-group/#groupzag-jsmonorepo","title":"group:zag-jsMonorepo","text":"

Group packages from zag-js monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:zag-js\" // (1)!\n      ],\n      \"groupName\": \"zag-js monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:zag-js: zag-js monorepo
"},{"location":"presets-group/#groupzxcvbn-tsmonorepo","title":"group:zxcvbn-tsMonorepo","text":"

Group packages from zxcvbn-ts monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:zxcvbn-ts\" // (1)!\n      ],\n      \"groupName\": \"zxcvbn-ts monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:zxcvbn-ts: zxcvbn-ts monorepo
"},{"location":"presets-group/#groupzxing-netmonorepo","title":"group:zxing-netMonorepo","text":"

Group packages from zxing-net monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:zxing-net\" // (1)!\n      ],\n      \"groupName\": \"zxing-net monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:zxing-net: zxing-net monorepo
"},{"location":"presets-group/#grouphapijsmonorepo","title":"group:hapijsMonorepo","text":"

Group packages from hapijs monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:hapijs\" // (1)!\n      ],\n      \"groupName\": \"hapijs monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:hapijs: hapijs monorepo
"},{"location":"presets-group/#grouplodashmonorepo","title":"group:lodashMonorepo","text":"

Group packages from lodash monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:lodash\" // (1)!\n      ],\n      \"groupName\": \"lodash monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:lodash: lodash monorepo
"},{"location":"presets-group/#groupngrxmonorepo","title":"group:ngrxMonorepo","text":"

Group packages from ngrx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:ngrx\" // (1)!\n      ],\n      \"groupName\": \"ngrx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:ngrx: ngrx monorepo
"},{"location":"presets-group/#groupnxmonorepo","title":"group:nxMonorepo","text":"

Group packages from nx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:nx\" // (1)!\n      ],\n      \"groupName\": \"nx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:nx: nx monorepo
"},{"location":"presets-group/#groupoctokitmonorepo","title":"group:octokitMonorepo","text":"

Group packages from octokit monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:octokit\" // (1)!\n      ],\n      \"groupName\": \"octokit monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:octokit: octokit monorepo
"},{"location":"presets-group/#groupphp-enqueuemonorepo","title":"group:php-enqueueMonorepo","text":"

Group packages from php-enqueue monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:php-enqueue\" // (1)!\n      ],\n      \"groupName\": \"php-enqueue monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:php-enqueue: php-enqueue monorepo
"},{"location":"presets-group/#groupsemantic-releasemonorepo","title":"group:semantic-releaseMonorepo","text":"

Group packages from semantic-release monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:semantic-release\" // (1)!\n      ],\n      \"groupName\": \"semantic-release monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:semantic-release: semantic-release monorepo
"},{"location":"presets-group/#groupswcmonorepo","title":"group:swcMonorepo","text":"

Group packages from swc monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:swc\" // (1)!\n      ],\n      \"groupName\": \"swc monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:swc: swc monorepo
"},{"location":"presets-group/#grouptwigmonorepo","title":"group:twigMonorepo","text":"

Group packages from twig monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:twig\" // (1)!\n      ],\n      \"groupName\": \"twig monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:twig: twig monorepo
"},{"location":"presets-group/#groupangularmaterialmonorepo","title":"group:angularmaterialMonorepo","text":"

Group packages from angularmaterial monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:angularmaterial\" // (1)!\n      ],\n      \"groupName\": \"angularmaterial monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:angularmaterial: angularmaterial monorepo
"},{"location":"presets-group/#groupapache-camelmonorepo","title":"group:apache-camelMonorepo","text":"

Group packages from apache-camel monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:apache-camel\" // (1)!\n      ],\n      \"groupName\": \"apache-camel monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:apache-camel: apache-camel monorepo
"},{"location":"presets-group/#groupapache-poimonorepo","title":"group:apache-poiMonorepo","text":"

Group packages from apache-poi monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:apache-poi\" // (1)!\n      ],\n      \"groupName\": \"apache-poi monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:apache-poi: apache-poi monorepo
"},{"location":"presets-group/#groupaws-java-sdkmonorepo","title":"group:aws-java-sdkMonorepo","text":"

Group packages from aws-java-sdk monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-java-sdk\" // (1)!\n      ],\n      \"groupName\": \"aws-java-sdk monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-java-sdk: aws-java-sdk monorepo
"},{"location":"presets-group/#groupaws-java-sdk-v2monorepo","title":"group:aws-java-sdk-v2Monorepo","text":"

Group packages from aws-java-sdk-v2 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:aws-java-sdk-v2\" // (1)!\n      ],\n      \"groupName\": \"aws-java-sdk-v2 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:aws-java-sdk-v2: aws-java-sdk-v2 monorepo
"},{"location":"presets-group/#groupaxis2monorepo","title":"group:axis2Monorepo","text":"

Group packages from axis2 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:axis2\" // (1)!\n      ],\n      \"groupName\": \"axis2 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:axis2: axis2 monorepo
"},{"location":"presets-group/#groupbabel6monorepo","title":"group:babel6Monorepo","text":"

Group packages from babel6 monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:babel6\" // (1)!\n      ],\n      \"groupName\": \"babel6 monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:babel6: babel6 monorepo
"},{"location":"presets-group/#groupembroidermonorepo","title":"group:embroiderMonorepo","text":"

Group packages from embroider monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:embroider\" // (1)!\n      ],\n      \"groupName\": \"embroider monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:embroider: embroider monorepo
"},{"location":"presets-group/#groupforgemonorepo","title":"group:forgeMonorepo","text":"

Group packages from forge monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:forge\" // (1)!\n      ],\n      \"groupName\": \"forge monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:forge: forge monorepo
"},{"location":"presets-group/#groupfullcalendarmonorepo","title":"group:fullcalendarMonorepo","text":"

Group packages from fullcalendar monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:fullcalendar\" // (1)!\n      ],\n      \"groupName\": \"fullcalendar monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:fullcalendar: fullcalendar monorepo
"},{"location":"presets-group/#grouporacle-databasemonorepo","title":"group:oracle-databaseMonorepo","text":"

Group packages from oracle-database monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:oracle-database\" // (1)!\n      ],\n      \"groupName\": \"oracle-database monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:oracle-database: oracle-database monorepo
"},{"location":"presets-group/#groupoxlintmonorepo","title":"group:oxlintMonorepo","text":"

Group packages from oxlint monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:oxlint\" // (1)!\n      ],\n      \"groupName\": \"oxlint monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:oxlint: oxlint monorepo
"},{"location":"presets-group/#groupprometheus-simpleclientmonorepo","title":"group:prometheus-simpleclientMonorepo","text":"

Group packages from prometheus-simpleclient monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:prometheus-simpleclient\" // (1)!\n      ],\n      \"groupName\": \"prometheus-simpleclient monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:prometheus-simpleclient: prometheus-simpleclient monorepo
"},{"location":"presets-group/#grouprusshmonorepo","title":"group:russhMonorepo","text":"

Group packages from russh monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:russh\" // (1)!\n      ],\n      \"groupName\": \"russh monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:russh: russh monorepo
"},{"location":"presets-group/#groupsolidmonorepo","title":"group:solidMonorepo","text":"

Group packages from solid monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:solid\" // (1)!\n      ],\n      \"groupName\": \"solid monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:solid: solid monorepo
"},{"location":"presets-group/#groupspfxmonorepo","title":"group:spfxMonorepo","text":"

Group packages from spfx monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:spfx\" // (1)!\n      ],\n      \"groupName\": \"spfx monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:spfx: spfx monorepo
"},{"location":"presets-group/#groupspockmonorepo","title":"group:spockMonorepo","text":"

Group packages from spock monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:spock\" // (1)!\n      ],\n      \"groupName\": \"spock monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:spock: spock monorepo
"},{"location":"presets-group/#groupsyncfusion-dotnetmonorepo","title":"group:syncfusion-dotnetMonorepo","text":"

Group packages from syncfusion-dotnet monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:syncfusion-dotnet\" // (1)!\n      ],\n      \"groupName\": \"syncfusion-dotnet monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:syncfusion-dotnet: syncfusion-dotnet monorepo
"},{"location":"presets-group/#grouptesting-librarymonorepo","title":"group:testing-libraryMonorepo","text":"

Group packages from testing-library monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:testing-library\" // (1)!\n      ],\n      \"groupName\": \"testing-library monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:testing-library: testing-library monorepo
"},{"location":"presets-group/#groupwordpressmonorepo","title":"group:wordpressMonorepo","text":"

Group packages from wordpress monorepo together.

{\n  \"packageRules\": [\n    {\n      \"extends\": [\n        \"monorepo:wordpress\" // (1)!\n      ],\n      \"groupName\": \"wordpress monorepo\",\n      \"matchUpdateTypes\": [\n        \"digest\",\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ]\n    }\n  ]\n}\n
  1. monorepo:wordpress: wordpress monorepo
"},{"location":"presets-group/#groupmonorepos","title":"group:monorepos","text":"

Group known monorepo packages together.

{\n  \"extends\": [\n    \"group:accountsMonorepo\", // (1)!\n    \"group:acotMonorepo\", // (2)!\n    \"group:ag-gridMonorepo\", // (3)!\n    \"group:algolia-instantsearchMonorepo\", // (4)!\n    \"group:algolia-react-instantsearchMonorepo\", // (5)!\n    \"group:algoliasearch-autocompleteMonorepo\", // (6)!\n    \"group:algoliasearch-client-javascriptMonorepo\", // (7)!\n    \"group:analogMonorepo\", // (8)!\n    \"group:angularMonorepo\", // (9)!\n    \"group:angular-cliMonorepo\", // (10)!\n    \"group:angular-eslintMonorepo\", // (11)!\n    \"group:angularfireMonorepo\", // (12)!\n    \"group:angularjsMonorepo\", // (13)!\n    \"group:apache-luceneMonorepo\", // (14)!\n    \"group:apollo-serverMonorepo\", // (15)!\n    \"group:apolloclientMonorepo\", // (16)!\n    \"group:appiumMonorepo\", // (17)!\n    \"group:applicationinsights-dotnetMonorepo\", // (18)!\n    \"group:arcus.background-jobsMonorepo\", // (19)!\n    \"group:arcus.event-gridMonorepo\", // (20)!\n    \"group:arcus.messagingMonorepo\", // (21)!\n    \"group:arcus.observabilityMonorepo\", // (22)!\n    \"group:arcus.securityMonorepo\", // (23)!\n    \"group:arcus.webapiMonorepo\", // (24)!\n    \"group:arrow-ktMonorepo\", // (25)!\n    \"group:arrow-rsMonorepo\", // (26)!\n    \"group:aspireMonorepo\", // (27)!\n    \"group:aspnet aspnetwebstackMonorepo\", // (28)!\n    \"group:aspnet extensionsMonorepo\", // (29)!\n    \"group:aspnet-api-versioningMonorepo\", // (30)!\n    \"group:aspnet-health-checksMonorepo\", // (31)!\n    \"group:aspnet-security-oauth-providersMonorepo\", // (32)!\n    \"group:astroMonorepo\", // (33)!\n    \"group:autoMonorepo\", // (34)!\n    \"group:autofixtureMonorepo\", // (35)!\n    \"group:automapper-dotnetMonorepo\", // (36)!\n    \"group:avaloniaMonorepo\", // (37)!\n    \"group:aws-cdkMonorepo\", // (38)!\n    \"group:aws-lambda-dotnetMonorepo\", // (39)!\n    \"group:aws-lambda-powertools-typescriptMonorepo\", // (40)!\n    \"group:aws-sdk-client-mockMonorepo\", // (41)!\n    \"group:aws-sdk-goMonorepo\", // (42)!\n    \"group:aws-sdk-go-v2Monorepo\", // (43)!\n    \"group:aws-sdk-js-v3Monorepo\", // (44)!\n    \"group:aws-sdk-netMonorepo\", // (45)!\n    \"group:aws-sdk-rustMonorepo\", // (46)!\n    \"group:awsappsyncMonorepo\", // (47)!\n    \"group:axumMonorepo\", // (48)!\n    \"group:azure azure-libraries-for-netMonorepo\", // (49)!\n    \"group:azure azure-sdk-for-netMonorepo\", // (50)!\n    \"group:azure azure-storage-netMonorepo\", // (51)!\n    \"group:azure-ad-microsoft-authentication-library-for-androidMonorepo\", // (52)!\n    \"group:azure-ad-microsoft-authentication-library-for-dotnetMonorepo\", // (53)!\n    \"group:azure-ad-microsoft-authentication-library-for-goMonorepo\", // (54)!\n    \"group:azure-ad-microsoft-authentication-library-for-javaMonorepo\", // (55)!\n    \"group:azure-ad-microsoft-authentication-library-for-jsMonorepo\", // (56)!\n    \"group:azure-ad-microsoft-authentication-library-for-objcMonorepo\", // (57)!\n    \"group:azure-ad-microsoft-authentication-library-for-pythonMonorepo\", // (58)!\n    \"group:azure-functions-dotnet-workerMonorepo\", // (59)!\n    \"group:azure-sdk-for-androidMonorepo\", // (60)!\n    \"group:azure-sdk-for-cMonorepo\", // (61)!\n    \"group:azure-sdk-for-cppMonorepo\", // (62)!\n    \"group:azure-sdk-for-goMonorepo\", // (63)!\n    \"group:azure-sdk-for-iosMonorepo\", // (64)!\n    \"group:azure-sdk-for-javaMonorepo\", // (65)!\n    \"group:azure-sdk-for-jsMonorepo\", // (66)!\n    \"group:azure-sdk-for-pythonMonorepo\", // (67)!\n    \"group:azure-sdk-for-rustMonorepo\", // (68)!\n    \"group:babelMonorepo\", // (69)!\n    \"group:backstageMonorepo\", // (70)!\n    \"group:basetMonorepo\", // (71)!\n    \"group:better-authMonorepo\", // (72)!\n    \"group:braveMonorepo\", // (73)!\n    \"group:bugsnag-jsMonorepo\", // (74)!\n    \"group:bull-boardMonorepo\", // (75)!\n    \"group:cakeMonorepo\", // (76)!\n    \"group:cake-issuesMonorepo\", // (77)!\n    \"group:capacitorMonorepo\", // (78)!\n    \"group:cedarMonorepo\", // (79)!\n    \"group:chakra-uiMonorepo\", // (80)!\n    \"group:chromelyMonorepo\", // (81)!\n    \"group:citation-jsMonorepo\", // (82)!\n    \"group:ckeditorMonorepo\", // (83)!\n    \"group:clarityMonorepo\", // (84)!\n    \"group:clearscriptMonorepo\", // (85)!\n    \"group:commitlintMonorepo\", // (86)!\n    \"group:confectMonorepo\", // (87)!\n    \"group:conformMonorepo\", // (88)!\n    \"group:contentful-rich-textMonorepo\", // (89)!\n    \"group:convexMonorepo\", // (90)!\n    \"group:cspellMonorepo\", // (91)!\n    \"group:datadog-browser-sdkMonorepo\", // (92)!\n    \"group:datafusionMonorepo\", // (93)!\n    \"group:datatables-netMonorepo\", // (94)!\n    \"group:datatables-net-autofillMonorepo\", // (95)!\n    \"group:datatables-net-buttonsMonorepo\", // (96)!\n    \"group:datatables-net-colreorderMonorepo\", // (97)!\n    \"group:datatables-net-fixedcolumnsMonorepo\", // (98)!\n    \"group:datatables-net-fixedheaderMonorepo\", // (99)!\n    \"group:datatables-net-keytableMonorepo\", // (100)!\n    \"group:datatables-net-responsiveMonorepo\", // (101)!\n    \"group:datatables-net-rowgroupMonorepo\", // (102)!\n    \"group:datatables-net-rowreorderMonorepo\", // (103)!\n    \"group:datatables-net-scrollerMonorepo\", // (104)!\n    \"group:datatables-net-searchbuilderMonorepo\", // (105)!\n    \"group:datatables-net-searchpanesMonorepo\", // (106)!\n    \"group:datatables-net-selectMonorepo\", // (107)!\n    \"group:datatables-net-staterestoreMonorepo\", // (108)!\n    \"group:date-ioMonorepo\", // (109)!\n    \"group:deck-glMonorepo\", // (110)!\n    \"group:denoMonorepo\", // (111)!\n    \"group:devextreme-reactiveMonorepo\", // (112)!\n    \"group:dnd-kitMonorepo\", // (113)!\n    \"group:docusaurusMonorepo\", // (114)!\n    \"group:dot-swashbuckleMonorepo\", // (115)!\n    \"group:dotnetMonorepo\", // (116)!\n    \"group:dotnet-azure-ad-identitymodel-extensionsMonorepo\", // (117)!\n    \"group:dotnet-azure-ad-microsoft-identity-webMonorepo\", // (118)!\n    \"group:dotnet-wcfMonorepo\", // (119)!\n    \"group:dotnetcore-capMonorepo\", // (120)!\n    \"group:dropwizardMonorepo\", // (121)!\n    \"group:duende-identityserverMonorepo\", // (122)!\n    \"group:effectMonorepo\", // (123)!\n    \"group:elastic-apm-agent-rum-jsMonorepo\", // (124)!\n    \"group:elastic-ecs-dotnetMonorepo\", // (125)!\n    \"group:electron-forgeMonorepo\", // (126)!\n    \"group:ember-decoratorsMonorepo\", // (127)!\n    \"group:embla-carouselMonorepo\", // (128)!\n    \"group:emojibaseMonorepo\", // (129)!\n    \"group:emotionMonorepo\", // (130)!\n    \"group:enumeratumMonorepo\", // (131)!\n    \"group:envelopMonorepo\", // (132)!\n    \"group:error-proneMonorepo\", // (133)!\n    \"group:error-prone-supportMonorepo\", // (134)!\n    \"group:eslintMonorepo\", // (135)!\n    \"group:eslint-config-globexMonorepo\", // (136)!\n    \"group:eslint-stylisticMonorepo\", // (137)!\n    \"group:expoMonorepo\", // (138)!\n    \"group:fabric-chaincode-nodeMonorepo\", // (139)!\n    \"group:fabric8-kubernetes-clientMonorepo\", // (140)!\n    \"group:faro-web-sdkMonorepo\", // (141)!\n    \"group:fastendpointsMonorepo\", // (142)!\n    \"group:feathersMonorepo\", // (143)!\n    \"group:featuremanagement-dotnetMonorepo\", // (144)!\n    \"group:feignMonorepo\", // (145)!\n    \"group:felaMonorepo\", // (146)!\n    \"group:fimbullinterMonorepo\", // (147)!\n    \"group:flipperMonorepo\", // (148)!\n    \"group:flopflipMonorepo\", // (149)!\n    \"group:flueMonorepo\", // (150)!\n    \"group:fontsourceMonorepo\", // (151)!\n    \"group:formatjsMonorepo\", // (152)!\n    \"group:framework7Monorepo\", // (153)!\n    \"group:funogramMonorepo\", // (154)!\n    \"group:fusioncacheMonorepo\", // (155)!\n    \"group:gatsbyMonorepo\", // (156)!\n    \"group:gitbeakerMonorepo\", // (157)!\n    \"group:github-workflows-ktMonorepo\", // (158)!\n    \"group:go-cloudMonorepo\", // (159)!\n    \"group:gomockMonorepo\", // (160)!\n    \"group:google-api-dotnet-clientMonorepo\", // (161)!\n    \"group:google-cloud-rustMonorepo\", // (162)!\n    \"group:grafanaMonorepo\", // (163)!\n    \"group:graphiqlMonorepo\", // (164)!\n    \"group:graphql-hive-gatewayMonorepo\", // (165)!\n    \"group:graphql-meshMonorepo\", // (166)!\n    \"group:graphql-modulesMonorepo\", // (167)!\n    \"group:graphql-platformMonorepo\", // (168)!\n    \"group:graphql-toolsMonorepo\", // (169)!\n    \"group:graphql-yogaMonorepo\", // (170)!\n    \"group:graphqlcodegeneratorMonorepo\", // (171)!\n    \"group:greenmailMonorepo\", // (172)!\n    \"group:groovyMonorepo\", // (173)!\n    \"group:grpc-dotnetMonorepo\", // (174)!\n    \"group:grpc-javaMonorepo\", // (175)!\n    \"group:gstreamer-rustMonorepo\", // (176)!\n    \"group:guavaMonorepo\", // (177)!\n    \"group:hangfireMonorepo\", // (178)!\n    \"group:happy-domMonorepo\", // (179)!\n    \"group:hibernate-modelsMonorepo\", // (180)!\n    \"group:hibernate-ormMonorepo\", // (181)!\n    \"group:hibernate-searchMonorepo\", // (182)!\n    \"group:hibernate-toolsMonorepo\", // (183)!\n    \"group:hickory-dnsMonorepo\", // (184)!\n    \"group:hocuspocusMonorepo\", // (185)!\n    \"group:html-eslintMonorepo\", // (186)!\n    \"group:humanizerMonorepo\", // (187)!\n    \"group:immichMonorepo\", // (188)!\n    \"group:infrastructure-uiMonorepo\", // (189)!\n    \"group:ionic-nativeMonorepo\", // (190)!\n    \"group:istanbuljsMonorepo\", // (191)!\n    \"group:istioMonorepo\", // (192)!\n    \"group:jacksonMonorepo\", // (193)!\n    \"group:jasmineMonorepo\", // (194)!\n    \"group:javafxMonorepo\", // (195)!\n    \"group:javahamcrestMonorepo\", // (196)!\n    \"group:javascriptengineswitcherMonorepo\", // (197)!\n    \"group:jaxb-riMonorepo\", // (198)!\n    \"group:jerseyMonorepo\", // (199)!\n    \"group:jestMonorepo\", // (200)!\n    \"group:jettyMonorepo\", // (201)!\n    \"group:jnaMonorepo\", // (202)!\n    \"group:json-smart-v2Monorepo\", // (203)!\n    \"group:jsonformsMonorepo\", // (204)!\n    \"group:jsplumbMonorepo\", // (205)!\n    \"group:juniorMonorepo\", // (206)!\n    \"group:junit-frameworkMonorepo\", // (207)!\n    \"group:kernelmemoryMonorepo\", // (208)!\n    \"group:kiotaMonorepo\", // (209)!\n    \"group:kotlinMonorepo\", // (210)!\n    \"group:kotlinx-coroutinesMonorepo\", // (211)!\n    \"group:krokiMonorepo\", // (212)!\n    \"group:kspMonorepo\", // (213)!\n    \"group:ktorMonorepo\", // (214)!\n    \"group:kubbMonorepo\", // (215)!\n    \"group:kubernetesMonorepo\", // (216)!\n    \"group:lamarMonorepo\", // (217)!\n    \"group:langchain4jMonorepo\", // (218)!\n    \"group:lernaMonorepo\", // (219)!\n    \"group:lerna-liteMonorepo\", // (220)!\n    \"group:lexicalMonorepo\", // (221)!\n    \"group:linguijsMonorepo\", // (222)!\n    \"group:linkifyjsMonorepo\", // (223)!\n    \"group:log4j2Monorepo\", // (224)!\n    \"group:logbackMonorepo\", // (225)!\n    \"group:logtapeMonorepo\", // (226)!\n    \"group:loopbackMonorepo\", // (227)!\n    \"group:lrnwebcomponentsMonorepo\", // (228)!\n    \"group:lucideMonorepo\", // (229)!\n    \"group:mailingMonorepo\", // (230)!\n    \"group:mantineMonorepo\", // (231)!\n    \"group:mapstructMonorepo\", // (232)!\n    \"group:martenMonorepo\", // (233)!\n    \"group:masstransitMonorepo\", // (234)!\n    \"group:material-components-webMonorepo\", // (235)!\n    \"group:material-uiMonorepo\", // (236)!\n    \"group:mdc-reactMonorepo\", // (237)!\n    \"group:mdxMonorepo\", // (238)!\n    \"group:middy-jsMonorepo\", // (239)!\n    \"group:mikro-ormMonorepo\", // (240)!\n    \"group:ml-dotnetMonorepo\", // (241)!\n    \"group:mockitoMonorepo\", // (242)!\n    \"group:mongo-csharp-driverMonorepo\", // (243)!\n    \"group:mongo-java-driverMonorepo\", // (244)!\n    \"group:mstestMonorepo\", // (245)!\n    \"group:mutation-testing-elementsMonorepo\", // (246)!\n    \"group:nestMonorepo\", // (247)!\n    \"group:nest-graphqlMonorepo\", // (248)!\n    \"group:nettyMonorepo\", // (249)!\n    \"group:neutrinoMonorepo\", // (250)!\n    \"group:nexpectMonorepo\", // (251)!\n    \"group:nextjsMonorepo\", // (252)!\n    \"group:nextraMonorepo\", // (253)!\n    \"group:ngx-cookie-serviceMonorepo\", // (254)!\n    \"group:ngx-formlyMonorepo\", // (255)!\n    \"group:ngxs-storeMonorepo\", // (256)!\n    \"group:nivoMonorepo\", // (257)!\n    \"group:njson-schemaMonorepo\", // (258)!\n    \"group:nswagMonorepo\", // (259)!\n    \"group:nugetMonorepo\", // (260)!\n    \"group:nuke-buildMonorepo\", // (261)!\n    \"group:nuxtjsMonorepo\", // (262)!\n    \"group:okhttpMonorepo\", // (263)!\n    \"group:openapi-dotnetMonorepo\", // (264)!\n    \"group:opencostMonorepo\", // (265)!\n    \"group:openiddictMonorepo\", // (266)!\n    \"group:opentelemetry-dotnetMonorepo\", // (267)!\n    \"group:opentelemetry-dotnet-contribMonorepo\", // (268)!\n    \"group:opentelemetry-erlangMonorepo\", // (269)!\n    \"group:opentelemetry-erlang-contribMonorepo\", // (270)!\n    \"group:opentelemetry-goMonorepo\", // (271)!\n    \"group:opentelemetry-go-contribMonorepo\", // (272)!\n    \"group:opentelemetry-javaMonorepo\", // (273)!\n    \"group:opentelemetry-java-contribMonorepo\", // (274)!\n    \"group:opentelemetry-jsMonorepo\", // (275)!\n    \"group:opentelemetry-js-contribMonorepo\", // (276)!\n    \"group:opentelemetry-phpMonorepo\", // (277)!\n    \"group:opentelemetry-php-contribMonorepo\", // (278)!\n    \"group:opentelemetry-pythonMonorepo\", // (279)!\n    \"group:opentelemetry-python-contribMonorepo\", // (280)!\n    \"group:opentelemetry-rustMonorepo\", // (281)!\n    \"group:opentelemetry-rust-contribMonorepo\", // (282)!\n    \"group:orleansMonorepo\", // (283)!\n    \"group:orpcMonorepo\", // (284)!\n    \"group:panda-cssMonorepo\", // (285)!\n    \"group:parcelMonorepo\", // (286)!\n    \"group:payloadcmsMonorepo\", // (287)!\n    \"group:pdfmeMonorepo\", // (288)!\n    \"group:percy-cliMonorepo\", // (289)!\n    \"group:picassojsMonorepo\", // (290)!\n    \"group:pixijsMonorepo\", // (291)!\n    \"group:playwrightMonorepo\", // (292)!\n    \"group:playwright-dotnetMonorepo\", // (293)!\n    \"group:pnpcoreMonorepo\", // (294)!\n    \"group:pnpjsMonorepo\", // (295)!\n    \"group:pollyMonorepo\", // (296)!\n    \"group:pollyjsMonorepo\", // (297)!\n    \"group:pothosMonorepo\", // (298)!\n    \"group:pouchdbMonorepo\", // (299)!\n    \"group:powermockMonorepo\", // (300)!\n    \"group:prismaMonorepo\", // (301)!\n    \"group:prometheus-netMonorepo\", // (302)!\n    \"group:promsterMonorepo\", // (303)!\n    \"group:protobufMonorepo\", // (304)!\n    \"group:quartznetMonorepo\", // (305)!\n    \"group:radix-ui-primitivesMonorepo\", // (306)!\n    \"group:reach-uiMonorepo\", // (307)!\n    \"group:reactMonorepo\", // (308)!\n    \"group:react-adminMonorepo\", // (309)!\n    \"group:react-apolloMonorepo\", // (310)!\n    \"group:react-dndMonorepo\", // (311)!\n    \"group:react-emailMonorepo\", // (312)!\n    \"group:react-navigationMonorepo\", // (313)!\n    \"group:react-pageMonorepo\", // (314)!\n    \"group:react-railsMonorepo\", // (315)!\n    \"group:react-routerMonorepo\", // (316)!\n    \"group:react-spectrumMonorepo\", // (317)!\n    \"group:react-springMonorepo\", // (318)!\n    \"group:reactivestack-cookiesMonorepo\", // (319)!\n    \"group:reakitMonorepo\", // (320)!\n    \"group:redwoodMonorepo\", // (321)!\n    \"group:refitMonorepo\", // (322)!\n    \"group:reg-suitMonorepo\", // (323)!\n    \"group:remarkMonorepo\", // (324)!\n    \"group:remixMonorepo\", // (325)!\n    \"group:retrofitMonorepo\", // (326)!\n    \"group:riverMonorepo\", // (327)!\n    \"group:rjsfMonorepo\", // (328)!\n    \"group:router5Monorepo\", // (329)!\n    \"group:rspackMonorepo\", // (330)!\n    \"group:ruby-on-railsMonorepo\", // (331)!\n    \"group:rust-analyzerMonorepo\", // (332)!\n    \"group:rust-futuresMonorepo\", // (333)!\n    \"group:rust-wasm-bindgenMonorepo\", // (334)!\n    \"group:sanityMonorepo\", // (335)!\n    \"group:scaffdogMonorepo\", // (336)!\n    \"group:scalarMonorepo\", // (337)!\n    \"group:sea-ormMonorepo\", // (338)!\n    \"group:secretlintMonorepo\", // (339)!\n    \"group:sendgrid-nodejsMonorepo\", // (340)!\n    \"group:sentry-dotnetMonorepo\", // (341)!\n    \"group:sentry-javascriptMonorepo\", // (342)!\n    \"group:sentry-rubyMonorepo\", // (343)!\n    \"group:sentry-rustMonorepo\", // (344)!\n    \"group:serdeMonorepo\", // (345)!\n    \"group:serenity-jsMonorepo\", // (346)!\n    \"group:serilog-uiMonorepo\", // (347)!\n    \"group:servicestackMonorepo\", // (348)!\n    \"group:serwistMonorepo\", // (349)!\n    \"group:shedlockMonorepo\", // (350)!\n    \"group:shikiMonorepo\", // (351)!\n    \"group:shopify-app-bridgeMonorepo\", // (352)!\n    \"group:sitecore-jssMonorepo\", // (353)!\n    \"group:size-limitMonorepo\", // (354)!\n    \"group:skiasharpMonorepo\", // (355)!\n    \"group:slack-netMonorepo\", // (356)!\n    \"group:slf4jMonorepo\", // (357)!\n    \"group:slim-message-busMonorepo\", // (358)!\n    \"group:spectre-consoleMonorepo\", // (359)!\n    \"group:spectre-console-cliMonorepo\", // (360)!\n    \"group:springfoxMonorepo\", // (361)!\n    \"group:stack-exchange-redis-extensionsMonorepo\", // (362)!\n    \"group:statsig-js-clientMonorepo\", // (363)!\n    \"group:steeltoeMonorepo\", // (364)!\n    \"group:storybookMonorepo\", // (365)!\n    \"group:storybook-react-nativeMonorepo\", // (366)!\n    \"group:strapiMonorepo\", // (367)!\n    \"group:strumMonorepo\", // (368)!\n    \"group:stryker-jsMonorepo\", // (369)!\n    \"group:stylex-swcMonorepo\", // (370)!\n    \"group:surveyjsMonorepo\", // (371)!\n    \"group:swashbuckle-aspnetcoreMonorepo\", // (372)!\n    \"group:system.io.abstractionsMonorepo\", // (373)!\n    \"group:taiga-uiMonorepo\", // (374)!\n    \"group:tailwindcssMonorepo\", // (375)!\n    \"group:tamaguiMonorepo\", // (376)!\n    \"group:tanstack-formMonorepo\", // (377)!\n    \"group:tanstack-queryMonorepo\", // (378)!\n    \"group:tanstack-routerMonorepo\", // (379)!\n    \"group:tanstack-tableMonorepo\", // (380)!\n    \"group:tanstack-virtualMonorepo\", // (381)!\n    \"group:tauriMonorepo\", // (382)!\n    \"group:telus-tdsMonorepo\", // (383)!\n    \"group:telus-tds-coreMonorepo\", // (384)!\n    \"group:temporalio-tsMonorepo\", // (385)!\n    \"group:terraformMonorepo\", // (386)!\n    \"group:testcontainers-dotnetMonorepo\", // (387)!\n    \"group:testcontainers-goMonorepo\", // (388)!\n    \"group:testcontainers-javaMonorepo\", // (389)!\n    \"group:testcontainers-nodeMonorepo\", // (390)!\n    \"group:theme-uiMonorepo\", // (391)!\n    \"group:tikaMonorepo\", // (392)!\n    \"group:timvirMonorepo\", // (393)!\n    \"group:tiptapMonorepo\", // (394)!\n    \"group:tokio-prostMonorepo\", // (395)!\n    \"group:tokio-tracingMonorepo\", // (396)!\n    \"group:tomcatMonorepo\", // (397)!\n    \"group:tonicMonorepo\", // (398)!\n    \"group:treatMonorepo\", // (399)!\n    \"group:trpcMonorepo\", // (400)!\n    \"group:trust-dnsMonorepo\", // (401)!\n    \"group:tsoaMonorepo\", // (402)!\n    \"group:tunitMonorepo\", // (403)!\n    \"group:turboMonorepo\", // (404)!\n    \"group:turfMonorepo\", // (405)!\n    \"group:typed-signalrMonorepo\", // (406)!\n    \"group:typefacesMonorepo\", // (407)!\n    \"group:typescript-eslintMonorepo\", // (408)!\n    \"group:typography-jsMonorepo\", // (409)!\n    \"group:ui5-webcomponentsMonorepo\", // (410)!\n    \"group:unheadMonorepo\", // (411)!\n    \"group:unocssMonorepo\", // (412)!\n    \"group:uppyMonorepo\", // (413)!\n    \"group:utoipaMonorepo\", // (414)!\n    \"group:vaadin-hillaMonorepo\", // (415)!\n    \"group:vaadinWebComponentsMonorepo\", // (416)!\n    \"group:vanilla-extractMonorepo\", // (417)!\n    \"group:visxMonorepo\", // (418)!\n    \"group:vite-plusMonorepo\", // (419)!\n    \"group:vitestMonorepo\", // (420)!\n    \"group:vstestMonorepo\", // (421)!\n    \"group:vueMonorepo\", // (422)!\n    \"group:vue-cliMonorepo\", // (423)!\n    \"group:vue-language-toolsMonorepo\", // (424)!\n    \"group:vuepressMonorepo\", // (425)!\n    \"group:vueuseMonorepo\", // (426)!\n    \"group:weaselMonorepo\", // (427)!\n    \"group:web3-reactMonorepo\", // (428)!\n    \"group:webdriverioMonorepo\", // (429)!\n    \"group:wolverineMonorepo\", // (430)!\n    \"group:workboxMonorepo\", // (431)!\n    \"group:wyw-in-jsMonorepo\", // (432)!\n    \"group:xstateMonorepo\", // (433)!\n    \"group:xtermMonorepo\", // (434)!\n    \"group:xunit-dotnetMonorepo\", // (435)!\n    \"group:yamldotnetMonorepo\", // (436)!\n    \"group:yarnMonorepo\", // (437)!\n    \"group:zag-jsMonorepo\", // (438)!\n    \"group:zxcvbn-tsMonorepo\", // (439)!\n    \"group:zxing-netMonorepo\", // (440)!\n    \"group:hapijsMonorepo\", // (441)!\n    \"group:lodashMonorepo\", // (442)!\n    \"group:ngrxMonorepo\", // (443)!\n    \"group:nxMonorepo\", // (444)!\n    \"group:octokitMonorepo\", // (445)!\n    \"group:php-enqueueMonorepo\", // (446)!\n    \"group:semantic-releaseMonorepo\", // (447)!\n    \"group:swcMonorepo\", // (448)!\n    \"group:twigMonorepo\", // (449)!\n    \"group:angularmaterialMonorepo\", // (450)!\n    \"group:apache-camelMonorepo\", // (451)!\n    \"group:apache-poiMonorepo\", // (452)!\n    \"group:aws-java-sdkMonorepo\", // (453)!\n    \"group:aws-java-sdk-v2Monorepo\", // (454)!\n    \"group:axis2Monorepo\", // (455)!\n    \"group:babel6Monorepo\", // (456)!\n    \"group:embroiderMonorepo\", // (457)!\n    \"group:forgeMonorepo\", // (458)!\n    \"group:fullcalendarMonorepo\", // (459)!\n    \"group:oracle-databaseMonorepo\", // (460)!\n    \"group:oxlintMonorepo\", // (461)!\n    \"group:prometheus-simpleclientMonorepo\", // (462)!\n    \"group:russhMonorepo\", // (463)!\n    \"group:solidMonorepo\", // (464)!\n    \"group:spfxMonorepo\", // (465)!\n    \"group:spockMonorepo\", // (466)!\n    \"group:syncfusion-dotnetMonorepo\", // (467)!\n    \"group:testing-libraryMonorepo\", // (468)!\n    \"group:wordpressMonorepo\" // (469)!\n  ]\n}\n
  1. group:accountsMonorepo: Group packages from accounts monorepo together.
  2. group:acotMonorepo: Group packages from acot monorepo together.
  3. group:ag-gridMonorepo: Group packages from ag-grid monorepo together.
  4. group:algolia-instantsearchMonorepo: Group packages from algolia-instantsearch monorepo together.
  5. group:algolia-react-instantsearchMonorepo: Group packages from algolia-react-instantsearch monorepo together.
  6. group:algoliasearch-autocompleteMonorepo: Group packages from algoliasearch-autocomplete monorepo together.
  7. group:algoliasearch-client-javascriptMonorepo: Group packages from algoliasearch-client-javascript monorepo together.
  8. group:analogMonorepo: Group packages from analog monorepo together.
  9. group:angularMonorepo: Group packages from angular monorepo together.
  10. group:angular-cliMonorepo: Group packages from angular-cli monorepo together.
  11. group:angular-eslintMonorepo: Group packages from angular-eslint monorepo together.
  12. group:angularfireMonorepo: Group packages from angularfire monorepo together.
  13. group:angularjsMonorepo: Group packages from angularjs monorepo together.
  14. group:apache-luceneMonorepo: Group packages from apache-lucene monorepo together.
  15. group:apollo-serverMonorepo: Group packages from apollo-server monorepo together.
  16. group:apolloclientMonorepo: Group packages from apolloclient monorepo together.
  17. group:appiumMonorepo: Group packages from appium monorepo together.
  18. group:applicationinsights-dotnetMonorepo: Group packages from applicationinsights-dotnet monorepo together.
  19. group:arcus.background-jobsMonorepo: Group packages from arcus.background-jobs monorepo together.
  20. group:arcus.event-gridMonorepo: Group packages from arcus.event-grid monorepo together.
  21. group:arcus.messagingMonorepo: Group packages from arcus.messaging monorepo together.
  22. group:arcus.observabilityMonorepo: Group packages from arcus.observability monorepo together.
  23. group:arcus.securityMonorepo: Group packages from arcus.security monorepo together.
  24. group:arcus.webapiMonorepo: Group packages from arcus.webapi monorepo together.
  25. group:arrow-ktMonorepo: Group packages from arrow-kt monorepo together.
  26. group:arrow-rsMonorepo: Group packages from arrow-rs monorepo together.
  27. group:aspireMonorepo: Group packages from aspire monorepo together.
  28. group:aspnet aspnetwebstackMonorepo: Group packages from aspnet aspnetwebstack monorepo together.
  29. group:aspnet extensionsMonorepo: Group packages from aspnet extensions monorepo together.
  30. group:aspnet-api-versioningMonorepo: Group packages from aspnet-api-versioning monorepo together.
  31. group:aspnet-health-checksMonorepo: Group packages from aspnet-health-checks monorepo together.
  32. group:aspnet-security-oauth-providersMonorepo: Group packages from aspnet-security-oauth-providers monorepo together.
  33. group:astroMonorepo: Group packages from astro monorepo together.
  34. group:autoMonorepo: Group packages from auto monorepo together.
  35. group:autofixtureMonorepo: Group packages from autofixture monorepo together.
  36. group:automapper-dotnetMonorepo: Group packages from automapper-dotnet monorepo together.
  37. group:avaloniaMonorepo: Group packages from avalonia monorepo together.
  38. group:aws-cdkMonorepo: Group packages from aws-cdk monorepo together.
  39. group:aws-lambda-dotnetMonorepo: Group packages from aws-lambda-dotnet monorepo together.
  40. group:aws-lambda-powertools-typescriptMonorepo: Group packages from aws-lambda-powertools-typescript monorepo together.
  41. group:aws-sdk-client-mockMonorepo: Group packages from aws-sdk-client-mock monorepo together.
  42. group:aws-sdk-goMonorepo: Group packages from aws-sdk-go monorepo together.
  43. group:aws-sdk-go-v2Monorepo: Group packages from aws-sdk-go-v2 monorepo together.
  44. group:aws-sdk-js-v3Monorepo: Group packages from aws-sdk-js-v3 monorepo together.
  45. group:aws-sdk-netMonorepo: Group packages from aws-sdk-net monorepo together.
  46. group:aws-sdk-rustMonorepo: Group packages from aws-sdk-rust monorepo together.
  47. group:awsappsyncMonorepo: Group packages from awsappsync monorepo together.
  48. group:axumMonorepo: Group packages from axum monorepo together.
  49. group:azure azure-libraries-for-netMonorepo: Group packages from azure azure-libraries-for-net monorepo together.
  50. group:azure azure-sdk-for-netMonorepo: Group packages from azure azure-sdk-for-net monorepo together.
  51. group:azure azure-storage-netMonorepo: Group packages from azure azure-storage-net monorepo together.
  52. group:azure-ad-microsoft-authentication-library-for-androidMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-android monorepo together.
  53. group:azure-ad-microsoft-authentication-library-for-dotnetMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-dotnet monorepo together.
  54. group:azure-ad-microsoft-authentication-library-for-goMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-go monorepo together.
  55. group:azure-ad-microsoft-authentication-library-for-javaMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-java monorepo together.
  56. group:azure-ad-microsoft-authentication-library-for-jsMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-js monorepo together.
  57. group:azure-ad-microsoft-authentication-library-for-objcMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-objc monorepo together.
  58. group:azure-ad-microsoft-authentication-library-for-pythonMonorepo: Group packages from azure-ad-microsoft-authentication-library-for-python monorepo together.
  59. group:azure-functions-dotnet-workerMonorepo: Group packages from azure-functions-dotnet-worker monorepo together.
  60. group:azure-sdk-for-androidMonorepo: Group packages from azure-sdk-for-android monorepo together.
  61. group:azure-sdk-for-cMonorepo: Group packages from azure-sdk-for-c monorepo together.
  62. group:azure-sdk-for-cppMonorepo: Group packages from azure-sdk-for-cpp monorepo together.
  63. group:azure-sdk-for-goMonorepo: Group packages from azure-sdk-for-go monorepo together.
  64. group:azure-sdk-for-iosMonorepo: Group packages from azure-sdk-for-ios monorepo together.
  65. group:azure-sdk-for-javaMonorepo: Group packages from azure-sdk-for-java monorepo together.
  66. group:azure-sdk-for-jsMonorepo: Group packages from azure-sdk-for-js monorepo together.
  67. group:azure-sdk-for-pythonMonorepo: Group packages from azure-sdk-for-python monorepo together.
  68. group:azure-sdk-for-rustMonorepo: Group packages from azure-sdk-for-rust monorepo together.
  69. group:babelMonorepo: Group packages from babel monorepo together.
  70. group:backstageMonorepo: Group packages from backstage monorepo together.
  71. group:basetMonorepo: Group packages from baset monorepo together.
  72. group:better-authMonorepo: Group packages from better-auth monorepo together.
  73. group:braveMonorepo: Group packages from brave monorepo together.
  74. group:bugsnag-jsMonorepo: Group packages from bugsnag-js monorepo together.
  75. group:bull-boardMonorepo: Group packages from bull-board monorepo together.
  76. group:cakeMonorepo: Group packages from cake monorepo together.
  77. group:cake-issuesMonorepo: Group packages from cake-issues monorepo together.
  78. group:capacitorMonorepo: Group packages from capacitor monorepo together.
  79. group:cedarMonorepo: Group packages from cedar monorepo together.
  80. group:chakra-uiMonorepo: Group packages from chakra-ui monorepo together.
  81. group:chromelyMonorepo: Group packages from chromely monorepo together.
  82. group:citation-jsMonorepo: Group packages from citation-js monorepo together.
  83. group:ckeditorMonorepo: Group packages from ckeditor monorepo together.
  84. group:clarityMonorepo: Group packages from clarity monorepo together.
  85. group:clearscriptMonorepo: Group packages from clearscript monorepo together.
  86. group:commitlintMonorepo: Group packages from commitlint monorepo together.
  87. group:confectMonorepo: Group packages from confect monorepo together.
  88. group:conformMonorepo: Group packages from conform monorepo together.
  89. group:contentful-rich-textMonorepo: Group packages from contentful-rich-text monorepo together.
  90. group:convexMonorepo: Group packages from convex monorepo together.
  91. group:cspellMonorepo: Group packages from cspell monorepo together.
  92. group:datadog-browser-sdkMonorepo: Group packages from datadog-browser-sdk monorepo together.
  93. group:datafusionMonorepo: Group packages from datafusion monorepo together.
  94. group:datatables-netMonorepo: Group packages from datatables-net monorepo together.
  95. group:datatables-net-autofillMonorepo: Group packages from datatables-net-autofill monorepo together.
  96. group:datatables-net-buttonsMonorepo: Group packages from datatables-net-buttons monorepo together.
  97. group:datatables-net-colreorderMonorepo: Group packages from datatables-net-colreorder monorepo together.
  98. group:datatables-net-fixedcolumnsMonorepo: Group packages from datatables-net-fixedcolumns monorepo together.
  99. group:datatables-net-fixedheaderMonorepo: Group packages from datatables-net-fixedheader monorepo together.
  100. group:datatables-net-keytableMonorepo: Group packages from datatables-net-keytable monorepo together.
  101. group:datatables-net-responsiveMonorepo: Group packages from datatables-net-responsive monorepo together.
  102. group:datatables-net-rowgroupMonorepo: Group packages from datatables-net-rowgroup monorepo together.
  103. group:datatables-net-rowreorderMonorepo: Group packages from datatables-net-rowreorder monorepo together.
  104. group:datatables-net-scrollerMonorepo: Group packages from datatables-net-scroller monorepo together.
  105. group:datatables-net-searchbuilderMonorepo: Group packages from datatables-net-searchbuilder monorepo together.
  106. group:datatables-net-searchpanesMonorepo: Group packages from datatables-net-searchpanes monorepo together.
  107. group:datatables-net-selectMonorepo: Group packages from datatables-net-select monorepo together.
  108. group:datatables-net-staterestoreMonorepo: Group packages from datatables-net-staterestore monorepo together.
  109. group:date-ioMonorepo: Group packages from date-io monorepo together.
  110. group:deck-glMonorepo: Group packages from deck-gl monorepo together.
  111. group:denoMonorepo: Group packages from deno monorepo together.
  112. group:devextreme-reactiveMonorepo: Group packages from devextreme-reactive monorepo together.
  113. group:dnd-kitMonorepo: Group packages from dnd-kit monorepo together.
  114. group:docusaurusMonorepo: Group packages from docusaurus monorepo together.
  115. group:dot-swashbuckleMonorepo: Group packages from dot-swashbuckle monorepo together.
  116. group:dotnetMonorepo: Group packages from dotnet monorepo together.
  117. group:dotnet-azure-ad-identitymodel-extensionsMonorepo: Group packages from dotnet-azure-ad-identitymodel-extensions monorepo together.
  118. group:dotnet-azure-ad-microsoft-identity-webMonorepo: Group packages from dotnet-azure-ad-microsoft-identity-web monorepo together.
  119. group:dotnet-wcfMonorepo: Group packages from dotnet-wcf monorepo together.
  120. group:dotnetcore-capMonorepo: Group packages from dotnetcore-cap monorepo together.
  121. group:dropwizardMonorepo: Group packages from dropwizard monorepo together.
  122. group:duende-identityserverMonorepo: Group packages from duende-identityserver monorepo together.
  123. group:effectMonorepo: Group packages from effect monorepo together.
  124. group:elastic-apm-agent-rum-jsMonorepo: Group packages from elastic-apm-agent-rum-js monorepo together.
  125. group:elastic-ecs-dotnetMonorepo: Group packages from elastic-ecs-dotnet monorepo together.
  126. group:electron-forgeMonorepo: Group packages from electron-forge monorepo together.
  127. group:ember-decoratorsMonorepo: Group packages from ember-decorators monorepo together.
  128. group:embla-carouselMonorepo: Group packages from embla-carousel monorepo together.
  129. group:emojibaseMonorepo: Group packages from emojibase monorepo together.
  130. group:emotionMonorepo: Group packages from emotion monorepo together.
  131. group:enumeratumMonorepo: Group packages from enumeratum monorepo together.
  132. group:envelopMonorepo: Group packages from envelop monorepo together.
  133. group:error-proneMonorepo: Group packages from error-prone monorepo together.
  134. group:error-prone-supportMonorepo: Group packages from error-prone-support monorepo together.
  135. group:eslintMonorepo: Group packages from eslint monorepo together.
  136. group:eslint-config-globexMonorepo: Group packages from eslint-config-globex monorepo together.
  137. group:eslint-stylisticMonorepo: Group packages from eslint-stylistic monorepo together.
  138. group:expoMonorepo: Group packages from expo monorepo together.
  139. group:fabric-chaincode-nodeMonorepo: Group packages from fabric-chaincode-node monorepo together.
  140. group:fabric8-kubernetes-clientMonorepo: Group packages from fabric8-kubernetes-client monorepo together.
  141. group:faro-web-sdkMonorepo: Group packages from faro-web-sdk monorepo together.
  142. group:fastendpointsMonorepo: Group packages from fastendpoints monorepo together.
  143. group:feathersMonorepo: Group packages from feathers monorepo together.
  144. group:featuremanagement-dotnetMonorepo: Group packages from featuremanagement-dotnet monorepo together.
  145. group:feignMonorepo: Group packages from feign monorepo together.
  146. group:felaMonorepo: Group packages from fela monorepo together.
  147. group:fimbullinterMonorepo: Group packages from fimbullinter monorepo together.
  148. group:flipperMonorepo: Group packages from flipper monorepo together.
  149. group:flopflipMonorepo: Group packages from flopflip monorepo together.
  150. group:flueMonorepo: Group packages from flue monorepo together.
  151. group:fontsourceMonorepo: Group packages from fontsource monorepo together.
  152. group:formatjsMonorepo: Group packages from formatjs monorepo together.
  153. group:framework7Monorepo: Group packages from framework7 monorepo together.
  154. group:funogramMonorepo: Group packages from funogram monorepo together.
  155. group:fusioncacheMonorepo: Group packages from fusioncache monorepo together.
  156. group:gatsbyMonorepo: Group packages from gatsby monorepo together.
  157. group:gitbeakerMonorepo: Group packages from gitbeaker monorepo together.
  158. group:github-workflows-ktMonorepo: Group packages from github-workflows-kt monorepo together.
  159. group:go-cloudMonorepo: Group packages from go-cloud monorepo together.
  160. group:gomockMonorepo: Group packages from gomock monorepo together.
  161. group:google-api-dotnet-clientMonorepo: Group packages from google-api-dotnet-client monorepo together.
  162. group:google-cloud-rustMonorepo: Group packages from google-cloud-rust monorepo together.
  163. group:grafanaMonorepo: Group packages from grafana monorepo together.
  164. group:graphiqlMonorepo: Group packages from graphiql monorepo together.
  165. group:graphql-hive-gatewayMonorepo: Group packages from graphql-hive-gateway monorepo together.
  166. group:graphql-meshMonorepo: Group packages from graphql-mesh monorepo together.
  167. group:graphql-modulesMonorepo: Group packages from graphql-modules monorepo together.
  168. group:graphql-platformMonorepo: Group packages from graphql-platform monorepo together.
  169. group:graphql-toolsMonorepo: Group packages from graphql-tools monorepo together.
  170. group:graphql-yogaMonorepo: Group packages from graphql-yoga monorepo together.
  171. group:graphqlcodegeneratorMonorepo: Group packages from graphqlcodegenerator monorepo together.
  172. group:greenmailMonorepo: Group packages from greenmail monorepo together.
  173. group:groovyMonorepo: Group packages from groovy monorepo together.
  174. group:grpc-dotnetMonorepo: Group packages from grpc-dotnet monorepo together.
  175. group:grpc-javaMonorepo: Group packages from grpc-java monorepo together.
  176. group:gstreamer-rustMonorepo: Group packages from gstreamer-rust monorepo together.
  177. group:guavaMonorepo: Group packages from guava monorepo together.
  178. group:hangfireMonorepo: Group packages from hangfire monorepo together.
  179. group:happy-domMonorepo: Group packages from happy-dom monorepo together.
  180. group:hibernate-modelsMonorepo: Group packages from hibernate-models monorepo together.
  181. group:hibernate-ormMonorepo: Group packages from hibernate-orm monorepo together.
  182. group:hibernate-searchMonorepo: Group packages from hibernate-search monorepo together.
  183. group:hibernate-toolsMonorepo: Group packages from hibernate-tools monorepo together.
  184. group:hickory-dnsMonorepo: Group packages from hickory-dns monorepo together.
  185. group:hocuspocusMonorepo: Group packages from hocuspocus monorepo together.
  186. group:html-eslintMonorepo: Group packages from html-eslint monorepo together.
  187. group:humanizerMonorepo: Group packages from humanizer monorepo together.
  188. group:immichMonorepo: Group packages from immich monorepo together.
  189. group:infrastructure-uiMonorepo: Group packages from infrastructure-ui monorepo together.
  190. group:ionic-nativeMonorepo: Group packages from ionic-native monorepo together.
  191. group:istanbuljsMonorepo: Group packages from istanbuljs monorepo together.
  192. group:istioMonorepo: Group packages from istio monorepo together.
  193. group:jacksonMonorepo: Group packages from jackson monorepo together.
  194. group:jasmineMonorepo: Group packages from jasmine monorepo together.
  195. group:javafxMonorepo: Group packages from javafx monorepo together.
  196. group:javahamcrestMonorepo: Group packages from javahamcrest monorepo together.
  197. group:javascriptengineswitcherMonorepo: Group packages from javascriptengineswitcher monorepo together.
  198. group:jaxb-riMonorepo: Group packages from jaxb-ri monorepo together.
  199. group:jerseyMonorepo: Group packages from jersey monorepo together.
  200. group:jestMonorepo: Group packages from jest monorepo together.
  201. group:jettyMonorepo: Group packages from jetty monorepo together.
  202. group:jnaMonorepo: Group packages from jna monorepo together.
  203. group:json-smart-v2Monorepo: Group packages from json-smart-v2 monorepo together.
  204. group:jsonformsMonorepo: Group packages from jsonforms monorepo together.
  205. group:jsplumbMonorepo: Group packages from jsplumb monorepo together.
  206. group:juniorMonorepo: Group packages from junior monorepo together.
  207. group:junit-frameworkMonorepo: Group packages from junit-framework monorepo together.
  208. group:kernelmemoryMonorepo: Group packages from kernelmemory monorepo together.
  209. group:kiotaMonorepo: Group packages from kiota monorepo together.
  210. group:kotlinMonorepo: Group packages from kotlin monorepo together.
  211. group:kotlinx-coroutinesMonorepo: Group packages from kotlinx-coroutines monorepo together.
  212. group:krokiMonorepo: Group packages from kroki monorepo together.
  213. group:kspMonorepo: Group packages from ksp monorepo together.
  214. group:ktorMonorepo: Group packages from ktor monorepo together.
  215. group:kubbMonorepo: Group packages from kubb monorepo together.
  216. group:kubernetesMonorepo: Group packages from kubernetes monorepo together.
  217. group:lamarMonorepo: Group packages from lamar monorepo together.
  218. group:langchain4jMonorepo: Group packages from langchain4j monorepo together.
  219. group:lernaMonorepo: Group packages from lerna monorepo together.
  220. group:lerna-liteMonorepo: Group packages from lerna-lite monorepo together.
  221. group:lexicalMonorepo: Group packages from lexical monorepo together.
  222. group:linguijsMonorepo: Group packages from linguijs monorepo together.
  223. group:linkifyjsMonorepo: Group packages from linkifyjs monorepo together.
  224. group:log4j2Monorepo: Group packages from log4j2 monorepo together.
  225. group:logbackMonorepo: Group packages from logback monorepo together.
  226. group:logtapeMonorepo: Group packages from logtape monorepo together.
  227. group:loopbackMonorepo: Group packages from loopback monorepo together.
  228. group:lrnwebcomponentsMonorepo: Group packages from lrnwebcomponents monorepo together.
  229. group:lucideMonorepo: Group packages from lucide monorepo together.
  230. group:mailingMonorepo: Group packages from mailing monorepo together.
  231. group:mantineMonorepo: Group packages from mantine monorepo together.
  232. group:mapstructMonorepo: Group packages from mapstruct monorepo together.
  233. group:martenMonorepo: Group packages from marten monorepo together.
  234. group:masstransitMonorepo: Group packages from masstransit monorepo together.
  235. group:material-components-webMonorepo: Group packages from material-components-web monorepo together.
  236. group:material-uiMonorepo: Group packages from material-ui monorepo together.
  237. group:mdc-reactMonorepo: Group packages from mdc-react monorepo together.
  238. group:mdxMonorepo: Group packages from mdx monorepo together.
  239. group:middy-jsMonorepo: Group packages from middy-js monorepo together.
  240. group:mikro-ormMonorepo: Group packages from mikro-orm monorepo together.
  241. group:ml-dotnetMonorepo: Group packages from ml-dotnet monorepo together.
  242. group:mockitoMonorepo: Group packages from mockito monorepo together.
  243. group:mongo-csharp-driverMonorepo: Group packages from mongo-csharp-driver monorepo together.
  244. group:mongo-java-driverMonorepo: Group packages from mongo-java-driver monorepo together.
  245. group:mstestMonorepo: Group packages from mstest monorepo together.
  246. group:mutation-testing-elementsMonorepo: Group packages from mutation-testing-elements monorepo together.
  247. group:nestMonorepo: Group packages from nest monorepo together.
  248. group:nest-graphqlMonorepo: Group packages from nest-graphql monorepo together.
  249. group:nettyMonorepo: Group packages from netty monorepo together.
  250. group:neutrinoMonorepo: Group packages from neutrino monorepo together.
  251. group:nexpectMonorepo: Group packages from nexpect monorepo together.
  252. group:nextjsMonorepo: Group packages from nextjs monorepo together.
  253. group:nextraMonorepo: Group packages from nextra monorepo together.
  254. group:ngx-cookie-serviceMonorepo: Group packages from ngx-cookie-service monorepo together.
  255. group:ngx-formlyMonorepo: Group packages from ngx-formly monorepo together.
  256. group:ngxs-storeMonorepo: Group packages from ngxs-store monorepo together.
  257. group:nivoMonorepo: Group packages from nivo monorepo together.
  258. group:njson-schemaMonorepo: Group packages from njson-schema monorepo together.
  259. group:nswagMonorepo: Group packages from nswag monorepo together.
  260. group:nugetMonorepo: Group packages from nuget monorepo together.
  261. group:nuke-buildMonorepo: Group packages from nuke-build monorepo together.
  262. group:nuxtjsMonorepo: Group packages from nuxtjs monorepo together.
  263. group:okhttpMonorepo: Group packages from okhttp monorepo together.
  264. group:openapi-dotnetMonorepo: Group packages from openapi-dotnet monorepo together.
  265. group:opencostMonorepo: Group packages from opencost monorepo together.
  266. group:openiddictMonorepo: Group packages from openiddict monorepo together.
  267. group:opentelemetry-dotnetMonorepo: Group packages from opentelemetry-dotnet monorepo together.
  268. group:opentelemetry-dotnet-contribMonorepo: Group packages from opentelemetry-dotnet-contrib monorepo together.
  269. group:opentelemetry-erlangMonorepo: Group packages from opentelemetry-erlang monorepo together.
  270. group:opentelemetry-erlang-contribMonorepo: Group packages from opentelemetry-erlang-contrib monorepo together.
  271. group:opentelemetry-goMonorepo: Group packages from opentelemetry-go monorepo together.
  272. group:opentelemetry-go-contribMonorepo: Group packages from opentelemetry-go-contrib monorepo together.
  273. group:opentelemetry-javaMonorepo: Group packages from opentelemetry-java monorepo together.
  274. group:opentelemetry-java-contribMonorepo: Group packages from opentelemetry-java-contrib monorepo together.
  275. group:opentelemetry-jsMonorepo: Group packages from opentelemetry-js monorepo together.
  276. group:opentelemetry-js-contribMonorepo: Group packages from opentelemetry-js-contrib monorepo together.
  277. group:opentelemetry-phpMonorepo: Group packages from opentelemetry-php monorepo together.
  278. group:opentelemetry-php-contribMonorepo: Group packages from opentelemetry-php-contrib monorepo together.
  279. group:opentelemetry-pythonMonorepo: Group packages from opentelemetry-python monorepo together.
  280. group:opentelemetry-python-contribMonorepo: Group packages from opentelemetry-python-contrib monorepo together.
  281. group:opentelemetry-rustMonorepo: Group packages from opentelemetry-rust monorepo together.
  282. group:opentelemetry-rust-contribMonorepo: Group packages from opentelemetry-rust-contrib monorepo together.
  283. group:orleansMonorepo: Group packages from orleans monorepo together.
  284. group:orpcMonorepo: Group packages from orpc monorepo together.
  285. group:panda-cssMonorepo: Group packages from panda-css monorepo together.
  286. group:parcelMonorepo: Group packages from parcel monorepo together.
  287. group:payloadcmsMonorepo: Group packages from payloadcms monorepo together.
  288. group:pdfmeMonorepo: Group packages from pdfme monorepo together.
  289. group:percy-cliMonorepo: Group packages from percy-cli monorepo together.
  290. group:picassojsMonorepo: Group packages from picassojs monorepo together.
  291. group:pixijsMonorepo: Group packages from pixijs monorepo together.
  292. group:playwrightMonorepo: Group packages from playwright monorepo together.
  293. group:playwright-dotnetMonorepo: Group packages from playwright-dotnet monorepo together.
  294. group:pnpcoreMonorepo: Group packages from pnpcore monorepo together.
  295. group:pnpjsMonorepo: Group packages from pnpjs monorepo together.
  296. group:pollyMonorepo: Group packages from polly monorepo together.
  297. group:pollyjsMonorepo: Group packages from pollyjs monorepo together.
  298. group:pothosMonorepo: Group packages from pothos monorepo together.
  299. group:pouchdbMonorepo: Group packages from pouchdb monorepo together.
  300. group:powermockMonorepo: Group packages from powermock monorepo together.
  301. group:prismaMonorepo: Group packages from prisma monorepo together.
  302. group:prometheus-netMonorepo: Group packages from prometheus-net monorepo together.
  303. group:promsterMonorepo: Group packages from promster monorepo together.
  304. group:protobufMonorepo: Group packages from protobuf monorepo together.
  305. group:quartznetMonorepo: Group packages from quartznet monorepo together.
  306. group:radix-ui-primitivesMonorepo: Group packages from radix-ui-primitives monorepo together.
  307. group:reach-uiMonorepo: Group packages from reach-ui monorepo together.
  308. group:reactMonorepo: Group packages from react monorepo together.
  309. group:react-adminMonorepo: Group packages from react-admin monorepo together.
  310. group:react-apolloMonorepo: Group packages from react-apollo monorepo together.
  311. group:react-dndMonorepo: Group packages from react-dnd monorepo together.
  312. group:react-emailMonorepo: Group packages from react-email monorepo together.
  313. group:react-navigationMonorepo: Group packages from react-navigation monorepo together.
  314. group:react-pageMonorepo: Group packages from react-page monorepo together.
  315. group:react-railsMonorepo: Group packages from react-rails monorepo together.
  316. group:react-routerMonorepo: Group packages from react-router monorepo together.
  317. group:react-spectrumMonorepo: Group packages from react-spectrum monorepo together.
  318. group:react-springMonorepo: Group packages from react-spring monorepo together.
  319. group:reactivestack-cookiesMonorepo: Group packages from reactivestack-cookies monorepo together.
  320. group:reakitMonorepo: Group packages from reakit monorepo together.
  321. group:redwoodMonorepo: Group packages from redwood monorepo together.
  322. group:refitMonorepo: Group packages from refit monorepo together.
  323. group:reg-suitMonorepo: Group packages from reg-suit monorepo together.
  324. group:remarkMonorepo: Group packages from remark monorepo together.
  325. group:remixMonorepo: Group packages from remix monorepo together.
  326. group:retrofitMonorepo: Group packages from retrofit monorepo together.
  327. group:riverMonorepo: Group packages from river monorepo together.
  328. group:rjsfMonorepo: Group packages from rjsf monorepo together.
  329. group:router5Monorepo: Group packages from router5 monorepo together.
  330. group:rspackMonorepo: Group packages from rspack monorepo together.
  331. group:ruby-on-railsMonorepo: Group packages from ruby-on-rails monorepo together.
  332. group:rust-analyzerMonorepo: Group packages from rust-analyzer monorepo together.
  333. group:rust-futuresMonorepo: Group packages from rust-futures monorepo together.
  334. group:rust-wasm-bindgenMonorepo: Group packages from rust-wasm-bindgen monorepo together.
  335. group:sanityMonorepo: Group packages from sanity monorepo together.
  336. group:scaffdogMonorepo: Group packages from scaffdog monorepo together.
  337. group:scalarMonorepo: Group packages from scalar monorepo together.
  338. group:sea-ormMonorepo: Group packages from sea-orm monorepo together.
  339. group:secretlintMonorepo: Group packages from secretlint monorepo together.
  340. group:sendgrid-nodejsMonorepo: Group packages from sendgrid-nodejs monorepo together.
  341. group:sentry-dotnetMonorepo: Group packages from sentry-dotnet monorepo together.
  342. group:sentry-javascriptMonorepo: Group packages from sentry-javascript monorepo together.
  343. group:sentry-rubyMonorepo: Group packages from sentry-ruby monorepo together.
  344. group:sentry-rustMonorepo: Group packages from sentry-rust monorepo together.
  345. group:serdeMonorepo: Group packages from serde monorepo together.
  346. group:serenity-jsMonorepo: Group packages from serenity-js monorepo together.
  347. group:serilog-uiMonorepo: Group packages from serilog-ui monorepo together.
  348. group:servicestackMonorepo: Group packages from servicestack monorepo together.
  349. group:serwistMonorepo: Group packages from serwist monorepo together.
  350. group:shedlockMonorepo: Group packages from shedlock monorepo together.
  351. group:shikiMonorepo: Group packages from shiki monorepo together.
  352. group:shopify-app-bridgeMonorepo: Group packages from shopify-app-bridge monorepo together.
  353. group:sitecore-jssMonorepo: Group packages from sitecore-jss monorepo together.
  354. group:size-limitMonorepo: Group packages from size-limit monorepo together.
  355. group:skiasharpMonorepo: Group packages from skiasharp monorepo together.
  356. group:slack-netMonorepo: Group packages from slack-net monorepo together.
  357. group:slf4jMonorepo: Group packages from slf4j monorepo together.
  358. group:slim-message-busMonorepo: Group packages from slim-message-bus monorepo together.
  359. group:spectre-consoleMonorepo: Group packages from spectre-console monorepo together.
  360. group:spectre-console-cliMonorepo: Group packages from spectre-console-cli monorepo together.
  361. group:springfoxMonorepo: Group packages from springfox monorepo together.
  362. group:stack-exchange-redis-extensionsMonorepo: Group packages from stack-exchange-redis-extensions monorepo together.
  363. group:statsig-js-clientMonorepo: Group packages from statsig-js-client monorepo together.
  364. group:steeltoeMonorepo: Group packages from steeltoe monorepo together.
  365. group:storybookMonorepo: Group packages from storybook monorepo together.
  366. group:storybook-react-nativeMonorepo: Group packages from storybook-react-native monorepo together.
  367. group:strapiMonorepo: Group packages from strapi monorepo together.
  368. group:strumMonorepo: Group packages from strum monorepo together.
  369. group:stryker-jsMonorepo: Group packages from stryker-js monorepo together.
  370. group:stylex-swcMonorepo: Group packages from stylex-swc monorepo together.
  371. group:surveyjsMonorepo: Group packages from surveyjs monorepo together.
  372. group:swashbuckle-aspnetcoreMonorepo: Group packages from swashbuckle-aspnetcore monorepo together.
  373. group:system.io.abstractionsMonorepo: Group packages from system.io.abstractions monorepo together.
  374. group:taiga-uiMonorepo: Group packages from taiga-ui monorepo together.
  375. group:tailwindcssMonorepo: Group packages from tailwindcss monorepo together.
  376. group:tamaguiMonorepo: Group packages from tamagui monorepo together.
  377. group:tanstack-formMonorepo: Group packages from tanstack-form monorepo together.
  378. group:tanstack-queryMonorepo: Group packages from tanstack-query monorepo together.
  379. group:tanstack-routerMonorepo: Group packages from tanstack-router monorepo together.
  380. group:tanstack-tableMonorepo: Group packages from tanstack-table monorepo together.
  381. group:tanstack-virtualMonorepo: Group packages from tanstack-virtual monorepo together.
  382. group:tauriMonorepo: Group packages from tauri monorepo together.
  383. group:telus-tdsMonorepo: Group packages from telus-tds monorepo together.
  384. group:telus-tds-coreMonorepo: Group packages from telus-tds-core monorepo together.
  385. group:temporalio-tsMonorepo: Group packages from temporalio-ts monorepo together.
  386. group:terraformMonorepo: Group packages from terraform monorepo together.
  387. group:testcontainers-dotnetMonorepo: Group packages from testcontainers-dotnet monorepo together.
  388. group:testcontainers-goMonorepo: Group packages from testcontainers-go monorepo together.
  389. group:testcontainers-javaMonorepo: Group packages from testcontainers-java monorepo together.
  390. group:testcontainers-nodeMonorepo: Group packages from testcontainers-node monorepo together.
  391. group:theme-uiMonorepo: Group packages from theme-ui monorepo together.
  392. group:tikaMonorepo: Group packages from tika monorepo together.
  393. group:timvirMonorepo: Group packages from timvir monorepo together.
  394. group:tiptapMonorepo: Group packages from tiptap monorepo together.
  395. group:tokio-prostMonorepo: Group packages from tokio-prost monorepo together.
  396. group:tokio-tracingMonorepo: Group packages from tokio-tracing monorepo together.
  397. group:tomcatMonorepo: Group packages from tomcat monorepo together.
  398. group:tonicMonorepo: Group packages from tonic monorepo together.
  399. group:treatMonorepo: Group packages from treat monorepo together.
  400. group:trpcMonorepo: Group packages from trpc monorepo together.
  401. group:trust-dnsMonorepo: Group packages from trust-dns monorepo together.
  402. group:tsoaMonorepo: Group packages from tsoa monorepo together.
  403. group:tunitMonorepo: Group packages from tunit monorepo together.
  404. group:turboMonorepo: Group packages from turbo monorepo together.
  405. group:turfMonorepo: Group packages from turf monorepo together.
  406. group:typed-signalrMonorepo: Group packages from typed-signalr monorepo together.
  407. group:typefacesMonorepo: Group packages from typefaces monorepo together.
  408. group:typescript-eslintMonorepo: Group packages from typescript-eslint monorepo together.
  409. group:typography-jsMonorepo: Group packages from typography-js monorepo together.
  410. group:ui5-webcomponentsMonorepo: Group packages from ui5-webcomponents monorepo together.
  411. group:unheadMonorepo: Group packages from unhead monorepo together.
  412. group:unocssMonorepo: Group packages from unocss monorepo together.
  413. group:uppyMonorepo: Group packages from uppy monorepo together.
  414. group:utoipaMonorepo: Group packages from utoipa monorepo together.
  415. group:vaadin-hillaMonorepo: Group packages from vaadin-hilla monorepo together.
  416. group:vaadinWebComponentsMonorepo: Group packages from vaadinWebComponents monorepo together.
  417. group:vanilla-extractMonorepo: Group packages from vanilla-extract monorepo together.
  418. group:visxMonorepo: Group packages from visx monorepo together.
  419. group:vite-plusMonorepo: Group packages from vite-plus monorepo together.
  420. group:vitestMonorepo: Group packages from vitest monorepo together.
  421. group:vstestMonorepo: Group packages from vstest monorepo together.
  422. group:vueMonorepo: Group packages from vue monorepo together.
  423. group:vue-cliMonorepo: Group packages from vue-cli monorepo together.
  424. group:vue-language-toolsMonorepo: Group packages from vue-language-tools monorepo together.
  425. group:vuepressMonorepo: Group packages from vuepress monorepo together.
  426. group:vueuseMonorepo: Group packages from vueuse monorepo together.
  427. group:weaselMonorepo: Group packages from weasel monorepo together.
  428. group:web3-reactMonorepo: Group packages from web3-react monorepo together.
  429. group:webdriverioMonorepo: Group packages from webdriverio monorepo together.
  430. group:wolverineMonorepo: Group packages from wolverine monorepo together.
  431. group:workboxMonorepo: Group packages from workbox monorepo together.
  432. group:wyw-in-jsMonorepo: Group packages from wyw-in-js monorepo together.
  433. group:xstateMonorepo: Group packages from xstate monorepo together.
  434. group:xtermMonorepo: Group packages from xterm monorepo together.
  435. group:xunit-dotnetMonorepo: Group packages from xunit-dotnet monorepo together.
  436. group:yamldotnetMonorepo: Group packages from yamldotnet monorepo together.
  437. group:yarnMonorepo: Group packages from yarn monorepo together.
  438. group:zag-jsMonorepo: Group packages from zag-js monorepo together.
  439. group:zxcvbn-tsMonorepo: Group packages from zxcvbn-ts monorepo together.
  440. group:zxing-netMonorepo: Group packages from zxing-net monorepo together.
  441. group:hapijsMonorepo: Group packages from hapijs monorepo together.
  442. group:lodashMonorepo: Group packages from lodash monorepo together.
  443. group:ngrxMonorepo: Group packages from ngrx monorepo together.
  444. group:nxMonorepo: Group packages from nx monorepo together.
  445. group:octokitMonorepo: Group packages from octokit monorepo together.
  446. group:php-enqueueMonorepo: Group packages from php-enqueue monorepo together.
  447. group:semantic-releaseMonorepo: Group packages from semantic-release monorepo together.
  448. group:swcMonorepo: Group packages from swc monorepo together.
  449. group:twigMonorepo: Group packages from twig monorepo together.
  450. group:angularmaterialMonorepo: Group packages from angularmaterial monorepo together.
  451. group:apache-camelMonorepo: Group packages from apache-camel monorepo together.
  452. group:apache-poiMonorepo: Group packages from apache-poi monorepo together.
  453. group:aws-java-sdkMonorepo: Group packages from aws-java-sdk monorepo together.
  454. group:aws-java-sdk-v2Monorepo: Group packages from aws-java-sdk-v2 monorepo together.
  455. group:axis2Monorepo: Group packages from axis2 monorepo together.
  456. group:babel6Monorepo: Group packages from babel6 monorepo together.
  457. group:embroiderMonorepo: Group packages from embroider monorepo together.
  458. group:forgeMonorepo: Group packages from forge monorepo together.
  459. group:fullcalendarMonorepo: Group packages from fullcalendar monorepo together.
  460. group:oracle-databaseMonorepo: Group packages from oracle-database monorepo together.
  461. group:oxlintMonorepo: Group packages from oxlint monorepo together.
  462. group:prometheus-simpleclientMonorepo: Group packages from prometheus-simpleclient monorepo together.
  463. group:russhMonorepo: Group packages from russh monorepo together.
  464. group:solidMonorepo: Group packages from solid monorepo together.
  465. group:spfxMonorepo: Group packages from spfx monorepo together.
  466. group:spockMonorepo: Group packages from spock monorepo together.
  467. group:syncfusion-dotnetMonorepo: Group packages from syncfusion-dotnet monorepo together.
  468. group:testing-libraryMonorepo: Group packages from testing-library monorepo together.
  469. group:wordpressMonorepo: Group packages from wordpress monorepo together.
"},{"location":"presets-helpers/","title":"Helper Presets","text":""},{"location":"presets-helpers/#helpersdisabletypesnodemajor","title":"helpers:disableTypesNodeMajor","text":"

Disable major updates to @types/node.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchPackageNames\": [\n        \"@types/node\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersfollowtypescriptnextarg0-arg1","title":"helpers:followTypescriptNext(<arg0>, <arg1>)","text":"

Keep typescript version in sync with the next tag.

{\n  \"extends\": [\n    \":followTag(typescript, next)\" // (1)!\n  ]\n}\n
  1. :followTag(typescript, next): For package arg0, strictly follow release tag arg1.
"},{"location":"presets-helpers/#helpersfollowtypescriptrcarg0-arg1","title":"helpers:followTypescriptRc(<arg0>, <arg1>)","text":"

Keep typescript version in sync with the rc tag.

{\n  \"extends\": [\n    \":followTag(typescript, rc)\" // (1)!\n  ]\n}\n
  1. :followTag(typescript, rc): For package arg0, strictly follow release tag arg1.
"},{"location":"presets-helpers/#helpersforgejodigestchangelogs","title":"helpers:forgejoDigestChangelogs","text":"

Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff

{\n  \"packageRules\": [\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"forgejo-releases\",\n        \"forgejo-tags\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    },\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"git-refs\",\n        \"git-tags\"\n      ],\n      \"matchJsonata\": [\n        \"$detectPlatform(sourceUrl) = 'forgejo'\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersgiteadigestchangelogs","title":"helpers:giteaDigestChangelogs","text":"

Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff

{\n  \"packageRules\": [\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"gitea-releases\",\n        \"gitea-tags\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    },\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"git-refs\",\n        \"git-tags\"\n      ],\n      \"matchJsonata\": [\n        \"$detectPlatform(sourceUrl) = 'gitea'\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersgithubdigestchangelogs","title":"helpers:githubDigestChangelogs","text":"

Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff

{\n  \"packageRules\": [\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"github-digest\",\n        \"github-releases\",\n        \"github-tags\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    },\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/compare/{{currentDigest}}..{{newDigest}}\",\n      \"matchDatasources\": [\n        \"git-refs\",\n        \"git-tags\"\n      ],\n      \"matchJsonata\": [\n        \"$detectPlatform(sourceUrl) = 'github'\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersgitlabdigestchangelogs","title":"helpers:gitlabDigestChangelogs","text":"

Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff

{\n  \"packageRules\": [\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/-/compare/{{currentDigest}}...{{newDigest}}\",\n      \"matchDatasources\": [\n        \"git-refs\",\n        \"git-tags\"\n      ],\n      \"matchJsonata\": [\n        \"$detectPlatform(sourceUrl) = 'gitlab'\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    },\n    {\n      \"changelogUrl\": \"{{sourceUrl}}/-/compare/{{currentDigest}}...{{newDigest}}\",\n      \"matchDatasources\": [\n        \"gitlab-releases\",\n        \"gitlab-tags\"\n      ],\n      \"matchUpdateTypes\": [\n        \"digest\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersgoxpackageschangeloglink","title":"helpers:goXPackagesChangelogLink","text":"

Correctly link to the source code for golang.org/x packages

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\n        \"gomod\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\",\n        \"minor\",\n        \"patch\"\n      ],\n      \"prBodyDefinitions\": {\n        \"Change\": \"{{#if (containsString depName 'golang.org/x/')}}[`{{{displayFrom}}}` \u2192 `{{{displayTo}}}`](https://cs.opensource.google/{{{replace '^golang\\\\.org' 'go' depName}}}/+/refs/tags/{{{currentValue}}}...refs/tags/{{{newValue}}}){{else}}`{{{displayFrom}}}` \u2192 `{{{displayTo}}}`{{/if}}\"\n      }\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helpersgoxpackagesnamelink","title":"helpers:goXPackagesNameLink","text":"

Link to pkg.go.dev/... for golang.org/x packages' title

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\n        \"gomod\"\n      ],\n      \"prBodyDefinitions\": {\n        \"Package\": \"{{#if (containsString depName 'golang.org/x/')}}[{{{depName}}}](https://pkg.go.dev/{{{depName}}}){{else}}{{{depNameLinked}}}{{/if}}\"\n      }\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helperspingithubactiondigests","title":"helpers:pinGitHubActionDigests","text":"

Pin github-action digests.

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\n        \"action\",\n        \"workflow\"\n      ],\n      \"pinDigests\": true\n    }\n  ]\n}\n
"},{"location":"presets-helpers/#helperspingithubactiondigeststosemver","title":"helpers:pinGitHubActionDigestsToSemver","text":"

Convert pinned GitHub Action digests to SemVer.

{\n  \"extends\": [\n    \"helpers:pinGitHubActionDigests\" // (1)!\n  ],\n  \"packageRules\": [\n    {\n      \"extractVersion\": \"^(?<version>v?\\\\d+\\\\.\\\\d+\\\\.\\\\d+)$\",\n      \"matchDepTypes\": [\n        \"action\",\n        \"workflow\"\n      ],\n      \"versioning\": \"regex:^v?(?<major>\\\\d+)(\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+))?$\"\n    }\n  ]\n}\n
  1. helpers:pinGitHubActionDigests: Pin github-action digests.
"},{"location":"presets-helpers/#helpersrenovatechangelog","title":"helpers:renovateChangelog","text":"

Provide a link to octochangelog's improved breakdown for Renovate's changelogs

{\n  \"packageRules\": [\n    {\n      \"matchSourceUrls\": [\n        \"https://github.com/renovatebot/renovate\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\",\n        \"minor\",\n        \"patch\"\n      ],\n      \"prBodyDefinitions\": {\n        \"Change\": \"[`{{{displayFrom}}}` \u2192 `{{{displayTo}}}`](https://octochangelog.com/compare?repo=renovatebot%2Frenovate&from={{ currentVersion }}&to={{ newVersion }})\"\n      }\n    }\n  ]\n}\n
"},{"location":"presets-mergeConfidence/","title":"MergeConfidence Presets","text":""},{"location":"presets-mergeConfidence/#mergeconfidenceage-confidence-badges","title":"mergeConfidence:age-confidence-badges","text":"

Show only the Age and Confidence Merge Confidence badges for pull requests.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"go\",\n        \"maven\",\n        \"npm\",\n        \"nuget\",\n        \"packagist\",\n        \"pypi\",\n        \"rubygems\"\n      ],\n      \"matchUpdateTypes\": [\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ],\n      \"prBodyColumns\": [\n        \"Package\",\n        \"Change\",\n        \"Age\",\n        \"Confidence\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-mergeConfidence/#mergeconfidenceall-badges","title":"mergeConfidence:all-badges","text":"

Show all Merge Confidence badges for pull requests.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"go\",\n        \"maven\",\n        \"npm\",\n        \"nuget\",\n        \"packagist\",\n        \"pypi\",\n        \"rubygems\"\n      ],\n      \"matchUpdateTypes\": [\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ],\n      \"prBodyColumns\": [\n        \"Package\",\n        \"Change\",\n        \"Age\",\n        \"Adoption\",\n        \"Passing\",\n        \"Confidence\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-monorepo/","title":"Monorepo Presets","text":""},{"location":"presets-monorepo/#monorepoaccounts","title":"monorepo:accounts","text":"

accounts monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/accounts-js/accounts\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoacot","title":"monorepo:acot","text":"

acot monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/acot-a11y/acot\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoag-grid","title":"monorepo:ag-grid","text":"

ag-grid monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ag-grid/ag-grid\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoalgolia-instantsearch","title":"monorepo:algolia-instantsearch","text":"

algolia-instantsearch monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/algolia/instantsearch\",\n    \"https://github.com/algolia/instantsearch.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoalgolia-react-instantsearch","title":"monorepo:algolia-react-instantsearch","text":"

algolia-react-instantsearch monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/algolia/react-instantsearch\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoalgoliasearch-autocomplete","title":"monorepo:algoliasearch-autocomplete","text":"

algoliasearch-autocomplete monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/algolia/autocomplete\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoalgoliasearch-client-javascript","title":"monorepo:algoliasearch-client-javascript","text":"

algoliasearch-client-javascript monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/algolia/algoliasearch-client-javascript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoanalog","title":"monorepo:analog","text":"

analog monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/analogjs/analog\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangular","title":"monorepo:angular","text":"

angular monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/angular/angular\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangular-cli","title":"monorepo:angular-cli","text":"

angular-cli monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/angular/angular-cli\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangular-eslint","title":"monorepo:angular-eslint","text":"

angular-eslint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/angular-eslint/angular-eslint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangularfire","title":"monorepo:angularfire","text":"

angularfire monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/angular/angularfire\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangularjs","title":"monorepo:angularjs","text":"

angularjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/angular/angular.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapache-lucene","title":"monorepo:apache-lucene","text":"

apache-lucene monorepo

{\n  \"matchSourceUrls\": [\n    \"https://gitbox.apache.org/repos/asf?p=lucene.git\",\n    \"https://github.com/apache/lucene\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapollo-server","title":"monorepo:apollo-server","text":"

apollo-server monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apollographql/apollo-server\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapolloclient","title":"monorepo:apolloclient","text":"

apolloclient monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apollographql/apollo-client\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoappium","title":"monorepo:appium","text":"

appium monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/appium/appium\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapplicationinsights-dotnet","title":"monorepo:applicationinsights-dotnet","text":"

applicationinsights-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Microsoft/ApplicationInsights-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcusbackground-jobs","title":"monorepo:arcus.background-jobs","text":"

arcus.background-jobs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.backgroundjobs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcusevent-grid","title":"monorepo:arcus.event-grid","text":"

arcus.event-grid monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.eventgrid\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcusmessaging","title":"monorepo:arcus.messaging","text":"

arcus.messaging monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.messaging\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcusobservability","title":"monorepo:arcus.observability","text":"

arcus.observability monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.observability\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcussecurity","title":"monorepo:arcus.security","text":"

arcus.security monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.security\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarcuswebapi","title":"monorepo:arcus.webapi","text":"

arcus.webapi monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arcus-azure/arcus.webapi\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarrow-kt","title":"monorepo:arrow-kt","text":"

arrow-kt monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/arrow-kt/arrow\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoarrow-rs","title":"monorepo:arrow-rs","text":"

arrow-rs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/arrow-rs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspire","title":"monorepo:aspire","text":"

aspire monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotnet/aspire\",\n    \"https://github.com/microsoft/aspire\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspnet-aspnetwebstack","title":"monorepo:aspnet aspnetwebstack","text":"

aspnet aspnetwebstack monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aspnet/AspNetWebStack\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspnet-extensions","title":"monorepo:aspnet extensions","text":"

aspnet extensions monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aspnet/Extensions\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspnet-api-versioning","title":"monorepo:aspnet-api-versioning","text":"

aspnet-api-versioning monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Microsoft/aspnet-api-versioning\",\n    \"https://github.com/dotnet/aspnet-api-versioning\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspnet-health-checks","title":"monorepo:aspnet-health-checks","text":"

aspnet-health-checks monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/xabaril/AspNetCore.Diagnostics.HealthChecks\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaspnet-security-oauth-providers","title":"monorepo:aspnet-security-oauth-providers","text":"

aspnet-security-oauth-providers monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoastro","title":"monorepo:astro","text":"

astro monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/withastro/astro\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoauto","title":"monorepo:auto","text":"

auto monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/intuit/auto\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoautofixture","title":"monorepo:autofixture","text":"

autofixture monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AutoFixture/AutoFixture\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoautomapper-dotnet","title":"monorepo:automapper-dotnet","text":"

automapper-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AutoMapper/AutoMapper\",\n    \"https://github.com/AutoMapper/AutoMapper.Extensions.Microsoft.DependencyInjection\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoavalonia","title":"monorepo:avalonia","text":"

avalonia monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AvaloniaUI/Avalonia\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-cdk","title":"monorepo:aws-cdk","text":"

aws-cdk monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-cdk\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-lambda-dotnet","title":"monorepo:aws-lambda-dotnet","text":"

aws-lambda-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-lambda-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-lambda-powertools-typescript","title":"monorepo:aws-lambda-powertools-typescript","text":"

aws-lambda-powertools-typescript monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/awslabs/aws-lambda-powertools-typescript\",\n    \"https://github.com/aws-powertools/powertools-lambda-typescript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-client-mock","title":"monorepo:aws-sdk-client-mock","text":"

aws-sdk-client-mock monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/m-radzikowski/aws-sdk-client-mock\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-go","title":"monorepo:aws-sdk-go","text":"

aws-sdk-go monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-sdk-go\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-go-v2","title":"monorepo:aws-sdk-go-v2","text":"

aws-sdk-go-v2 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-sdk-go-v2\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-js-v3","title":"monorepo:aws-sdk-js-v3","text":"

aws-sdk-js-v3 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-sdk-js-v3\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-net","title":"monorepo:aws-sdk-net","text":"

aws-sdk-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aws/aws-sdk-net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-sdk-rust","title":"monorepo:aws-sdk-rust","text":"

aws-sdk-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/smithy-lang/smithy-rs\",\n    \"https://github.com/awslabs/smithy-rs\",\n    \"https://github.com/awslabs/aws-sdk-rust\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoawsappsync","title":"monorepo:awsappsync","text":"

awsappsync monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/awslabs/aws-mobile-appsync-sdk-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaxum","title":"monorepo:axum","text":"

axum monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tokio-rs/axum\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-azure-libraries-for-net","title":"monorepo:azure azure-libraries-for-net","text":"

azure azure-libraries-for-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-libraries-for-net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-azure-sdk-for-net","title":"monorepo:azure azure-sdk-for-net","text":"

azure azure-sdk-for-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-azure-storage-net","title":"monorepo:azure azure-storage-net","text":"

azure azure-storage-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-storage-net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-android","title":"monorepo:azure-ad-microsoft-authentication-library-for-android","text":"

azure-ad-microsoft-authentication-library-for-android monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-android\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-dotnet","title":"monorepo:azure-ad-microsoft-authentication-library-for-dotnet","text":"

azure-ad-microsoft-authentication-library-for-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-go","title":"monorepo:azure-ad-microsoft-authentication-library-for-go","text":"

azure-ad-microsoft-authentication-library-for-go monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-go\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-java","title":"monorepo:azure-ad-microsoft-authentication-library-for-java","text":"

azure-ad-microsoft-authentication-library-for-java monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-java\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-js","title":"monorepo:azure-ad-microsoft-authentication-library-for-js","text":"

azure-ad-microsoft-authentication-library-for-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-objc","title":"monorepo:azure-ad-microsoft-authentication-library-for-objc","text":"

azure-ad-microsoft-authentication-library-for-objc monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-objc\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-ad-microsoft-authentication-library-for-python","title":"monorepo:azure-ad-microsoft-authentication-library-for-python","text":"

azure-ad-microsoft-authentication-library-for-python monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-authentication-library-for-python\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-functions-dotnet-worker","title":"monorepo:azure-functions-dotnet-worker","text":"

azure-functions-dotnet-worker monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-functions-dotnet-worker\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-android","title":"monorepo:azure-sdk-for-android","text":"

azure-sdk-for-android monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-android\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-c","title":"monorepo:azure-sdk-for-c","text":"

azure-sdk-for-c monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-c\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-cpp","title":"monorepo:azure-sdk-for-cpp","text":"

azure-sdk-for-cpp monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-cpp\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-go","title":"monorepo:azure-sdk-for-go","text":"

azure-sdk-for-go monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-go\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-ios","title":"monorepo:azure-sdk-for-ios","text":"

azure-sdk-for-ios monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-ios\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-java","title":"monorepo:azure-sdk-for-java","text":"

azure-sdk-for-java monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-java\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-js","title":"monorepo:azure-sdk-for-js","text":"

azure-sdk-for-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-python","title":"monorepo:azure-sdk-for-python","text":"

azure-sdk-for-python monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-python\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoazure-sdk-for-rust","title":"monorepo:azure-sdk-for-rust","text":"

azure-sdk-for-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Azure/azure-sdk-for-rust\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobabel","title":"monorepo:babel","text":"

babel monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/babel/babel\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobackstage","title":"monorepo:backstage","text":"

backstage monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/backstage/backstage\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobaset","title":"monorepo:baset","text":"

baset monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/igmat/baset\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobetter-auth","title":"monorepo:better-auth","text":"

better-auth monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/better-auth/better-auth\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobrave","title":"monorepo:brave","text":"

brave monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/openzipkin/brave\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobugsnag-js","title":"monorepo:bugsnag-js","text":"

bugsnag-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/bugsnag/bugsnag-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobull-board","title":"monorepo:bull-board","text":"

bull-board monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/felixmosh/bull-board\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocake","title":"monorepo:cake","text":"

cake monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/cake-build/cake\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocake-issues","title":"monorepo:cake-issues","text":"

cake-issues monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/cake-contrib/Cake.Issues\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocapacitor","title":"monorepo:capacitor","text":"

capacitor monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ionic-team/capacitor\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocedar","title":"monorepo:cedar","text":"

cedar monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/cedarjs/cedar\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepochakra-ui","title":"monorepo:chakra-ui","text":"

chakra-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/chakra-ui/chakra-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepochromely","title":"monorepo:chromely","text":"

chromely monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/chromelyapps/Chromely\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocitation-js","title":"monorepo:citation-js","text":"

citation-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/citation-js/citation-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepockeditor","title":"monorepo:ckeditor","text":"

ckeditor monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ckeditor/ckeditor5\",\n    \"https://github.com/ckeditor/ckeditor5-premium-features\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoclarity","title":"monorepo:clarity","text":"

clarity monorepo

{\n  \"matchPackageNames\": [\n    \"/^@cds//\",\n    \"/^@clr//\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoclearscript","title":"monorepo:clearscript","text":"

clearscript monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/ClearScript\",\n    \"https://github.com/Microsoft/ClearScript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocommitlint","title":"monorepo:commitlint","text":"

commitlint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/conventional-changelog/commitlint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoconfect","title":"monorepo:confect","text":"

confect monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/rjdellecese/confect\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoconform","title":"monorepo:conform","text":"

conform monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/edmundhung/conform\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocontentful-rich-text","title":"monorepo:contentful-rich-text","text":"

contentful-rich-text monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/contentful/rich-text\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoconvex","title":"monorepo:convex","text":"

convex monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/get-convex/convex-backend\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepocspell","title":"monorepo:cspell","text":"

cspell monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/streetsidesoftware/cspell\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatadog-browser-sdk","title":"monorepo:datadog-browser-sdk","text":"

datadog-browser-sdk monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataDog/browser-sdk\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatafusion","title":"monorepo:datafusion","text":"

datafusion monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/datafusion\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net","title":"monorepo:datatables-net","text":"

datatables-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/DataTablesSrc\",\n    \"https://github.com/DataTables/Dist-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-autofill","title":"monorepo:datatables-net-autofill","text":"

datatables-net-autofill monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/AutoFill\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-AutoFill-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-buttons","title":"monorepo:datatables-net-buttons","text":"

datatables-net-buttons monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/Buttons\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-Buttons-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-colreorder","title":"monorepo:datatables-net-colreorder","text":"

datatables-net-colreorder monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/ColReorder\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-ColReorder-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-fixedcolumns","title":"monorepo:datatables-net-fixedcolumns","text":"

datatables-net-fixedcolumns monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/FixedColumns\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedColumns-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-fixedheader","title":"monorepo:datatables-net-fixedheader","text":"

datatables-net-fixedheader monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/FixedHeader\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-FixedHeader-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-keytable","title":"monorepo:datatables-net-keytable","text":"

datatables-net-keytable monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/KeyTable\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-KeyTable-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-responsive","title":"monorepo:datatables-net-responsive","text":"

datatables-net-responsive monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/Responsive\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-Responsive-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-rowgroup","title":"monorepo:datatables-net-rowgroup","text":"

datatables-net-rowgroup monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/RowGroup\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-RowGroup-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-rowreorder","title":"monorepo:datatables-net-rowreorder","text":"

datatables-net-rowreorder monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/RowReorder\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-RowReorder-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-scroller","title":"monorepo:datatables-net-scroller","text":"

datatables-net-scroller monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/Scroller\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-Scroller-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-searchbuilder","title":"monorepo:datatables-net-searchbuilder","text":"

datatables-net-searchbuilder monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/SearchBuilder\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchBuilder-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-searchpanes","title":"monorepo:datatables-net-searchpanes","text":"

datatables-net-searchpanes monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/SearchPanes\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-SearchPanes-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-select","title":"monorepo:datatables-net-select","text":"

datatables-net-select monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/Select\",\n    \"https://github.com/DataTables/Dist-DataTables-Select\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-Select-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodatatables-net-staterestore","title":"monorepo:datatables-net-staterestore","text":"

datatables-net-staterestore monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DataTables/StateRestore\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-Bootstrap\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-Bootstrap4\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-Bootstrap5\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-Bulma\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-DataTables\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-Foundation\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-SemanticUI\",\n    \"https://github.com/DataTables/Dist-DataTables-StateRestore-jQueryUI\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodate-io","title":"monorepo:date-io","text":"

date-io monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dmtrKovalenko/date-io\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodeck-gl","title":"monorepo:deck-gl","text":"

deck-gl monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/visgl/deck.gl\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodeno","title":"monorepo:deno","text":"

deno monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/denoland/deno\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodevextreme-reactive","title":"monorepo:devextreme-reactive","text":"

devextreme-reactive monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DevExpress/devextreme-reactive\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodnd-kit","title":"monorepo:dnd-kit","text":"

dnd-kit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/clauderic/dnd-kit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodocusaurus","title":"monorepo:docusaurus","text":"

docusaurus monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/facebook/docusaurus\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodot-swashbuckle","title":"monorepo:dot-swashbuckle","text":"

dot-swashbuckle monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Havunen/DotSwashbuckle\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodotnet","title":"monorepo:dotnet","text":"

dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://asp.net/\",\n    \"https://docs.microsoft.com/ef/core/\",\n    \"https://dot.net/\",\n    \"https://github.com/dotnet/aspnetcore\",\n    \"https://github.com/dotnet/dotnet\",\n    \"https://github.com/dotnet/efcore\",\n    \"https://github.com/dotnet/extensions\",\n    \"https://github.com/dotnet/fsharp\",\n    \"https://github.com/dotnet/maui\",\n    \"https://github.com/dotnet/msbuild\",\n    \"https://github.com/dotnet/roslyn\",\n    \"https://github.com/dotnet/runtime\",\n    \"https://github.com/dotnet/scaffolding\",\n    \"https://github.com/dotnet/sdk\",\n    \"https://github.com/dotnet/windowsdesktop\",\n    \"https://github.com/dotnet/winforms\",\n    \"https://github.com/dotnet/wpf\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodotnet-azure-ad-identitymodel-extensions","title":"monorepo:dotnet-azure-ad-identitymodel-extensions","text":"

dotnet-azure-ad-identitymodel-extensions monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodotnet-azure-ad-microsoft-identity-web","title":"monorepo:dotnet-azure-ad-microsoft-identity-web","text":"

dotnet-azure-ad-microsoft-identity-web monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/AzureAD/microsoft-identity-web\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodotnet-wcf","title":"monorepo:dotnet-wcf","text":"

dotnet-wcf monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotnet/wcf\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodotnetcore-cap","title":"monorepo:dotnetcore-cap","text":"

dotnetcore-cap monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotnetcore/CAP\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepodropwizard","title":"monorepo:dropwizard","text":"

dropwizard monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dropwizard/dropwizard\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoduende-identityserver","title":"monorepo:duende-identityserver","text":"

duende-identityserver monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/DuendeSoftware/IdentityServer\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoeffect","title":"monorepo:effect","text":"

effect monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Effect-TS/effect-smol\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoelastic-apm-agent-rum-js","title":"monorepo:elastic-apm-agent-rum-js","text":"

elastic-apm-agent-rum-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/elastic/apm-agent-rum-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoelastic-ecs-dotnet","title":"monorepo:elastic-ecs-dotnet","text":"

elastic-ecs-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/elastic/ecs-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoelectron-forge","title":"monorepo:electron-forge","text":"

electron-forge monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/electron-userland/electron-forge\",\n    \"https://github.com/electron/forge\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoember-decorators","title":"monorepo:ember-decorators","text":"

ember-decorators monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ember-decorators/ember-decorators\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoembla-carousel","title":"monorepo:embla-carousel","text":"

embla-carousel monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/davidjerleke/embla-carousel\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoemojibase","title":"monorepo:emojibase","text":"

emojibase monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/milesj/emojibase\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoemotion","title":"monorepo:emotion","text":"

emotion monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/emotion-js/emotion\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoenumeratum","title":"monorepo:enumeratum","text":"

enumeratum monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lloydmeta/enumeratum\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoenvelop","title":"monorepo:envelop","text":"

envelop monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/n1ru4l/envelop\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoerror-prone","title":"monorepo:error-prone","text":"

error-prone monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/google/error-prone\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoerror-prone-support","title":"monorepo:error-prone-support","text":"

error-prone-support monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/PicnicSupermarket/error-prone-support\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoeslint","title":"monorepo:eslint","text":"

eslint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/eslint/eslint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoeslint-config-globex","title":"monorepo:eslint-config-globex","text":"

eslint-config-globex monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/GlobexDesignsInc/eslint-config-globex\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoeslint-stylistic","title":"monorepo:eslint-stylistic","text":"

eslint-stylistic monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/eslint-stylistic/eslint-stylistic\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoexpo","title":"monorepo:expo","text":"

expo monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/expo/expo\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofabric-chaincode-node","title":"monorepo:fabric-chaincode-node","text":"

fabric-chaincode-node monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hyperledger/fabric-chaincode-node\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofabric8-kubernetes-client","title":"monorepo:fabric8-kubernetes-client","text":"

fabric8-kubernetes-client monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/fabric8io/kubernetes-client\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofaro-web-sdk","title":"monorepo:faro-web-sdk","text":"

faro-web-sdk monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/grafana/faro-web-sdk\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofastendpoints","title":"monorepo:fastendpoints","text":"

fastendpoints monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/FastEndpoints/FastEndpoints\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofeathers","title":"monorepo:feathers","text":"

feathers monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/feathersjs/feathers\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofeaturemanagement-dotnet","title":"monorepo:featuremanagement-dotnet","text":"

featuremanagement-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/FeatureManagement-Dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofeign","title":"monorepo:feign","text":"

feign monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/OpenFeign/feign\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofela","title":"monorepo:fela","text":"

fela monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/robinweser/fela\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofimbullinter","title":"monorepo:fimbullinter","text":"

fimbullinter monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/fimbullinter/wotan\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoflipper","title":"monorepo:flipper","text":"

flipper monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/flippercloud/flipper\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoflopflip","title":"monorepo:flopflip","text":"

flopflip monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tdeekens/flopflip\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoflue","title":"monorepo:flue","text":"

flue monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/withastro/flue\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofontsource","title":"monorepo:fontsource","text":"

fontsource monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/fontsource/fontsource\",\n    \"https://github.com/fontsource/font-files\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoformatjs","title":"monorepo:formatjs","text":"

formatjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/formatjs/formatjs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoframework7","title":"monorepo:framework7","text":"

framework7 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/framework7io/framework7\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofunogram","title":"monorepo:funogram","text":"

funogram monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Dolfik1/Funogram\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofusioncache","title":"monorepo:fusioncache","text":"

fusioncache monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ZiggyCreatures/FusionCache\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogatsby","title":"monorepo:gatsby","text":"

gatsby monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/gatsbyjs/gatsby\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogitbeaker","title":"monorepo:gitbeaker","text":"

gitbeaker monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/jdalrymple/gitbeaker\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogithub-workflows-kt","title":"monorepo:github-workflows-kt","text":"

github-workflows-kt monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/typesafegithub/github-workflows-kt\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogo-cloud","title":"monorepo:go-cloud","text":"

go-cloud monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/google/go-cloud\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogomock","title":"monorepo:gomock","text":"

gomock monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/uber-go/mock\",\n    \"https://github.com/uber/mock\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogoogle-api-dotnet-client","title":"monorepo:google-api-dotnet-client","text":"

google-api-dotnet-client monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/googleapis/google-api-dotnet-client\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogoogle-cloud-rust","title":"monorepo:google-cloud-rust","text":"

google-cloud-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/googleapis/google-cloud-rust\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepografana","title":"monorepo:grafana","text":"

grafana monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/grafana/grafana\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographiql","title":"monorepo:graphiql","text":"

graphiql monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/graphql/graphiql\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-hive-gateway","title":"monorepo:graphql-hive-gateway","text":"

graphql-hive-gateway monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/graphql-hive/gateway\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-mesh","title":"monorepo:graphql-mesh","text":"

graphql-mesh monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Urigo/graphql-mesh\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-modules","title":"monorepo:graphql-modules","text":"

graphql-modules monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Urigo/graphql-modules\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-platform","title":"monorepo:graphql-platform","text":"

graphql-platform monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ChilliCream/graphql-platform\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-tools","title":"monorepo:graphql-tools","text":"

graphql-tools monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ardatan/graphql-tools\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographql-yoga","title":"monorepo:graphql-yoga","text":"

graphql-yoga monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotansimha/graphql-yoga\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepographqlcodegenerator","title":"monorepo:graphqlcodegenerator","text":"

graphqlcodegenerator monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotansimha/graphql-code-generator-community\",\n    \"https://github.com/dotansimha/graphql-code-generator\",\n    \"https://github.com/dotansimha/graphql-codegen\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogreenmail","title":"monorepo:greenmail","text":"

greenmail monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/greenmail-mail-test/greenmail\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogroovy","title":"monorepo:groovy","text":"

groovy monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/groovy\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogrpc-dotnet","title":"monorepo:grpc-dotnet","text":"

grpc-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/grpc/grpc-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogrpc-java","title":"monorepo:grpc-java","text":"

grpc-java monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/grpc/grpc-java\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepogstreamer-rust","title":"monorepo:gstreamer-rust","text":"

gstreamer-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://gitlab.freedesktop.org/gstreamer/gstreamer-rs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoguava","title":"monorepo:guava","text":"

guava monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/google/guava\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohangfire","title":"monorepo:hangfire","text":"

hangfire monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/HangfireIO/Hangfire\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohappy-dom","title":"monorepo:happy-dom","text":"

happy-dom monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/capricorn86/happy-dom\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohibernate-models","title":"monorepo:hibernate-models","text":"

hibernate-models monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hibernate/hibernate-models\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohibernate-orm","title":"monorepo:hibernate-orm","text":"

hibernate-orm monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hibernate/hibernate-orm\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohibernate-search","title":"monorepo:hibernate-search","text":"

hibernate-search monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hibernate/hibernate-search\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohibernate-tools","title":"monorepo:hibernate-tools","text":"

hibernate-tools monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hibernate/hibernate-tools\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohickory-dns","title":"monorepo:hickory-dns","text":"

hickory-dns monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hickory-dns/hickory-dns\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohocuspocus","title":"monorepo:hocuspocus","text":"

hocuspocus monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ueberdosis/hocuspocus\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohtml-eslint","title":"monorepo:html-eslint","text":"

html-eslint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/yeonjuan/html-eslint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohumanizer","title":"monorepo:humanizer","text":"

humanizer monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Humanizr/Humanizer\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoimmich","title":"monorepo:immich","text":"

immich monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/immich-app/immich\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoinfrastructure-ui","title":"monorepo:infrastructure-ui","text":"

infrastructure-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/instructure/instructure-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoionic-native","title":"monorepo:ionic-native","text":"

ionic-native monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ionic-team/ionic-native\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoistanbuljs","title":"monorepo:istanbuljs","text":"

istanbuljs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/istanbuljs/istanbuljs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoistio","title":"monorepo:istio","text":"

istio monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/istio/istio\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojackson","title":"monorepo:jackson","text":"

jackson monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/FasterXML/jackson\",\n    \"https://github.com/FasterXML/jackson-annotations\",\n    \"https://github.com/FasterXML/jackson-bom\",\n    \"https://github.com/FasterXML/jackson-core\",\n    \"https://github.com/FasterXML/jackson-databind\",\n    \"https://github.com/FasterXML/jackson-dataformat-xml\",\n    \"https://github.com/FasterXML/jackson-dataformats-binary\",\n    \"https://github.com/FasterXML/jackson-dataformats-text\",\n    \"https://github.com/FasterXML/jackson-datatype-hibernate\",\n    \"https://github.com/FasterXML/jackson-datatype-joda\",\n    \"https://github.com/FasterXML/jackson-datatypes-collections\",\n    \"https://github.com/FasterXML/jackson-datatypes-misc\",\n    \"https://github.com/FasterXML/jackson-jakarta-rs-providers\",\n    \"https://github.com/FasterXML/jackson-jaxrs-providers\",\n    \"https://github.com/FasterXML/jackson-jr\",\n    \"https://github.com/FasterXML/jackson-module-jsonSchema\",\n    \"https://github.com/FasterXML/jackson-module-kotlin\",\n    \"https://github.com/FasterXML/jackson-module-scala\",\n    \"https://github.com/FasterXML/jackson-modules-base\",\n    \"https://github.com/FasterXML/jackson-modules-java8\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojasmine","title":"monorepo:jasmine","text":"

jasmine monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/jasmine/jasmine\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojavafx","title":"monorepo:javafx","text":"

javafx monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/openjdk/jfx\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojavahamcrest","title":"monorepo:javahamcrest","text":"

javahamcrest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hamcrest/JavaHamcrest\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojavascriptengineswitcher","title":"monorepo:javascriptengineswitcher","text":"

javascriptengineswitcher monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Taritsyn/JavaScriptEngineSwitcher\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojaxb-ri","title":"monorepo:jaxb-ri","text":"

jaxb-ri monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/eclipse-ee4j/jaxb-ri\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojersey","title":"monorepo:jersey","text":"

jersey monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/eclipse-ee4j/jersey\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojest","title":"monorepo:jest","text":"

jest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/facebook/jest\",\n    \"https://github.com/jestjs/jest\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojetty","title":"monorepo:jetty","text":"

jetty monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/jetty/jetty.project\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojna","title":"monorepo:jna","text":"

jna monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/java-native-access/jna\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojson-smart-v2","title":"monorepo:json-smart-v2","text":"

json-smart-v2 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/netplex/json-smart-v2\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojsonforms","title":"monorepo:jsonforms","text":"

jsonforms monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/eclipsesource/jsonforms\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojsplumb","title":"monorepo:jsplumb","text":"

jsplumb monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/jsplumb/jsplumb\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojunior","title":"monorepo:junior","text":"

junior monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/getsentry/junior\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepojunit-framework","title":"monorepo:junit-framework","text":"

junit-framework monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/junit-team/junit5\",\n    \"https://github.com/junit-team/junit-framework\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokernelmemory","title":"monorepo:kernelmemory","text":"

kernelmemory monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/kernel-memory\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokiota","title":"monorepo:kiota","text":"

kiota monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/kiota\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokotlin","title":"monorepo:kotlin","text":"

kotlin monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/JetBrains/kotlin\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokotlinx-coroutines","title":"monorepo:kotlinx-coroutines","text":"

kotlinx-coroutines monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Kotlin/kotlinx.coroutines\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokroki","title":"monorepo:kroki","text":"

kroki monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/yuzutech/kroki\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoksp","title":"monorepo:ksp","text":"

ksp monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/google/ksp\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoktor","title":"monorepo:ktor","text":"

ktor monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ktorio/ktor\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokubb","title":"monorepo:kubb","text":"

kubb monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/kubb-labs/kubb\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepokubernetes","title":"monorepo:kubernetes","text":"

kubernetes monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/kubernetes/api\",\n    \"https://github.com/kubernetes/apiextensions-apiserver\",\n    \"https://github.com/kubernetes/apimachinery\",\n    \"https://github.com/kubernetes/apiserver\",\n    \"https://github.com/kubernetes/cli-runtime\",\n    \"https://github.com/kubernetes/client-go\",\n    \"https://github.com/kubernetes/cloud-provider\",\n    \"https://github.com/kubernetes/cluster-bootstrap\",\n    \"https://github.com/kubernetes/code-generator\",\n    \"https://github.com/kubernetes/component-base\",\n    \"https://github.com/kubernetes/component-helpers\",\n    \"https://github.com/kubernetes/controller-manager\",\n    \"https://github.com/kubernetes/cri-api\",\n    \"https://github.com/kubernetes/cri-client\",\n    \"https://github.com/kubernetes/csi-translation-lib\",\n    \"https://github.com/kubernetes/dynamic-resource-allocation\",\n    \"https://github.com/kubernetes/endpointslice\",\n    \"https://github.com/kubernetes/externaljwt\",\n    \"https://github.com/kubernetes/kms\",\n    \"https://github.com/kubernetes/kube-aggregator\",\n    \"https://github.com/kubernetes/kube-controller-manager\",\n    \"https://github.com/kubernetes/kube-proxy\",\n    \"https://github.com/kubernetes/kube-scheduler\",\n    \"https://github.com/kubernetes/kubectl\",\n    \"https://github.com/kubernetes/kubelet\",\n    \"https://github.com/kubernetes/legacy-cloud-providers\",\n    \"https://github.com/kubernetes/metrics\",\n    \"https://github.com/kubernetes/mount-utils\",\n    \"https://github.com/kubernetes/pod-security-admission\",\n    \"https://github.com/kubernetes/sample-apiserver\",\n    \"https://github.com/kubernetes/sample-cli-plugin\",\n    \"https://github.com/kubernetes/sample-controller\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolamar","title":"monorepo:lamar","text":"

lamar monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/JasperFx/lamar\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolangchain4j","title":"monorepo:langchain4j","text":"

langchain4j monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/langchain4j/langchain4j\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolerna","title":"monorepo:lerna","text":"

lerna monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lerna/lerna\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolerna-lite","title":"monorepo:lerna-lite","text":"

lerna-lite monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lerna-lite/lerna-lite\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolexical","title":"monorepo:lexical","text":"

lexical monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/facebook/lexical\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolinguijs","title":"monorepo:linguijs","text":"

linguijs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lingui/js-lingui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolinkifyjs","title":"monorepo:linkifyjs","text":"

linkifyjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nfrasser/linkifyjs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolog4j2","title":"monorepo:log4j2","text":"

log4j2 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/logging-log4j2\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepologback","title":"monorepo:logback","text":"

logback monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/qos-ch/logback\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepologtape","title":"monorepo:logtape","text":"

logtape monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dahlia/logtape\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoloopback","title":"monorepo:loopback","text":"

loopback monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/strongloop/loopback-next\",\n    \"https://github.com/loopbackio/loopback-next\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolrnwebcomponents","title":"monorepo:lrnwebcomponents","text":"

lrnwebcomponents monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/elmsln/lrnwebcomponents\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolucide","title":"monorepo:lucide","text":"

lucide monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lucide-icons/lucide\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomailing","title":"monorepo:mailing","text":"

mailing monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/sofn-xyz/mailing\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomantine","title":"monorepo:mantine","text":"

mantine monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mantinedev/mantine\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomapstruct","title":"monorepo:mapstruct","text":"

mapstruct monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mapstruct/mapstruct\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomarten","title":"monorepo:marten","text":"

marten monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/JasperFx/marten\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomasstransit","title":"monorepo:masstransit","text":"

masstransit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/MassTransit/MassTransit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomaterial-components-web","title":"monorepo:material-components-web","text":"

material-components-web monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/material-components/material-components-web\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomaterial-ui","title":"monorepo:material-ui","text":"

material-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mui-org/material-ui\",\n    \"https://github.com/mui/material-ui\",\n    \"https://github.com/mui/mui-x\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomdc-react","title":"monorepo:mdc-react","text":"

mdc-react monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/material-components/material-components-web-react\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomdx","title":"monorepo:mdx","text":"

mdx monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mdx-js/mdx\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomiddy-js","title":"monorepo:middy-js","text":"

middy-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/middyjs/middy\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomikro-orm","title":"monorepo:mikro-orm","text":"

mikro-orm monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mikro-orm/mikro-orm\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoml-dotnet","title":"monorepo:ml-dotnet","text":"

ml-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotnet/machinelearning\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomockito","title":"monorepo:mockito","text":"

mockito monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mockito/mockito\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomongo-csharp-driver","title":"monorepo:mongo-csharp-driver","text":"

mongo-csharp-driver monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mongodb/mongo-csharp-driver\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomongo-java-driver","title":"monorepo:mongo-java-driver","text":"

mongo-java-driver monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mongodb/mongo-java-driver\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomstest","title":"monorepo:mstest","text":"

mstest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/testfx\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepomutation-testing-elements","title":"monorepo:mutation-testing-elements","text":"

mutation-testing-elements monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/stryker-mutator/mutation-testing-elements\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponest","title":"monorepo:nest","text":"

nest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nestjs/config\",\n    \"https://github.com/nestjs/nest\",\n    \"https://github.com/nestjs/nest-cli\",\n    \"https://github.com/nestjs/passport\",\n    \"https://github.com/nestjs/schematics\",\n    \"https://github.com/nestjs/terminus\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponest-graphql","title":"monorepo:nest-graphql","text":"

nest-graphql monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nestjs/graphql\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponetty","title":"monorepo:netty","text":"

netty monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/netty/netty\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponeutrino","title":"monorepo:neutrino","text":"

neutrino monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/neutrinojs/neutrino\",\n    \"https://github.com/mozilla-neutrino/neutrino-dev\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponexpect","title":"monorepo:nexpect","text":"

nexpect monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/fluffynuts/NExpect\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponextjs","title":"monorepo:nextjs","text":"

nextjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/zeit/next.js\",\n    \"https://github.com/vercel/next.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponextra","title":"monorepo:nextra","text":"

nextra monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/shuding/nextra\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepongx-cookie-service","title":"monorepo:ngx-cookie-service","text":"

ngx-cookie-service monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/stevermeister/ngx-cookie-service\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepongx-formly","title":"monorepo:ngx-formly","text":"

ngx-formly monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ngx-formly/ngx-formly\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepongxs-store","title":"monorepo:ngxs-store","text":"

ngxs-store monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ngxs/store\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponivo","title":"monorepo:nivo","text":"

nivo monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/plouc/nivo\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponjson-schema","title":"monorepo:njson-schema","text":"

njson-schema monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/RicoSuter/NJsonSchema\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponswag","title":"monorepo:nswag","text":"

nswag monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/RicoSuter/NSwag\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponuget","title":"monorepo:nuget","text":"

nuget monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/NuGet/NuGet.Client\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponuke-build","title":"monorepo:nuke-build","text":"

nuke-build monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nuke-build/nuke\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponuxtjs","title":"monorepo:nuxtjs","text":"

nuxtjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nuxt/nuxt.js\",\n    \"https://github.com/nuxt/nuxt\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepookhttp","title":"monorepo:okhttp","text":"

okhttp monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/square/okhttp\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopenapi-dotnet","title":"monorepo:openapi-dotnet","text":"

openapi-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/OpenAPI.NET\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopencost","title":"monorepo:opencost","text":"

opencost monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/opencost/opencost\",\n    \"https://github.com/opencost/opencost-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopeniddict","title":"monorepo:openiddict","text":"

openiddict monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/openiddict/openiddict-core\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-dotnet","title":"monorepo:opentelemetry-dotnet","text":"

opentelemetry-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-dotnet-contrib","title":"monorepo:opentelemetry-dotnet-contrib","text":"

opentelemetry-dotnet-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-dotnet-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-erlang","title":"monorepo:opentelemetry-erlang","text":"

opentelemetry-erlang monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-erlang\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-erlang-contrib","title":"monorepo:opentelemetry-erlang-contrib","text":"

opentelemetry-erlang-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-erlang-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-go","title":"monorepo:opentelemetry-go","text":"

opentelemetry-go monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-go\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-go-contrib","title":"monorepo:opentelemetry-go-contrib","text":"

opentelemetry-go-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-go-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-java","title":"monorepo:opentelemetry-java","text":"

opentelemetry-java monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-java\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-java-contrib","title":"monorepo:opentelemetry-java-contrib","text":"

opentelemetry-java-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-java-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-js","title":"monorepo:opentelemetry-js","text":"

opentelemetry-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-js-contrib","title":"monorepo:opentelemetry-js-contrib","text":"

opentelemetry-js-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-js-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-php","title":"monorepo:opentelemetry-php","text":"

opentelemetry-php monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-php\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-php-contrib","title":"monorepo:opentelemetry-php-contrib","text":"

opentelemetry-php-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-php-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-python","title":"monorepo:opentelemetry-python","text":"

opentelemetry-python monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-python\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-python-contrib","title":"monorepo:opentelemetry-python-contrib","text":"

opentelemetry-python-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-python-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-rust","title":"monorepo:opentelemetry-rust","text":"

opentelemetry-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-rust\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoopentelemetry-rust-contrib","title":"monorepo:opentelemetry-rust-contrib","text":"

opentelemetry-rust-contrib monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/open-telemetry/opentelemetry-rust-contrib\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoorleans","title":"monorepo:orleans","text":"

orleans monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/dotnet/orleans\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoorpc","title":"monorepo:orpc","text":"

orpc monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/middleapi/orpc\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopanda-css","title":"monorepo:panda-css","text":"

panda-css monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/chakra-ui/panda\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoparcel","title":"monorepo:parcel","text":"

parcel monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/parcel-bundler/parcel\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopayloadcms","title":"monorepo:payloadcms","text":"

payloadcms monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/payloadcms/payload\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopdfme","title":"monorepo:pdfme","text":"

pdfme monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pdfme/pdfme\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopercy-cli","title":"monorepo:percy-cli","text":"

percy-cli monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/percy/cli\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopicassojs","title":"monorepo:picassojs","text":"

picassojs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/qlik-oss/picasso.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopixijs","title":"monorepo:pixijs","text":"

pixijs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pixijs/pixi.js\",\n    \"https://github.com/pixijs/pixijs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoplaywright","title":"monorepo:playwright","text":"

playwright monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/playwright\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoplaywright-dotnet","title":"monorepo:playwright-dotnet","text":"

playwright-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/playwright-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopnpcore","title":"monorepo:pnpcore","text":"

pnpcore monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pnp/pnpcore\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopnpjs","title":"monorepo:pnpjs","text":"

pnpjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pnp/pnpjs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopolly","title":"monorepo:polly","text":"

polly monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/App-vNext/Polly\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopollyjs","title":"monorepo:pollyjs","text":"

pollyjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Netflix/pollyjs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopothos","title":"monorepo:pothos","text":"

pothos monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hayes/pothos\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopouchdb","title":"monorepo:pouchdb","text":"

pouchdb monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pouchdb/pouchdb\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopowermock","title":"monorepo:powermock","text":"

powermock monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/powermock/powermock\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoprisma","title":"monorepo:prisma","text":"

prisma monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/prisma/orm\",\n    \"https://github.com/prisma/prisma\",\n    \"https://github.com/prisma/prisma-cli\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoprometheus-net","title":"monorepo:prometheus-net","text":"

prometheus-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/prometheus-net/prometheus-net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepopromster","title":"monorepo:promster","text":"

promster monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tdeekens/promster\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoprotobuf","title":"monorepo:protobuf","text":"

protobuf monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/protocolbuffers/protobuf\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoquartznet","title":"monorepo:quartznet","text":"

quartznet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/quartznet/quartznet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporadix-ui-primitives","title":"monorepo:radix-ui-primitives","text":"

radix-ui-primitives monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/radix-ui/primitives\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeach-ui","title":"monorepo:reach-ui","text":"

reach-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reach/reach-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact","title":"monorepo:react","text":"

react monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/facebook/react\",\n    \"https://github.com/react/react\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-admin","title":"monorepo:react-admin","text":"

react-admin monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/marmelab/react-admin\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-apollo","title":"monorepo:react-apollo","text":"

react-apollo monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apollographql/react-apollo\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-dnd","title":"monorepo:react-dnd","text":"

react-dnd monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/react-dnd/react-dnd\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-email","title":"monorepo:react-email","text":"

react-email monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/resend/react-email\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-navigation","title":"monorepo:react-navigation","text":"

react-navigation monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/react-navigation/react-navigation\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-page","title":"monorepo:react-page","text":"

react-page monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/react-page/react-page\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-rails","title":"monorepo:react-rails","text":"

react-rails monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reactjs/react-rails\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-router","title":"monorepo:react-router","text":"

react-router monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ReactTraining/react-router\",\n    \"https://github.com/remix-run/react-router\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-spectrum","title":"monorepo:react-spectrum","text":"

react-spectrum monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/adobe/react-spectrum\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeact-spring","title":"monorepo:react-spring","text":"

react-spring monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/pmndrs/react-spring\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeactivestack-cookies","title":"monorepo:reactivestack-cookies","text":"

reactivestack-cookies monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reactivestack/cookies\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeakit","title":"monorepo:reakit","text":"

reakit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reakit/reakit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporedwood","title":"monorepo:redwood","text":"

redwood monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/redwoodjs/redwood\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporefit","title":"monorepo:refit","text":"

refit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reactiveui/refit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporeg-suit","title":"monorepo:reg-suit","text":"

reg-suit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/reg-viz/reg-suit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporemark","title":"monorepo:remark","text":"

remark monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/remarkjs/remark\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporemix","title":"monorepo:remix","text":"

remix monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/remix-run/remix\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporetrofit","title":"monorepo:retrofit","text":"

retrofit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/square/retrofit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporiver","title":"monorepo:river","text":"

river monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/riverqueue/river\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporjsf","title":"monorepo:rjsf","text":"

rjsf monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/rjsf-team/react-jsonschema-form\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporouter5","title":"monorepo:router5","text":"

router5 monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/router5/router5\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporspack","title":"monorepo:rspack","text":"

rspack monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/web-infra-dev/rspack\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporuby-on-rails","title":"monorepo:ruby-on-rails","text":"

ruby-on-rails monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/rails/rails\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporust-analyzer","title":"monorepo:rust-analyzer","text":"

rust-analyzer monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/rust-lang/rust-analyzer\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporust-futures","title":"monorepo:rust-futures","text":"

rust-futures monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/rust-lang/futures-rs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporust-wasm-bindgen","title":"monorepo:rust-wasm-bindgen","text":"

rust-wasm-bindgen monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/wasm-bindgen/wasm-bindgen\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposanity","title":"monorepo:sanity","text":"

sanity monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/sanity-io/sanity\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposcaffdog","title":"monorepo:scaffdog","text":"

scaffdog monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/scaffdog/scaffdog\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposcalar","title":"monorepo:scalar","text":"

scalar monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/scalar/scalar\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposea-orm","title":"monorepo:sea-orm","text":"

sea-orm monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/SeaQL/sea-orm\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposecretlint","title":"monorepo:secretlint","text":"

secretlint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/secretlint/secretlint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposendgrid-nodejs","title":"monorepo:sendgrid-nodejs","text":"

sendgrid-nodejs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/sendgrid/sendgrid-nodejs\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposentry-dotnet","title":"monorepo:sentry-dotnet","text":"

sentry-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/getsentry/sentry-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposentry-javascript","title":"monorepo:sentry-javascript","text":"

sentry-javascript monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/getsentry/sentry-javascript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposentry-ruby","title":"monorepo:sentry-ruby","text":"

sentry-ruby monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/getsentry/sentry-ruby\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposentry-rust","title":"monorepo:sentry-rust","text":"

sentry-rust monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/getsentry/sentry-rust\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposerde","title":"monorepo:serde","text":"

serde monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/serde-rs/serde\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposerenity-js","title":"monorepo:serenity-js","text":"

serenity-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/serenity-js/serenity-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposerilog-ui","title":"monorepo:serilog-ui","text":"

serilog-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/serilog-contrib/serilog-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposervicestack","title":"monorepo:servicestack","text":"

servicestack monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ServiceStack/ServiceStack\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposerwist","title":"monorepo:serwist","text":"

serwist monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/serwist/serwist\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposhedlock","title":"monorepo:shedlock","text":"

shedlock monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lukas-krecan/ShedLock\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposhiki","title":"monorepo:shiki","text":"

shiki monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/shikijs/shiki\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposhopify-app-bridge","title":"monorepo:shopify-app-bridge","text":"

shopify-app-bridge monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Shopify/app-bridge\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepositecore-jss","title":"monorepo:sitecore-jss","text":"

sitecore-jss monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Sitecore/jss\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposize-limit","title":"monorepo:size-limit","text":"

size-limit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ai/size-limit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposkiasharp","title":"monorepo:skiasharp","text":"

skiasharp monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/mono/SkiaSharp\",\n    \"https://go.microsoft.com/fwlink/?linkid=868515\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposlack-net","title":"monorepo:slack-net","text":"

slack-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/soxtoby/SlackNet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposlf4j","title":"monorepo:slf4j","text":"

slf4j monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/qos-ch/slf4j\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposlim-message-bus","title":"monorepo:slim-message-bus","text":"

slim-message-bus monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/zarusz/SlimMessageBus\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepospectre-console","title":"monorepo:spectre-console","text":"

spectre-console monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/spectreconsole/spectre.console\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepospectre-console-cli","title":"monorepo:spectre-console-cli","text":"

spectre-console-cli monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/spectreconsole/spectre.console.cli\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepospringfox","title":"monorepo:springfox","text":"

springfox monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/springfox/springfox\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostack-exchange-redis-extensions","title":"monorepo:stack-exchange-redis-extensions","text":"

stack-exchange-redis-extensions monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/imperugo/StackExchange.Redis.Extensions\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostatsig-js-client","title":"monorepo:statsig-js-client","text":"

statsig-js-client monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/statsig-io/js-client-monorepo\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposteeltoe","title":"monorepo:steeltoe","text":"

steeltoe monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/SteeltoeOSS/steeltoe\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostorybook","title":"monorepo:storybook","text":"

storybook monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/storybookjs/storybook\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostorybook-react-native","title":"monorepo:storybook-react-native","text":"

storybook-react-native monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/storybookjs/react-native\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostrapi","title":"monorepo:strapi","text":"

strapi monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/strapi/strapi\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostrum","title":"monorepo:strum","text":"

strum monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Peternator7/strum\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostryker-js","title":"monorepo:stryker-js","text":"

stryker-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/stryker-mutator/stryker-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepostylex-swc","title":"monorepo:stylex-swc","text":"

stylex-swc monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Dwlad90/stylex-swc-plugin\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposurveyjs","title":"monorepo:surveyjs","text":"

surveyjs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/surveyjs/surveyjs\",\n    \"https://github.com/surveyjs/survey-library\",\n    \"https://github.com/surveyjs/survey-creator\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposwashbuckle-aspnetcore","title":"monorepo:swashbuckle-aspnetcore","text":"

swashbuckle-aspnetcore monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/domaindrivendev/Swashbuckle.AspNetCore\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposystemioabstractions","title":"monorepo:system.io.abstractions","text":"

system.io.abstractions monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/System-IO-Abstractions/System.IO.Abstractions/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotaiga-ui","title":"monorepo:taiga-ui","text":"

taiga-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/taiga-family/taiga-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotailwindcss","title":"monorepo:tailwindcss","text":"

tailwindcss monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tailwindlabs/tailwindcss\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotamagui","title":"monorepo:tamagui","text":"

tamagui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tamagui/tamagui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotanstack-form","title":"monorepo:tanstack-form","text":"

tanstack-form monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/TanStack/form\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotanstack-query","title":"monorepo:tanstack-query","text":"

tanstack-query monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/TanStack/query\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotanstack-router","title":"monorepo:tanstack-router","text":"

tanstack-router monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/TanStack/router\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotanstack-table","title":"monorepo:tanstack-table","text":"

tanstack-table monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/TanStack/table\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotanstack-virtual","title":"monorepo:tanstack-virtual","text":"

tanstack-virtual monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/TanStack/virtual\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotauri","title":"monorepo:tauri","text":"

tauri monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tauri-apps/tauri\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotelus-tds","title":"monorepo:telus-tds","text":"

telus-tds monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/telusdigital/tds\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotelus-tds-core","title":"monorepo:telus-tds-core","text":"

telus-tds-core monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/telus/tds-core\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotemporalio-ts","title":"monorepo:temporalio-ts","text":"

temporalio-ts monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/temporalio/sdk-typescript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoterraform","title":"monorepo:terraform","text":"

terraform monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hashicorp/terraform\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotestcontainers-dotnet","title":"monorepo:testcontainers-dotnet","text":"

testcontainers-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/testcontainers/testcontainers-dotnet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotestcontainers-go","title":"monorepo:testcontainers-go","text":"

testcontainers-go monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/testcontainers/testcontainers-go\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotestcontainers-java","title":"monorepo:testcontainers-java","text":"

testcontainers-java monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/testcontainers/testcontainers-java\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotestcontainers-node","title":"monorepo:testcontainers-node","text":"

testcontainers-node monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/testcontainers/testcontainers-node\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotheme-ui","title":"monorepo:theme-ui","text":"

theme-ui monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/system-ui/theme-ui\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotika","title":"monorepo:tika","text":"

tika monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/tika\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotimvir","title":"monorepo:timvir","text":"

timvir monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/timvir/timvir\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotiptap","title":"monorepo:tiptap","text":"

tiptap monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ueberdosis/tiptap\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotokio-prost","title":"monorepo:tokio-prost","text":"

tokio-prost monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tokio-rs/prost\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotokio-tracing","title":"monorepo:tokio-tracing","text":"

tokio-tracing monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/tokio-rs/tracing\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotomcat","title":"monorepo:tomcat","text":"

tomcat monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apache/tomcat\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotonic","title":"monorepo:tonic","text":"

tonic monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hyperium/tonic\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotreat","title":"monorepo:treat","text":"

treat monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/seek-oss/treat\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotrpc","title":"monorepo:trpc","text":"

trpc monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/trpc/trpc\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotrust-dns","title":"monorepo:trust-dns","text":"

trust-dns monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/bluejekyll/trust-dns\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotsoa","title":"monorepo:tsoa","text":"

tsoa monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lukeautry/tsoa\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotunit","title":"monorepo:tunit","text":"

tunit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/thomhurst/TUnit\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoturbo","title":"monorepo:turbo","text":"

turbo monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vercel/turbo\",\n    \"https://github.com/vercel/turborepo\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoturf","title":"monorepo:turf","text":"

turf monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Turfjs/turf\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotyped-signalr","title":"monorepo:typed-signalr","text":"

typed-signalr monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nenoNaninu/TypedSignalR.Client.TypeScript\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotypefaces","title":"monorepo:typefaces","text":"

typefaces monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/KyleAMathews/typefaces\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotypescript-eslint","title":"monorepo:typescript-eslint","text":"

typescript-eslint monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/typescript-eslint/typescript-eslint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotypography-js","title":"monorepo:typography-js","text":"

typography-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/KyleAMathews/typography.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoui5-webcomponents","title":"monorepo:ui5-webcomponents","text":"

ui5-webcomponents monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/SAP/ui5-webcomponents\",\n    \"https://github.com/SAP/ui5-webcomponents-react\",\n    \"https://github.com/SAP/ui5-webcomponents-ngx\",\n    \"https://github.com/UI5/webcomponents\",\n    \"https://github.com/UI5/webcomponents-react\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepounhead","title":"monorepo:unhead","text":"

unhead monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/unjs/unhead\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepounocss","title":"monorepo:unocss","text":"

unocss monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/unocss/unocss\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepouppy","title":"monorepo:uppy","text":"

uppy monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/transloadit/uppy\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoutoipa","title":"monorepo:utoipa","text":"

utoipa monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/juhaku/utoipa\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovaadin-hilla","title":"monorepo:vaadin-hilla","text":"

vaadin-hilla monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vaadin/hilla\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovaadinwebcomponents","title":"monorepo:vaadinWebComponents","text":"

vaadinWebComponents monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vaadin/web-components\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovanilla-extract","title":"monorepo:vanilla-extract","text":"

vanilla-extract monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vanilla-extract-css/vanilla-extract\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovisx","title":"monorepo:visx","text":"

visx monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/airbnb/visx\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovite-plus","title":"monorepo:vite-plus","text":"

vite-plus monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/voidzero-dev/vite-plus\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovitest","title":"monorepo:vitest","text":"

vitest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vitest-dev/vitest\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovstest","title":"monorepo:vstest","text":"

vstest monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/microsoft/vstest\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovue","title":"monorepo:vue","text":"

vue monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vuejs/vue\",\n    \"https://github.com/vuejs/core\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovue-cli","title":"monorepo:vue-cli","text":"

vue-cli monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vuejs/vue-cli\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovue-language-tools","title":"monorepo:vue-language-tools","text":"

vue-language-tools monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vuejs/language-tools\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovuepress","title":"monorepo:vuepress","text":"

vuepress monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vuejs/vuepress\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepovueuse","title":"monorepo:vueuse","text":"

vueuse monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/vueuse/vueuse\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoweasel","title":"monorepo:weasel","text":"

weasel monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/JasperFx/weasel\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoweb3-react","title":"monorepo:web3-react","text":"

web3-react monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Uniswap/web3-react\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepowebdriverio","title":"monorepo:webdriverio","text":"

webdriverio monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/webdriverio/webdriverio\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepowolverine","title":"monorepo:wolverine","text":"

wolverine monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/jasperfx/wolverine\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoworkbox","title":"monorepo:workbox","text":"

workbox monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/googlechrome/workbox\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepowyw-in-js","title":"monorepo:wyw-in-js","text":"

wyw-in-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/Anber/wyw-in-js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoxstate","title":"monorepo:xstate","text":"

xstate monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/statelyai/xstate\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoxterm","title":"monorepo:xterm","text":"

xterm monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/xtermjs/xterm.js\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoxunit-dotnet","title":"monorepo:xunit-dotnet","text":"

xunit-dotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/xunit/assert.xunit\",\n    \"https://github.com/xunit/visualstudio.xunit\",\n    \"https://github.com/xunit/xunit\",\n    \"https://github.com/xunit/xunit.analyzers\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoyamldotnet","title":"monorepo:yamldotnet","text":"

yamldotnet monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/aaubry/YamlDotNet\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoyarn","title":"monorepo:yarn","text":"

yarn monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/yarnpkg/berry\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepozag-js","title":"monorepo:zag-js","text":"

zag-js monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/chakra-ui/zag\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepozxcvbn-ts","title":"monorepo:zxcvbn-ts","text":"

zxcvbn-ts monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/zxcvbn-ts/zxcvbn\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepozxing-net","title":"monorepo:zxing-net","text":"

zxing-net monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/micjahn/ZXing.Net\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepohapijs","title":"monorepo:hapijs","text":"

hapijs monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/hapijs/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepolodash","title":"monorepo:lodash","text":"

lodash monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/lodash/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepongrx","title":"monorepo:ngrx","text":"

ngrx monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/ngrx/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreponx","title":"monorepo:nx","text":"

nx monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/nrwl/nx**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepooctokit","title":"monorepo:octokit","text":"

octokit monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/octokit/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepophp-enqueue","title":"monorepo:php-enqueue","text":"

php-enqueue monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/php-enqueue/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposemantic-release","title":"monorepo:semantic-release","text":"

semantic-release monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/semantic-release/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposwc","title":"monorepo:swc","text":"

swc monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/swc-project/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotwig","title":"monorepo:twig","text":"

twig monorepo

{\n  \"matchSourceUrls\": [\n    \"https://github.com/twigphp/**\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoangularmaterial","title":"monorepo:angularmaterial","text":"

angularmaterial monorepo

{\n  \"matchPackageNames\": [\n    \"/^@angular/material/\",\n    \"/^@angular/cdk/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapache-camel","title":"monorepo:apache-camel","text":"

apache-camel monorepo

{\n  \"matchPackageNames\": [\n    \"/^org.apache.camel:/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoapache-poi","title":"monorepo:apache-poi","text":"

apache-poi monorepo

{\n  \"matchPackageNames\": [\n    \"/^org.apache.poi:/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-java-sdk","title":"monorepo:aws-java-sdk","text":"

aws-java-sdk monorepo

{\n  \"matchPackageNames\": [\n    \"/^com.amazonaws:aws-java-sdk-/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaws-java-sdk-v2","title":"monorepo:aws-java-sdk-v2","text":"

aws-java-sdk-v2 monorepo

{\n  \"matchPackageNames\": [\n    \"/^software.amazon.awssdk:/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoaxis2","title":"monorepo:axis2","text":"

axis2 monorepo

{\n  \"matchPackageNames\": [\n    \"/^org.apache.axis2:/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepobabel6","title":"monorepo:babel6","text":"

babel6 monorepo

{\n  \"matchPackageNames\": [\n    \"/^babel6$/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoembroider","title":"monorepo:embroider","text":"

embroider monorepo

{\n  \"matchPackageNames\": [\n    \"/^@embroider//\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoforge","title":"monorepo:forge","text":"

forge monorepo

{\n  \"matchPackageNames\": [\n    \"/^@forge//\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepofullcalendar","title":"monorepo:fullcalendar","text":"

fullcalendar monorepo

{\n  \"matchPackageNames\": [\n    \"/^@fullcalendar//\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepooracle-database","title":"monorepo:oracle-database","text":"

oracle-database monorepo

{\n  \"matchPackageNames\": [\n    \"/^com.oracle.database.jdbc:/\",\n    \"/^com.oracle.database.nls:/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepooxlint","title":"monorepo:oxlint","text":"

oxlint monorepo

{\n  \"matchPackageNames\": [\n    \"oxlint\",\n    \"@oxlint/plugins\",\n    \"eslint-plugin-oxlint\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepoprometheus-simpleclient","title":"monorepo:prometheus-simpleclient","text":"

prometheus-simpleclient monorepo

{\n  \"matchPackageNames\": [\n    \"/^io.prometheus:simpleclient/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreporussh","title":"monorepo:russh","text":"

russh monorepo

{\n  \"matchPackageNames\": [\n    \"/^russh$/\",\n    \"/^russh-keys$/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposolid","title":"monorepo:solid","text":"

solid monorepo

{\n  \"matchPackageNames\": [\n    \"@solid-design-system/tokens\",\n    \"@solid-design-system/styles\",\n    \"@solid-design-system/components\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepospfx","title":"monorepo:spfx","text":"

spfx monorepo

{\n  \"matchPackageNames\": [\n    \"/^@microsoft/sp-/\",\n    \"/^@microsoft/eslint-.+-spfx$/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepospock","title":"monorepo:spock","text":"

spock monorepo

{\n  \"matchPackageNames\": [\n    \"/^org\\\\.spockframework:spock-/\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monoreposyncfusion-dotnet","title":"monorepo:syncfusion-dotnet","text":"

syncfusion-dotnet monorepo

{\n  \"matchPackageNames\": [\n    \"/^Syncfusion\\\\./\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepotesting-library","title":"monorepo:testing-library","text":"

testing-library monorepo

{\n  \"matchPackageNames\": [\n    \"/^@testing-library//\"\n  ]\n}\n
"},{"location":"presets-monorepo/#monorepowordpress","title":"monorepo:wordpress","text":"

wordpress monorepo

{\n  \"matchPackageNames\": [\n    \"/^@wordpress/\"\n  ]\n}\n
"},{"location":"presets-packages/","title":"Package Presets","text":""},{"location":"presets-packages/#packagesangularjs","title":"packages:angularJs","text":"

All AngularJS packages.

{\n  \"matchPackageNames\": [\n    \"angular\",\n    \"angular-animate\",\n    \"angular-scroll\",\n    \"angular-sanitize\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesapollographql","title":"packages:apollographql","text":"

All packages published by Apollo GraphQL.

{\n  \"matchSourceUrls\": [\n    \"https://github.com/apollographql/**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesatlaskit","title":"packages:atlaskit","text":"

All @atlaskit packages published by Atlassian.

{\n  \"matchPackageNames\": [\n    \"@atlaskit/**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesembertemplatelint","title":"packages:emberTemplateLint","text":"

All ember-template-lint packages.

{\n  \"matchPackageNames\": [\n    \"ember-template-lint**\"\n  ]\n}\n
"},{"location":"presets-packages/#packageseslint","title":"packages:eslint","text":"

All ESLint packages.

{\n  \"matchPackageNames\": [\n    \"*/eslint-plugin\",\n    \"@babel/eslint-parser\",\n    \"@eslint/**\",\n    \"@eslint-community/**\",\n    \"@stylistic/eslint-plugin**\",\n    \"@types/eslint\",\n    \"@types/eslint__**\",\n    \"@typescript-eslint/**\",\n    \"babel-eslint\",\n    \"eslint**\",\n    \"typescript-eslint\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesgatsby","title":"packages:gatsby","text":"

All packages published by Gatsby.

{\n  \"extends\": [\n    \"monorepo:gatsby\" // (1)!\n  ]\n}\n
  1. monorepo:gatsby: gatsby monorepo
"},{"location":"presets-packages/#packagesgoogleapis","title":"packages:googleapis","text":"

All googleapis packages.

{\n  \"matchDatasources\": [\n    \"npm\"\n  ],\n  \"matchPackageNames\": [\n    \"@google-cloud/**\",\n    \"google-auth-library\",\n    \"googleapis\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesjstest","title":"packages:jsTest","text":"

JavaScript test packages.

{\n  \"extends\": [\n    \"packages:jsUnitTest\" // (1)!\n  ]\n}\n
  1. packages:jsUnitTest: Unit test packages for JavaScript.
"},{"location":"presets-packages/#packagesjsunittest","title":"packages:jsUnitTest","text":"

Unit test packages for JavaScript.

{\n  \"matchPackageNames\": [\n    \"@types/chai\",\n    \"@types/ember-mocha\",\n    \"@types/ember-qunit\",\n    \"@types/enzyme\",\n    \"@types/istanbul\",\n    \"@types/jest\",\n    \"@types/mocha\",\n    \"@types/mock-fs\",\n    \"@types/proxyquire\",\n    \"@types/sinon\",\n    \"@types/supertest\",\n    \"coveralls\",\n    \"ember-exam\",\n    \"ember-mocha\",\n    \"ember-qunit\",\n    \"enzyme\",\n    \"istanbul\",\n    \"mock-fs\",\n    \"nock\",\n    \"nyc\",\n    \"proxyquire\",\n    \"supertest\",\n    \"ts-auto-mock\",\n    \"ts-jest\",\n    \"vitest\",\n    \"@jest/**\",\n    \"@testing-library/**\",\n    \"@types/testing-library__**\",\n    \"@vitest/**\",\n    \"chai**\",\n    \"jest**\",\n    \"mocha**\",\n    \"qunit**\",\n    \"should**\",\n    \"sinon**\"\n  ]\n}\n
"},{"location":"presets-packages/#packageslinters","title":"packages:linters","text":"

All lint-related packages.

{\n  \"extends\": [\n    \"packages:emberTemplateLint\", // (1)!\n    \"packages:eslint\", // (2)!\n    \"packages:phpLinters\", // (3)!\n    \"packages:stylelint\", // (4)!\n    \"packages:tslint\" // (5)!\n  ],\n  \"matchPackageNames\": [\n    \"@biomejs/**\",\n    \"@oxlint/**\",\n    \"oxfmt\",\n    \"oxlint\",\n    \"prettier\",\n    \"remark-lint\",\n    \"ruff\",\n    \"rumdl\",\n    \"standard\"\n  ]\n}\n
  1. packages:emberTemplateLint: All ember-template-lint packages.
  2. packages:eslint: All ESLint packages.
  3. packages:phpLinters: All PHP lint-related packages.
  4. packages:stylelint: All Stylelint packages.
  5. packages:tslint: All TSLint packages.
"},{"location":"presets-packages/#packagesmapbox","title":"packages:mapbox","text":"

All Mapbox-related packages.

{\n  \"matchPackageNames\": [\n    \"leaflet**\",\n    \"mapbox**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesphplinters","title":"packages:phpLinters","text":"

All PHP lint-related packages.

{\n  \"matchPackageNames\": [\n    \"friendsofphp/php-cs-fixer\",\n    \"squizlabs/php_codesniffer\",\n    \"symplify/easy-coding-standard\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesphpunittest","title":"packages:phpUnitTest","text":"

Unit test packages for PHP.

{\n  \"matchPackageNames\": [\n    \"behat/behat\",\n    \"brianium/paratest\",\n    \"facile-it/paraunit\",\n    \"mockery/mockery\",\n    \"phpspec/prophecy\",\n    \"phpspec/prophecy-phpunit\",\n    \"phpspec/phpspec\",\n    \"phpunit/phpunit\",\n    \"pestphp/**\",\n    \"php-mock/**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagespostcss","title":"packages:postcss","text":"

All PostCSS packages.

{\n  \"matchPackageNames\": [\n    \"postcss\",\n    \"postcss-**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesreact","title":"packages:react","text":"

All React packages.

{\n  \"matchDatasources\": [\n    \"npm\"\n  ],\n  \"matchPackageNames\": [\n    \"@types/react**\",\n    \"react**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesstylelint","title":"packages:stylelint","text":"

All Stylelint packages.

{\n  \"matchPackageNames\": [\n    \"stylelint**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagestest","title":"packages:test","text":"

Test packages.

{\n  \"extends\": [\n    \"packages:unitTest\" // (1)!\n  ]\n}\n
  1. packages:unitTest: All unit test packages.
"},{"location":"presets-packages/#packagestslint","title":"packages:tslint","text":"

All TSLint packages.

{\n  \"matchPackageNames\": [\n    \"codelyzer\",\n    \"/\\\\btslint\\\\b/\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesunittest","title":"packages:unitTest","text":"

All unit test packages.

{\n  \"extends\": [\n    \"packages:jsUnitTest\", // (1)!\n    \"packages:phpUnitTest\" // (2)!\n  ]\n}\n
  1. packages:jsUnitTest: Unit test packages for JavaScript.
  2. packages:phpUnitTest: Unit test packages for PHP.
"},{"location":"presets-packages/#packagesvite","title":"packages:vite","text":"

All Vite related packages

{\n  \"matchDatasources\": [\n    \"npm\"\n  ],\n  \"matchPackageNames\": [\n    \"vite\",\n    \"**vite-plugin**\",\n    \"@vitejs/**\"\n  ]\n}\n
"},{"location":"presets-packages/#packagesviteplus","title":"packages:vitePlus","text":"

All Vite+ related packages

{\n  \"extends\": [\n    \"monorepo:vite-plus\", // (1)!\n    \"monorepo:vitest\" // (2)!\n  ]\n}\n
  1. monorepo:vite-plus: vite-plus monorepo
  2. monorepo:vitest: vitest monorepo
"},{"location":"presets-preview/","title":"Preview Presets","text":""},{"location":"presets-preview/#previewbuildkite","title":"preview:buildkite","text":"

Enable Buildkite functionality.

{\n  \"buildkite\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-preview/#previewdockercompose","title":"preview:dockerCompose","text":"

Enable Docker Compose image updating.

{\n  \"docker-compose\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"presets-preview/#previewdockerversions","title":"preview:dockerVersions","text":"

Upgrade Docker tags to newer versions.

{\n  \"docker-compose\": {\n    \"major\": {\n      \"enabled\": true\n    },\n    \"minor\": {\n      \"enabled\": true\n    }\n  },\n  \"dockerfile\": {\n    \"major\": {\n      \"enabled\": true\n    },\n    \"minor\": {\n      \"enabled\": true\n    }\n  }\n}\n
"},{"location":"presets-replacements/","title":"Replacement Presets","text":""},{"location":"presets-replacements/#replacementsall","title":"replacements:all","text":"

Apply crowd-sourced package replacement rules.

{\n  \"extends\": [\n    \"replacements:actions-attest-build-provenance-to-actions-attest\", // (1)!\n    \"replacements:airbnb-prop-types-to-prop-types-tools\", // (2)!\n    \"replacements:apollo-server-to-scoped\", // (3)!\n    \"replacements:aws-sdk-smithy-client-to-smithy\", // (4)!\n    \"replacements:babel-eslint-to-eslint-parser\", // (5)!\n    \"replacements:base-ui-components-to-base-ui\", // (6)!\n    \"replacements:containerbase\", // (7)!\n    \"replacements:cpx-to-maintenance-fork\", // (8)!\n    \"replacements:cucumber-to-scoped\", // (9)!\n    \"replacements:dev-oidc-provider-to-unscoped\", // (10)!\n    \"replacements:dev-process-manager-to-unscoped\", // (11)!\n    \"replacements:docker-compose\", // (12)!\n    \"replacements:edb-jdbc-to-enterprisedb\", // (13)!\n    \"replacements:eslint-config-standard-with-typescript-to-eslint-config-love\", // (14)!\n    \"replacements:eslint-plugin-eslint-comments-to-maintained-fork\", // (15)!\n    \"replacements:eslint-plugin-node-to-maintained-fork\", // (16)!\n    \"replacements:eslint-plugin-vitest-to-scoped\", // (17)!\n    \"replacements:express-mung-to-express-response-middleware\", // (18)!\n    \"replacements:fakerjs-to-scoped\", // (19)!\n    \"replacements:fastify-to-scoped\", // (20)!\n    \"replacements:framer-motion-to-motion\", // (21)!\n    \"replacements:google-github-action-release-please-to-googleapis\", // (22)!\n    \"replacements:grafana-oss-to-grafana\", // (23)!\n    \"replacements:hapi-to-scoped\", // (24)!\n    \"replacements:home-operations-to-official\", // (25)!\n    \"replacements:jade-to-pug\", // (26)!\n    \"replacements:joi-to-scoped\", // (27)!\n    \"replacements:joi-to-unscoped\", // (28)!\n    \"replacements:k8s-registry-move\", // (29)!\n    \"replacements:kotlin-logging-to-oshai\", // (30)!\n    \"replacements:material-ui-to-mui\", // (31)!\n    \"replacements:mem-rename\", // (32)!\n    \"replacements:messageFormat-to-scoped\", // (33)!\n    \"replacements:middie-to-scoped\", // (34)!\n    \"replacements:monochromata-cucumber-reporting-plugin-to-jvt\", // (35)!\n    \"replacements:now-to-vercel\", // (36)!\n    \"replacements:npm-run-all-to-maintenance-fork\", // (37)!\n    \"replacements:ojdbc-to-ojdbc11\", // (38)!\n    \"replacements:opencost-registry-move\", // (39)!\n    \"replacements:parcel-css-to-lightningcss\", // (40)!\n    \"replacements:passport-saml\", // (41)!\n    \"replacements:pwpush-to-universal-container\", // (42)!\n    \"replacements:react-native-magic-modal-to-magic-modal\", // (43)!\n    \"replacements:react-query-devtools-to-scoped\", // (44)!\n    \"replacements:react-query-to-scoped\", // (45)!\n    \"replacements:react-scripts-ts-to-react-scripts\", // (46)!\n    \"replacements:read-pkg-up-rename\", // (47)!\n    \"replacements:redux-devtools-extension-to-scope\", // (48)!\n    \"replacements:renovate-pep440-to-renovatebot-pep440\", // (49)!\n    \"replacements:rolldown-vite-to-vite\", // (50)!\n    \"replacements:rollup-babel-to-scoped\", // (51)!\n    \"replacements:rollup-json-to-scoped\", // (52)!\n    \"replacements:rollup-node-resolve-to-scoped\", // (53)!\n    \"replacements:rollup-terser-to-scoped\", // (54)!\n    \"replacements:rome-to-biome\", // (55)!\n    \"replacements:scorecard-registry-move\", // (56)!\n    \"replacements:semantic-release-replace-plugin-to-unscoped\", // (57)!\n    \"replacements:spectre-cli-to-spectre-console-cli\", // (58)!\n    \"replacements:standard-version-to-commit-and-tag\", // (59)!\n    \"replacements:temporalio-interceptors-opentelemetry-to-v2\", // (60)!\n    \"replacements:terraform-provider-mrparkers-keycloak-to-keycloak-keycloak\", // (61)!\n    \"replacements:tsconfig-bases-node\", // (62)!\n    \"replacements:typeorm-seeding-to-scoped\", // (63)!\n    \"replacements:ucanaccess-to-io-github-spannm\", // (64)!\n    \"replacements:vitest-coverage-c8-to-coverage-v8\", // (65)!\n    \"replacements:vso-task-lib-to-azure-pipelines-task-lib\", // (66)!\n    \"replacements:vsts-task-lib-to-azure-pipelines-task-lib\", // (67)!\n    \"replacements:wuchale-vite-plugin-to-wuchale\", // (68)!\n    \"replacements:xlsx-to-scoped\", // (69)!\n    \"replacements:xmldom-to-scoped\", // (70)!\n    \"replacements:zap\" // (71)!\n  ]\n}\n
  1. replacements:actions-attest-build-provenance-to-actions-attest: actions/attest-build-provenance was renamed to actions/attest.
  2. replacements:airbnb-prop-types-to-prop-types-tools: airbnb-prop-types was given to a new maintainer and renamed to prop-types-tools.
  3. replacements:apollo-server-to-scoped: apollo-server packages became scoped.
  4. replacements:aws-sdk-smithy-client-to-smithy: @aws-sdk/smithy-client was moved to @smithy/smithy-client.
  5. replacements:babel-eslint-to-eslint-parser: babel-eslint was renamed under the @babel scope.
  6. replacements:base-ui-components-to-base-ui: @base-ui-components/react was renamed to @base-ui/react.
  7. replacements:containerbase: Replace containerbase dependencies.
  8. replacements:cpx-to-maintenance-fork: Maintenance fork of cpx
  9. replacements:cucumber-to-scoped: cucumber became scoped.
  10. replacements:dev-oidc-provider-to-unscoped: dev-oidc-provider became unscoped.
  11. replacements:dev-process-manager-to-unscoped: dev-process-manager became unscoped.
  12. replacements:docker-compose: Compose is now part of the official Docker image.
  13. replacements:edb-jdbc-to-enterprisedb: com.edb:edb-jdbc and com.edb:edb-jdbc18 were moved to com.enterprisedb:edb-jdbc.
  14. replacements:eslint-config-standard-with-typescript-to-eslint-config-love: eslint-config-standard-with-typescript was renamed to eslint-config-love.
  15. replacements:eslint-plugin-eslint-comments-to-maintained-fork: Replace eslint-plugin-eslint-comments with a maintained fork: @eslint-community/eslint-plugin-eslint-comments.
  16. replacements:eslint-plugin-node-to-maintained-fork: Replace stale eslint-plugin-node with a maintained fork: eslint-plugin-n.
  17. replacements:eslint-plugin-vitest-to-scoped: eslint-plugin-vitest became scoped.
  18. replacements:express-mung-to-express-response-middleware: Replace stale express-mung with a maintained fork: express-response-middleware.
  19. replacements:fakerjs-to-scoped: fakerjs packages became scoped.
  20. replacements:fastify-to-scoped: fastify packages became scoped.
  21. replacements:framer-motion-to-motion: framer-motion and Motion One have merged under the package name motion, though framer-motion is still being published. motion is now the recommended name.
  22. replacements:google-github-action-release-please-to-googleapis: google-github-action/release-please was renamed to googleapis/release-please.
  23. replacements:grafana-oss-to-grafana: grafana/grafana-oss was replaced by grafana/grafana with the same images
  24. replacements:hapi-to-scoped: hapi became scoped.
  25. replacements:home-operations-to-official: home-operations only builts these until official versions are released
  26. replacements:jade-to-pug: Jade was renamed to Pug.
  27. replacements:joi-to-scoped: joi became scoped under the hapi organization.
  28. replacements:joi-to-unscoped: joi was moved out of the hapi organization.
  29. replacements:k8s-registry-move: The Kubernetes container registry has changed from k8s.gcr.io to registry.k8s.io.
  30. replacements:kotlin-logging-to-oshai: replaces kotlin-logging github organization and maven group from MicroUtils to oshai
  31. replacements:material-ui-to-mui: The material-ui monorepo org was renamed from @material-ui to @mui.
  32. replacements:mem-rename: mem was renamed to memoize.
  33. replacements:messageFormat-to-scoped: The messageformat monorepo package naming scheme changed from messageFormat-{{package}} to @messageformat/{{package}}.
  34. replacements:middie-to-scoped: middie became scoped.
  35. replacements:monochromata-cucumber-reporting-plugin-to-jvt: de.monochromata.cucumber:reporting-plugin was moved to me.jvt.cucumber:reporting-plugin.
  36. replacements:now-to-vercel: now was renamed to vercel.
  37. replacements:npm-run-all-to-maintenance-fork: Maintenance fork of npm-run-all
  38. replacements:ojdbc-to-ojdbc11: ojdbc:ojdbc and com.oracle.database.jdbc:ojdbc10 were moved to com.oracle.database.jdbc:ojdbc11.
  39. replacements:opencost-registry-move: Replace OpenCost registry from quay.io to ghcr.io.
  40. replacements:parcel-css-to-lightningcss: @parcel/css was renamed to lightningcss.
  41. replacements:passport-saml: passport-saml was renamed to @node-saml/passport-saml.
  42. replacements:pwpush-to-universal-container: Replace deprecated Password Pusher database-specific images with its universal image.
  43. replacements:react-native-magic-modal-to-magic-modal: react-native-magic-modal was renamed to magic-modal in version 10.0.0. The old name is deprecated but still published at the same version, depending on and re-exporting magic-modal.
  44. replacements:react-query-devtools-to-scoped: react-query/devtools became scoped under the tanstack organization.
  45. replacements:react-query-to-scoped: react-query became scoped under the tanstack organization.
  46. replacements:react-scripts-ts-to-react-scripts: react-scripts supports TypeScript since version 2.1.0.
  47. replacements:read-pkg-up-rename: read-pkg-up was renamed to read-package-up.
  48. replacements:redux-devtools-extension-to-scope: The redux-devtools-extension package was renamed to @redux-devtools/extension.
  49. replacements:renovate-pep440-to-renovatebot-pep440: The @renovate/pep440 package was renamed to @renovatebot/pep440.
  50. replacements:rolldown-vite-to-vite: rolldown-vite was merged to vite in version 8.0.0.
  51. replacements:rollup-babel-to-scoped: The babel plugin for rollup became scoped.
  52. replacements:rollup-json-to-scoped: The json plugin for rollup became scoped.
  53. replacements:rollup-node-resolve-to-scoped: The node-resolve plugin for rollup became scoped.
  54. replacements:rollup-terser-to-scoped: The terser plugin for rollup became scoped.
  55. replacements:rome-to-biome: The Rome repository is archived, and Biome is the community replacement. Read the Biome announcement for migration instructions.
  56. replacements:scorecard-registry-move: The OpenSSF Scorecard container images moved from gcr.io/openssf/scorecard to ghcr.io/ossf/scorecard.
  57. replacements:semantic-release-replace-plugin-to-unscoped: semantic-release-replace-plugin was moved out of the google organization.
  58. replacements:spectre-cli-to-spectre-console-cli: The Spectre.Cli package was renamed to Spectre.Console.Cli.
  59. replacements:standard-version-to-commit-and-tag: standard-version is now maintained as commit-and-tag-version.
  60. replacements:temporalio-interceptors-opentelemetry-to-v2: @temporalio/interceptors-opentelemetry was replaced by @temporalio/interceptors-opentelemetry-v2, which supports OpenTelemetry v2.
  61. replacements:terraform-provider-mrparkers-keycloak-to-keycloak-keycloak: The Keycloak Terraform/OpenTofu provider was moved to keycloak/keycloak.
  62. replacements:tsconfig-bases-node: @tsconfig-bases node updates.
  63. replacements:typeorm-seeding-to-scoped: typeorm-seeding is now maintained as scoped package.
  64. replacements:ucanaccess-to-io-github-spannm: net.sf.ucanaccess:ucanaccess is no longer maintained, development continues at io.github.spannm:ucanaccess.
  65. replacements:vitest-coverage-c8-to-coverage-v8: @vitest/coverage-c8 was renamed to @vitest/coverage-v8.
  66. replacements:vso-task-lib-to-azure-pipelines-task-lib: The vso-task-lib package is now published as azure-pipelines-task-lib.
  67. replacements:vsts-task-lib-to-azure-pipelines-task-lib: The vsts-task-lib package is now published as azure-pipelines-task-lib.
  68. replacements:wuchale-vite-plugin-to-wuchale: The @wuchale/vite-plugin package is now included in wuchale at wuchale/vite.
  69. replacements:xlsx-to-scoped: The xlsx package is now published as @e965/xlsx.
  70. replacements:xmldom-to-scoped: The xmldom package is now published as @xmldom/xmldom.
  71. replacements:zap: Replace ZAP dependencies.
"},{"location":"presets-replacements/#replacementsactions-attest-build-provenance-to-actions-attest","title":"replacements:actions-attest-build-provenance-to-actions-attest","text":"

actions/attest-build-provenance was renamed to actions/attest.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=4\",\n      \"matchDatasources\": [\n        \"github-tags\"\n      ],\n      \"matchPackageNames\": [\n        \"actions/attest-build-provenance\"\n      ],\n      \"replacementName\": \"actions/attest\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsairbnb-prop-types-to-prop-types-tools","title":"replacements:airbnb-prop-types-to-prop-types-tools","text":"

airbnb-prop-types was given to a new maintainer and renamed to prop-types-tools.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^2\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"airbnb-prop-types\"\n      ],\n      \"replacementName\": \"prop-types-tools\",\n      \"replacementVersion\": \"2.17.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsapollo-server-to-scoped","title":"replacements:apollo-server-to-scoped","text":"

apollo-server packages became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=3.10.3\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-server\",\n        \"apollo-server-core\",\n        \"apollo-server-express\"\n      ],\n      \"replacementName\": \"@apollo/server\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.3.1\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-server-errors\"\n      ],\n      \"replacementName\": \"@apollo/server\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.6.3\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-server-types\",\n        \"apollo-server-plugin-base\"\n      ],\n      \"replacementName\": \"@apollo/server\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.7.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-datasource-rest\"\n      ],\n      \"replacementName\": \"@apollo/datasource-rest\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.7.1\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-server-plugin-response-cache\"\n      ],\n      \"replacementName\": \"@apollo/server-plugin-response-cache\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.5.1\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-server-plugin-operation-registry\"\n      ],\n      \"replacementName\": \"@apollo/server-plugin-operation-registry\",\n      \"replacementVersion\": \"3.5.6\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.3.3\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"apollo-reporting-protobuf\"\n      ],\n      \"replacementName\": \"@apollo/usage-reporting-protobuf\",\n      \"replacementVersion\": \"4.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsaws-sdk-smithy-client-to-smithy","title":"replacements:aws-sdk-smithy-client-to-smithy","text":"

@aws-sdk/smithy-client was moved to @smithy/smithy-client.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@aws-sdk/smithy-client\"\n      ],\n      \"replacementName\": \"@smithy/smithy-client\",\n      \"replacementVersion\": \"1.0.5\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsbabel-eslint-to-eslint-parser","title":"replacements:babel-eslint-to-eslint-parser","text":"

babel-eslint was renamed under the @babel scope.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=7.11.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"babel-eslint\"\n      ],\n      \"replacementName\": \"@babel/eslint-parser\",\n      \"replacementVersion\": \"7.11.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsbase-ui-components-to-base-ui","title":"replacements:base-ui-components-to-base-ui","text":"

@base-ui-components/react was renamed to @base-ui/react.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@base-ui-components/react\"\n      ],\n      \"replacementName\": \"@base-ui/react\",\n      \"replacementVersion\": \"1.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsclang-format-to-maintenance-fork","title":"replacements:clang-format-to-maintenance-fork","text":"

Maintenance fork of clang-format

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"clang-format\"\n      ],\n      \"replacementName\": \"clang-format-node\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementscontainerbase","title":"replacements:containerbase","text":"

Replace containerbase dependencies.

{\n  \"packageRules\": [\n    {\n      \"description\": \"Replace `containerbase/(buildpack|base)` and `renovate/buildpack` with `ghcr.io/containerbase/base`.\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?containerbase/(?:buildpack|base)$/\",\n        \"/^ghcr\\\\.io/containerbase/buildpack$/\",\n        \"/^(?:docker\\\\.io/)?renovate/buildpack$/\"\n      ],\n      \"replacementName\": \"ghcr.io/containerbase/base\"\n    },\n    {\n      \"description\": \"Replace `containerbase/node` and `renovate/node` with `ghcr.io/containerbase/node`.\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?(?:containerbase|renovate)/node$/\"\n      ],\n      \"replacementName\": \"ghcr.io/containerbase/node\"\n    },\n    {\n      \"description\": \"Replace `containerbase/sidecar` and `renovate/sidecar` with `ghcr.io/containerbase/sidecar`.\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?(?:containerbase|renovate)/sidecar$/\"\n      ],\n      \"replacementName\": \"ghcr.io/containerbase/sidecar\"\n    },\n    {\n      \"description\": \"Replace `renovatebot/internal-tools` with `containerbase/internal-tools`.\",\n      \"matchDatasources\": [\n        \"github-tags\"\n      ],\n      \"matchPackageNames\": [\n        \"renovatebot/internal-tools\"\n      ],\n      \"replacementName\": \"containerbase/internal-tools\"\n    },\n    {\n      \"description\": \"Replace `renovate` `slim` docker tag with `latest`.\",\n      \"matchCurrentValue\": \"/^slim$/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"ghcr.io/renovatebot/renovate\",\n        \"/^(?:docker\\\\.io/)?renovate/renovate$/\"\n      ],\n      \"replacementVersion\": \"latest\"\n    },\n    {\n      \"description\": \"Remove `renovate` `-slim` docker tag suffix.\",\n      \"extractVersion\": \"^(?<version>.+)-slim$\",\n      \"matchCurrentValue\": \"/-slim$/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"ghcr.io/renovatebot/renovate\",\n        \"/^(?:docker\\\\.io/)?renovate/renovate$/\"\n      ],\n      \"versioning\": \"semver\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementscorentinmusard-otel-cicd-action-to-dash0hq","title":"replacements:corentinmusard-otel-cicd-action-to-dash0hq","text":"

corentinmusard/otel-cicd-action was transferred to dash0hq/otel-cicd-action.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"github-releases\",\n        \"github-tags\"\n      ],\n      \"matchPackageNames\": [\n        \"corentinmusard/otel-cicd-action\"\n      ],\n      \"replacementName\": \"dash0hq/otel-cicd-action\",\n      \"replacementVersion\": \"4.0.1\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementscpx-to-maintenance-fork","title":"replacements:cpx-to-maintenance-fork","text":"

Maintenance fork of cpx

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"cpx\"\n      ],\n      \"replacementName\": \"cpx2\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementscucumber-to-scoped","title":"replacements:cucumber-to-scoped","text":"

cucumber became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"cucumber\"\n      ],\n      \"replacementName\": \"@cucumber/cucumber\",\n      \"replacementVersion\": \"7.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsdev-oidc-provider-to-unscoped","title":"replacements:dev-oidc-provider-to-unscoped","text":"

dev-oidc-provider became unscoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@comet/dev-oidc-provider\"\n      ],\n      \"replacementName\": \"dev-oidc-provider\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsdev-process-manager-to-unscoped","title":"replacements:dev-process-manager-to-unscoped","text":"

dev-process-manager became unscoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@comet/dev-process-manager\"\n      ],\n      \"replacementName\": \"dev-process-manager\",\n      \"replacementVersion\": \"4.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsdocker-compose","title":"replacements:docker-compose","text":"

Compose is now part of the official Docker image.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"docker/compose\"\n      ],\n      \"matchCurrentValue\": \"/^((debian|alpine)-)?1\\\\.29\\\\.2$/\",\n      \"replacementName\": \"docker\",\n      \"replacementVersion\": \"23.0.0-cli\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsedb-jdbc-to-enterprisedb","title":"replacements:edb-jdbc-to-enterprisedb","text":"

com.edb:edb-jdbc and com.edb:edb-jdbc18 were moved to com.enterprisedb:edb-jdbc.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"com.edb:edb-jdbc\"\n      ],\n      \"replacementName\": \"com.enterprisedb:edb-jdbc\",\n      \"replacementVersion\": \"42.5.4.2\"\n    },\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"com.edb:edb-jdbc18\"\n      ],\n      \"replacementName\": \"com.enterprisedb:edb-jdbc\",\n      \"replacementVersion\": \"42.5.4.2\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementseslint-config-standard-with-typescript-to-eslint-config-love","title":"replacements:eslint-config-standard-with-typescript-to-eslint-config-love","text":"

eslint-config-standard-with-typescript was renamed to eslint-config-love.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^43.0.1\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"eslint-config-standard-with-typescript\"\n      ],\n      \"replacementName\": \"eslint-config-love\",\n      \"replacementVersion\": \"43.1.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementseslint-plugin-eslint-comments-to-maintained-fork","title":"replacements:eslint-plugin-eslint-comments-to-maintained-fork","text":"

Replace eslint-plugin-eslint-comments with a maintained fork: @eslint-community/eslint-plugin-eslint-comments.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"eslint-plugin-eslint-comments\"\n      ],\n      \"matchCurrentVersion\": \"^3.2.0\",\n      \"replacementName\": \"@eslint-community/eslint-plugin-eslint-comments\",\n      \"replacementVersion\": \"3.2.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementseslint-plugin-node-to-maintained-fork","title":"replacements:eslint-plugin-node-to-maintained-fork","text":"

Replace stale eslint-plugin-node with a maintained fork: eslint-plugin-n.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^11.1.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"eslint-plugin-node\"\n      ],\n      \"replacementName\": \"eslint-plugin-n\",\n      \"replacementVersion\": \"14.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementseslint-plugin-vitest-to-scoped","title":"replacements:eslint-plugin-vitest-to-scoped","text":"

eslint-plugin-vitest became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=0.5.4\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"eslint-plugin-vitest\"\n      ],\n      \"replacementName\": \"@vitest/eslint-plugin\",\n      \"replacementVersion\": \"1.0.1\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsexpress-mung-to-express-response-middleware","title":"replacements:express-mung-to-express-response-middleware","text":"

Replace stale express-mung with a maintained fork: express-response-middleware.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=0.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"express-mung\"\n      ],\n      \"replacementName\": \"express-response-middleware\",\n      \"replacementVersion\": \"1.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsfakerjs-to-scoped","title":"replacements:fakerjs-to-scoped","text":"

fakerjs packages became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"faker\"\n      ],\n      \"replacementName\": \"@faker-js/faker\",\n      \"replacementVersion\": \"5.5.3\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"faker\"\n      ],\n      \"replacementName\": \"@faker-js/faker\",\n      \"replacementVersion\": \"4.1.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.0.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"faker\"\n      ],\n      \"replacementName\": \"@faker-js/faker\",\n      \"replacementVersion\": \"3.1.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.0.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"faker\"\n      ],\n      \"replacementName\": \"@faker-js/faker\",\n      \"replacementVersion\": \"2.1.5\"\n    },\n    {\n      \"matchCurrentVersion\": \"<2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"faker\"\n      ],\n      \"replacementName\": \"@faker-js/faker\",\n      \"replacementVersion\": \"1.1.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsfastify-to-scoped","title":"replacements:fastify-to-scoped","text":"

fastify packages became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=3.3.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-accepts-serializer\"\n      ],\n      \"replacementName\": \"@fastify/accepts-serializer\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.3.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-accepts\"\n      ],\n      \"replacementName\": \"@fastify/accepts\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.2.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-auth\"\n      ],\n      \"replacementName\": \"@fastify/auth\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.13.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-autoload\"\n      ],\n      \"replacementName\": \"@fastify/autoload\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.3.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-awilix\"\n      ],\n      \"replacementName\": \"@fastify/awilix\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.3.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-basic-auth\"\n      ],\n      \"replacementName\": \"@fastify/basic-auth\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=6.3.0 <7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-bearer-auth\"\n      ],\n      \"replacementName\": \"@fastify/bearer-auth\",\n      \"replacementVersion\": \"7.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=6.3.0 <7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-caching\"\n      ],\n      \"replacementName\": \"@fastify/caching\",\n      \"replacementVersion\": \"7.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.2.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-circuit-breaker\"\n      ],\n      \"replacementName\": \"@fastify/circuit-breaker\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.1.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-compress\"\n      ],\n      \"replacementName\": \"@fastify/compress\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=5.7.0 <6.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-cookie\"\n      ],\n      \"replacementName\": \"@fastify/cookie\",\n      \"replacementVersion\": \"6.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=6.1.0 <7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-cors\"\n      ],\n      \"replacementName\": \"@fastify/cors\",\n      \"replacementVersion\": \"7.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.1.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-diagnostics-channel\"\n      ],\n      \"replacementName\": \"@fastify/diagnostics-channel\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.2.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-elasticsearch\"\n      ],\n      \"replacementName\": \"@fastify/elasticsearch\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.2.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-env\"\n      ],\n      \"replacementName\": \"@fastify/env\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.2.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-error\"\n      ],\n      \"replacementName\": \"@fastify/error\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.2.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-etag\"\n      ],\n      \"replacementName\": \"@fastify/etag\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.4.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-express\"\n      ],\n      \"replacementName\": \"@fastify/express\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.1.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-flash\"\n      ],\n      \"replacementName\": \"@fastify/flash\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=5.3.0 <6.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-formbody\"\n      ],\n      \"replacementName\": \"@fastify/formbody\",\n      \"replacementVersion\": \"6.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.1.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-funky\"\n      ],\n      \"replacementName\": \"@fastify/funky\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=7.1.0 <8.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-helmet\"\n      ],\n      \"replacementName\": \"@fastify/helmet\",\n      \"replacementVersion\": \"8.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.3.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-hotwire\"\n      ],\n      \"replacementName\": \"@fastify/hotwire\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=6.3.0 <7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-http-proxy\"\n      ],\n      \"replacementName\": \"@fastify/http-proxy\",\n      \"replacementVersion\": \"7.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.2.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-jwt\"\n      ],\n      \"replacementName\": \"@fastify/jwt\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.3.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-kafka\"\n      ],\n      \"replacementName\": \"@fastify/kafka\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.2.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-leveldb\"\n      ],\n      \"replacementName\": \"@fastify/leveldb\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.2.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-mongodb\"\n      ],\n      \"replacementName\": \"@fastify/mongodb\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=5.4.0 <6.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-multipart\"\n      ],\n      \"replacementName\": \"@fastify/multipart\",\n      \"replacementVersion\": \"6.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.2.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-mysql\"\n      ],\n      \"replacementName\": \"@fastify/mysql\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=7.3.0 <8.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-nextjs\"\n      ],\n      \"replacementName\": \"@fastify/nextjs\",\n      \"replacementVersion\": \"8.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.6.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-oauth2\"\n      ],\n      \"replacementName\": \"@fastify/oauth2\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.5.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-passport\"\n      ],\n      \"replacementName\": \"@fastify/passport\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.7.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-postgres\"\n      ],\n      \"replacementName\": \"@fastify/postgres\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=5.9.0 <6.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-rate-limit\"\n      ],\n      \"replacementName\": \"@fastify/rate-limit\",\n      \"replacementVersion\": \"6.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.4.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-redis\"\n      ],\n      \"replacementName\": \"@fastify/redis\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=6.7.0 <7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-reply-from\"\n      ],\n      \"replacementName\": \"@fastify/reply-from\",\n      \"replacementVersion\": \"7.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.3.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-request-context\"\n      ],\n      \"replacementName\": \"@fastify/request-context\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.3.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-response-validation\"\n      ],\n      \"replacementName\": \"@fastify/response-validation\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.1.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-routes-stats\"\n      ],\n      \"replacementName\": \"@fastify/routes-stats\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.2.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-routes\"\n      ],\n      \"replacementName\": \"@fastify/routes\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=1.1.0 <2.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-schedule\"\n      ],\n      \"replacementName\": \"@fastify/schedule\",\n      \"replacementVersion\": \"2.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.2.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-secure-session\"\n      ],\n      \"replacementName\": \"@fastify/secure-session\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.2.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-sensible\"\n      ],\n      \"replacementName\": \"@fastify/sensible\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.3.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-soap-client\"\n      ],\n      \"replacementName\": \"@fastify/soap-client\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.7.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-static\"\n      ],\n      \"replacementName\": \"@fastify/static\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=5.2.0 <6.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-swagger\"\n      ],\n      \"replacementName\": \"@fastify/swagger\",\n      \"replacementVersion\": \"6.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=3.1.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-url-data\"\n      ],\n      \"replacementName\": \"@fastify/url-data\",\n      \"replacementVersion\": \"4.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.3.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-websocket\"\n      ],\n      \"replacementName\": \"@fastify/websocket\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.1.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"fastify-zipkin\"\n      ],\n      \"replacementName\": \"@fastify/zipkin\",\n      \"replacementVersion\": \"3.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsframer-motion-to-motion","title":"replacements:framer-motion-to-motion","text":"

framer-motion and Motion One have merged under the package name motion, though framer-motion is still being published. motion is now the recommended name.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=11.11.12\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"framer-motion\"\n      ],\n      \"replacementName\": \"motion\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsgoogle-github-action-release-please-to-googleapis","title":"replacements:google-github-action-release-please-to-googleapis","text":"

google-github-action/release-please was renamed to googleapis/release-please.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"github-tags\"\n      ],\n      \"matchPackageNames\": [\n        \"google-github-actions/release-please-action\"\n      ],\n      \"replacementName\": \"googleapis/release-please-action\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsgrafana-oss-to-grafana","title":"replacements:grafana-oss-to-grafana","text":"

grafana/grafana-oss was replaced by grafana/grafana with the same images

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?grafana/grafana-oss$/\"\n      ],\n      \"matchCurrentVersion\": \"12.1.1\",\n      \"replacementName\": \"grafana/grafana\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementshapi-to-scoped","title":"replacements:hapi-to-scoped","text":"

hapi became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=18.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"hapi\"\n      ],\n      \"replacementName\": \"@hapi/hapi\",\n      \"replacementVersion\": \"18.2.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementshome-operations-to-official","title":"replacements:home-operations-to-official","text":"

home-operations only builts these until official versions are released

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=1.18.6\",\n      \"matchDatasources\": [\n        \"helm\",\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"ghcr.io/home-operations/charts-mirror/cilium\"\n      ],\n      \"replacementName\": \"quay.io/cilium/charts/cilium\",\n      \"replacementVersion\": \"1.18.6\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsjade-to-pug","title":"replacements:jade-to-pug","text":"

Jade was renamed to Pug.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"jade\"\n      ],\n      \"replacementName\": \"pug\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsjoi-to-scoped","title":"replacements:joi-to-scoped","text":"

joi became scoped under the hapi organization.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=14.0.0 <14.4.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"joi\"\n      ],\n      \"replacementName\": \"@hapi/joi\",\n      \"replacementVersion\": \"14.4.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsjoi-to-unscoped","title":"replacements:joi-to-unscoped","text":"

joi was moved out of the hapi organization.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=17.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@hapi/joi\"\n      ],\n      \"replacementName\": \"joi\",\n      \"replacementVersion\": \"17.1.1\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsk8s-registry-move","title":"replacements:k8s-registry-move","text":"

The Kubernetes container registry has changed from k8s.gcr.io to registry.k8s.io.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^k8s\\\\.gcr\\\\.io/.+$/\"\n      ],\n      \"replacementNameTemplate\": \"{{{replace 'k8s\\\\.gcr\\\\.io/' 'registry.k8s.io/' packageName}}}\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementskotlin-logging-to-oshai","title":"replacements:kotlin-logging-to-oshai","text":"

replaces kotlin-logging github organization and maven group from MicroUtils to oshai

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"[3,4)\",\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"/^io\\\\.github\\\\.microutils:kotlin-logging/\"\n      ],\n      \"replacementNameTemplate\": \"{{{replace 'io.github.microutils' 'io.github.oshai' packageName}}}\",\n      \"replacementVersion\": \"5.1.4\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsmem-rename","title":"replacements:mem-rename","text":"

mem was renamed to memoize.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^10.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"mem\"\n      ],\n      \"replacementName\": \"memoize\",\n      \"replacementVersion\": \"10.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsmiddie-to-scoped","title":"replacements:middie-to-scoped","text":"

middie became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=7.1.0 <8.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"middie\"\n      ],\n      \"replacementName\": \"@fastify/middie\",\n      \"replacementVersion\": \"8.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsmonochromata-cucumber-reporting-plugin-to-jvt","title":"replacements:monochromata-cucumber-reporting-plugin-to-jvt","text":"

de.monochromata.cucumber:reporting-plugin was moved to me.jvt.cucumber:reporting-plugin.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"de.monochromata.cucumber:reporting-plugin\"\n      ],\n      \"replacementName\": \"me.jvt.cucumber:reporting-plugin\",\n      \"replacementVersion\": \"5.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsnow-to-vercel","title":"replacements:now-to-vercel","text":"

now was renamed to vercel.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=21.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"now\"\n      ],\n      \"replacementName\": \"vercel\",\n      \"replacementVersion\": \"21.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsnpm-run-all-to-maintenance-fork","title":"replacements:npm-run-all-to-maintenance-fork","text":"

Maintenance fork of npm-run-all

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"npm-run-all\"\n      ],\n      \"replacementName\": \"npm-run-all2\",\n      \"replacementVersion\": \"5.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsojdbc-to-ojdbc11","title":"replacements:ojdbc-to-ojdbc11","text":"

ojdbc:ojdbc and com.oracle.database.jdbc:ojdbc10 were moved to com.oracle.database.jdbc:ojdbc11.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"ojdbc:ojdbc\"\n      ],\n      \"replacementName\": \"com.oracle.database.jdbc:ojdbc11\",\n      \"replacementVersion\": \"21.1.0.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"com.oracle.database.jdbc:ojdbc10\"\n      ],\n      \"replacementName\": \"com.oracle.database.jdbc:ojdbc11\",\n      \"replacementVersion\": \"21.1.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsopencost-registry-move","title":"replacements:opencost-registry-move","text":"

Replace OpenCost registry from quay.io to ghcr.io.

{\n  \"packageRules\": [\n    {\n      \"description\": \"Replace `quay.io/kubecost1/kubecost-cost-model` with `ghcr.io/opencost/opencost`.\",\n      \"matchCurrentVersion\": \"1.108.0\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"quay.io/kubecost1/kubecost-cost-model\"\n      ],\n      \"replacementName\": \"ghcr.io/opencost/opencost\",\n      \"replacementVersion\": \"1.109.0\"\n    },\n    {\n      \"description\": \"Replace `quay.io/kubecost1/opencost-ui` with `ghcr.io/opencost/opencost-ui`.\",\n      \"matchCurrentVersion\": \"1.108.0\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"quay.io/kubecost1/opencost-ui\"\n      ],\n      \"replacementName\": \"ghcr.io/opencost/opencost-ui\",\n      \"replacementVersion\": \"1.109.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsparcel-css-to-lightningcss","title":"replacements:parcel-css-to-lightningcss","text":"

@parcel/css was renamed to lightningcss.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@parcel/css\"\n      ],\n      \"replacementName\": \"lightningcss\",\n      \"replacementVersion\": \"1.14.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementspassport-saml","title":"replacements:passport-saml","text":"

passport-saml was renamed to @node-saml/passport-saml.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"passport-saml\"\n      ],\n      \"replacementName\": \"@node-saml/passport-saml\",\n      \"replacementVersion\": \"4.0.4\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementspwpush-to-universal-container","title":"replacements:pwpush-to-universal-container","text":"

Replace deprecated Password Pusher database-specific images with its universal image.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"1.35.0\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?pglombardo/pwpush-(?:ephemeral|mysql|postgres)$/\"\n      ],\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Follow Password Pusher's [universal-container migration guide](https://docs.pwpush.com/docs/how-to-universal/) before merging. Back up the database and validate existing data after migration.\"\n      ],\n      \"replacementName\": \"pglombardo/pwpush\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsreact-native-magic-modal-to-magic-modal","title":"replacements:react-native-magic-modal-to-magic-modal","text":"

react-native-magic-modal was renamed to magic-modal in version 10.0.0. The old name is deprecated but still published at the same version, depending on and re-exporting magic-modal.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=10.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"react-native-magic-modal\"\n      ],\n      \"replacementName\": \"magic-modal\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsreact-query-devtools-to-scoped","title":"replacements:react-query-devtools-to-scoped","text":"

react-query/devtools became scoped under the tanstack organization.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=2.0.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"react-query/devtools\"\n      ],\n      \"replacementName\": \"@tanstack/react-query-devtools\",\n      \"replacementVersion\": \"4.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsreact-query-to-scoped","title":"replacements:react-query-to-scoped","text":"

react-query became scoped under the tanstack organization.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=3.0.0 <4.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"react-query\"\n      ],\n      \"replacementName\": \"@tanstack/react-query\",\n      \"replacementVersion\": \"4.0.5\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsreact-scripts-ts-to-react-scripts","title":"replacements:react-scripts-ts-to-react-scripts","text":"

react-scripts supports TypeScript since version 2.1.0.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"react-scripts-ts\"\n      ],\n      \"replacementName\": \"react-scripts\",\n      \"replacementVersion\": \"2.1.8\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsread-pkg-up-rename","title":"replacements:read-pkg-up-rename","text":"

read-pkg-up was renamed to read-package-up.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"read-pkg-up\"\n      ],\n      \"replacementName\": \"read-package-up\",\n      \"replacementVersion\": \"11.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsredux-devtools-extension-to-scope","title":"replacements:redux-devtools-extension-to-scope","text":"

The redux-devtools-extension package was renamed to @redux-devtools/extension.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"redux-devtools-extension\"\n      ],\n      \"replacementName\": \"@redux-devtools/extension\",\n      \"replacementVersion\": \"3.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrenovate-pep440-to-renovatebot-pep440","title":"replacements:renovate-pep440-to-renovatebot-pep440","text":"

The @renovate/pep440 package was renamed to @renovatebot/pep440.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@renovate/pep440\"\n      ],\n      \"replacementName\": \"@renovatebot/pep440\",\n      \"replacementVersion\": \"1.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrolldown-vite-to-vite","title":"replacements:rolldown-vite-to-vite","text":"

rolldown-vite was merged to vite in version 8.0.0.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rolldown-vite\"\n      ],\n      \"replacementName\": \"vite\",\n      \"replacementVersion\": \"8.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrollup-babel-to-scoped","title":"replacements:rollup-babel-to-scoped","text":"

The babel plugin for rollup became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rollup-plugin-babel\"\n      ],\n      \"replacementName\": \"@rollup/plugin-babel\",\n      \"replacementVersion\": \"5.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrollup-json-to-scoped","title":"replacements:rollup-json-to-scoped","text":"

The json plugin for rollup became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rollup-plugin-json\"\n      ],\n      \"replacementName\": \"@rollup/plugin-json\",\n      \"replacementVersion\": \"4.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrollup-node-resolve-to-scoped","title":"replacements:rollup-node-resolve-to-scoped","text":"

The node-resolve plugin for rollup became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rollup-plugin-node-resolve\"\n      ],\n      \"replacementName\": \"@rollup/plugin-node-resolve\",\n      \"replacementVersion\": \"6.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrollup-terser-to-scoped","title":"replacements:rollup-terser-to-scoped","text":"

The terser plugin for rollup became scoped.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=7.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rollup-plugin-terser\"\n      ],\n      \"replacementName\": \"@rollup/plugin-terser\",\n      \"replacementVersion\": \"0.1.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsrome-to-biome","title":"replacements:rome-to-biome","text":"

The Rome repository is archived, and Biome is the community replacement. Read the Biome announcement for migration instructions.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"rome\"\n      ],\n      \"replacementName\": \"@biomejs/biome\",\n      \"replacementVersion\": \"1.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsscorecard-registry-move","title":"replacements:scorecard-registry-move","text":"

The OpenSSF Scorecard container images moved from gcr.io/openssf/scorecard to ghcr.io/ossf/scorecard.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"gcr.io/openssf/scorecard\"\n      ],\n      \"replacementName\": \"ghcr.io/ossf/scorecard\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementssemantic-release-replace-plugin-to-unscoped","title":"replacements:semantic-release-replace-plugin-to-unscoped","text":"

semantic-release-replace-plugin was moved out of the google organization.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@google/semantic-release-replace-plugin\"\n      ],\n      \"replacementName\": \"semantic-release-replace-plugin\",\n      \"replacementVersion\": \"1.2.1\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsspectre-cli-to-spectre-console-cli","title":"replacements:spectre-cli-to-spectre-console-cli","text":"

The Spectre.Cli package was renamed to Spectre.Console.Cli.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"nuget\"\n      ],\n      \"matchPackageNames\": [\n        \"Spectre.Cli\"\n      ],\n      \"replacementName\": \"Spectre.Console.Cli\",\n      \"replacementVersion\": \"0.45.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsstandard-version-to-commit-and-tag","title":"replacements:standard-version-to-commit-and-tag","text":"

standard-version is now maintained as commit-and-tag-version.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^9.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"standard-version\"\n      ],\n      \"replacementName\": \"commit-and-tag-version\",\n      \"replacementVersion\": \"9.5.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementstemporalio-interceptors-opentelemetry-to-v2","title":"replacements:temporalio-interceptors-opentelemetry-to-v2","text":"

@temporalio/interceptors-opentelemetry was replaced by @temporalio/interceptors-opentelemetry-v2, which supports OpenTelemetry v2.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=1.19.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@temporalio/interceptors-opentelemetry\"\n      ],\n      \"replacementName\": \"@temporalio/interceptors-opentelemetry-v2\",\n      \"replacementVersion\": \"1.19.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsterraform-provider-mrparkers-keycloak-to-keycloak-keycloak","title":"replacements:terraform-provider-mrparkers-keycloak-to-keycloak-keycloak","text":"

The Keycloak Terraform/OpenTofu provider was moved to keycloak/keycloak.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"terraform-provider\"\n      ],\n      \"matchPackageNames\": [\n        \"mrparkers/keycloak\"\n      ],\n      \"matchCurrentVersion\": \"4.4.0\",\n      \"replacementName\": \"keycloak/keycloak\",\n      \"replacementVersion\": \"4.5.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementstsconfig-bases-node","title":"replacements:tsconfig-bases-node","text":"

@tsconfig-bases node updates.

{\n  \"extends\": [\n    \"customManagers:tsconfigNodeVersions\" // (1)!\n  ],\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node**\"\n      ],\n      \"commitMessageExtra\": \"{{#if isReplacement}}with {{{newName}}}{{else}}to {{{prettyNewVersion}}}{{/if}}\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node10\"\n      ],\n      \"replacementName\": \"@tsconfig/node12\",\n      \"replacementVersion\": \"12.1.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node12\"\n      ],\n      \"replacementName\": \"@tsconfig/node14\",\n      \"replacementVersion\": \"14.1.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node14\"\n      ],\n      \"replacementName\": \"@tsconfig/node16\",\n      \"replacementVersion\": \"16.1.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node16\",\n        \"@tsconfig/node17\"\n      ],\n      \"replacementName\": \"@tsconfig/node18\",\n      \"replacementVersion\": \"18.2.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node18\",\n        \"@tsconfig/node19\"\n      ],\n      \"replacementName\": \"@tsconfig/node20\",\n      \"replacementVersion\": \"20.1.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node20\",\n        \"@tsconfig/node21\"\n      ],\n      \"replacementName\": \"@tsconfig/node22\",\n      \"replacementVersion\": \"22.0.0\"\n    },\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@tsconfig/node22\",\n        \"@tsconfig/node23\"\n      ],\n      \"replacementName\": \"@tsconfig/node24\",\n      \"replacementVersion\": \"24.0.0\"\n    }\n  ]\n}\n
  1. customManagers:tsconfigNodeVersions: Update @tsconfig/node extends in tsconfig.json and jsconfig.json files.
"},{"location":"presets-replacements/#replacementstypeorm-seeding-to-scoped","title":"replacements:typeorm-seeding-to-scoped","text":"

typeorm-seeding is now maintained as scoped package.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"1.6.1\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"typeorm-seeding\"\n      ],\n      \"replacementName\": \"@jorgebodega/typeorm-seeding\",\n      \"replacementVersion\": \"2.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsucanaccess-to-io-github-spannm","title":"replacements:ucanaccess-to-io-github-spannm","text":"

net.sf.ucanaccess:ucanaccess is no longer maintained, development continues at io.github.spannm:ucanaccess.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=5.0.1\",\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"net.sf.ucanaccess:ucanaccess\"\n      ],\n      \"replacementName\": \"io.github.spannm:ucanaccess\",\n      \"replacementVersion\": \"5.1.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsvitest-coverage-c8-to-coverage-v8","title":"replacements:vitest-coverage-c8-to-coverage-v8","text":"

@vitest/coverage-c8 was renamed to @vitest/coverage-v8.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=0.32.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@vitest/coverage-c8\"\n      ],\n      \"replacementName\": \"@vitest/coverage-v8\",\n      \"replacementVersion\": \"0.33.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsvso-task-lib-to-azure-pipelines-task-lib","title":"replacements:vso-task-lib-to-azure-pipelines-task-lib","text":"

The vso-task-lib package is now published as azure-pipelines-task-lib.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"vso-task-lib\"\n      ],\n      \"replacementName\": \"azure-pipelines-task-lib\",\n      \"replacementVersion\": \"3.4.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsvsts-task-lib-to-azure-pipelines-task-lib","title":"replacements:vsts-task-lib-to-azure-pipelines-task-lib","text":"

The vsts-task-lib package is now published as azure-pipelines-task-lib.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"vsts-task-lib\"\n      ],\n      \"replacementName\": \"azure-pipelines-task-lib\",\n      \"replacementVersion\": \"3.4.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementswuchale-vite-plugin-to-wuchale","title":"replacements:wuchale-vite-plugin-to-wuchale","text":"

The @wuchale/vite-plugin package is now included in wuchale at wuchale/vite.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"^0.17.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@wuchale/vite-plugin\"\n      ],\n      \"replacementName\": \"wuchale\",\n      \"replacementVersion\": \"0.22.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsxlsx-to-scoped","title":"replacements:xlsx-to-scoped","text":"

The xlsx package is now published as @e965/xlsx.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \"0.18.5\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"xlsx\"\n      ],\n      \"replacementName\": \"@e965/xlsx\",\n      \"replacementVersion\": \"0.20.3\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsxmldom-to-scoped","title":"replacements:xmldom-to-scoped","text":"

The xmldom package is now published as @xmldom/xmldom.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"xmldom\",\n        \"xmldom-alpha\"\n      ],\n      \"replacementName\": \"@xmldom/xmldom\",\n      \"replacementVersion\": \"0.7.5\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementszap","title":"replacements:zap","text":"

Replace ZAP dependencies.

{\n  \"packageRules\": [\n    {\n      \"description\": \"The `zap-stable` image has moved to the `zaproxy` organization.\",\n      \"matchCurrentVersion\": \">=2.0.0 <2.14.0\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?owasp/zap2docker-stable$/\",\n        \"/^(?:docker\\\\.io/)?softwaresecurityproject/zap-stable$/\"\n      ],\n      \"replacementName\": \"zaproxy/zap-stable\",\n      \"replacementVersion\": \"2.14.0\"\n    },\n    {\n      \"description\": \"The `zap-bare` image has moved to the `zaproxy` organization.\",\n      \"matchCurrentVersion\": \">=2.0.0 <2.14.0\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:docker\\\\.io/)?owasp/zap2docker-bare$/\",\n        \"/^(?:docker\\\\.io/)?softwaresecurityproject/zap-bare$/\"\n      ],\n      \"replacementName\": \"zaproxy/zap-bare\",\n      \"replacementVersion\": \"2.14.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsmessageformat-to-scoped","title":"replacements:messageFormat-to-scoped","text":"

The messageformat monorepo package naming scheme changed from messageFormat-{{package}} to @messageformat/{{package}}.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=2.0.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"messageformat-cli\"\n      ],\n      \"replacementName\": \"@messageformat/cli\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=2.0.0 <3.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"messageformat\"\n      ],\n      \"replacementName\": \"@messageformat/core\",\n      \"replacementVersion\": \"3.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.4.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"messageformat-convert\"\n      ],\n      \"replacementName\": \"@messageformat/convert\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=0.4.0 <1.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"react-message-context\"\n      ],\n      \"replacementName\": \"@messageformat/react\",\n      \"replacementVersion\": \"1.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"messageformat-parser\"\n      ],\n      \"replacementName\": \"@messageformat/parser\",\n      \"replacementVersion\": \"5.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-replacements/#replacementsmaterial-ui-to-mui","title":"replacements:material-ui-to-mui","text":"

The material-ui monorepo org was renamed from @material-ui to @mui.

{\n  \"packageRules\": [\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/codemod\"\n      ],\n      \"replacementName\": \"@mui/codemod\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/core\"\n      ],\n      \"replacementName\": \"@mui/material\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/icons\"\n      ],\n      \"replacementName\": \"@mui/icons-material\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/lab\"\n      ],\n      \"replacementName\": \"@mui/lab\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/private-theming\"\n      ],\n      \"replacementName\": \"@mui/private-theming\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/styled-engine\"\n      ],\n      \"replacementName\": \"@mui/styled-engine\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/styled-engine-sc\"\n      ],\n      \"replacementName\": \"@mui/styled-engine-sc\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/styles\"\n      ],\n      \"replacementName\": \"@mui/styles\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/system\"\n      ],\n      \"replacementName\": \"@mui/system\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/types\"\n      ],\n      \"replacementName\": \"@mui/types\",\n      \"replacementVersion\": \"5.0.0\"\n    },\n    {\n      \"matchCurrentVersion\": \">=4.0.0 <5.0.0\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@material-ui/unstyled\"\n      ],\n      \"replacementName\": \"@mui/core\",\n      \"replacementVersion\": \"5.0.0\"\n    }\n  ]\n}\n
"},{"location":"presets-schedule/","title":"Schedule Presets","text":""},{"location":"presets-schedule/#scheduleautomergedaily","title":"schedule:automergeDaily","text":"

Schedule automerge daily before 4 AM.

{\n  \"automergeSchedule\": [\n    \"* 0-3 * * *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergeearlymondays","title":"schedule:automergeEarlyMondays","text":"

Schedule automerge on Monday mornings (before 4 AM).

{\n  \"automergeSchedule\": [\n    \"* 0-3 * * 1\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergemonthly","title":"schedule:automergeMonthly","text":"

Schedule automerge for the first day of each month, before 4 AM.

{\n  \"automergeSchedule\": [\n    \"* 0-3 1 * *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergenonofficehours","title":"schedule:automergeNonOfficeHours","text":"

Schedule automerge during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends.

{\n  \"automergeSchedule\": [\n    \"* 0-4,22-23 * * 1-5\",\n    \"* * * * 0,6\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergeofficehours","title":"schedule:automergeOfficeHours","text":"

Schedule automerge during typical office hours on weekdays (i.e., 8 AM - 6 PM).

{\n  \"automergeSchedule\": [\n    \"* 8-17 * * 1-5\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergequarterly","title":"schedule:automergeQuarterly","text":"

Schedule automerge on the first day of each quarter (i.e., January, April, July, October).

{\n  \"automergeSchedule\": [\n    \"* * 1 */3 *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergeweekdays","title":"schedule:automergeWeekdays","text":"

Schedule automerge anytime on weekdays.

{\n  \"automergeSchedule\": [\n    \"* * * * 1-5\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergeweekends","title":"schedule:automergeWeekends","text":"

Schedule automerge anytime on weekends.

{\n  \"automergeSchedule\": [\n    \"* * * * 0,6\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleautomergeweekly","title":"schedule:automergeWeekly","text":"

Schedule automerge weekly.

{\n  \"extends\": [\n    \"schedule:automergeEarlyMondays\" // (1)!\n  ]\n}\n
  1. schedule:automergeEarlyMondays: Schedule automerge on Monday mornings (before 4 AM).
"},{"location":"presets-schedule/#scheduleautomergeyearly","title":"schedule:automergeYearly","text":"

Schedule automerge once a year on the first day of January (not recommended).

{\n  \"automergeSchedule\": [\n    \"* * 1 */12 *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduledaily","title":"schedule:daily","text":"

Schedule daily before 4 AM.

{\n  \"schedule\": [\n    \"* 0-3 * * *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleearlymondays","title":"schedule:earlyMondays","text":"

Weekly schedule on early Monday mornings (before 4 AM).

{\n  \"schedule\": [\n    \"* 0-3 * * 1\"\n  ]\n}\n
"},{"location":"presets-schedule/#schedulemonthly","title":"schedule:monthly","text":"

Schedule once a month on the first day of the month before 4 AM.

{\n  \"schedule\": [\n    \"* 0-3 1 * *\"\n  ]\n}\n
"},{"location":"presets-schedule/#schedulenonofficehours","title":"schedule:nonOfficeHours","text":"

Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends.

{\n  \"schedule\": [\n    \"* 0-4,22-23 * * 1-5\",\n    \"* * * * 0,6\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleofficehours","title":"schedule:officeHours","text":"

Schedule during typical office hours on weekdays (i.e., 8 AM - 6 PM).

{\n  \"schedule\": [\n    \"* 8-17 * * 1-5\"\n  ]\n}\n
"},{"location":"presets-schedule/#schedulequarterly","title":"schedule:quarterly","text":"

Schedule on the first day of each quarter (i.e., January, April, July, October).

{\n  \"schedule\": [\n    \"* * 1 */3 *\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleweekdays","title":"schedule:weekdays","text":"

Schedule for weekdays.

{\n  \"schedule\": [\n    \"* * * * 1-5\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleweekends","title":"schedule:weekends","text":"

Schedule for weekends.

{\n  \"schedule\": [\n    \"* * * * 0,6\"\n  ]\n}\n
"},{"location":"presets-schedule/#scheduleweekly","title":"schedule:weekly","text":"

Schedule weekly.

{\n  \"extends\": [\n    \"schedule:earlyMondays\" // (1)!\n  ]\n}\n
  1. schedule:earlyMondays: Weekly schedule on early Monday mornings (before 4 AM).
"},{"location":"presets-schedule/#scheduleyearly","title":"schedule:yearly","text":"

Schedule once a year on the first day of January (not recommended).

{\n  \"schedule\": [\n    \"* * 1 */12 *\"\n  ]\n}\n
"},{"location":"presets-security/","title":"Security Presets","text":""},{"location":"presets-security/#securitygomodindirectsecurityupdates","title":"security:gomodIndirectSecurityUpdates","text":"

Enable go.mod indirect dependency updates only when vulnerabilities have been detected.

{\n  \"extends\": [\n    \":enableVulnerabilityAlerts\" // (1)!\n  ],\n  \"packageRules\": [\n    {\n      \"description\": \"Enable lookups for indirect go.mod dependencies\",\n      \"enabled\": true,\n      \"matchDepTypes\": [\n        \"indirect\"\n      ],\n      \"matchManagers\": [\n        \"gomod\"\n      ]\n    },\n    {\n      \"description\": \"Disable non-security updates for indirect go.mod dependencies (vulnerability alerts use force to override this)\",\n      \"enabled\": false,\n      \"matchDepTypes\": [\n        \"indirect\"\n      ],\n      \"matchManagers\": [\n        \"gomod\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\",\n        \"minor\",\n        \"patch\",\n        \"pin\",\n        \"digest\",\n        \"pinDigest\",\n        \"lockFileMaintenance\",\n        \"rollback\",\n        \"replacement\"\n      ]\n    }\n  ]\n}\n
  1. :enableVulnerabilityAlerts: Raise PR when vulnerability alerts are detected.
"},{"location":"presets-security/#securityminimumreleaseagecrate","title":"security:minimumReleaseAgeCrate","text":"

Wait until the Crate version is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in crates, and b) reduces the risk of upgrading to a newly published crate that its owner deletes during crates.io's initial 72-hour deletion window.

{\n  \"packageRules\": [\n    {\n      \"internalChecksFilter\": \"strict\",\n      \"matchDatasources\": [\n        \"crate\"\n      ],\n      \"minimumReleaseAge\": \"3 days\"\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that are controlled by the package manager\",\n      \"matchUpdateTypes\": [\n        \"lockFileMaintenance\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's lock file maintenance functionality does not support validating Minimum Release Age, as the package manager performs the required changes to update package(s). Confirm whether your package manager perform its own validation for the Minimum Release Age of packages.\"\n      ],\n      \"matchDatasources\": [\n        \"crate\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package replacements\",\n      \"matchUpdateTypes\": [\n        \"replacement\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's replacement functionality [does not currently](https://github.com/renovatebot/renovate/issues/39400) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"crate\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package pinning\",\n      \"matchUpdateTypes\": [\n        \"pin\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's pin functionality [does not currently](https://github.com/renovatebot/renovate/issues/40288) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"crate\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that do not provide a release timestamp\",\n      \"matchUpdateTypes\": [\n        \"bump\",\n        \"lockfileUpdate\",\n        \"rollback\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate does not enforce Minimum Release Age for `bump`, `lockfileUpdate`, or `rollback` updates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"crate\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-security/#securityminimumreleaseagenpm","title":"security:minimumReleaseAgeNpm","text":"

Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.

{\n  \"packageRules\": [\n    {\n      \"internalChecksFilter\": \"strict\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"minimumReleaseAge\": \"3 days\"\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that are controlled by the package manager\",\n      \"matchUpdateTypes\": [\n        \"lockFileMaintenance\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's lock file maintenance functionality does not support validating Minimum Release Age, as the package manager performs the required changes to update package(s). Confirm whether your package manager perform its own validation for the Minimum Release Age of packages.\"\n      ],\n      \"matchDatasources\": [\n        \"npm\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package replacements\",\n      \"matchUpdateTypes\": [\n        \"replacement\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's replacement functionality [does not currently](https://github.com/renovatebot/renovate/issues/39400) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"npm\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package pinning\",\n      \"matchUpdateTypes\": [\n        \"pin\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's pin functionality [does not currently](https://github.com/renovatebot/renovate/issues/40288) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"npm\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that do not provide a release timestamp\",\n      \"matchUpdateTypes\": [\n        \"bump\",\n        \"lockfileUpdate\",\n        \"rollback\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate does not enforce Minimum Release Age for `bump`, `lockfileUpdate`, or `rollback` updates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"npm\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-security/#securityminimumreleaseagepypi","title":"security:minimumReleaseAgePypi","text":"

Wait until the Python package is three days old before raising the update. This introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages.

{\n  \"packageRules\": [\n    {\n      \"internalChecksFilter\": \"strict\",\n      \"matchDatasources\": [\n        \"pypi\"\n      ],\n      \"minimumReleaseAge\": \"3 days\"\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that are controlled by the package manager\",\n      \"matchUpdateTypes\": [\n        \"lockFileMaintenance\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's lock file maintenance functionality does not support validating Minimum Release Age, as the package manager performs the required changes to update package(s). Confirm whether your package manager perform its own validation for the Minimum Release Age of packages.\"\n      ],\n      \"matchDatasources\": [\n        \"pypi\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package replacements\",\n      \"matchUpdateTypes\": [\n        \"replacement\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's replacement functionality [does not currently](https://github.com/renovatebot/renovate/issues/39400) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"pypi\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for package pinning\",\n      \"matchUpdateTypes\": [\n        \"pin\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate's pin functionality [does not currently](https://github.com/renovatebot/renovate/issues/40288) wire in the release age for a package, so the Minimum Release Age checks can apply. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"pypi\"\n      ]\n    },\n    {\n      \"description\": \"Do not require Minimum Release Age for update types that do not provide a release timestamp\",\n      \"matchUpdateTypes\": [\n        \"bump\",\n        \"lockfileUpdate\",\n        \"rollback\"\n      ],\n      \"minimumReleaseAge\": null,\n      \"prBodyNotes\": [\n        \"\u26a0\ufe0f Renovate does not enforce Minimum Release Age for `bump`, `lockfileUpdate`, or `rollback` updates, so these are raised without a Minimum Release Age check. You will need to manually validate the Minimum Release Age for these package(s).\"\n      ],\n      \"matchDatasources\": [\n        \"pypi\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-security/#securityonly-security-updates","title":"security:only-security-updates","text":"

Only update dependencies if vulnerabilities have been detected.

{\n  \"extends\": [\n    \"config:recommended\" // (1)!\n  ],\n  \"osvVulnerabilityAlerts\": true,\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchPackageNames\": [\n        \"*\"\n      ]\n    }\n  ],\n  \"vulnerabilityAlerts\": {\n    \"enabled\": true\n  }\n}\n
  1. config:recommended: Recommended configuration for most users. It does not matter what programming language you use.
"},{"location":"presets-security/#securityopenssf-scorecard","title":"security:openssf-scorecard","text":"

Show OpenSSF badge on pull requests.

{\n  \"packageRules\": [\n    {\n      \"matchSourceUrls\": [\n        \"https://github.com/**\"\n      ],\n      \"prBodyColumns\": [\n        \"Package\",\n        \"Type\",\n        \"Update\",\n        \"Change\",\n        \"Pending\",\n        \"OpenSSF\"\n      ],\n      \"prBodyDefinitions\": {\n        \"OpenSSF\": \"[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/{{sourceRepo}}/badge)](https://securityscorecards.dev/viewer/?uri=github.com/{{sourceRepo}})\"\n      }\n    }\n  ]\n}\n
"},{"location":"presets-security/#securityphp2shell","title":"security:php2shell","text":"

Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"github-tags\",\n      \"depNameTemplate\": \"php\",\n      \"depTypeTemplate\": \"php2shell-runtime\",\n      \"extractVersionTemplate\": \"^php-(?<version>\\\\S+)\",\n      \"managerFilePatterns\": [\n        \"/(^|/)\\\\.php-version$/\"\n      ],\n      \"matchStrings\": [\n        \"^\\\\s*(?<currentValue>8\\\\.[2-5]\\\\.\\\\d+)\\\\s*$\"\n      ],\n      \"packageNameTemplate\": \"php/php-src\"\n    },\n    {\n      \"customType\": \"jsonata\",\n      \"datasourceTemplate\": \"github-tags\",\n      \"depNameTemplate\": \"php\",\n      \"depTypeTemplate\": \"php2shell-runtime\",\n      \"extractVersionTemplate\": \"^php-(?<version>\\\\S+)\",\n      \"fileFormat\": \"yaml\",\n      \"managerFilePatterns\": [\n        \"/(^|/)(workflow-templates|\\\\.(?:github|gitea|forgejo)/(?:workflows|actions))/.+\\\\.ya?ml$/\",\n        \"/(^|/)action\\\\.ya?ml$/\"\n      ],\n      \"matchStrings\": [\n        \"**[uses and $exists($match(uses, /^shivammathur\\\\/setup-php@/))].with.\\\"php-version\\\"[$type($) = \\\"string\\\" and $exists($match($, /^8\\\\.[2-5]\\\\.\\\\d+$/))].{\\\"currentValue\\\": $}\"\n      ],\n      \"packageNameTemplate\": \"php/php-src\"\n    }\n  ],\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDepTypes\": [\n        \"php2shell-runtime\"\n      ],\n      \"matchManagers\": [\n        \"custom.regex\",\n        \"custom.jsonata\"\n      ]\n    },\n    {\n      \"enabled\": true,\n      \"matchDepTypes\": [\n        \"php2shell-runtime\"\n      ],\n      \"matchJsonata\": [\n        \"(\\n  $value := (manager = \\\"mise\\\" and isLockfileOnly) ? lockedVersion : currentValue;\\n  $version := datasource = \\\"docker\\\" ? $split($value, \\\"-\\\")[0] : $value;\\n  $parts := $match($version, /^(8\\\\.[2-5])\\\\.(\\\\d+)$/).groups;\\n\\n  $not(vulnerabilityAlerts.enabled = false) and $exists($parts)\\n    and $number($parts[1]) < $lookup({\\\"8.2\\\":35,\\\"8.3\\\":36,\\\"8.4\\\":27,\\\"8.5\\\":12}, $parts[0])\\n)\"\n      ],\n      \"matchManagers\": [\n        \"custom.regex\",\n        \"custom.jsonata\"\n      ]\n    },\n    {\n      \"isVulnerabilityAlert\": true,\n      \"matchJsonata\": [\n        \"(\\n  $value := (manager = \\\"mise\\\" and isLockfileOnly) ? lockedVersion : currentValue;\\n  $version := datasource = \\\"docker\\\" ? $split($value, \\\"-\\\")[0] : $value;\\n  $parts := $match($version, /^(8\\\\.[2-5])\\\\.(\\\\d+)$/).groups;\\n\\n  $not(vulnerabilityAlerts.enabled = false) and $exists($parts)\\n    and $number($parts[1]) < $lookup({\\\"8.2\\\":35,\\\"8.3\\\":36,\\\"8.4\\\":27,\\\"8.5\\\":12}, $parts[0])\\n) and (\\n      $version := datasource = \\\"docker\\\" ? $split(newVersion, \\\"-\\\")[0] : newVersion;\\n      $parts := $match($version, /^(8\\\\.[2-5])\\\\.(\\\\d+)$/).groups;\\n\\n      $exists($parts) and $number($parts[1]) >= $lookup({\\\"8.2\\\":35,\\\"8.3\\\":36,\\\"8.4\\\":27,\\\"8.5\\\":12}, $parts[0])\\n    )\"\n      ],\n      \"matchUpdateTypes\": [\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ],\n      \"prBodyNotes\": [\n        \"> \u26a0\ufe0f PHP2Shell vulnerabilities can allow remote code execution. This PR updates affected PHP versions to patched releases. Rebuild affected images, deploy the updates, and restart PHP workers.\\n>\\n> Details: [CVE-2026-109618](https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w) and [CVE-2026-109619](https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp).\"\n      ],\n      \"schedule\": [],\n      \"matchDatasources\": [\n        \"github-tags\"\n      ],\n      \"matchPackageNames\": [\n        \"containerbase/php-prebuild\",\n        \"php/php-src\"\n      ]\n    },\n    {\n      \"isVulnerabilityAlert\": true,\n      \"matchJsonata\": [\n        \"(\\n  $value := (manager = \\\"mise\\\" and isLockfileOnly) ? lockedVersion : currentValue;\\n  $version := datasource = \\\"docker\\\" ? $split($value, \\\"-\\\")[0] : $value;\\n  $parts := $match($version, /^(8\\\\.[2-5])\\\\.(\\\\d+)$/).groups;\\n\\n  $not(vulnerabilityAlerts.enabled = false) and $exists($parts)\\n    and $number($parts[1]) < $lookup({\\\"8.2\\\":35,\\\"8.3\\\":36,\\\"8.4\\\":27,\\\"8.5\\\":12}, $parts[0])\\n) and (\\n      $version := datasource = \\\"docker\\\" ? $split(newVersion, \\\"-\\\")[0] : newVersion;\\n      $parts := $match($version, /^(8\\\\.[2-5])\\\\.(\\\\d+)$/).groups;\\n\\n      $exists($parts) and $number($parts[1]) >= $lookup({\\\"8.2\\\":35,\\\"8.3\\\":36,\\\"8.4\\\":27,\\\"8.5\\\":12}, $parts[0])\\n    )\"\n      ],\n      \"matchUpdateTypes\": [\n        \"patch\",\n        \"minor\",\n        \"major\"\n      ],\n      \"prBodyNotes\": [\n        \"> \u26a0\ufe0f PHP2Shell vulnerabilities can allow remote code execution. This PR updates affected PHP versions to patched releases. Rebuild affected images, deploy the updates, and restart PHP workers.\\n>\\n> Details: [CVE-2026-109618](https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w) and [CVE-2026-109619](https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp).\"\n      ],\n      \"schedule\": [],\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:(?:docker\\\\.io|index\\\\.docker\\\\.io)\\\\/)?(?:library\\\\/)?php$/\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/","title":"Workaround Presets","text":""},{"location":"presets-workarounds/#workaroundsall","title":"workarounds:all","text":"

Apply crowd-sourced workarounds for known problems with packages.

{\n  \"extends\": [\n    \"workarounds:mavenCommonsAncientVersion\", // (1)!\n    \"workarounds:ignoreSpringCloudNumeric\", // (2)!\n    \"workarounds:ignoreWeb3jCoreWithOldReleaseTimestamp\", // (3)!\n    \"workarounds:ignoreHttp4sDigestMilestones\", // (4)!\n    \"workarounds:typesNodeVersioning\", // (5)!\n    \"workarounds:nodeDockerVersioning\", // (6)!\n    \"workarounds:doNotUpgradeFromAlpineStableToEdge\", // (7)!\n    \"workarounds:supportRedHatImageVersion\", // (8)!\n    \"workarounds:javaLTSVersions\", // (9)!\n    \"workarounds:disableEclipseLifecycleMapping\", // (10)!\n    \"workarounds:disableGradleReplacements\", // (11)!\n    \"workarounds:disableMavenParentRoot\", // (12)!\n    \"workarounds:containerbase\", // (13)!\n    \"workarounds:bitnamiDockerImageVersioning\", // (14)!\n    \"workarounds:clamavDockerImageVersioning\", // (15)!\n    \"workarounds:grafanaDockerImageVersioning\", // (16)!\n    \"workarounds:k3sKubernetesVersioning\", // (17)!\n    \"workarounds:rke2KubernetesVersioning\", // (18)!\n    \"workarounds:libericaJdkDockerVersioning\", // (19)!\n    \"workarounds:ubuntuDockerVersioning\", // (20)!\n    \"workarounds:groupings\", // (21)!\n    \"workarounds:helmDocs\", // (22)!\n    \"workarounds:guavaVariants\" // (23)!\n  ]\n}\n
  1. workarounds:mavenCommonsAncientVersion: Fix some problems with very old Maven commons versions.
  2. workarounds:ignoreSpringCloudNumeric: Ignore spring cloud 1.x releases.
  3. workarounds:ignoreWeb3jCoreWithOldReleaseTimestamp: Ignore web3j 5.0.0 release.
  4. workarounds:ignoreHttp4sDigestMilestones: Ignore http4s digest-based 1.x milestones.
  5. workarounds:typesNodeVersioning: Use node versioning for @types/node.
  6. workarounds:nodeDockerVersioning: Use node versioning for node docker images.
  7. workarounds:doNotUpgradeFromAlpineStableToEdge: Do not upgrade from Alpine stable to edge.
  8. workarounds:supportRedHatImageVersion: Use specific versioning for Red Hat-maintained container images.
  9. workarounds:javaLTSVersions: Limit Java runtime versions to LTS releases.
  10. workarounds:disableEclipseLifecycleMapping: Disable Eclipse m2e lifecycle-mapping placeholder package.
  11. workarounds:disableGradleReplacements: Disable package replacement updates for gradle dependencies.
  12. workarounds:disableMavenParentRoot: Avoid version fetching for Maven packages detected as project root.
  13. workarounds:containerbase: Add some containerbase overrides.
  14. workarounds:bitnamiDockerImageVersioning: Use custom regex versioning for bitnami images
  15. workarounds:clamavDockerImageVersioning: Use custom regex versioning for ClamAV images
  16. workarounds:grafanaDockerImageVersioning: Support security releases on Grafana (product) images
  17. workarounds:k3sKubernetesVersioning: Use custom regex versioning for k3s-io/k3s
  18. workarounds:rke2KubernetesVersioning: Use custom regex versioning for rancher/rke2
  19. workarounds:libericaJdkDockerVersioning: Use custom regex versioning for bellsoft/liberica-runtime-container
  20. workarounds:ubuntuDockerVersioning: Use ubuntu versioning for ubuntu docker images.
  21. workarounds:groupings: Groupings for specific package updates.
  22. workarounds:helmDocs: Block helm-docs calver-like versions from 2019
  23. workarounds:guavaVariants: Keep Guava on its -jre or -android variant.
"},{"location":"presets-workarounds/#workaroundsbitnamidockerimageversioning","title":"workarounds:bitnamiDockerImageVersioning","text":"

Use custom regex versioning for bitnami images

{\n  \"packageRules\": [\n    {\n      \"matchCurrentValue\": \"/^(?<major>\\\\d+)(?:\\\\.(?<minor>\\\\d+)(?:\\\\.(?<patch>\\\\d+))?)?-(?<compatibility>.+)-(?<build>\\\\d+)(?:-r(?<revision>\\\\d+))?$/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"bitnami/**\",\n        \"docker.io/bitnami/**\",\n        \"gcr.io/bitnami-containers/**\",\n        \"*-docker.pkg.dev/vmw-app-catalog/**\"\n      ],\n      \"versioning\": \"regex:^(?<major>\\\\d+)(?:\\\\.(?<minor>\\\\d+)(?:\\\\.(?<patch>\\\\d+))?)?(:?-(?<compatibility>.+)-(?<build>\\\\d+)(?:-r(?<revision>\\\\d+))?)?$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsclamavdockerimageversioning","title":"workarounds:clamavDockerImageVersioning","text":"

Use custom regex versioning for ClamAV images

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"clamav/clamav\",\n        \"clamav/clamav-debian\"\n      ],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)(\\\\.(?<patch>\\\\d+))?(-(?<build>\\\\d+))?(_(?<compatibility>.+))?$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundscontainerbase","title":"workarounds:containerbase","text":"

Add some containerbase overrides.

{\n  \"packageRules\": [\n    {\n      \"description\": \"Use node versioning for `(containerbase|renovate)/node` images\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/^(?:(?:docker|ghcr)\\\\.io/)?(?:containerbase|renovate)/node$/\"\n      ],\n      \"versioning\": \"node\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsdisableeclipselifecyclemapping","title":"workarounds:disableEclipseLifecycleMapping","text":"

Disable Eclipse m2e lifecycle-mapping placeholder package.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"org.eclipse.m2e:lifecycle-mapping\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsdisablegradlereplacements","title":"workarounds:disableGradleReplacements","text":"

Disable package replacement updates for gradle dependencies.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchManagers\": [\n        \"gradle\"\n      ],\n      \"matchUpdateTypes\": [\n        \"replacement\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsdisablemavenparentroot","title":"workarounds:disableMavenParentRoot","text":"

Avoid version fetching for Maven packages detected as project root.

{\n  \"packageRules\": [\n    {\n      \"enabled\": false,\n      \"matchDepTypes\": [\n        \"parent-root\"\n      ],\n      \"matchManagers\": [\n        \"maven\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsdonotupgradefromalpinestabletoedge","title":"workarounds:doNotUpgradeFromAlpineStableToEdge","text":"

Do not upgrade from Alpine stable to edge.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"<20000000\",\n      \"matchCurrentVersion\": \"!/^\\\\d{8}$/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchDepNames\": [\n        \"alpine\"\n      ]\n    },\n    {\n      \"allowedVersions\": \"<20000000\",\n      \"matchCurrentVersion\": \"!/^\\\\d{8}$/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"alpine\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsgrafanadockerimageversioning","title":"workarounds:grafanaDockerImageVersioning","text":"

Support security releases on Grafana (product) images

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"grafana/grafana\",\n        \"docker.io/grafana/grafana\",\n        \"grafana/grafana-enterprise\",\n        \"docker.io/grafana/grafana-enterprise\"\n      ],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)(?:-security-(?<build>\\\\d+))?(?:-(?<compatibility>.*))?$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsgroupings","title":"workarounds:groupings","text":"

Groupings for specific package updates.

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group commander major updates, they depend on each other.\",\n      \"groupName\": \"commander\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@commander-js/extra-typings\",\n        \"commander\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    },\n    {\n      \"description\": \"Group SimpleWebAuthn major updates to keep browser and server compatible.\",\n      \"groupName\": \"SimpleWebAuthn\",\n      \"matchDatasources\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@simplewebauthn/browser\",\n        \"@simplewebauthn/server\"\n      ],\n      \"matchUpdateTypes\": [\n        \"major\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsguavavariants","title":"workarounds:guavaVariants","text":"

Keep Guava on its -jre or -android variant.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"maven\",\n        \"sbt-package\"\n      ],\n      \"matchPackageNames\": [\n        \"com.google.guava:guava\"\n      ],\n      \"versionCompatibility\": \"^(?<version>.+)-(?<compatibility>jre|android)$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundshelmdocs","title":"workarounds:helmDocs","text":"

Block helm-docs calver-like versions from 2019

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"!/^19\\\\.(0614|0110)$/\",\n      \"matchPackageNames\": [\n        \"norwoodj/helm-docs\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsignorehttp4sdigestmilestones","title":"workarounds:ignoreHttp4sDigestMilestones","text":"

Ignore http4s digest-based 1.x milestones.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"!/^1\\\\.0-\\\\d+-[a-fA-F0-9]{7}$/\",\n      \"matchManagers\": [\n        \"sbt\"\n      ],\n      \"matchPackageNames\": [\n        \"org.http4s:**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsignorespringcloudnumeric","title":"workarounds:ignoreSpringCloudNumeric","text":"

Ignore spring cloud 1.x releases.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"/^[A-Z]/\",\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"org.springframework.cloud:spring-cloud-starter-parent\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsignoreweb3jcorewitholdreleasetimestamp","title":"workarounds:ignoreWeb3jCoreWithOldReleaseTimestamp","text":"

Ignore web3j 5.0.0 release.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"!/^5\\\\.0\\\\.0/\",\n      \"matchDatasources\": [\n        \"maven\"\n      ],\n      \"matchPackageNames\": [\n        \"org.web3j:core\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsjavaltsversions","title":"workarounds:javaLTSVersions","text":"

Limit Java runtime versions to LTS releases.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"/^(?:8|11|17|21|25)(?:\\\\.|-|$)/\",\n      \"description\": \"Limit Java runtime versions to LTS releases. To receive all major releases add `workarounds:javaLTSVersions` to the `ignorePresets` array.\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"java-version\"\n      ],\n      \"matchPackageNames\": [\n        \"eclipse-temurin\",\n        \"amazoncorretto\",\n        \"adoptopenjdk\",\n        \"openjdk\",\n        \"java\",\n        \"java-jdk\",\n        \"java-jre\",\n        \"sapmachine\",\n        \"/^azul/zulu-openjdk/\",\n        \"/^bellsoft/liberica-openj(dk|re)-/\",\n        \"/^cimg/openjdk/\"\n      ],\n      \"versioning\": \"regex:^(?<major>\\\\d+)?(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?([\\\\._+](?<build>(\\\\d\\\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$\"\n    },\n    {\n      \"allowedVersions\": \"/^(?:8|11|17|21|25)(?:\\\\.|-|$)/\",\n      \"description\": \"Limit Java runtime versions to LTS releases. To receive all major releases add `workarounds:javaLTSVersions` to the `ignorePresets` array.\",\n      \"matchDatasources\": [\n        \"docker\",\n        \"java-version\"\n      ],\n      \"matchDepNames\": [\n        \"eclipse-temurin\",\n        \"amazoncorretto\",\n        \"adoptopenjdk\",\n        \"openjdk\",\n        \"java\",\n        \"java-jre\",\n        \"sapmachine\"\n      ],\n      \"versioning\": \"regex:^(?<major>\\\\d+)?(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?([\\\\._+](?<build>(\\\\d\\\\.?)+)(LTS)?)?(-(?<compatibility>.*))?$\"\n    },\n    {\n      \"description\": \"Use docker versioning for major-only Java image tags so rolling tags (e.g. 21-jre) are not upgraded to full-precision tags (e.g. 21.0.11_10-jre).\",\n      \"matchCurrentValue\": \"/^\\\\d+(-|$)/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"eclipse-temurin\",\n        \"amazoncorretto\",\n        \"adoptopenjdk\",\n        \"openjdk\",\n        \"java\",\n        \"java-jdk\",\n        \"java-jre\",\n        \"sapmachine\",\n        \"/^azul/zulu-openjdk/\",\n        \"/^bellsoft/liberica-openj(dk|re)-/\",\n        \"/^cimg/openjdk/\"\n      ],\n      \"versioning\": \"docker\"\n    },\n    {\n      \"description\": \"Use docker versioning for major-only Java image tags so rolling tags (e.g. 21-jre) are not upgraded to full-precision tags (e.g. 21.0.11_10-jre).\",\n      \"matchCurrentValue\": \"/^\\\\d+(-|$)/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchDepNames\": [\n        \"eclipse-temurin\",\n        \"amazoncorretto\",\n        \"adoptopenjdk\",\n        \"openjdk\",\n        \"java\",\n        \"java-jre\",\n        \"sapmachine\"\n      ],\n      \"versioning\": \"docker\"\n    },\n    {\n      \"description\": \"Use partial semver versioning for partial mise and GitHub Actions Java versions so rolling versions (e.g. 21) are not upgraded to full-precision versions (e.g. 21.0.11+9.0.LTS).\",\n      \"matchCurrentValue\": \"/^\\\\d+(?:\\\\.\\\\d+)?$/\",\n      \"matchDatasources\": [\n        \"java-version\"\n      ],\n      \"matchManagers\": [\n        \"github-actions\",\n        \"mise\"\n      ],\n      \"versioning\": \"semver-partial\"\n    },\n    {\n      \"allowedVersions\": \"/^(?:jdk|jdk-all|jre)-(?:8|11|17|21|25)(?:\\\\.|-|$)/\",\n      \"description\": \"Limit Java runtime versions to LTS releases. To receive all major releases add `workarounds:javaLTSVersions` to the `ignorePresets` array.\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"bellsoft/hardened-liberica-runtime-container\",\n        \"bellsoft/liberica-runtime-container\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsk3skubernetesversioning","title":"workarounds:k3sKubernetesVersioning","text":"

Use custom regex versioning for k3s-io/k3s

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"github-releases\"\n      ],\n      \"matchPackageNames\": [\n        \"k3s-io/k3s\"\n      ],\n      \"versioning\": \"regex:^v(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)(?:-(?<prerelease>[a-z]+\\\\d+))?(?<compatibility>\\\\+k3s)(?<build>\\\\d+)$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundslibericajdkdockerversioning","title":"workarounds:libericaJdkDockerVersioning","text":"

Use custom regex versioning for bellsoft/liberica-runtime-container

{\n  \"packageRules\": [\n    {\n      \"description\": \"Liberica JDK Lite version optimized for the Cloud\",\n      \"matchCurrentValue\": \"/^jdk-[^a][^l]{2}/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"bellsoft/hardened-liberica-runtime-container\",\n        \"bellsoft/liberica-runtime-container\"\n      ],\n      \"versioning\": \"regex:^jdk-(?<major>\\\\d+)?(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?([\\\\._+](?<build>(\\\\d\\\\.?)+))?(-(?<compatibility>.*))?$\"\n    },\n    {\n      \"description\": \"Liberica JDK that can be used to create a custom runtime with a help of jlink tool\",\n      \"matchCurrentValue\": \"/^jdk-all/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"bellsoft/hardened-liberica-runtime-container\",\n        \"bellsoft/liberica-runtime-container\"\n      ],\n      \"versioning\": \"regex:^jdk-all-(?<major>\\\\d+)?(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?([\\\\._+](?<build>(\\\\d\\\\.?)+))?(-(?<compatibility>.*))?$\"\n    },\n    {\n      \"description\": \"Liberica JRE (only the runtime without the rest of JDK tools) for running Java applications\",\n      \"matchCurrentValue\": \"/^jre-/\",\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"bellsoft/hardened-liberica-runtime-container\",\n        \"bellsoft/liberica-runtime-container\"\n      ],\n      \"versioning\": \"regex:^jre-(?<major>\\\\d+)?(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?([\\\\._+](?<build>(\\\\d\\\\.?)+))?(-(?<compatibility>.*))?$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsmavencommonsancientversion","title":"workarounds:mavenCommonsAncientVersion","text":"

Fix some problems with very old Maven commons versions.

{\n  \"packageRules\": [\n    {\n      \"allowedVersions\": \"!/^200\\\\d{5}(\\\\.\\\\d+)?/\",\n      \"matchDatasources\": [\n        \"maven\",\n        \"sbt-package\"\n      ],\n      \"matchPackageNames\": [\n        \"commons-**\"\n      ]\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsnodedockerversioning","title":"workarounds:nodeDockerVersioning","text":"

Use node versioning for node docker images.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"/(?:^|/)node$/\",\n        \"!calico/node\",\n        \"!docker.io/calico/node\",\n        \"!ghcr.io/devcontainers/features/node\",\n        \"!kindest/node\",\n        \"!docker.io/kindest/node\"\n      ],\n      \"versionCompatibility\": \"^(?<version>[^-]+)(?<compatibility>-.*)?$\",\n      \"versioning\": \"node\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsrke2kubernetesversioning","title":"workarounds:rke2KubernetesVersioning","text":"

Use custom regex versioning for rancher/rke2

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"github-releases\"\n      ],\n      \"matchPackageNames\": [\n        \"rancher/rke2\"\n      ],\n      \"versioning\": \"regex:^v(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)(?:-(?<prerelease>[a-z]+\\\\d+))?(?<compatibility>\\\\+rke2r)(?<build>\\\\d+)$\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundssupportredhatimageversion","title":"workarounds:supportRedHatImageVersion","text":"

Use specific versioning for Red Hat-maintained container images.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchPackageNames\": [\n        \"registry.access.redhat.com/rhel\",\n        \"registry.access.redhat.com/rhel-atomic\",\n        \"registry.access.redhat.com/rhel-init\",\n        \"registry.access.redhat.com/rhel-minimal\",\n        \"registry.access.redhat.com/rhceph/**\",\n        \"registry.access.redhat.com/rhgs3/**\",\n        \"registry.access.redhat.com/rhel7**\",\n        \"registry.access.redhat.com/rhel8/**\",\n        \"registry.access.redhat.com/rhel9/**\",\n        \"registry.access.redhat.com/rhscl/**\",\n        \"registry.access.redhat.com/ubi*{,/}**\",\n        \"redhat/**\"\n      ],\n      \"versioning\": \"redhat\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundstypesnodeversioning","title":"workarounds:typesNodeVersioning","text":"

Use node versioning for @types/node.

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\n        \"npm\"\n      ],\n      \"matchPackageNames\": [\n        \"@types/node\"\n      ],\n      \"versioning\": \"node\"\n    }\n  ]\n}\n
"},{"location":"presets-workarounds/#workaroundsubuntudockerversioning","title":"workarounds:ubuntuDockerVersioning","text":"

Use ubuntu versioning for ubuntu docker images.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\n        \"docker\"\n      ],\n      \"matchDepNames\": [\n        \"ubuntu\"\n      ],\n      \"versioning\": \"ubuntu\"\n    }\n  ]\n}\n
"},{"location":"python/","title":"Python package manager support","text":"

Renovate supports several Python package managers, including pip, pipenv, poetry, etc. See all supported managers.

"},{"location":"python/#versioning-support","title":"Versioning support","text":"

We've written a JavaScript version of the PEP440 specification so we can use it in Renovate. You can find this project in our renovatebot/pep440 repository.

Our PEP440 implementation supports pinned versions and ranges. Legacy versions with the === prefix are ignored.

"},{"location":"python/#how-it-works","title":"How it works","text":"
  1. Renovate searches through each repository for package files
  2. Existing dependencies are extracted from the package files
  3. Renovate searches for the latest version on PyPI to decide if there are upgrades
  4. If the source package includes a GitHub URL as its source, and has a \"changelog\" file or uses GitHub releases, a Release Note will be embedded in the generated PR
"},{"location":"python/#package-name-matching","title":"Package name matching","text":"

Your matchPackageName or matchPackagePattern rules will be matching against normalized names. So if you have specified package some.package or ANOTHER_DEP in your package files (requirements.txt, pyproject.toml), they will be treated as some-package and another-dep respectively. Not only they will be case insensitive but will replace any amount ._- to a single -. Consult Python packaging documentation for the specification.

"},{"location":"python/#alternate-registries","title":"Alternate registries","text":"

By default Renovate checks for upgrades on the pypi.org registry.

If you want, you can set alternative index URLs. There are three ways to do this:

"},{"location":"python/#index-url-in-requirementstxt","title":"index-url in requirements.txt","text":"Setting index URL in first line of requirements.txt
--index-url http://example.com/private-pypi/\nsome-package==0.3.1\nsome-other-package==1.0.0\n
"},{"location":"python/#sources-in-pipfile","title":"Sources in Pipfile","text":"

Renovate finds and uses any custom sources in your Pipfile.

"},{"location":"python/#sources-in-pyprojecttoml","title":"Sources in pyproject.toml","text":"

Renovate detects any custom-configured sources in pyproject.toml and uses them.

"},{"location":"python/#specify-url-in-configuration","title":"Specify URL in configuration","text":"

Create a packageRules entry with matchDatasources=pypi and a registryUrls array. Fill the array with alternate index URL(s).

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"pypi\"],\n      \"registryUrls\": [\"http://example.com/private-pypi/\"]\n    }\n  ]\n}\n

Tip

If a requirements.txt file has an index-url then Renovate follows that link, instead of following any link set in the registryUrls array. To override the URL found in requirements.txt, you must create a custom packageRules setting. This is because packageRules are applied after package file extraction.

"},{"location":"python/#disabling-python-support","title":"Disabling Python support","text":"Disabling all managers in the Python category
{\n  \"packageRules\": [\n    {\n      \"matchCategories\": [\"python\"],\n      \"enabled\": false\n    }\n  ]\n}\n

Alternatively, you can use enabledManagers to tell Renovate what package managers it can use.

Only use Renovate's npm package manager
{\n  \"enabledManagers\": [\"npm\"]\n}\n
"},{"location":"reading-list/","title":"Reading list","text":"

Renovate's documentation has a lot of pages. To ease you into using Renovate we created reading lists. The reading lists contain the essential information for each type of user.

How much you should read depends on how much you want to customize Renovate's behavior.

"},{"location":"reading-list/#how-to-use-this-page","title":"How to use this page","text":"

We created reading lists for these types of users:

Start with the \"Beginners\" reading list. If you're self-hosting or need to update private packages, complete the relevant reading lists for those.

"},{"location":"reading-list/#i-dont-know-where-to-start","title":"I don't know where to start","text":"

If you're new to Renovate, you should:

"},{"location":"reading-list/#beginners","title":"Beginners","text":"

Start by reading:

"},{"location":"reading-list/#intermediate","title":"Intermediate","text":"

First, complete the \"Beginners\" reading list. Read this list after experiencing Renovate's default behavior, once you really want/need to make changes to Renovate's behavior.

Skim the repository configuration options to learn about the kind of customizations you can make to Renovate. Feel free to read up on anything that looks interesting to you.

"},{"location":"reading-list/#advanced","title":"Advanced","text":"

First, complete the \"Beginners\" and the \"Intermediate\" reading list. Then read:

"},{"location":"reading-list/#self-hosting-renovate","title":"Self-hosting Renovate","text":"

If you're going to self-host Renovate then read:

"},{"location":"reading-list/#private-packages","title":"Private packages","text":"

If you want Renovate to update private packages then read:

"},{"location":"ruby/","title":"Automated dependency updates for Ruby Bundler dependencies","text":"

Renovate supports upgrading dependencies in Bundler's Gemfiles and associated Gemfile.lock files.

"},{"location":"ruby/#how-it-works","title":"How it works","text":"
  1. Renovate searches in each repository for any Gemfiles
  2. Existing dependencies are extracted from the Gemfiles
  3. Renovate resolves the dependency on Rubygems.org (or elsewhere if configured), and checks for newer versions
  4. A PR is created which updates the Gemfile and Gemfile.lock in a single commit
"},{"location":"ruby/#warnings","title":"Warnings","text":"

When using \"rangeStrategy\": \"update-lockfile\", all gems listed in the Gemfile will be updated, even if they do not have a version specified.

When using other rangeStrategy options, Renovate doesn't update dependencies without a version constraint. Example: gem 'some-gem', '~> 1.2.3' will update some-gem if a new version matching the constraint is available, but gem 'some-gem' won't. If you always want to have the latest available version, consider specifying gem 'some-gem', '> 0'.

"},{"location":"ruby/#enabling","title":"Enabling","text":"

You can install the Renovate App on GitHub. Or you can check out Renovate OSS to self-host Renovate.

"},{"location":"rust/","title":"Automated Dependency Updates for Rust crates","text":"

Renovate supports upgrading dependencies in Cargo.toml files and associated Cargo.lock checksums.

"},{"location":"rust/#how-it-works","title":"How it works","text":"
  1. Renovate searches in each repository for any Cargo.toml files
  2. Renovate extracts existing dependencies from [dependencies], [dev-dependencies], [build-dependencies] and [workspace.dependencies]
  3. Renovate looks up Cargo configuration to find index URLs for private registries
  4. Renovate resolves the dependency's version using the crates.io API or by cloning the index URL
  5. If Renovate finds an update, Renovate will use cargo update to update both Cargo.toml and Cargo.lock
"},{"location":"rust/#enabling-rust-modules-updating","title":"Enabling Rust Modules Updating","text":"

Renovate updates Rust crates by default.

"},{"location":"rust/#cargo-configuration-and-private-registry-discovery","title":"Cargo configuration and private registry discovery","text":"

Renovate can find private registry URLs in these Cargo configuration files:

If both files exist, Renovate reads .cargo/config, like cargo.

Renovate can also find private registry URLs via a CARGO_REGISTRIES_<name>_INDEX environment variable. Read the Rust environment variables docs to learn more.

"},{"location":"rust/#private-crate-registries-and-private-git-dependencies","title":"Private crate registries and private Git dependencies","text":"

You as user can set authentication for private crates by adding a hostRules configuration to your renovate.json file.

All token hostRules with a hostType (e.g. github, gitlab, bitbucket, etc.) and host rules without a hostType will be automatically setup for authentication. You can also configure a hostRules that's only for Cargo authentication (e.g. hostType: 'crate').

Example of authentication for a private GitHub and Cargo registry:
module.exports = {\n  hostRules: [\n    {\n      matchHost: 'github.enterprise.com',\n      token: process.env.GITHUB_TOKEN,\n      hostType: 'github',\n    },\n    {\n      matchHost: 'someGitHost.enterprise.com',\n      token: process.env.CARGO_GIT_TOKEN,\n      hostType: 'crate',\n    },\n  ],\n};\n
"},{"location":"security-and-permissions/","title":"Security and Permissions","text":"

This page talks about our security stance, and explains what permissions are needed for the different ways you can run Renovate.

"},{"location":"security-and-permissions/#security-stance","title":"Security Stance","text":"

Renovate is open source software, and comes with no guarantees or warranties of any kind. That said, we will try to fix security problems in a reasonable timeframe if possible.

"},{"location":"security-and-permissions/#certifications","title":"Certifications","text":"

Renovate the open source project is not certified.

Mend is the company which maintains Renovate and provides the Mend Renovate App. Mend is ISO 27001 and SOC2 certified.

"},{"location":"security-and-permissions/#security-disclosure","title":"Security / Disclosure","text":"

If you find any bug with Renovate that may be a security problem, please report it through the GitHub Security Advisories process. This way we can evaluate the bug and hopefully fix it before it gets abused. Please give us enough time to investigate the bug before you report it anywhere else.

If you would like to discuss a potential finding before raising the Advisory, then e-mail us at: renovate-disclosure@mend.io.

Please do not create GitHub issues for security-related doubts or problems.

"},{"location":"security-and-permissions/#permissions","title":"Permissions","text":"

We apply the Principle of Least Privilege (PoLP) but do need substantial privileges for our apps to work.

"},{"location":"security-and-permissions/#global-permissions","title":"Global Permissions","text":"

These permissions are always needed to run the respective app.

Permission The Mend Renovate App Forking Renovate Why Dependabot alerts read read Create vulnerability fix PRs Administration read read Read branch protections and to be able to assign teams to PRs Metadata read read Mandatory for all apps Checks read and write not applicable Read and write status checks Code read and write read Read for repository content and write for creating branches Commit statuses read and write read and write Read and write commit statuses for Renovate PRs Issues read and write read and write Create Dependency Dashboard or Config Warning issues Pull Requests read and write read and write Create update PRs Workflows read and write not applicable Explicit permission needed to update workflows"},{"location":"security-and-permissions/#user-permissions","title":"User permissions","text":"

Renovate can also request users's permission to the following resources. These permissions will be requested and authorized on an individual-user basis.

Permission The Mend Renovate App Forking Renovate Why email read not applicable Per-user consent requested if logging into App dashboard"},{"location":"security-and-permissions/#privacy","title":"Privacy","text":""},{"location":"security-and-permissions/#self-hosted-renovate-oss-cli-mend-renovate-on-premises","title":"Self-hosted (Renovate OSS CLI, Mend Renovate On-Premises)","text":"

Renovate is designed to operate autonomously and directly with package and source repositories, so does not \"phone home\", send telemetry, or need to request information from Mend or any project infrastructure. An exception to this is when Merge Confidence badges are requested, because those are hosted on Mend servers. Such badges are public, do not require authentication, and Renovate does not identify the source user or repository when requesting them. Self-hosted Renovate does not send or submit any package data to Mend for the purpose of calculating Merge Confidence figures.

According to a strict definition, Renovate may \"send data\" to third-party registries and source code hosts directly to look up new releases. For example, if you have an npm package and do not configure a private registry then Renovate will query URLs on https://registry.npmjs.org including names of packages used in your repositories. You could avoid this by configuring private registries but such registries need to query public registries anyway. We don't know of any public registries which reverse lookup IP addresses to associate companies with packages.

"},{"location":"security-and-permissions/#security-awareness-for-self-hosted-renovate-instances","title":"Security awareness for self-hosted Renovate instances","text":""},{"location":"security-and-permissions/#introduction","title":"Introduction","text":"

Before you start self-hosting Renovate you must understand the security implications associated with monitoring and updating repositories. The process that Renovate uses to update dependencies runs under the same user context as the Renovate process itself. This also means the process has the same level of access to information and resources as the user context!

"},{"location":"security-and-permissions/#trusting-repository-developers","title":"Trusting Repository Developers","text":"

All self-hosted Renovate instances must operate under a trust relationship with the developers of the monitored repositories. This has the following implications:

Keep reading to learn more.

"},{"location":"security-and-permissions/#access-to-information","title":"Access to information","text":"

Since the update process runs with the same user privileges as the Renovate process, it inherently has access to the same information and resources. This includes sensitive data that may be stored within the environment where Renovate is hosted.

"},{"location":"security-and-permissions/#execution-of-code-insider-attack","title":"Execution of code (insider attack)","text":"

In certain scenarios, code from the monitored repository is executed as part of the update process. This is particularly true during, for example:

These scripts can contain arbitrary code. This may pose a significant security risk if the repository's integrity is compromised, or if the repository maintainers have malicious intentions.

Because such insider attack is an inherent and unavoidable risk, the Renovate project will not issue CVEs (or GHSAs) for such attacks or weaknesses other than in exceptional circumstances.

If you require postUpgradeTasks to run inside a shell, you can enable this using allowShellExecutorForPostUpgradeCommands=true. Note that this means that these commands can call out to other commands or access shell variables, if the allowlist via allowedCommands does not restrict it. As it is difficult to craft a regular expression that may deny usage of special characters to shells, it is likely that this will not be possible to avoid at this time.

"},{"location":"security-and-permissions/#execution-of-code-outsider-attack","title":"Execution of code (outsider attack)","text":"

Separately, there are also opportunities for malicious external code to execute, as part of Renovate's update process.

Warning

Below are some of the options, but note that this is not exhaustive.

For instance:

Depending on the self-hosted configuration, it may also be possible for package manager scripts to execute post-update (if using allowScripts=true alongside ignoreScripts=false):

"},{"location":"security-and-permissions/#centralized-logging-and-sensitive-information-management","title":"Centralized logging and sensitive information management","text":"

Centralized logging is key to monitor and troubleshoot self-hosted Renovate environments. But logging may inadvertently capture and expose sensitive information. Operations that involve customEnvVariables, among others, could expose sensitive data, when logging is used.

"},{"location":"security-and-permissions/#recommendations","title":"Recommendations","text":"

The Renovate maintainers recommend you follow these guidelines.

"},{"location":"security-and-permissions/#vet-and-monitor-repositories","title":"Vet and monitor repositories","text":"

Before integrating a repository with your self-hosted Renovate instance, thoroughly vet the repository for security and trustworthiness. This means that you should review the:

"},{"location":"security-and-permissions/#limit-permissions","title":"Limit permissions","text":"

Configure the environment running Renovate with the principle of least privilege. Ensure that the Renovate process has only the permissions needed to perform its tasks and no more. This reduces the impact of any malicious code execution.

"},{"location":"security-and-permissions/#regularly-review-post-upgrade-tasks","title":"Regularly review post-upgrade tasks","text":"

Regularly review the actions taken by postUpgradeTasks to make sure they do not execute unnecessary or risky operations. Consider implementing a review process for changes to these tasks within repositories.

Where possible, restrict the commands executed to an allowlist you control, and try to limit the opportunity for those commands to execute additional commands.

For instance, allowlisting the command make lint-fix could run other tasks, including running npm install --foreground-scripts, which would bypass the global allowScripts configuration

"},{"location":"security-and-permissions/#use-security-tools","title":"Use security tools","text":"

Employ security tools and practices, like code scanning and vulnerability assessments, on the Renovate configuration and the repositories Renovate manages. This helps identify potentially malicious code before it is executed.

"},{"location":"security-and-permissions/#securing-environment-variables","title":"Securing environment variables","text":"

When configuring customEnvVariables: always use Renovate's secrets management syntax ({{ secrets.VAR_NAME }}) to reference sensitive variables securely. This makes sure that sensitive data is not exposed as plain text.

"},{"location":"security-and-permissions/#logging-infrastructure-security","title":"Logging infrastructure security","text":"

Ensure that the logging infrastructure is configured to handle logs as sensitive data. This includes measures like:

"},{"location":"security-and-permissions/#log-review-and-redaction-processes","title":"Log review and redaction processes","text":"

Implement rigorous log review mechanisms to regularly scan for and redact sensitive information that might be logged inadvertently. Automated tools can assist in identifying patterns indicative of sensitive data, such as credentials or personal information, enabling timely redaction or alerting.

"},{"location":"security-and-permissions/#stay-informed","title":"Stay informed","text":"

Keep abreast of updates and security advisories related to Renovate itself. Apply updates promptly to ensure that your self-hosted instances get the latest security enhancements and bug fixes.

"},{"location":"security-and-permissions/#conclusion","title":"Conclusion","text":"

The flexibility and power of self-hosting Renovate also means you must take steps to manage your security. By understanding the risks associated with repository management and taking steps to mitigate those risks, organizations can maintain a secure and efficient development workflow.

"},{"location":"security-and-permissions/#hostedsaas-the-mend-renovate-app","title":"Hosted/SaaS (the Mend Renovate App)","text":"

Users of the Mend Renovate App fall under Mend's Terms of Service and Privacy Policy.

In this case the app needs to temporarily clone source code for Renovate to run, but the app does not keep the source code anywhere after jobs are completed.

Mend anonymizes and aggregates package use and update success rates within the hosted app to derive Merge Confidence scores.

The app database keeps a list of dependencies and versions per repo, plus basic into about any Renovate PRs it's created.

"},{"location":"self-hosted-configuration/","title":"Self-Hosted configuration options","text":"

Only use these configuration options when you self-host Renovate.

Do not put the self-hosted config options listed on this page in your \"repository config\" file (renovate.json for example), because Renovate will ignore those config options, and may also create a config error issue.

The config options below must be configured in the admin config, so in either an environment variable, CLI option, or a special file like config.js.

Note

Renovate supports JSONC for .json files and any config files without file extension (e.g. .renovaterc).

For information about how to configure Renovate with a config.js see the Using config.js documentation.

Tip

This documentation corresponds with the JSON schema in docs.renovatebot.com/renovate-global-schema.json, and any inherited config options are also present in docs.renovatebot.com/renovate-inherited-schema.json.

Please also see Self-Hosted Experimental Options.

Note

Config options with type=string are always non-mergeable, so mergeable=false.

"},{"location":"self-hosted-configuration/#allowcustomcrategitregistries","title":"allowCustomCrateGitRegistries","text":"

Set this to true to allow cloning custom Cargo git registries. This only restricts non-sparse registries.

Name Value type boolean default false cli --allow-custom-crate-git-registries env RENOVATE_ALLOW_CUSTOM_CRATE_GIT_REGISTRIES previouslyKnownAs 
[\"allowCustomCrateRegistries\"]\n
"},{"location":"self-hosted-configuration/#allowplugins","title":"allowPlugins","text":"

Set this to true if repositories are allowed to run install plugins.

Name Value type boolean default false cli --allow-plugins env RENOVATE_ALLOW_PLUGINS"},{"location":"self-hosted-configuration/#allowscripts","title":"allowScripts","text":"

Set this to true if repositories are allowed to run install scripts.

Name Value type boolean default false cli --allow-scripts env RENOVATE_ALLOW_SCRIPTS"},{"location":"self-hosted-configuration/#allowshellexecutorforpostupgradecommands","title":"allowShellExecutorForPostUpgradeCommands","text":"

Whether to run commands for postUpgradeTasks inside a shell. This has security implications, as it means that they can call out to other commands or access shell variables. It is difficult to craft an allowedCommands regex to restrict this.

Name Value type boolean default false cli --allow-shell-executor-for-post-upgrade-commands env RENOVATE_ALLOW_SHELL_EXECUTOR_FOR_POST_UPGRADE_COMMANDS

Enabling this allows postUpgradeTasks' commands to execute as if they're in a shell.

This takes effect if you are using shell semantics, such as:

allowShellExecutorForPostUpgradeCommands=true will allow this to run as expected
{\n  \"postUpgradeTasks\": {\n    \"commands\": [\"echo '...' > go.mod\", \"go mod tidy || true\"],\n    \"fileFilters\": [\"**/*.go\"],\n    \"executionMode\": \"branch\"\n  }\n}\n

This will not affect calling a script like:

allowShellExecutorForPostUpgradeCommands=true will have not effect
{\n  \"postUpgradeTasks\": {\n    \"commands\": [\"bash .scripts/post-yarn-update.sh\"],\n    \"fileFilters\": [\"yarn.lock\", \"**/*.js\"],\n    \"executionMode\": \"update\"\n  }\n}\n

Warning

This has the risk of arbitrary environment variable access or additional command execution. It is very likely this will be susceptible to these risks, even if you allowlist (via allowedCommands), as there may be special characters included in the given commands that can be leveraged

"},{"location":"self-hosted-configuration/#allowedcommands","title":"allowedCommands","text":"

A list of regular expressions that decide which commands are allowed in post-upgrade tasks.

Name Value type array subType string cli --allowed-commands env RENOVATE_ALLOWED_COMMANDS previouslyKnownAs 
[\"allowedPostUpgradeCommands\"]\n
default []

A list of regular expressions that decide which commands in postUpgradeTasks are allowed to run.

If you are using a template command, the regular expression should match the final resolved value. If this list is empty then no tasks will be executed.

For example:

{\n  \"allowedCommands\": [\"^tslint --fix$\", \"^tslint --[a-z]+$\"]\n}\n

This configuration option was formerly known as allowedPostUpgradeCommands.

"},{"location":"self-hosted-configuration/#allowedenv","title":"allowedEnv","text":"

List of allowed patterns for environment variable names in repository env config.

Name Value type array subType string mergeable true cli --allowed-env env RENOVATE_ALLOWED_ENV default []

Administrators can allow users to configure custom environment variables within repo config. Only environment variables matching the list will be accepted in the env configuration.

Examples:

renovate.json
{\n  \"env\": {\n    \"SOME_ENV_VARIABLE\": \"some_value\",\n    \"EXTRA_ENV_NAME\": \"value\"\n  }\n}\n

The above would require allowedEnv to be configured similar to the following:

config.js
module.exports = {\n  allowedEnv: ['SOME_ENV_*', 'EXTRA_ENV_NAME'],\n};\n

allowedEnv values can be exact match header names, glob patterns, or regex patterns. For more details on the syntax and supported patterns, see Renovate's String Pattern Matching documentation.

Note

allowedEnv constrains what a repository, and the presets it extends, may set - it does not constrain you, the self-hosted administrator. The env you set in your own config is always applied, as is any env set by a preset you chose to extends, whether in your global config or in a repositories[] entry. A repository can override one of your environment variables only where its name is in the allowedEnv allowlist. A repository could override an allowlisted environment variable's value to the empty string, which may or may not disable it, depending on how the tool(s) that consume that environment variable respond. Where the name is not permitted by allowedEnv, the self-hosted administrator's value is always used.

"},{"location":"self-hosted-configuration/#allowedheaders","title":"allowedHeaders","text":"

List of allowed patterns for header names in repository hostRules config.

Name Value type array default 
[\"X-*\"]\n
subType string cli --allowed-headers env RENOVATE_ALLOWED_HEADERS

allowedHeaders can be useful when a registry uses a authentication system that's not covered by Renovate's default credential handling in hostRules. By default, all headers starting with \"X-\" are allowed. If needed, you can allow additional headers with the allowedHeaders option. Any set allowedHeaders overrides the default \"X-\" allowed headers, so you should include them in your config if you wish for them to remain allowed. The allowedHeaders config option takes an array of minimatch-compatible globs or re2-compatible regex strings. For more details on this syntax see Renovate's string pattern matching documentation.

allowedHeaders constrains what a repository, and the presets it extends, may set - it does not constrain you, the self-hosted administrator.

The headers you set in your own hostRules - whether in your global config or in a repositories[] entry - are always applied, regardless of allowedHeaders, as is any headers set by a preset a repositories[] entry chose to extends.

Note

This does not (yet) extend to a preset your global config itself chooses to extends when no repositories[] entry is involved: those headers are still constrained by allowedHeaders, unlike the equivalent case for env.

Where more than one of your own rules matches a request, the headers of the most specific rule are used, and replace those of the broader rules it matched alongside. So to keep a header away from a host that a broader rule of yours also matches, give that host a rule of its own which sets headers. Whichever of your headers that leaves for a request are then applied over any a repository set, and always with the value you set: a repository's hostRules - or those of a preset it extends - can neither stop one of them being sent, nor replace its value, and can only set a header name of its own where it is permitted by allowedHeaders.

Examples:

Example header Kind of pattern Explanation /X/ Regex Any header with x anywhere in the name !/X/ Regex Any header without X anywhere in the name X-* Global pattern Any header starting with X- X Exact match glob Only the header matching exactly X 
{\n  \"allowedHeaders\": [\"X-Auth-Token\"],\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://domain.com/all-versions\",\n      \"headers\": {\n        \"X-Auth-Token\": \"secret\"\n      }\n    }\n  ]\n}\n

Or with custom allowedHeaders:

config.js
module.exports = {\n  allowedHeaders: ['custom-header'],\n};\n
"},{"location":"self-hosted-configuration/#allowedunsafeexecutions","title":"allowedUnsafeExecutions","text":"

List of possibly unsafe executions which are permitted to run. This enables global control over any implicit commands which are run as part of a renovate run. This is similar to allowedCommands but is specifically used to control executions which run automatically, and are not explicitly added in postUpgradeTasks

Name Value type array subType string allowedValues 
[\"bazelModDeps\", \"goGenerate\", \"gradleWrapper\", \"mise\", \"pixi\"]\n
cli --allowed-unsafe-executions env RENOVATE_ALLOWED_UNSAFE_EXECUTIONS default []

This should be configured to a list of commands which are allowed to be run automatically as part of a dependency upgrade.

This is a separate class of commands that could be executed compared to allowedCommands, or package managers that are controlled with allowScripts=true and ignoreScripts=false, where seemingly \"safe\" commands can result in code execution. As there is a security risk of running these commands automatically when a dependency upgrades, self hosted implementations need to explicitly declare which commands are permitted for their installation. For more details of where this may be found, see \"Trusting Repository Developers\".

Allowed options:

Option Description bazelModDeps Allows the bazel mod deps when perfoming bazelisk or bazel-module updates. goGenerate Allows the goGenerate postUpdateOption to run after a go mod update. gradleWrapper Allows using ./gradlew or gradle.bat when performing updates with Gradle. mise Allows running any mise commands, for instance mise lock when updating mise.lock files. pixi Allows running pixi lock when updating pixi.lock files (pixi and pep621 managers)."},{"location":"self-hosted-configuration/#autodiscover","title":"autodiscover","text":"

Autodiscover all repositories.

Name Value type boolean default false cli --autodiscover env RENOVATE_AUTODISCOVER

When you enable autodiscover, by default, Renovate runs on every repository that the Renovate account can access. You can limit which repositories Renovate can access by using the autodiscoverFilter config option.

"},{"location":"self-hosted-configuration/#autodiscoverfilter","title":"autodiscoverFilter","text":"

Filter the list of autodiscovered repositories.

Name Value type array subType string cli --autodiscover-filter env RENOVATE_AUTODISCOVER_FILTER default []

You can use this option to filter the list of repositories that the Renovate account can access through autodiscover. The pattern matches against the organization/repo path.

This option supports an array of minimatch-compatible globs or RE2-compatible regex strings. For more details on this syntax see Renovate's string pattern matching documentation.

If you set multiple filters, then the matches of each filter are added to the overall result.

If you use an environment variable or the CLI to set the value for autodiscoverFilter, then commas , within filters are not supported. Commas will be used as delimiter for a new filter.

# DO NOT use commas inside the filter if your are using env or cli variables to configure it.\nRENOVATE_AUTODISCOVER_FILTER=\"/MyOrg/{my-repo,foo-repo}\"\n\n\n# in this example you can use regex instead\nRENOVATE_AUTODISCOVER_FILTER=\"/MyOrg\\/(my|foo)-repo/\"\n

Minimatch:

The configuration:

{\n  \"autodiscoverFilter\": [\"my-org/*\", \"!my-org/old-*\"]\n}\n

Glob patterns are case-insensitive.

Regex:

All text inside the start and end / will be treated as a regular expression. If using negations, all repositories except those who match the regex are added to the result:

{\n  \"autodiscoverFilter\": [\"/project/.*/\", \"!/project/old-/\"]\n}\n
"},{"location":"self-hosted-configuration/#autodiscovernamespaces","title":"autodiscoverNamespaces","text":"

Filter the list of autodiscovered repositories by namespaces.

Name Value type array subType string supportedPlatforms forgejo, gitea, gitlab cli --autodiscover-namespaces env RENOVATE_AUTODISCOVER_NAMESPACES default []

You can use this option to autodiscover projects in specific namespaces (a.k.a. groups/organizations/workspaces). In contrast to autodiscoverFilter the filtering is done by the platform and therefore more efficient.

For example:

{\n  \"platform\": \"gitlab\",\n  \"autodiscoverNamespaces\": [\"a-group\", \"another-group/some-subgroup\"]\n}\n

Note

On Gitea/Forgejo, you can't use autodiscoverTopics together with autodiscoverNamespaces because both platforms do not support this. Topics are preferred and autodiscoverNamespaces will be ignored when you configure autodiscoverTopics on Gitea/Forgejo.

"},{"location":"self-hosted-configuration/#autodiscoverprojects","title":"autodiscoverProjects","text":"

Filter the list of autodiscovered repositories by project names.

Name Value type array subType string supportedPlatforms bitbucket cli --autodiscover-projects env RENOVATE_AUTODISCOVER_PROJECTS default []

You can use this option to filter the list of autodiscovered repositories by project names. This feature is useful for users who want Renovate to only work on repositories within specific projects or exclude certain repositories from being processed.

Example for Bitbucket
{\n  \"platform\": \"bitbucket\",\n  \"autodiscoverProjects\": [\"a-group\", \"!another-group/some-subgroup\"]\n}\n

The autodiscoverProjects config option takes an array of minimatch-compatible globs or RE2-compatible regex strings. For more details on this syntax see Renovate's string pattern matching documentation.

"},{"location":"self-hosted-configuration/#autodiscoverrepoorder","title":"autodiscoverRepoOrder","text":"

The order method for autodiscover server side repository search.

Name Value type string allowedValues 
[\"asc\", \"desc\"]\n
supportedPlatforms forgejo, gitea, gitlab cli --autodiscover-repo-order env RENOVATE_AUTODISCOVER_REPO_ORDER previouslyKnownAs 
[\"RENOVATE_X_AUTODISCOVER_REPO_ORDER\"]\n

The order method for autodiscover server side repository search.

If multiple autodiscoverTopics are used resulting order will be per topic not global.

"},{"location":"self-hosted-configuration/#autodiscoverreposort","title":"autodiscoverRepoSort","text":"

The sort method for autodiscover server side repository search.

Name Value type string allowedValues 
[\"alpha\", \"created\", \"created_at\", \"updated\", \"updated_at\", \"size\", \"id\"]\n
supportedPlatforms forgejo, gitea, gitlab cli --autodiscover-repo-sort env RENOVATE_AUTODISCOVER_REPO_SORT previouslyKnownAs 
[\"RENOVATE_X_AUTODISCOVER_REPO_SORT\"]\n

The sort method for autodiscover server side repository search.

Platform supported sort options:

Platform Supported sort options GitLab created_at, updated_at, id Forgejo, Gitea alpha, created, updated, size, id

If multiple autodiscoverTopics are used resulting order will be per topic not global.

"},{"location":"self-hosted-configuration/#autodiscovertopics","title":"autodiscoverTopics","text":"

Filter the list of autodiscovered repositories by topics.

Name Value type array subType string supportedPlatforms forgejo, gitea, github, gitlab cli --autodiscover-topics env RENOVATE_AUTODISCOVER_TOPICS default []

Some platforms allow you to add tags, or topics, to repositories and retrieve repository lists by specifying those topics. Set this variable to a list of strings, all of which will be topics for the autodiscovered repositories.

For example:

{\n  \"autodiscoverTopics\": [\"managed-by-renovate\"]\n}\n
"},{"location":"self-hosted-configuration/#basedir","title":"baseDir","text":"

The base directory for Renovate to store local files, including repository files and cache. If left empty, Renovate will create its own temporary directory to use.

Name Value type string cli --base-dir env RENOVATE_BASE_DIR default null

By default Renovate uses a temporary directory like /tmp/renovate to store its data. You can override this default with the baseDir option.

For example:

{\n  \"baseDir\": \"/my-own-different-temporary-folder\"\n}\n
"},{"location":"self-hosted-configuration/#bbusedevelopmentbranch","title":"bbUseDevelopmentBranch","text":"

Use the repository's development branch as the repository's default branch.

Name Value type boolean default false supportedPlatforms bitbucket inheritConfigSupport true cli --bb-use-development-branch env RENOVATE_BB_USE_DEVELOPMENT_BRANCH

By default, Renovate will use a repository's \"main branch\" (typically called main or master) as the \"default branch\".

Configuring this to true means that Renovate will detect and use the Bitbucket development branch as defined by the repository's branching model.

If the \"development branch\" is configured but the branch itself does not exist (e.g. it was deleted), Renovate will fall back to using the repository's \"main branch\". This fall back behavior matches that of the Bitbucket Cloud web interface.

"},{"location":"self-hosted-configuration/#binarysource","title":"binarySource","text":"

Controls how third-party tools like npm or Gradle are called: directly, via Docker sidecar containers, or via dynamic install.

Name Value type string allowedValues 
[\"global\", \"docker\", \"install\", \"hermit\"]\n
default \"install\" cli --binary-source env RENOVATE_BINARY_SOURCE

Renovate often needs to use third-party tools in its PRs, like npm to update package-lock.json or go to update go.sum.

Renovate supports three possible ways to access those tools:

If you are running Renovate in an environment where runtime download and install of tools is not possible then you should use the \"full\" image.

If you are building your own Renovate image, e.g. by installing Renovate using npm, then you will need to ensure that all necessary tools are installed globally before running Renovate so that binarySource=global will work.

Warning

The usage of binarySource=docker is deprecated, and will be removed in the future.

We also have a deprecated docker mode.

For this to work, docker needs to be installed and the Docker socket available to Renovate.

If you are using this mode, and cannot migrate to binarySource=install, please provide feedback in this Discussion.

"},{"location":"self-hosted-configuration/#cachedir","title":"cacheDir","text":"

The directory where Renovate stores its cache. If left empty, Renovate creates a subdirectory within the baseDir.

Name Value type string cli --cache-dir env RENOVATE_CACHE_DIR default null

By default Renovate stores cache data in a temporary directory like /tmp/renovate/cache. Use the cacheDir option to override this default.

The baseDir and cacheDir option may point to different directories. You can use one directory for the repo data, and another for the cache data.

For example:

{\n  \"baseDir\": \"/my-own-different-temporary-folder\",\n  \"cacheDir\": \"/my-own-different-cache-folder\"\n}\n
"},{"location":"self-hosted-configuration/#cachehardttlminutes","title":"cacheHardTtlMinutes","text":"

Maximum duration in minutes to keep datasource cache entries.

Name Value type integer default 10080 cli --cache-hard-ttl-minutes env RENOVATE_CACHE_HARD_TTL_MINUTES

This experimental feature configures the physical lifetime of cache entries. Renovate internally uses two types of Time-to-Live (TTL) for its cache:

This two-level cache expiry is used for:

  1. HTTP caching with ETag, Last-Modified, and If-Modified-Since headers
  2. getReleases and getDigest datasource methods, i.e. the package release data

If an upstream request fails, Renovate can still use stale data from the cache as long as its hard TTL has not expired.

The cacheHardTtlMinutes option lets you configure the hard TTL. Set this to a non-zero value, the recommended minimum is 60 (one hour).

If the soft TTL for a cache entry is longer than the hard TTL, Renovate uses the soft TTL value for both. The soft TTL is hard-coded but can be overridden with cacheTtlOverride.

Example:

The npm datasource has a default soft TTL of 15 minutes. When cacheHardTtlMinutes is set, for example to 60, Renovate will use the stale npm data in the following ways:

"},{"location":"self-hosted-configuration/#cacheprivatepackages","title":"cachePrivatePackages","text":"

Cache private packages in the datasource cache. This is useful for self-hosted setups

Name Value type boolean default false cli --cache-private-packages env RENOVATE_CACHE_PRIVATE_PACKAGES

In the self-hosted setup, use option to enable caching of private packages to improve performance.

"},{"location":"self-hosted-configuration/#cachettloverride","title":"cacheTtlOverride","text":"

An object that contains cache namespace TTL override values.

Name Value type object additionalProperties 
{\"type\": \"number\"}\n
cli --cache-ttl-override env RENOVATE_CACHE_TTL_OVERRIDE

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Warning

For advanced use only! Use at your own risk!

Use this key-value map to override the default package cache TTL values for a specific namespace. This object contains pairs of namespaces and their corresponding TTL values in minutes.

Internally, Renovate has the notion of soft TTL and hard TTL. In some contexts they are equal, but when they differ, this option overrides the soft TTL. See cacheHardTtlMinutes for more information.

You can use:

Priority order:

  1. Exact namespace matches take highest priority
  2. If no exact match, the longest (most specific) matching pattern wins

Example:

{\n  \"cacheTtlOverride\": {\n    \"datasource-rubygems\": 120,\n    \"datasource-*\": 60,\n    \"datasource-{crate,go}\": 90,\n    \"/^changelog-/\": 45,\n    \"*\": 30\n  }\n}\n

In this example:

Namespaces of special interest follow the pattern datasource-{datasource}. When releases for a datasource are fetched, they are stored in this namespace. Whether caching is enabled for a particular datasource depends on whether it's private or caching is forced with cachePrivatePackages.

Other valid cache namespaces are as follows:

"},{"location":"self-hosted-configuration/#checkedbranches","title":"checkedBranches","text":"

A list of branch names to mark for creation or rebasing as if it was selected in the Dependency Dashboard issue.

Name Value type array subType string cli --checked-branches env RENOVATE_CHECKED_BRANCHES default []

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

This array will allow you to set the names of the branches you want to rebase/create, as if you selected their checkboxes in the Dependency Dashboard issue.

Warning

When using checkedBranches, Renovate treats this as you, the self-hosted administrator, consenting to any updates the given branch introduces. This can lead to branches that have not yet passed their internalChecksFilter / minimumReleaseAge to be created. There is not currently a way to control this.

It has been designed with the intention of being run on one repository, in a one-off manner, e.g. to \"force\" the rebase of a known existing branch. It is highly unlikely that you should ever need to add this to your permanent global config.

Example: renovate --checked-branches=renovate/chalk-4.x renovate-reproductions/checked will rebase the renovate/chalk-4.x branch in the renovate-reproductions/checked repository.

"},{"location":"self-hosted-configuration/#configfilenames","title":"configFileNames","text":"

List of filenames where repository config will be stored.

Name Value type array subType string inheritConfigSupport true cli --config-file-names env RENOVATE_CONFIG_FILE_NAMES default []

A list of filenames where repository config can be stored.

This list doesn't replace the existing list of default config filenames used internally, instead these filenames are prepended to the list.

Example:

{\n  \"configFileNames\": [\"myrenovate.json\"]\n}\n

Note

If you want renovate to use a custom filename for the onboarding branch you also need to change the onboardingConfigFileName.

"},{"location":"self-hosted-configuration/#configvalidationerror","title":"configValidationError","text":"

If enabled, config validation errors will be reported as errors instead of warnings, and Renovate will exit with a non-zero exit code.

Name Value type boolean default false inheritConfigSupport true cli --config-validation-error env RENOVATE_CONFIG_VALIDATION_ERROR

If enabled, config validation errors will be reported as errors instead of warnings, and Renovate will exit with a non-zero exit code.

This applies to the repo configuration and any resolved extends presets - any validation issues in that resolved configuration will also abort the repository run. Leave this disabled if your repositories extend presets you do not control, as a problem introduced by a preset would then stop Renovate from running against your repository.

Note

Violations of sensitive configuration options, like those governed by allowedEnv and allowedHeaders, will always abort the repository, regardless of the configValidationError setting.

"},{"location":"self-hosted-configuration/#containerbasedir","title":"containerbaseDir","text":"

The directory where Renovate stores its containerbase cache. If left empty, Renovate creates a subdirectory within the cacheDir.

Name Value type string cli --containerbase-dir env RENOVATE_CONTAINERBASE_DIR default null

This directory is used to cache downloads when binarySource=docker or binarySource=install.

Use this option if you need such downloads to be stored outside of Renovate's regular cache directory (cacheDir).

"},{"location":"self-hosted-configuration/#customenvvariables","title":"customEnvVariables","text":"

Custom environment variables for child processes and sidecar Docker containers.

Name Value type object additionalProperties 
{\"type\": \"string\"}\n
cli --custom-env-variables env RENOVATE_CUSTOM_ENV_VARIABLES

This configuration will be applied after all other environment variables so you can use it to override defaults.

Warning

Do not configure any secret values directly into customEnvVariables because they may be logged to stdout. Instead, configure them into secrets first so that they will be redacted in logs.

If configuring secrets in to customEnvVariables, take this approach:

{\n  secrets: {\n    SECRET_TOKEN: process.env.SECRET_TOKEN,\n  },\n  customEnvVariables: {\n    SECRET_TOKEN: '{{ secrets.SECRET_TOKEN }}',\n  },\n}\n

The above configuration approach will mean the values are redacted in logs like in the following example:

         \"secrets\": {\"SECRET_TOKEN\": \"***********\"},\n         \"customEnvVariables\": {\"SECRET_TOKEN\": \"{{ secrets.SECRET_TOKEN }}\"},\n
"},{"location":"self-hosted-configuration/#deleteadditionalconfigfile","title":"deleteAdditionalConfigFile","text":"

If set to true, Renovate tries to delete the additional self-hosted config file after reading it.

Name Value type boolean default false cli --delete-additional-config-file env RENOVATE_DELETE_ADDITIONAL_CONFIG_FILE

If set to true Renovate tries to delete the additional self-hosted config file after reading it.

The process that runs Renovate must have the correct permissions to delete the additional config file.

Tip

You can tell Renovate where to find your config file with the RENOVATE_ADDITONAL_CONFIG_FILE environment variable.

"},{"location":"self-hosted-configuration/#deleteconfigfile","title":"deleteConfigFile","text":"

If set to true, Renovate tries to delete the self-hosted config file after reading it.

Name Value type boolean default false cli --delete-config-file env RENOVATE_DELETE_CONFIG_FILE previouslyKnownAs 
[\"RENOVATE_X_DELETE_CONFIG_FILE\"]\n

If set to true Renovate tries to delete the self-hosted config file after reading it.

The process that runs Renovate must have the correct permissions to delete the config file.

Tip

You can tell Renovate where to find your config file with the RENOVATE_CONFIG_FILE environment variable.

"},{"location":"self-hosted-configuration/#detectglobalmanagerconfig","title":"detectGlobalManagerConfig","text":"

If true, Renovate tries to detect global manager configuration from the file system.

Name Value type boolean default false cli --detect-global-manager-config env RENOVATE_DETECT_GLOBAL_MANAGER_CONFIG

The purpose of this config option is to allow you (as an administrator) to configure manager-specific files such as a global .npmrc file, instead of configuring it in Renovate config.

This config option is disabled by default because it may prove surprising or undesirable for some users who don't expect Renovate to go into their home directory and import registry or credential information.

Currently this config option is supported for the npm manager only - specifically the ~/.npmrc file. If found, it will be imported into config.npmrc with config.npmrcMerge set to true.

"},{"location":"self-hosted-configuration/#detecthostrulesfromenv","title":"detectHostRulesFromEnv","text":"

If true, Renovate tries to detect host rules from environment variables.

Name Value type boolean default false cli --detect-host-rules-from-env env RENOVATE_DETECT_HOST_RULES_FROM_ENV

The format of the environment variables must follow:

Hyphens (-) in datasource or host name must be replaced with double underscores (__). Periods (.) in host names must be replaced with a single underscore (_).

Note

You can't use these prefixes with the detectHostRulesFromEnv config option: npm_config_, npm_lifecycle_, npm_package_. In addition, platform host rules will only be picked up when matchHost is supplied.

"},{"location":"self-hosted-configuration/#npmjs-registry-token-example","title":"npmjs registry token example","text":"

NPM_REGISTRY_NPMJS_ORG_TOKEN=abc123:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"npm\",\n      \"matchHost\": \"registry.npmjs.org\",\n      \"token\": \"abc123\"\n    }\n  ]\n}\n
"},{"location":"self-hosted-configuration/#gitlab-tags-usernamepassword-example","title":"GitLab Tags username/password example","text":"

GITLAB__TAGS_CODE__HOST_COMPANY_COM_USERNAME=bot GITLAB__TAGS_CODE__HOST_COMPANY_COM_PASSWORD=botpass123:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"gitlab-tags\",\n      \"matchHost\": \"code-host.company.com\",\n      \"username\": \"bot\",\n      \"password\": \"botpass123\"\n    }\n  ]\n}\n
"},{"location":"self-hosted-configuration/#datasource-and-credentials-only","title":"Datasource and credentials only","text":"

You can skip the host part, and use only the datasource and credentials.

DOCKER_USERNAME=bot DOCKER_PASSWORD=botpass123:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"docker\",\n      \"username\": \"bot\",\n      \"password\": \"botpass123\"\n    }\n  ]\n}\n
"},{"location":"self-hosted-configuration/#platform-with-https-authentication-options","title":"Platform with https authentication options","text":"

GITHUB_SOME_GITHUB__ENTERPRISE_HOST_HTTPSCERTIFICATE=certificate GITHUB_SOME_GITHUB__ENTERPRISE_HOST_HTTPSPRIVATEKEY=private-key GITHUB_SOME_GITHUB__ENTERPRISE_HOST_HTTPSCERTIFICATEAUTHORITY=certificate-authority:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"github\",\n      \"matchHost\": \"some.github-enterprise.host\",\n      \"httpsPrivateKey\": \"private-key\",\n      \"httpsCertificate\": \"certificate\",\n      \"httpsCertificateAuthority\": \"certificate-authority\"\n    }\n  ]\n}\n
"},{"location":"self-hosted-configuration/#dockerchildprefix","title":"dockerChildPrefix","text":"

Change this value to add a prefix to the Renovate Docker sidecar container names and labels.

Name Value type string default \"renovate_\" cli --docker-child-prefix env RENOVATE_DOCKER_CHILD_PREFIX

This feature has been deprecated

The usage of binarySource=docker is deprecated, and will be removed in the future

Adds a custom prefix to the default Renovate sidecar Docker containers name and label.

For example, if you set dockerChildPrefix=myprefix_ then the final container created from the ghcr.io/renovatebot/base-image is:

Note

Dangling containers are only removed when Renovate runs again with the same prefix.

"},{"location":"self-hosted-configuration/#dockerclioptions","title":"dockerCliOptions","text":"

Pass CLI flags to docker run command when binarySource=docker.

Name Value type string cli --docker-cli-options env RENOVATE_DOCKER_CLI_OPTIONS default null

This feature has been deprecated

The usage of binarySource=docker is deprecated, and will be removed in the future

You can use dockerCliOptions to pass Docker CLI options to Renovate's sidecar Docker containers.

For example, {\"dockerCliOptions\": \"--memory=4g\"} will add a CLI flag to the docker run command that limits the amount of memory Renovate's sidecar Docker container can use to 4 gigabytes.

Read the Docker Docs, configure runtime resource constraints to learn more.

"},{"location":"self-hosted-configuration/#dockermaxpages","title":"dockerMaxPages","text":"

By default, Renovate fetches up to 20 pages of Docker tags from registries. But you can set your own limit with this config option.

Name Value type integer default 20 cli --docker-max-pages env RENOVATE_DOCKER_MAX_PAGES previouslyKnownAs 
[\"RENOVATE_X_DOCKER_MAX_PAGES\"]\n

If set to an positive integer, Renovate will use this value as the maximum page number. Setting a different limit is useful for registries that ignore the n parameter in Renovate's query string and thus only return 50 tags per page.

"},{"location":"self-hosted-configuration/#dockersidecarimage","title":"dockerSidecarImage","text":"

Change this value to override the default Renovate sidecar image.

Name Value type string default \"ghcr.io/renovatebot/base-image:13.155.0\" cli --docker-sidecar-image env RENOVATE_DOCKER_SIDECAR_IMAGE

This feature has been deprecated

The usage of binarySource=docker is deprecated, and will be removed in the future

By default Renovate pulls the sidecar Docker containers from ghcr.io/renovatebot/base-image. You can use the dockerSidecarImage option to override this default.

Say you want to pull a custom image from ghcr.io/your_company/sidecar. You would put this in your configuration file:

{\n  \"dockerSidecarImage\": \"ghcr.io/your_company/sidecar\"\n}\n

Now when Renovate pulls a new sidecar image, the final image is ghcr.io/your_company/sidecar instead of ghcr.io/renovatebot/base-image.

"},{"location":"self-hosted-configuration/#dockeruser","title":"dockerUser","text":"

Set the UID and GID for Docker-based binaries if you use binarySource=docker.

Name Value type string default \"12021\" cli --docker-user env RENOVATE_DOCKER_USER

This feature has been deprecated

The usage of binarySource=docker is deprecated, and will be removed in the future

Override default user and group used by Docker-based tools. The user-id (UID) and group-id (GID) must match the user that executes Renovate.

Read the Docker run reference for more information on user and group syntax. Set this to 1001:1002 to use UID 1001 and GID 1002.

Setting UID to 1001 and GID to 1002
{\n  \"dockerUser\": \"1001:1002\"\n}\n

If you use binarySource=docker|install read the section below.

If you need to change the Docker user please make sure to use the root (0) group, otherwise you'll get in trouble with missing file and directory permissions. Like this:

> export RENOVATE_DOCKER_USER=\"$(id -u):0\" # 500:0 (username:root)\n
"},{"location":"self-hosted-configuration/#dryrun","title":"dryRun","text":"

If enabled, perform a dry run by logging messages instead of creating/updating/deleting branches and PRs.

Name Value type string allowedValues 
[\"extract\", \"lookup\", \"full\"]\n
cli --dry-run env RENOVATE_DRY_RUN

Use dryRun to preview the behavior of Renovate in logs, without making any changes to the repository files.

You can choose from the following behaviors for the dryRun config option:

Information provided mainly in debug log level.

"},{"location":"self-hosted-configuration/#encryptedwarning","title":"encryptedWarning","text":"

Warning text to use if encrypted config is found.

Name Value type string cli --encrypted-warning env RENOVATE_ENCRYPTED_WARNING default null

Warning

For advanced use only! Use at your own risk!

Use this if you want to stop supporting encrypted configuration capabilities but want to warn users first to migrate.

If set to a string value, Renovate will log warnings with the encryptedWarning text, meaning the message will be visible to users such as on the Dependency Dashboard.

"},{"location":"self-hosted-configuration/#endpoint","title":"endpoint","text":"

Custom endpoint to use.

Name Value type string cli --endpoint env RENOVATE_ENDPOINT"},{"location":"self-hosted-configuration/#executiontimeout","title":"executionTimeout","text":"

Default execution timeout in minutes for child processes Renovate creates.

Name Value type integer default 15 cli --execution-timeout env RENOVATE_EXECUTION_TIMEOUT

Default execution timeout in minutes for child processes Renovate creates. If this option is not set, Renovate will fallback to 15 minutes.

"},{"location":"self-hosted-configuration/#exitcodeforerrors","title":"exitCodeForErrors","text":"

Exit with an error-specific exit code when a repository run ends in a known error state.

Name Value type boolean default false cli --exit-code-for-errors env RENOVATE_EXIT_CODE_FOR_ERRORS

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Set exitCodeForErrors to true to exit with a code that says which kind of error ended the repository run. The groups are the exported error constants in lib/constants/error-messages.ts:

Exit code Repository result 0 Success, or a RepositoryErrors result 1 Renovate logged an error, but no repository ended in one of the states below 2 Renovate could not parse its own configuration 3 SystemErrors 4 PlatformErrors 5 ConfigErrors 6 TemporaryErrors 7 External host error, lockfile error, or missing API credentials 8 Unknown error

Codes 3 to 8 take precedence over 1, so a repository that ends in one of those states sets the exit code even if errors were logged as well. Renovate still exits 1 when no repository ended in an error state but something was logged at error level, such as a failed changelog fetch during an otherwise successful run.

The results in RepositoryErrors map to 0, because they mean the repository is disabled, archived, empty and so on, and not that the run failed.

When Renovate runs against multiple repositories, the exit code comes from the first repository that ended in an error state. Renovate still processes the remaining repositories.

The exit code a repository maps to is always logged in the Repository finished message, even when this option is disabled.

"},{"location":"self-hosted-configuration/#exposeallenv","title":"exposeAllEnv","text":"

Set this to true to allow passing of all environment variables to package managers.

Name Value type boolean default false cli --expose-all-env env RENOVATE_EXPOSE_ALL_ENV previouslyKnownAs 
[\"exposeEnv\"]\n

Warning

For advanced use only! Use at your own risk!

To keep you safe, Renovate only passes a limited set of environment variables to package managers. If you must expose all environment variables to package managers, you can set this option to true.

Warning

Always consider the security implications of using exposeAllEnv! Secrets and other confidential information stored in environment variables could be leaked by a malicious script, that enumerates all environment variables.

Set exposeAllEnv to true only if you have reviewed, and trust, the repositories which Renovate runs against. Alternatively, you can use the customEnvVariables config option to handpick a set of variables you need to expose.

Setting this to true also allows for variable substitution in .npmrc files.

"},{"location":"self-hosted-configuration/#force","title":"force","text":"

Any configuration set in this object will force override existing settings.

Name Value type object mergeable true env RENOVATE_FORCE

This object is used as a \"force override\" when you need to make sure certain configuration overrides whatever is configured in the repository. For example, forcing a null (no) schedule to make sure Renovate raises PRs on a run even if the repository itself or its preset defines a schedule that's currently inactive.

In practice, it is implemented by converting the force configuration into a packageRule that matches all packages.

"},{"location":"self-hosted-configuration/#forcecli","title":"forceCli","text":"

Decides if CLI configuration options are moved to the force config section.

Name Value type boolean default true cli --force-cli env RENOVATE_FORCE_CLI

This is set to true by default, meaning that any settings (such as schedule) take maximum priority even against custom settings existing inside individual repositories. It will also override any settings in packageRules.

"},{"location":"self-hosted-configuration/#forkcreation","title":"forkCreation","text":"

Whether to create forks as needed at runtime when running in \"fork mode\".

Name Value type boolean supportedPlatforms github default true cli --fork-creation env RENOVATE_FORK_CREATION

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

This configuration lets you disable the runtime forking of repositories when running in \"fork mode\".

Usually you will need to keep this as the default true, and only set to false if you have some out of band process to handle the creation of forks.

"},{"location":"self-hosted-configuration/#forkorg","title":"forkOrg","text":"

The preferred organization to create or find forked repositories, when in fork mode.

Name Value type string supportedPlatforms github cli --fork-org env RENOVATE_FORK_ORG default null

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

This configuration option lets you choose an organization you want repositories forked into when \"fork mode\" is enabled. It must be set to a GitHub Organization name and not a GitHub user account. When set, \"allow edits by maintainers\" will be false for PRs because GitHub does not allow this setting for organizations.

This can be used if you're migrating from user-based forks to organization-based forks.

If you've set a forkOrg then Renovate will:

  1. Check if a fork exists in the preferred organization before checking it exists in the fork user's account
  2. If no fork exists: it will be created in the forkOrg, not the user account
"},{"location":"self-hosted-configuration/#forktoken","title":"forkToken","text":"

Set a personal access token here to enable \"fork mode\".

Name Value type string supportedPlatforms github cli --fork-token env RENOVATE_FORK_TOKEN default null

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

If this value is configured then Renovate:

Renovate will then create branches on the fork and opens Pull Requests on the parent repository.

Note

Forked repositories will always be skipped when forkToken is set, even if includeForks is true.

"},{"location":"self-hosted-configuration/#gitnoverify","title":"gitNoVerify","text":"

Which Git commands will be run with the --no-verify option.

Name Value type array subType string allowedValues 
[\"commit\", \"push\"]\n
default 
[\"commit\", \"push\"]\n
cli --git-no-verify env RENOVATE_GIT_NO_VERIFY

Controls when Renovate passes the --no-verify flag to git. The flag can be passed to git commit and/or git push. Read the documentation for git commit --no-verify and git push --no-verify to learn exactly what each flag does. To learn more about Git hooks, read the Pro Git 2 book, section on Git Hooks.

"},{"location":"self-hosted-configuration/#gitprivatekey","title":"gitPrivateKey","text":"

PGP key to use for signing Git commits.

Name Value type string env RENOVATE_GIT_PRIVATE_KEY default null

This is a private PGP or SSH key for signing Git commits.

For PGP, it should be an armored private key, so the type you get from running gpg --export-secret-keys --armor 92066A17F0D1707B4E96863955FEF5171C45FAE5 > private.key. Replace the newlines with \\n before adding the resulting single-line value to your self-hosted config.

Note

The private key can't be protected with a passphrase if running in a headless environment. Renovate will not be able to handle entering the passphrase.

It will be loaded lazily. Before the first commit in a repository, Renovate will:

  1. Run gpg import (if you haven't before) when using PGP
  2. Run git config user.signingkey, git config commit.gpgsign true and git config gpg.format

The git commands are run locally in the cloned repo instead of globally. This reduces the chance of unintended consequences with global Git configs on shared systems.

"},{"location":"self-hosted-configuration/#gitprivatekeypassphrase","title":"gitPrivateKeyPassphrase","text":"

Passphrase for the gitPrivateKey

Name Value type string env RENOVATE_GIT_PRIVATE_KEY_PASSPHRASE default null

Passphrase for the gitPrivateKey when the private key is protected with a passphrase.

Currently supported for SSH keys only. When provided, Renovate will automatically decrypt the SSH private key during the signing process.

Note

Passphrases are not yet supported for GPG keys. If you provide a passphrase for a GPG key, it will be ignored and a warning will be logged.

Warning

Store this value securely as it provides access to decrypt your private key. Consider using environment variables or secure secret management systems rather than storing it in plain text configuration files.

"},{"location":"self-hosted-configuration/#gittimeout","title":"gitTimeout","text":"

Configure the timeout with a number of milliseconds to wait for a Git task.

Name Value type integer default 0 cli --git-timeout env RENOVATE_GIT_TIMEOUT

To handle the case where the underlying Git processes appear to hang, configure the timeout with the number of milliseconds to wait after last received content on either stdOut or stdErr streams before sending a SIGINT kill message.

"},{"location":"self-hosted-configuration/#giturl","title":"gitUrl","text":"

Overrides the default resolution for Git remote, e.g. to switch GitLab from HTTPS to SSH-based.

Name Value type string supportedPlatforms bitbucket-server, forgejo, gerrit, gitea, github, gitlab, scm-manager allowedValues 
[\"default\", \"ssh\", \"endpoint\"]\n
default \"default\" cli --git-url env RENOVATE_GIT_URL

Override the default resolution for Git remote, e.g. to switch GitLab from HTTPS to SSH-based.

Possible values:

Note

On GitHub, default and endpoint are equivalent: both build the HTTPS URL from the configured endpoint with credentials embedded. ssh uses the repository's sshUrl and authenticates via SSH key. In fork mode (forkToken set with forkCreation), ssh applies to both the fork's working URL and the upstream URL.

"},{"location":"self-hosted-configuration/#githubtokenwarn","title":"githubTokenWarn","text":"

Display warnings about GitHub token not being set.

Name Value type boolean default true cli --github-token-warn env RENOVATE_GITHUB_TOKEN_WARN

By default, Renovate logs and displays a warning when the RENOVATE_GITHUB_COM_TOKEN is not set. By setting githubTokenWarn to false, Renovate suppresses these warnings on Pull Requests, etc. Disabling the warning is helpful for self-hosted environments that can't access the github.com domain, because the warning is useless in these environments.

"},{"location":"self-hosted-configuration/#globalextends","title":"globalExtends","text":"

Configuration presets to use or extend for a self-hosted config.

Name Value type array subType string cli --global-extends env RENOVATE_GLOBAL_EXTENDS default []

Unlike the extends field, which is passed through unresolved to be part of repository config, any presets in globalExtends are resolved immediately as part of global config. Use the globalExtends field if your preset has any global-only configuration options, such as the list of repositories to run against.

Use the extends field instead of this if, for example, you need the ability for a repository config (e.g. renovate.json) to be able to use ignorePresets for any preset defined in global config.

Note

Renovate applies your own hostRules, internalHostAccess, platform and endpoint when it fetches globalExtends presets. A globalExtends preset on an internal host is judged like any other preset, so a scoped allowInternal grant permits it. The hostRules, internalHostAccess and secrets set inside a globalExtends preset do not apply when Renovate fetches that preset, or the presets it extends.

Warning

Renovate resolves globalExtends before it initializes the platform, so it does not have the platform token yet. To fetch a private globalExtends preset, including a local> preset, add a hostRules entry with the credentials for its host.

"},{"location":"self-hosted-configuration/#goenvfromhostrules","title":"goEnvFromHostRules","text":"

Derive GOPROXY, GONOPROXY and GONOSUMDB from host rules when they are not set in the environment.

Name Value type boolean default false cli --go-env-from-host-rules env RENOVATE_GO_ENV_FROM_HOST_RULES

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Set to true to derive the GOPROXY, GONOPROXY and GONOSUMDB environment variables from your host rules, if you have not set them yourself. Read the Go Modules docs to learn more.

"},{"location":"self-hosted-configuration/#hostrules","title":"hostRules","text":"

These hostRules fields are only allowed in self-hosted config, and are ignored (or rejected with a config error) if set in repository config or a preset. See hostRules for the rest of the available fields.

When Renovate prepares outgoing HTTP traffic, it considers:

could this outbound HTTP call lead to configuration being included? (i.e. it's part of an extends, but not part of i.e. customDatasources)

If it is, Renovate treats it more cautiously, alongside the current configuration for internalHostAccess.

Could request become config internalHostAccess setting Host being requested Result How to allow traffic Yes internalHostAccess=block https://docs.renovatebot.com Allowed Yes internalHostAccess=block 169.254.169.254 Blocked Not possible Yes internalHostAccess=block http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Blocked Create a host rule setting allowInternal=true, scoped with a hostType or a URL-prefix matchHost No internalHostAccess=block https://docs.renovatebot.com Allowed No internalHostAccess=block 169.254.169.254 Blocked Not possible No internalHostAccess=block http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Blocked Create a host rule naming the host with matchHost (trusted1), or one setting allowInternal=true Yes internalHostAccess=warn https://docs.renovatebot.com Allowed Yes internalHostAccess=warn 169.254.169.254 Blocked Not possible Yes internalHostAccess=warn http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Allowed, with a WARN log Create a host rule setting allowInternal=true, scoped with a hostType or a URL-prefix matchHost2 No internalHostAccess=warn https://docs.renovatebot.com Allowed No internalHostAccess=warn 169.254.169.254 Blocked Not possible No internalHostAccess=warn http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Allowed, with a WARN log Create a host rule naming the host with matchHost (trusted1), or one setting allowInternal=true2 Yes internalHostAccess=allow https://docs.renovatebot.com Allowed Yes internalHostAccess=allow 169.254.169.254 Blocked Not possible Yes internalHostAccess=allow http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Allowed, no warning Already allowed - no host rule needed No internalHostAccess=allow https://docs.renovatebot.com Allowed No internalHostAccess=allow 169.254.169.254 Blocked Not possible No internalHostAccess=allow http://172.16.1.5:8081/artifactory/repo/internal-presets/default.json Allowed, no warning Already allowed - no host rule needed

1: a \"trusted\" host rule is one that's configured by the self-hosted administrator

2: under internalHostAccess=warn, the request is allowed either way - the host rule only silences the WARN log, it isn't required for the request to go through

"},{"location":"self-hosted-configuration/#hostrulesallowinternal","title":"hostRules.allowInternal","text":"

Whether requests to this host may reach internal addresses when internalHostAccess=block. Only honored from the self-hosted administrator's own configuration, or from inherited config when inheritConfigTrusted=true.

Name Value type boolean parents hostRules inheritConfigSupport true default true

Warning

For advanced use only! Use at your own risk!

As seen above, specifying allowInternal is required when Renovate interacts with private addresses, and is dependent on how internalHostAccess is configured.

If a host is being used i.e. in a customDatasources or a registryUrl configuration, then an implicit grant is sufficient. For instance, if the self-hosted configuration authenticates to a private Artifactory deployment:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"http://172.16.1.5:8081/artifactory\",\n      \"username\": \"renovate-user\",\n      \"password\": \"{{ secrets.ARTIFACTORY_PASSWORD }}\"\n    }\n  ]\n}\n

Warning

An implicit grant does not depend on the rule carrying credentials. Any host rule in your own configuration whose matchHost matches the host grants internal access to it, even a rule that only sets something like timeout or concurrentRequestLimit. This means that when you upgrade, the hostRules you already have silently become internal-access grants for the hosts they name.

If there are hosts that you do not want Renovate to access, it is worth explicitly blocking them with:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"http://localhost:8500/v1/flags/\",\n      \"allowInternal\": false\n    }\n  ]\n}\n

Setting allowInternal=false is also how you keep a rule you need for another reason - credentials, for instance - without it granting internal access to the host it names.

It is recommended to use a URL-prefix matchHost (as above) over a bare hostname when permitting loopback addresses, so that only the intended service - and not everything else running on the same host - becomes reachable. Include the port in that prefix for the same reason. A bare hostname matchHost also matches every subdomain of that host, so prefer a URL prefix whenever you want the grant to stay narrow.

If a host is being used i.e. in an extends, an explicit grant is required to permit fetching that configuration. This covers HTTP presets, and npm: presets - whose registry a repository can point at any host with its own npmrc. The grant must be deliberately scoped, by setting allowInternal on a rule with a hostType, or on one with a URL-prefix matchHost:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"preset\",\n      \"matchHost\": \"https://config-server.corp/renovate-presets/\",\n      \"allowInternal\": true\n    },\n    {\n      \"hostType\": \"npm\",\n      \"matchHost\": \"https://registry.corp/\",\n      \"allowInternal\": true\n    }\n  ]\n}\n

The first rule permits HTTP presets from that server, the second npm: presets from that registry.

Note

A URL-form matchHost is scoped enough on its own, so a hostType is not required. A rule such as { \"matchHost\": \"http://10.1.2.3\", \"allowInternal\": true } therefore permits config-fetching requests - such as HTTP presets - to that URL prefix, and not only lookups. A bare hostname such as { \"matchHost\": \"10.1.2.3\", \"allowInternal\": true } is not scoped, and permits lookups only.

Cloud instance-metadata endpoints are always blocked, and cannot be permitted with this field.

"},{"location":"self-hosted-configuration/#httpcachettldays","title":"httpCacheTtlDays","text":"

Maximum duration in days to keep HTTP cache entries.

Name Value type integer default 90 cli --http-cache-ttl-days env RENOVATE_HTTP_CACHE_TTL_DAYS

This option sets the number of days that Renovate will cache HTTP responses. The default value is 90 days. Value of 0 means no caching.

Warning

When you set httpCacheTtlDays to 0, Renovate will remove the cached HTTP data.

"},{"location":"self-hosted-configuration/#ignoreprauthor","title":"ignorePrAuthor","text":"

Set to true to fetch the entire list of PRs instead of only those authored by the Renovate user.

Name Value type boolean default false cli --ignore-pr-author env RENOVATE_IGNORE_PR_AUTHOR

This is usually needed if someone needs to migrate the account Renovate runs as, including from the Mend Renovate App to self-hosted. An additional use case is for GitLab users of project or group access tokens who need to rotate them.

If ignorePrAuthor is configured to true, it means Renovate will fetch the entire list of repository PRs instead of optimizing to fetch only those PRs which it created itself. You should only want to enable this if you are changing the account Renovate runs as (e.g. from @old-bot to @new-bot) and want @new-bot to find and update any existing PRs created by @old-bot.

Setting this field to true in Github or GitLab will also mean that all Issues will be fetched instead of only those by Renovate itself.

"},{"location":"self-hosted-configuration/#includemirrors","title":"includeMirrors","text":"

Whether to process repositories that are mirrors. By default, repositories that are mirrors are skipped.

Name Value type boolean default false supportedPlatforms gitlab cli --include-mirrors env RENOVATE_INCLUDE_MIRRORS

By default, Renovate does not autodiscover repositories that are mirrors.

Change this setting to true to include repositories that are mirrors as Renovate targets.

"},{"location":"self-hosted-configuration/#inheritconfig","title":"inheritConfig","text":"

If true, Renovate will inherit configuration from the inheritConfigFileName file in inheritConfigRepoName.

Name Value type boolean default false cli --inherit-config env RENOVATE_INHERIT_CONFIG

When you enable this option, Renovate will look for the inheritConfigFileName file in the inheritConfigRepoName repository before processing a repository, and read this in as config.

If the repository is in a nested organization or group on a supported platform such as GitLab, such as topGroup/nestedGroup/projectName then Renovate will look in topGroup/nestedGroup/renovate-config.

If inheritConfig is true but the inherited config file does not exist then Renovate will proceed without warning. If the file exists but cannot be parsed, then Renovate will raise a config warning issue and abort the job.

The inherited config may include all valid repository config and these config options:

This way organizations can change/control the default behavior, like whether configs are required and how repositories are onboarded.

Configured hostRules in inherited config are treated as if they are repository configuration, when applying precedence and whether internalHostAccess can be configured. If you trust each organisation onboarded to this Renovate deployment to be able to specify at an organisation level whether they should be able to access internal hosts, you can set inheritConfigTrusted=true.

We disabled inheritConfig in the Mend Renovate App to avoid wasting millions of API calls per week. This is because each 404 response from the GitHub API due to a missing org inherited config counts as a used API call. We will add a smart/dynamic approach in future, so that we can selectively enable inheritConfig per organization.

"},{"location":"self-hosted-configuration/#inheritconfigfilename","title":"inheritConfigFileName","text":"

Renovate will look for this config file name in the inheritConfigRepoName.

Name Value type string default \"org-inherited-config.json\" cli --inherit-config-file-name env RENOVATE_INHERIT_CONFIG_FILE_NAME

Change this setting if you want Renovate to look for a different file name within the inheritConfigRepoName repository. You may use nested files, for example: \"some-dir/config.json\".

"},{"location":"self-hosted-configuration/#inheritconfigreponame","title":"inheritConfigRepoName","text":"

Renovate will look in this repo for the inheritConfigFileName.

Name Value type string default \"{{parentOrg}}/renovate-config\" supportsTemplating true cli --inherit-config-repo-name env RENOVATE_INHERIT_CONFIG_REPO_NAME

This option supports Renovate's template syntax

See templates for available variables and helpers.

Change this setting if you want Renovate to look in an alternative repository for the inherited config. The repository must be on the same platform and endpoint, and Renovate's token must have read permissions to the repository.

"},{"location":"self-hosted-configuration/#inheritconfigstrict","title":"inheritConfigStrict","text":"

If true, any inheritedConfig fetch error will result in an aborted run.

Name Value type boolean default false cli --inherit-config-strict env RENOVATE_INHERIT_CONFIG_STRICT

By default Renovate will silently (debug log message only) ignore cases where inheritConfig=true but no inherited config is found. When you set inheritConfigStrict=true then Renovate will abort the run and raise a config error if Renovate can't find the inherited config.

Warning

Only set this config option to true if every organization has an inherited config file and you want to make sure Renovate always uses that inherited config.

"},{"location":"self-hosted-configuration/#inheritconfigtrusted","title":"inheritConfigTrusted","text":"

If true, hostRules in inherited config may grant access to internal hosts.

Name Value type boolean default false cli --inherit-config-trusted env RENOVATE_INHERIT_CONFIG_TRUSTED

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Warning

For advanced use only! Use at your own risk!

Warning

Only set this to true if everyone who can push to the inheritConfigRepoName repositories are trusted to control these additional settings. This trust is transitive: hostRules defined in any preset the inherited config extends are trusted at the same level, so everyone who can change those preset sources must be trusted too. If you're running a multi-tenant platform, it is recommended you leave this disabled.

"},{"location":"self-hosted-configuration/#host-rules","title":"Host Rules","text":"

By default, hostRules in inherited config are treated like a repository's own: they may carry credentials or headers, but they cannot grant access to internal hosts.

This is because the inheritConfigRepoName repository is controlled by each organization's administrators, rather than the self-hosted administrators themselves. As this repository is outside of the self-hosted administrator's control, there may be looser access control than may be wanted on the repository and its ability to provide settings, and so an additional level of opt-in trust is required.

If you opt in by setting inheritConfigTrusted=true, this will permit the inherited config to set hostRules:

A self-hosted administrator's configuration still takes precedence for:

Inherited config cannot permit the hosts of its own extends presets, whatever this option is set to: those presets are resolved before its hostRules are registered. A preset that inherited config extends from an internal host still needs a grant in global config.

Trust does however extend to the hostRules defined in those presets: once the inherited config's extends are resolved, the hostRules they contribute are registered at the same inherited trust level, as if the inherited config had defined them itself.

"},{"location":"self-hosted-configuration/#internalhostaccess","title":"internalHostAccess","text":"

Whether Renovate may make HTTP requests to internal hosts, such as loopback, private-range and link-local addresses. warn logs the requests which block would refuse.

Name Value type string allowedValues 
[\"allow\", \"warn\", \"block\"]\n
default \"warn\" cli --internal-host-access env RENOVATE_INTERNAL_HOST_ACCESS

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Warning

For advanced use only! Use at your own risk!

Controls whether Renovate may make HTTP requests to internal hosts: loopback, RFC1918 private ranges, link-local, carrier-grade NAT, IPv6 unique-local, and similar special-use addresses. This applies whether the URL names an IP address directly, or a hostname which resolves to one, and covers redirects too.

The default will become block in a future major release, so treat the warnings as the work to do before then. Hosted platforms, such as the Mend Renovate App, may run with block regardless of this setting.

Warning

allow is a migration escape hatch, and we plan to remove it in a future major release. After that, every internal host Renovate should reach needs a hostRules entry permitting it, and there is no way to silence the warnings in bulk. Use the time before then to add those grants, rather than to keep allow set.

The policy applies no matter where the URL came from - repository configuration such as extends presets or registryUrls, package file contents, or your own configuration - if Renovate should be able to reach an internal host, you need to permit it with a hostRule rather than setting allow.

For most deployments there is nothing to do: internal registries nearly always already have a hostRules entry carrying their credentials, which permits them implicitly, and so are never warned about. Hosts without one only need naming:

{\n  \"hostRules\": [\n    { \"matchHost\": \"artifactory.corp\" },\n    {\n      \"hostType\": \"preset\",\n      \"matchHost\": \"https://config-server.corp/renovate-presets/\",\n      \"allowInternal\": true\n    }\n  ]\n}\n

The first rule permits an internal registry the same way a credentialed rule would, and the second deliberately permits fetching HTTP presets from an internal host. Anything whose response becomes configuration - HTTP presets, and npm: presets - always requires such an explicit, scoped allowInternal grant, even for a host your other rules already permit.

Once your grants are in place and the warnings have stopped, set internalHostAccess=block to enforce the policy today, rather than waiting for the default to change. Set internalHostAccess=allow only as a temporary escape hatch while you work out which hosts to permit.

If you manage hostRules centrally through inheritConfig, those rules do not grant anything by default, because that repository is the organization's rather than yours. Either opt into trusting them with inheritConfigTrusted=true, or move the rules for internal hosts into your own global config or a repositories[] entry.

Cloud instance-metadata endpoints (such as 169.254.169.254, 169.254.170.2 and metadata.google.internal) are always blocked, regardless of internalHostAccess' setting, as Renovate's HTTP layer never has a legitimate reason to request them. This does not affect Renovate's cloud environment detection or cloud SDK authentication, which do not use Renovate's HTTP layer - see useCloudMetadataServices.

If you run Renovate behind a proxy (HTTP_PROXY or HTTPS_PROXY), the proxy resolves the target hostname, so Renovate cannot check the address it actually connects to. Renovate still checks the URL itself and every redirect target, and resolves the hostname up front as a best-effort check, but as the proxy resolves the name again the two answers can differ - such as with DNS rebinding, or split-horizon DNS. Renovate lets the request through when it cannot resolve the hostname itself, which is common in locked-down proxy environments. Restrict what your proxy may reach with egress controls on the proxy, for defense in depth.

"},{"location":"self-hosted-configuration/#logcontext","title":"logContext","text":"

Add a global or per-repo log context to each log entry.

Name Value type string cli --log-context env RENOVATE_LOG_CONTEXT

logContext is included with each log entry only if logFormat=\"json\" - it is not included in the pretty log output. If left as default (null), a random short ID will be selected.

"},{"location":"self-hosted-configuration/#mergeconfidencedatasources","title":"mergeConfidenceDatasources","text":"

If set, Renovate will query the merge-confidence JSON API only for datasources that are part of this list.

Name Value allowedValues 
[\"go\", \"maven\", \"npm\", \"nuget\", \"packagist\", \"pypi\", \"rubygems\"]\n
default 
[\"go\", \"maven\", \"npm\", \"nuget\", \"packagist\", \"pypi\", \"rubygems\"]\n
type array subType string cli --merge-confidence-datasources env RENOVATE_MERGE_CONFIDENCE_DATASOURCES previouslyKnownAs 
[\"RENOVATE_X_MERGE_CONFIDENCE_SUPPORTED_DATASOURCES\"]\n

This feature is applicable only if you have an access token for Mend's Merge Confidence API.

If set, Renovate will query the merge-confidence JSON API only for datasources that are part of this list. Otherwise, it queries all the supported datasources (check default value).

Example:

module.exports = {\n  mergeConfidenceDatasources: ['npm'],\n};\n
"},{"location":"self-hosted-configuration/#mergeconfidenceendpoint","title":"mergeConfidenceEndpoint","text":"

If set, Renovate will query this API for Merge Confidence data.

Name Value type string default \"https://developer.mend.io/\" cli --merge-confidence-endpoint env RENOVATE_MERGE_CONFIDENCE_ENDPOINT previouslyKnownAs 
[\"RENOVATE_X_MERGE_CONFIDENCE_API_BASE_URL\"]\n

Warning

For advanced use only! Use at your own risk!

This feature is applicable only if you have an access token for Mend's Merge Confidence API.

If set, Renovate will retrieve Merge Confidence data by querying this API. Otherwise, it will use the default URL, which is https://developer.mend.io/.

If you use the Mend Renovate Enterprise Edition (Renovate EE) and:

Then you must set this variable at the server and the workers.

But if you have specified the token as a matchConfidence packageRule, you only need to set this variable at the workers.

This feature is in private beta.

"},{"location":"self-hosted-configuration/#migratepresets","title":"migratePresets","text":"

Define presets here which have been removed or renamed and should be migrated automatically.

Name Value type object additionalProperties 
{\"type\": \"string\"}\n
cli --migrate-presets env RENOVATE_MIGRATE_PRESETS

Use this if you have repositories that extend from a particular preset, which has now been renamed or removed. This is handy if you have a large number of repositories that all extend from a particular preset which you want to rename, without the hassle of manually updating every repository individually. Use an empty string to indicate that the preset should be ignored rather than replaced.

Example:

module.exports = {\n  migratePresets: {\n    '@company': 'local>org/renovate-config',\n  },\n};\n

In the above example any reference to the @company preset will be replaced with local>org/renovate-config.

Tip

Combine migratePresets with configMigration if you'd like your config migrated by PR.

"},{"location":"self-hosted-configuration/#onboarding","title":"onboarding","text":"

Require a Configuration PR first.

Name Value type boolean inheritConfigSupport true cli --onboarding env RENOVATE_ONBOARDING default true

Only set this to false if all three statements are true:

"},{"location":"self-hosted-configuration/#onboardingautocloseage","title":"onboardingAutoCloseAge","text":"

Maximum number of days after which Renovate will stop trying to onboard the repository, and will close any existing onboarding PRs

Name Value type integer inheritConfigSupport true env RENOVATE_ONBOARDING_AUTO_CLOSE_AGE

Maximum number of days after which Renovate will stop trying to onboard the repository, and will close any existing onboarding PRs.

By default this option is set to null.

"},{"location":"self-hosted-configuration/#onboardingbranch","title":"onboardingBranch","text":"

Change this value to override the default onboarding branch name.

Name Value type string default \"renovate/configure\" inheritConfigSupport true env RENOVATE_ONBOARDING_BRANCH

Note

This setting is independent of branchPrefix.

For example, if you configure branchPrefix to be renovate- then you'd still have the onboarding PR created with branch renovate/configure until you configure onboardingBranch=renovate-configure or similar. If you have an existing Renovate installation and you change onboardingBranch then it's possible that you'll get onboarding PRs for repositories that had previously closed the onboarding PR unmerged.

"},{"location":"self-hosted-configuration/#onboardingcommitmessage","title":"onboardingCommitMessage","text":"

Change this value to override the default onboarding commit message.

Name Value type string inheritConfigSupport true env RENOVATE_ONBOARDING_COMMIT_MESSAGE

If commitMessagePrefix or semanticCommits values are set then they will be prepended to the commit message using the same logic that is used for adding them to non-onboarding commit messages.

"},{"location":"self-hosted-configuration/#onboardingconfig","title":"onboardingConfig","text":"

Configuration to use for onboarding PRs.

Name Value type object default 
{\"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\"}\n
inheritConfigSupport true mergeable true cli --onboarding-config env RENOVATE_ONBOARDING_CONFIG"},{"location":"self-hosted-configuration/#onboardingconfigfilename","title":"onboardingConfigFileName","text":"

Change this value to override the default onboarding config file name.

Name Value type string default \"renovate.json\" inheritConfigSupport true env RENOVATE_ONBOARDING_CONFIG_FILE_NAME

If set to one of the valid config file names, the onboarding PR will create a configuration file with the provided name instead of renovate.json. Falls back to renovate.json if the name provided is not valid.

Note

If you want renovate to use a custom filename for the onboarding branch you need add allow that filename using the configFileNames option.

"},{"location":"self-hosted-configuration/#onboardingnodeps","title":"onboardingNoDeps","text":"

Onboard the repository even if no dependencies are found.

Name Value type string default \"auto\" allowedValues 
[\"auto\", \"enabled\", \"disabled\"]\n
inheritConfigSupport true cli --onboarding-no-deps env RENOVATE_ONBOARDING_NO_DEPS

The default auto setting is converted to disabled if autodiscoverRepositories is true, or converted to enabled if false.

In other words, the default behavior is:

"},{"location":"self-hosted-configuration/#onboardingprtitle","title":"onboardingPrTitle","text":"

Change this value to override the default onboarding PR title.

Name Value type string default \"Configure Renovate\" inheritConfigSupport true env RENOVATE_ONBOARDING_PR_TITLE

If you have an existing Renovate installation and you change the onboardingPrTitle: then you may get onboarding PRs again for repositories with closed non-merged onboarding PRs. This is similar to what happens when you change the onboardingBranch config option.

"},{"location":"self-hosted-configuration/#onboardingrebasecheckbox","title":"onboardingRebaseCheckbox","text":"

Set to enable rebase/retry markdown checkbox for onboarding PRs.

Name Value type boolean default false supportedPlatforms forgejo, gitea, github, gitlab cli --onboarding-rebase-checkbox env RENOVATE_ONBOARDING_REBASE_CHECKBOX

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.To track this feature visit the following GitHub issue #17633.

"},{"location":"self-hosted-configuration/#optimizefordisabled","title":"optimizeForDisabled","text":"

Set to true to perform a check for disabled config prior to cloning.

Name Value type boolean default false cli --optimize-for-disabled env RENOVATE_OPTIMIZE_FOR_DISABLED

When this option is true, Renovate will do the following during repository initialization:

  1. Try to fetch the default config file (e.g. renovate.json)
  2. Check if the file contains \"enabled\": false
  3. If so, skip cloning and skip the repository immediately

If onboardingConfigFileName is set, that file name will be used instead of the default.

If the file exists and the config is disabled, Renovate will skip the repo without cloning it. Otherwise, it will continue as normal.

optimizeForDisabled can make initialization quicker in cases where most repositories are disabled, but it uses an extra API call for enabled repositories.

A second, advanced, use also exists when the global config has extends: [\":disableRenovate\"]. In that case, Renovate searches the repository config file for any of these configurations:

If Renovate finds any of the above configurations, it continues initializing the repository. If not, then Renovate skips the repository without cloning it.

"},{"location":"self-hosted-configuration/#password","title":"password","text":"

Password for authentication.

Name Value type string supportedPlatforms azure, bitbucket, bitbucket-server cli --password env RENOVATE_PASSWORD default null"},{"location":"self-hosted-configuration/#persistrepodata","title":"persistRepoData","text":"

If set to true: keep repository data between runs instead of deleting the data.

Name Value type boolean default false cli --persist-repo-data env RENOVATE_PERSIST_REPO_DATA

Set this to true if you want Renovate to persist repo data between runs. The intention is that this allows Renovate to do a faster git fetch between runs rather than git clone. It also may mean that ignored directories like node_modules can be preserved and save time on operations like npm install.

"},{"location":"self-hosted-configuration/#platform","title":"platform","text":"

Platform type of repository.

Name Value type string allowedValues 
[\n  \"azure\",\n  \"bitbucket\",\n  \"bitbucket-server\",\n  \"codecommit\",\n  \"forgejo\",\n  \"gerrit\",\n  \"gitea\",\n  \"github\",\n  \"gitlab\",\n  \"local\",\n  \"scm-manager\"\n]\n
default \"github\" cli --platform env RENOVATE_PLATFORM"},{"location":"self-hosted-configuration/#prcachesyncmaxpages","title":"prCacheSyncMaxPages","text":"

Maximum number of pages to fetch when syncing the pull request cache.

Name Value type integer default 100 supportedPlatforms github cli --pr-cache-sync-max-pages env RENOVATE_PR_CACHE_SYNC_MAX_PAGES

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.To track this feature visit the following GitHub issue #41485.

Maximum number of pages to fetch when syncing the pull request cache.

"},{"location":"self-hosted-configuration/#prcommitsperrunlimit","title":"prCommitsPerRunLimit","text":"

Set the maximum number of commits per Renovate run. By default there is no limit.

Name Value type integer default 0 cli --pr-commits-per-run-limit env RENOVATE_PR_COMMITS_PER_RUN_LIMIT

Parameter to reduce CI load. CI jobs are usually triggered by these events: pull-request creation, pull-request update, automerge events. Set as an integer. Default is no limit.

"},{"location":"self-hosted-configuration/#presetcachepersistence","title":"presetCachePersistence","text":"

Cache resolved presets in package cache.

Name Value type boolean default false cli --preset-cache-persistence env RENOVATE_PRESET_CACHE_PERSISTENCE

When this feature is enabled, resolved presets will be cached in Renovate's package cache, enabling reuse across multiple repositories.

TTL is 15 minutes by default, and it is adjustable in cacheTtlOverride.

Warning

Doing so improves efficiency because shared presets don't need to be reloaded/resolved for every repository, however it also means that private presets can be \"leaked\" between repositories. You should only enable this when all repositories are trusted, such as a corporate environment.

"},{"location":"self-hosted-configuration/#privatekey","title":"privateKey","text":"

Server-side private key.

Name Value type string replaceLineReturns true cli --private-key env RENOVATE_PRIVATE_KEY default null

This private key is used to decrypt config files.

The corresponding public key can be used to create encrypted values for config files. If you want a UI to encrypt values you can put the public key in a HTML page similar to https://app.renovatebot.com/encrypt.

To create the PGP key pair with GPG use the following commands:

key generation log 
\u276f gpg --full-generate-key\ngpg (GnuPG) 2.2.24; Copyright (C) 2020 Free Software Foundation, Inc.\nThis is free software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitted by law.\n\nPlease select what kind of key you want:\n   (1) RSA and RSA (default)\n   (2) DSA and Elgamal\n   (3) DSA (sign only)\n   (4) RSA (sign only)\n  (14) Existing key from card\nYour selection? 1\nRSA keys may be between 1024 and 4096 bits long.\nWhat keysize do you want? (3072) 4096\nRequested keysize is 4096 bits\nPlease specify how long the key should be valid.\n         0 = key does not expire\n      <n>  = key expires in n days\n      <n>w = key expires in n weeks\n      <n>m = key expires in n months\n      <n>y = key expires in n years\nKey is valid for? (0)\nKey does not expire at all\nIs this correct? (y/N) y\n\nGnuPG needs to construct a user ID to identify your key.\n\nReal name: Renovate\nEmail address: renovate@whitesourcesoftware.com\nComment:\nYou selected this USER-ID:\n    \"Renovate <renovate@whitesourcesoftware.com>\"\n\nChange (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O\n\ngpg: key 0649CC3899F22A66 marked as ultimately trusted\ngpg: revocation certificate stored as '/Users/rhys/.gnupg/openpgp-revocs.d/794B820F34B34A8DF32AADB20649CC3899F22A66.rev'\npublic and secret key created and signed.\n\npub   rsa4096 2021-09-10 [SC]\n      794B820F34B34A8DF32AADB20649CEXAMPLEONLY\nuid                      Renovate <renovate@whitesourcesoftware.com>\nsub   rsa4096 2021-09-10 [E]\n

Note

If you use GnuPG v2.4 (or newer) to generate the key, then you must disable AEAD preferences. This is needed to allow Renovate to decrypt the encrypted values.

key edit log 
\u276f gpg --edit-key renovate@whitesourcesoftware.com\ngpg> showpref\n[ultimate] (1). Renovate <renovate@whitesourcesoftware.com>\n     Cipher: AES256, AES192, AES, 3DES\n     AEAD: OCB, EAX\n     Digest: SHA512, SHA384, SHA256, SHA224, SHA1\n     Compression: ZLIB, BZIP2, ZIP, Uncompressed\n     Features: MDC, AEAD, Keyserver no-modify\n\ngpg> setpref AES256 AES192 AES 3DES SHA512 SHA384 SHA256 SHA224 SHA1 ZLIB BZIP2 ZIP\nSet preference list to:\n     Cipher: AES256, AES192, AES, 3DES\n     AEAD:\n     Digest: SHA512, SHA384, SHA256, SHA224, SHA1\n     Compression: ZLIB, BZIP2, ZIP, Uncompressed\n     Features: MDC, Keyserver no-modify\nReally update the preferences? (y/N) y\ngpg> save\n

The private key should then be added to your Renovate global config (either using privateKeyPath or exporting it to the RENOVATE_PRIVATE_KEY environment variable). The public key can be used to replace the existing key in https://app.renovatebot.com/encrypt for your own use.

Base64 Encoding Support

Renovate supports base64-encoded private keys for easier handling in environment variables or configuration files. Simply provide the base64-encoded version of your private key, and Renovate will automatically detect and decode it. This works for both GPG and SSH private keys.

Any PGP-encrypted secrets must have a mandatory organization/group scope, and optionally can be scoped for a single repository only. The reason for this is to avoid \"replay\" attacks where someone could learn your encrypted secret and then reuse it in their own Renovate repositories. Instead, with scoped secrets it means that Renovate ensures that the organization and optionally repository values encrypted with the secret match against the running repository.

Note

You could use public key encryption with earlier versions of Renovate. We deprecated this approach and removed the documentation for it. If you're still using public key encryption then we recommend that you use private keys instead.

"},{"location":"self-hosted-configuration/#privatekeyold","title":"privateKeyOld","text":"

Secondary or old private key to try.

Name Value type string replaceLineReturns true cli --private-key-old env RENOVATE_PRIVATE_KEY_OLD default null

Use this field if you need to perform a \"key rotation\" and support more than one keypair at a time. Decryption with this key will be tried after privateKey.

If you are migrating from the legacy public key encryption approach to use a PGP key, then move your legacy private key from privateKey to privateKeyOld and then put your new PGP private key in privateKey. Doing so will mean that Renovate will first try to decrypt using the PGP key but fall back to the legacy key and try that next.

You can remove the privateKeyOld config option once all the old encrypted values have been migrated, or if you no longer want to support the old key and let the processing of repositories fail.

Note

Renovate now logs a warning whenever repositories use non-PGP encrypted config variables.

"},{"location":"self-hosted-configuration/#privatekeypath","title":"privateKeyPath","text":"

Path to the Server-side private key.

Name Value type string cli --private-key-path env RENOVATE_PRIVATE_KEY_PATH default null

Used as an alternative to privateKey, if you want the key to be read from disk instead.

"},{"location":"self-hosted-configuration/#privatekeypathold","title":"privateKeyPathOld","text":"

Path to the Server-side old private key.

Name Value type string cli --private-key-path-old env RENOVATE_PRIVATE_KEY_PATH_OLD default null

Used as an alternative to privateKeyOld, if you want the key to be read from disk instead.

"},{"location":"self-hosted-configuration/#processenv","title":"processEnv","text":"

Environment variables to be used in global config only.

Name Value type object additionalProperties 
{\"type\": \"string\"}\n
cli --process-env env RENOVATE_PROCESS_ENV

Used to set environment variables through the configuration file instead of using actual environment variables.

Example:

{\n  \"processEnv\": {\n    \"AWS_ACCESS_KEY_ID\": \"AKIAIOSFODNN7EXAMPLE\",\n    \"AWS_SECRET_ACCESS_KEY\": \"wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY\",\n    \"AWS_DEFAULT_REGION\": \"us-west-2\"\n  }\n}\n

Note

"},{"location":"self-hosted-configuration/#productlinks","title":"productLinks","text":"

Links which are used in PRs, issues and comments.

Name Value type object mergeable true default 
{\n  \"documentation\": \"https://docs.renovatebot.com/\",\n  \"help\": \"https://github.com/renovatebot/renovate/discussions\",\n  \"homepage\": \"https://github.com/renovatebot/renovate\"\n}\n
additionalProperties 
{\"type\": \"string\", \"format\": \"uri\"}\n
cli --product-links env RENOVATE_PRODUCT_LINKS

Override this object if you want to change the URLs that Renovate links to, e.g. if you have an internal forum for asking for help.

"},{"location":"self-hosted-configuration/#rebaseallopenbranches","title":"rebaseAllOpenBranches","text":"

Rebase all open branches at once, as if the rebase-all-open-PRs checkbox was selected in the Dependency Dashboard issue.

Name Value type boolean cli --rebase-all-open-branches default false env RENOVATE_REBASE_ALL_OPEN_BRANCHES

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

It has been designed with the intention of being run on one repository, in a one-off manner, e.g. to \"force\" the rebase of all open PRs. It is highly unlikely that you should ever need to add this to your permanent global config.

Example: renovate --rebase-all-open-branches=true renovate-reproductions/checked will rebase all open PRs in the renovate-reproductions/checked repository.

"},{"location":"self-hosted-configuration/#redisprefix","title":"redisPrefix","text":"

Key prefix for redis cache entries.

Name Value type string cli --redis-prefix env RENOVATE_REDIS_PREFIX default null

If this value is set then Renovate will prepend this string to the name of all Redis cache entries used in Renovate. It's only used if redisUrl is configured.

"},{"location":"self-hosted-configuration/#redisurl","title":"redisUrl","text":"

If set, this Redis URL will be used for caching instead of the file system.

Name Value type string cli --redis-url env RENOVATE_REDIS_URL default null

If this value is set then Renovate will use Redis for its global cache instead of the local file system. The global cache is used to store lookup results (e.g. dependency versions and changelogs) between repositories and runs.

For non encrypted connections,

Example URL structure: redis://[[username]:[password]]@localhost:6379/0.

For TLS/SSL-enabled connections, use rediss prefix

Example URL structure: rediss://[[username]:[password]]@localhost:6379/0.

Renovate also supports connecting to Redis clusters as well. In order to connect to a cluster, provide the connection string using the redis+cluster or rediss+cluster schema as appropriate.

Example URL structure: redis+cluster://[[username]:[password]]@redis.cluster.local:6379/0

"},{"location":"self-hosted-configuration/#reportformatting","title":"reportFormatting","text":"

If set to true, Renovate will format the report JSON with Prettier before writing.

Name Value type boolean default false env RENOVATE_REPORT_FORMATTING

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

This option only applies when reportType is file or s3.

"},{"location":"self-hosted-configuration/#reportpath","title":"reportPath","text":"

Path to where the file should be written. In case of s3 this has to be a full S3 URI.

Name Value type string cli --report-path env RENOVATE_REPORT_PATH

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

reportPath describes the location where the report is written to.

If reportType is set to file, then set reportPath to a filepath. For example: /foo/bar.json.

If the value s3 is used in reportType, then use a S3 URI. For example: s3://bucket-name/key-name.

"},{"location":"self-hosted-configuration/#reporttype","title":"reportType","text":"

Set how, or if, reports should be generated.

Name Value type string allowedValues 
[\"logging\", \"file\", \"s3\"]\n
cli --report-type env RENOVATE_REPORT_TYPE

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Defines how the report is exposed:

"},{"location":"self-hosted-configuration/#repositories","title":"repositories","text":"

List of Repositories, or an object that contains a repository, and any Global or Repo config to target that specific repository.

Name Value type array subType string env RENOVATE_REPOSITORIES default []

The repositories array can contain a mix of repository names, and objects which can override Global and Repo configuration for a specified repository.

For instance:

module.exports = {\n  repositories: [\n    // we trust this repository's authors to run `make generate` in some cases\n    {\n      repository: 'g/r1',\n      allowedCommands: ['^make generate$'],\n    },\n    // this repository doesn't get any specific configuration\n    'g/r2',\n  ],\n};\n
"},{"location":"self-hosted-configuration/#repositorycache","title":"repositoryCache","text":"

This option decides if Renovate uses a JSON cache to speed up extractions.

Name Value type string allowedValues 
[\"disabled\", \"enabled\", \"reset\"]\n
default \"disabled\" cli --repository-cache env RENOVATE_REPOSITORY_CACHE

Set this to \"enabled\" to have Renovate maintain a JSON file cache per-repository to speed up extractions. Set to \"reset\" if you ever need to bypass the cache and have it overwritten. JSON files will be stored inside the cacheDir beside the existing file-based package cache.

"},{"location":"self-hosted-configuration/#repositorycacheforcelocal","title":"repositoryCacheForceLocal","text":"

If set to true, Renovate will persist repository cache locally after uploading to S3.

Name Value type boolean default false cli --repository-cache-force-local env RENOVATE_REPOSITORY_CACHE_FORCE_LOCAL previouslyKnownAs 
[\"RENOVATE_X_REPO_CACHE_FORCE_LOCAL\"]\n

If set to true, Renovate will persist repository cache locally after uploading to S3.

This is useful if you want to keep a local copy of the cache for debugging purposes or for faster access to the cache.

"},{"location":"self-hosted-configuration/#repositorycachetype","title":"repositoryCacheType","text":"

Set the type of renovate repository cache if repositoryCache is enabled.

Name Value type string default \"local\" cli --repository-cache-type env RENOVATE_REPOSITORY_CACHE_TYPE Set repositoryCacheType to an S3 URI to enable S3 backed repository cache
{\n  repositoryCacheType: 's3://bucket-name';\n}\n

Renovate uses the AWS SDK for JavaScript V3 to connect to the S3 instance. Therefore, Renovate supports all the authentication methods supported by the AWS SDK. Read more about the default credential provider chain for AWS SDK for JavaScript V3.

Tip

If you're storing the repository cache on Amazon S3 then you may set a folder hierarchy as part of repositoryCacheType. For example, repositoryCacheType: 's3://bucket-name/dir1/.../dirN/'.

Note

S3 repository is used as a repository cache (e.g. extracted dependencies) and not a lookup cache (e.g. available versions of dependencies). To keep the latter remotely, define Redis URL.

"},{"location":"self-hosted-configuration/#requireconfig","title":"requireConfig","text":"

Controls Renovate's behavior regarding repository config files such as renovate.json.

Name Value type string default \"required\" allowedValues 
[\"required\", \"optional\", \"ignored\"]\n
inheritConfigSupport true cli --require-config env RENOVATE_REQUIRE_CONFIG

By default, Renovate needs a Renovate config file in each repository where it runs before it will propose any dependency updates.

You can choose any of these settings:

This feature is closely related to the onboarding config option. The combinations of requireConfig and onboarding are:

onboarding=true onboarding=false requireConfig=required An onboarding PR will be created if no config file exists. If the onboarding PR is closed and there's no config file, then the repository is skipped. Repository is skipped unless a config file is added manually. requireConfig=optional An onboarding PR will be created if no config file exists. If the onboarding PR is closed and there's no config file, the repository will be processed. Repository is processed regardless of config file presence. requireConfig=ignored No onboarding PR will be created and repo will be processed while ignoring any config file present. Repository is processed, any config file is ignored."},{"location":"self-hosted-configuration/#s3endpoint","title":"s3Endpoint","text":"

If set, Renovate will use this string as the endpoint when creating the AWS S3 client instance.

Name Value type string cli --s3-endpoint env RENOVATE_S3_ENDPOINT previouslyKnownAs 
[\"RENOVATE_X_S3_ENDPOINT\"]\n
default null

If set, Renovate will use this string as the endpoint when creating the AWS S3 client instance.

"},{"location":"self-hosted-configuration/#s3pathstyle","title":"s3PathStyle","text":"

If set, Renovate will enable forcePathStyle when creating the AWS S3 client instance.

Name Value type boolean default false cli --s3-path-style env RENOVATE_S3_PATH_STYLE previouslyKnownAs 
[\"RENOVATE_X_S3_PATH_STYLE\"]\n

If set, Renovate will enable forcePathStyle when creating the AWS S3 client instance.

For example:

s3PathStyle Path off https://bucket.s3.amazonaws.com/ on https://s3.amazonaws.com/bucket/

Read the AWS S3 docs, Interface BucketEndpointInputConfig to learn more about path-style URLs.

"},{"location":"self-hosted-configuration/#secrets","title":"secrets","text":"

Object which holds secret name/value pairs.

Name Value type object mergeable true additionalProperties 
{\"type\": \"string\"}\n
cli --secrets env RENOVATE_SECRETS

Secrets may be configured by an administrator in config.js, which will then make them available for templating within repository configs. For example, to configure a GOOGLE_TOKEN to be accessible by all repositories:

module.exports = {\n  secrets: {\n    GOOGLE_TOKEN: 'abc123',\n  },\n};\n

They can also be configured per repository, e.g.

module.exports = {\n  repositories: [\n    {\n      repository: 'abc/def',\n      secrets: {\n        GOOGLE_TOKEN: 'abc123',\n      },\n    },\n  ],\n};\n

It could then be used in a repository config or preset like so:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"google.com\",\n      \"token\": \"{{ secrets.GOOGLE_TOKEN }}\"\n    }\n  ]\n}\n

Secret names must start with an upper or lower case character and can have only characters, digits, or underscores.

"},{"location":"self-hosted-configuration/#token","title":"token","text":"

Repository Auth Token.

Name Value type string cli --token env RENOVATE_TOKEN default null"},{"location":"self-hosted-configuration/#unicodeemoji","title":"unicodeEmoji","text":"

Enable or disable Unicode emoji.

Name Value type boolean default true cli --unicode-emoji env RENOVATE_UNICODE_EMOJI

If enabled emoji shortcodes are replaced with their Unicode equivalents. For example: :warning: will be replaced with \u26a0\ufe0f.

"},{"location":"self-hosted-configuration/#usecloudmetadataservices","title":"useCloudMetadataServices","text":"

If false, Renovate does not try to access cloud metadata services.

Name Value type boolean default true env RENOVATE_USE_CLOUD_METADATA_SERVICES

Some cloud providers offer services to receive metadata about the current instance, for example AWS Instance metadata or GCP VM metadata. You can control if Renovate should try to access these services with the useCloudMetadataServices config option.

Note

This should only be set via an environment variable, as it is used before Renovate initialises its global configuration.

"},{"location":"self-hosted-configuration/#useragent","title":"userAgent","text":"

Sets the user-agent header to be sent with HTTP requests. Supports {{renovateVersion}} as a template variable for the current Renovate version.

Name Value type string default \"Renovate/{{renovateVersion}} (https://github.com/renovatebot/renovate)\" supportsTemplating true cli --user-agent env RENOVATE_USER_AGENT

This option supports Renovate's template syntax

See templates for available variables and helpers.

Specifies the user-agent header sent with HTTP requests. Supports {{renovateVersion}} as a template variable for the current Renovate version.

"},{"location":"self-hosted-configuration/#username","title":"username","text":"

Username for authentication.

Name Value type string supportedPlatforms azure, bitbucket, bitbucket-server, scm-manager cli --username env RENOVATE_USERNAME default null

The only time where username is required is if using username + password credentials for the bitbucket platform. You don't need to configure username directly if you have already configured token. Renovate will use the token to discover its username on the platform, including if you're running Renovate as a GitHub App.

"},{"location":"self-hosted-configuration/#variables","title":"variables","text":"

Object which holds variable name/value pairs.

Name Value type object mergeable true additionalProperties 
{\"type\": \"string\"}\n
cli --variables env RENOVATE_VARIABLES

Variables may be configured by an administrator in config.js, which will then make them available for templating within repository configs. This config option behaves exactly like secrets, except that it won't be masked in the logs. For example, to configure a SOME_VARIABLE to be accessible by all repositories:

module.exports = {\n  variables: {\n    SOME_VARIABLE: 'abc123',\n  },\n};\n

They can also be configured per repository, e.g.

module.exports = {\n  repositories: [\n    {\n      repository: 'abc/def',\n      variables: {\n        SOME_VARIABLE: 'abc123',\n      },\n    },\n  ],\n};\n

It could then be used in a repository config or preset like so:

{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"patch\"],\n      \"addLabels\": [\"{{ variables.SOME_VARIABLE }}\"]\n    }\n  ]\n}\n
"},{"location":"self-hosted-configuration/#writediscoveredrepos","title":"writeDiscoveredRepos","text":"

Writes discovered repositories to a JSON file and then exit.

Name Value type string cli --write-discovered-repos env RENOVATE_WRITE_DISCOVERED_REPOS default null

By default, Renovate processes each repository that it finds. You can use this optional parameter so Renovate writes the discovered repositories to a JSON file and exits.

Known use cases consist, among other things, of horizontal scaling setups. See Scaling Renovate on self-hosted GitLab.

Usage: renovate --write-discovered-repos=/tmp/renovate-repos.json

[\"myOrg/myRepo\", \"myOrg/anotherRepo\"]\n
"},{"location":"self-hosted-experimental/","title":"Self-hosted experimental environment variables","text":"

The following environment variables are \"experimental\" because they:

Experimental variables which are commonly used and for which there is no external solution in sight can be converted to an official configuration option by the Renovate developers.

Use these experimental variables at your own risk. We do not follow Semantic Versioning for any experimental variables. These variables may be removed or have their behavior changed in any version. We will try to keep breakage to a minimum, but make no guarantees that an experimental variable will keep working.

"},{"location":"self-hosted-experimental/#otel_exporter_otlp_endpoint","title":"OTEL_EXPORTER_OTLP_ENDPOINT","text":"

If set, Renovate will export OpenTelemetry data to the supplied endpoint. For more information see the OpenTelemetry docs.

"},{"location":"self-hosted-experimental/#renovate_paginate_all","title":"RENOVATE_PAGINATE_ALL","text":"

If set to any value, Renovate will always paginate requests to GitHub fully, instead of stopping after 10 pages.

"},{"location":"self-hosted-experimental/#renovate_x_docker_hub_disable_label_lookup","title":"RENOVATE_X_DOCKER_HUB_DISABLE_LABEL_LOOKUP","text":"

If set to any value, Renovate will skip attempting to get release labels (e.g. gitRef, sourceUrl) from manifest annotations for https://index.docker.io.

Due to the missing label information like sourceUrl, Renovate will not be able to perform certain actions dependent on these information for the images.

This includes the following:

"},{"location":"self-hosted-experimental/#renovate_x_docker_hub_tags_disable","title":"RENOVATE_X_DOCKER_HUB_TAGS_DISABLE","text":"

If set to any value, Renovate will stop using the Docker Hub API (https://hub.docker.com) to fetch tags and instead use the normal Docker API for images pulled from https://index.docker.io.

"},{"location":"self-hosted-experimental/#renovate_x_docker_pagination_allow_cross_origin","title":"RENOVATE_X_DOCKER_PAGINATION_ALLOW_CROSS_ORIGIN","text":"

Warning

This is an explicit opt-out of a security control.

If set to any value, the docker datasource will follow paginated next links pointing to a different origin than the registry it is querying.

By default Renovate drops such cross-origin pagination links, so a malicious or compromised registry cannot redirect an authenticated request to an attacker-controlled host and exfiltrate credentials. Set this only if you trust the registry and it legitimately paginates across hosts (for example, an absolute next link pointing at a CDN or backend host).

"},{"location":"self-hosted-experimental/#renovate_x_encrypted_strict","title":"RENOVATE_X_ENCRYPTED_STRICT","text":"

If set to \"true\", a config error Issue will be raised in case repository config contains encrypted objects without any privateKey defined.

"},{"location":"self-hosted-experimental/#renovate_x_exec_gpid_handle","title":"RENOVATE_X_EXEC_GPID_HANDLE","text":"

If set, Renovate will terminate the whole process group of a terminated child process spawned by Renovate.

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_auto_approve_token","title":"RENOVATE_X_GITLAB_AUTO_APPROVE_TOKEN","text":"

If set, when autoApprove is enabled, the provided token is used to authenticate GitLab approve requests instead of the default one. This is useful in environments where a user cannot approve its own PRs.

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_auto_mergeable_check_attemps","title":"RENOVATE_X_GITLAB_AUTO_MERGEABLE_CHECK_ATTEMPS","text":"

If set to an positive integer, Renovate will use this as the number of attempts to check if a merge request on GitLab is mergeable before trying to automerge. The formula for the delay between attempts is RENOVATE_X_GITLAB_MERGE_REQUEST_DELAY * attempt * attempt milliseconds.

Default value: 5 (attempts results in max. 13.75 seconds timeout).

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_branch_status_check_attempts","title":"RENOVATE_X_GITLAB_BRANCH_STATUS_CHECK_ATTEMPTS","text":"

If set to a positive integer, Renovate will use this as the number of attempts to check branch status before trying to add a status check. The delay between attempts is RENOVATE_X_GITLAB_BRANCH_STATUS_DELAY milliseconds.

Default value: 2 (attempts results in maximum 2 seconds timeout).

!!! warning Increasing this value too much penalizes projects that do not have defined pipelines, Renovate will systematically wait RENOVATE_X_GITLAB_BRANCH_STATUS_CHECK_ATTEMPTS * RENOVATE_X_GITLAB_BRANCH_STATUS_DELAY milliseconds on these projects and slow down the Renovate analyzes.

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_branch_status_delay","title":"RENOVATE_X_GITLAB_BRANCH_STATUS_DELAY","text":"

Adjust default time (in milliseconds) given to GitLab to create pipelines for a commit pushed by Renovate.

Can be useful for slow-running, self-hosted GitLab instances that don't react fast enough for the default delay to help.

Default value: 1000 (milliseconds).

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_merge_request_delay","title":"RENOVATE_X_GITLAB_MERGE_REQUEST_DELAY","text":"

If set, Renovate will use this as a delay to proceed with an automerge.

Default value: 250 (milliseconds).

"},{"location":"self-hosted-experimental/#renovate_x_gitlab_skip_status_without_pipeline","title":"RENOVATE_X_GITLAB_SKIP_STATUS_WITHOUT_PIPELINE","text":"

If set to true value, Renovate will skip setting a branch status check on GitLab when no pipeline is found for the commit. This is useful for GitLab configurations where pipelines are only created for merge requests, not for branches. If the merge request has a merged results pipeline, Renovate sets the status check on that pipeline instead of skipping it.

"},{"location":"self-hosted-experimental/#renovate_x_hard_exit","title":"RENOVATE_X_HARD_EXIT","text":"

If set to any value, Renovate will use a \"hard\" process.exit() once all work is done, even if a sub-process is otherwise delaying Node.js from exiting. See issue 8660 for background on why this was created.

"},{"location":"self-hosted-experimental/#renovate_x_ignore_containerbase_version","title":"RENOVATE_X_IGNORE_CONTAINERBASE_VERSION","text":"

If set to any value, Renovate skips the check that the version of the Containerbase image is compatible with Renovate. An image is compatible when it has the same major version as the @containerbase/base package bundled with Renovate and the same or a newer minor or patch version.

For instance, when Renovate bundles @containerbase/base 14.46.0:

Image version Compatible Reason 14.46.0 yes same version 14.46.1 yes newer patch version 14.50.0 yes newer minor version 14.45.0 no older minor version 13.20.0 no other major version 15.0.0 no other major version

Development images are not checked. This must be set in the environment of the Renovate process, not via customEnvVariables.

"},{"location":"self-hosted-experimental/#renovate_x_ignore_re2","title":"RENOVATE_X_IGNORE_RE2","text":"

Skip initializing RE2 for regular expressions and instead use Node-native RegExp instead.

"},{"location":"self-hosted-experimental/#renovate_x_nuget_download_nupkgs","title":"RENOVATE_X_NUGET_DOWNLOAD_NUPKGS","text":"

If set to any value, Renovate will download nupkg files for determining package metadata.

"},{"location":"self-hosted-experimental/#renovate_x_nuget_pagination_allow_cross_origin","title":"RENOVATE_X_NUGET_PAGINATION_ALLOW_CROSS_ORIGIN","text":"

Warning

This is an explicit opt-out of a security control.

If set to any value, the nuget datasource will follow paginated next links pointing to a different origin than the feed it is querying.

By default Renovate drops such cross-origin pagination links, so a malicious or compromised feed cannot redirect an authenticated request to an attacker-controlled host and exfiltrate credentials. Set this only if you trust the feed and it legitimately paginates across hosts (for example, an absolute next link pointing at a backend host).

"},{"location":"self-hosted-experimental/#renovate_x_pgp_runtime","title":"RENOVATE_X_PGP_RUNTIME","text":"

Specify which PGP runtime to use for decrypting Renovate config. Allowed values are js-java, wasm-java and wasm-dotnet.

Note

js-java and wasm-dotnet are not recommended due to performance reasons. Incompatible with RENOVATE_X_USE_OPENPGP.

Default: wasm-java.

"},{"location":"self-hosted-experimental/#renovate_x_platform_version","title":"RENOVATE_X_PLATFORM_VERSION","text":"

Specify this string for Renovate to skip API checks and provide Bitbucket server, Forgejo or GitLab version directly. Particularly useful with GitLab's CI_JOB_TOKEN to authenticate Renovate or to reduce API calls for Bitbucket.

Read platform details to learn why we need the server version on GitLab.

"},{"location":"self-hosted-experimental/#renovate_x_rebase_pagination_links","title":"RENOVATE_X_REBASE_PAGINATION_LINKS","text":"

If set, Renovate will rewrite GitHub Enterprise Server's pagination responses to use the endpoint URL from the Renovate config.

Note

For the GitHub Enterprise Server platform only.

"},{"location":"self-hosted-experimental/#renovate_x_sqlite_busy_timeout","title":"RENOVATE_X_SQLITE_BUSY_TIMEOUT","text":"

Set the SQLite busy timeout in milliseconds. Defaults to 5000.

Only applies when RENOVATE_X_SQLITE_PACKAGE_CACHE is set.

"},{"location":"self-hosted-experimental/#renovate_x_sqlite_package_cache","title":"RENOVATE_X_SQLITE_PACKAGE_CACHE","text":"

If set, Renovate will use SQLite as the backend for the package cache. Don't combine with redisUrl, Redis would be preferred over SQlite.

"},{"location":"self-hosted-experimental/#renovate_x_static_repo_config_file","title":"RENOVATE_X_STATIC_REPO_CONFIG_FILE","text":"

If set to a valid path pointing to a file containing a valid Renovate configuration in JSON format, it will be applied to the repository config before resolving the actual configuration file within the repository.

Warning

If the file is missing or contains invalid configuration, the scan will be aborted.

Note

You probably shouldn\u2019t use this unless you have a very specific reason to override the repository\u2019s normal configuration resolution process.

"},{"location":"self-hosted-experimental/#renovate_x_suppress_pre_commit_warning","title":"RENOVATE_X_SUPPRESS_PRE_COMMIT_WARNING","text":"

Suppress the pre-commit support warning in PR bodies.

"},{"location":"self-hosted-experimental/#renovate_x_use_openpgp","title":"RENOVATE_X_USE_OPENPGP","text":"

Note

Incompatible with RENOVATE_X_PGP_RUNTIME.

Use openpgp instead of Bouncy Castle for PGP decryption.

"},{"location":"self-hosted-experimental/#renovate_x_yarn_proxy","title":"RENOVATE_X_YARN_PROXY","text":"

Configure global Yarn proxy settings if HTTP proxy environment variables are detected.

"},{"location":"semantic-commits/","title":"Semantic Commit messages","text":"

Renovate looks at the last 20 commit messages in the base branch to decide if the repository uses semantic commits. If there are Semantic Commits, Renovate uses an algorithm inspired by the conventional-commits-detector package to decide what convention the commit messages follow. Merge commits are ignored when looking for semantic commits, so they do not affect the result.

Renovate can only find conventional commits style (including Angular-style conventional commits), it does not \"understand\" other commit conventions.

When Renovate finds conventional commits, Renovate creates commit messages and PR titles like this:

By default, Renovate uses the chore prefix.

If you extend from config:recommended then Renovate uses the chore prefix for nearly all updates. There are some exceptions:

Be aware that the semantic commits feature does not work if you have a commitMessagePrefix configured - commitMessagePrefix will take priority.

"},{"location":"semantic-commits/#manually-enabling-or-disabling-semantic-commits","title":"Manually enabling or disabling semantic commits","text":"

You can override the default settings, and disable or enable Semantic Commits.

If you want Renovate to use Semantic Commits
{\n  \"extends\": [\":semanticCommits\"]\n}\n
If you want Renovate to stop using Semantic Commits
{\n  \"extends\": [\":semanticCommitsDisabled\"]\n}\n
"},{"location":"semantic-commits/#changing-the-semantic-commit-type","title":"Changing the Semantic Commit type","text":"

You can change the Semantic Commit type that Renovate uses. For example:

"},{"location":"semantic-commits/#changing-the-semantic-commit-scope","title":"Changing the Semantic Commit scope","text":"

You can set your own word for the scope, if you do not like the default \"deps\" scope. For example, to set the scope to \"package\", add the preset \":semanticCommitScope(package)\" to your extends array:

{\n  \"extends\": [\":semanticCommitScope(package)\"]\n}\n

To remove the Semantic Commit scope, so Renovate uses chore: instead of chore(deps):, add the \":semanticCommitScopeDisabled\" preset to your extends array:

{\n  \"extends\": [\":semanticCommitScopeDisabled\"]\n}\n
"},{"location":"string-pattern-matching/","title":"String Pattern Matching - Regex or Glob","text":"

Renovate string matching syntax for some configuration options allows you, as user, to choose between:

In cases where there are potentially multiple inputs, e.g. managers can have multiple categories, then the matcher will return true if any of them match.

"},{"location":"string-pattern-matching/#special-case-match-everything","title":"Special case: Match everything","text":"

The value * is a special case which means \"match everything\". It is not valid to combine * with any other positive or negative match.

Example of valid wildcard use
{\n  \"allowedEnv\": [\"*\"]\n}\n
Example of invalid wildcard use with additional match
{\n  \"allowedEnv\": [\"*\", \"ABC\"]\n}\n
Example of invalid wildcard use with negation
{\n  \"allowedEnv\": [\"*\", \"!ABC\"]\n}\n

In the latter case, the * can be omitted and achieve the same thing.

"},{"location":"string-pattern-matching/#regex-matching","title":"Regex matching","text":"

A valid regex pattern:

  1. Starts with / or !/
  2. Ends with / or /i
"},{"location":"string-pattern-matching/#regex-is-case-sensitive-by-default","title":"Regex is case sensitive by default","text":"

By default, regex patterns are evaluated as case sensitive. To ignore case sensitivity you must set the i flag, see the regex patterns table for an example.

"},{"location":"string-pattern-matching/#renovate-uses-re2-syntax","title":"Renovate uses re2 syntax","text":"

Renovate uses the re2 library for regex matching. re2 is different from the full regex specification, because re2 has a different syntax/support.

For the full re2 syntax, read the re2 syntax wiki page.

"},{"location":"string-pattern-matching/#example-regex-patterns","title":"Example regex patterns","text":"Pattern Regex pattern explanation /^abc/ matches any string starting with lower-case abc /^abc/i matches any string starting with abc in lower or upper case, or a mix !/^a/ matches any string not starting with a in lower case"},{"location":"string-pattern-matching/#use-regex101-to-test-your-patterns","title":"Use regex101 to test your patterns","text":"

If you want to test your patterns interactively online, we recommend regex101.com. You can use the Code Generator in the sidebar and copy the regex in the generated \"Alternative syntax\" comment into JSON.

Escape the backslashes from regex101

Before you copy/paste the regex from regex101 into your Renovate config, you must escape the backslashes (\\) first. For example: \\n\\s \u2192 \\\\n\\\\s.

"},{"location":"string-pattern-matching/#glob-matching","title":"Glob matching","text":"

If the string provided is not a regex pattern then it will be treated as a glob pattern and parsed using the minimatch library. Although glob patterns were designed originally for file name matching, many users find glob syntax easier to understand than regex so prefer it.

"},{"location":"string-pattern-matching/#glob-patterns-always-ignore-casing","title":"Glob patterns always ignore casing","text":"

Glob patterns are always evaluated with case insensitivity and you can not change this. If you need a case-sensitive pattern you must use a regex pattern.

"},{"location":"string-pattern-matching/#example-glob-patterns","title":"Example glob patterns","text":"Pattern Glob pattern explanation abc123 matches abc123 exactly, or AbC123 abc* matches abc, abc123, ABCabc, but not abc/def abc**/* matches abc/def but not abc, abcd, or abc/def/ghi, abc**/** matches abc/def and abc/def/ghi, but not abc or abcd abc{/,}** matches abc, abcd, abc/def, and abc/def/ghi

All matches above are case-insensitive, even if not shown.

"},{"location":"string-pattern-matching/#test-your-glob-patterns","title":"Test your glob patterns","text":"

If you want to test your glob patterns interactively online, we recommend Digital Ocean's glob tool.

"},{"location":"string-pattern-matching/#negative-matching","title":"Negative matching","text":"

Renovate has a specific approach to negative matching strings.

\"Positive\" matches are patterns (in glob or regex) which do not start with !. \"Negative\" matches are patterns starting with !, like !/^a/ or !b*.

For an array of patterns to match, the following must be true:

For example, the pattern [\"/^abc/\", \"!/^abcd/\", \"!/abce/\"]:

If you find yourself in a situation where you need to positive-match a string which starts with !, then you need to do so using a regular expression pattern. For example, [\"/^!abc$/\"] will positively match against the string \"!abc\".

One limitation of negative matching is when there may be multiple inputs to match against. For example, a manager may have multiple categories, such as java and docker. If you have a rule such as \"matchCategories\": [\"!docker\"] then this will return true because the java category satisfies this rule.

"},{"location":"string-pattern-matching/#usage-in-renovate-configuration-options","title":"Usage in Renovate configuration options","text":"

Renovate has evolved its approach to string pattern matching over time, but this means that existing configurations may have a mix of approaches and not be entirely consistent with each other.

The configuration options that support \"regex or glob\" syntax mention this in their documentation, and also link to this page.

"},{"location":"templates/","title":"Template fields","text":"

In order to provide flexible configuration, Renovate supports using \"templates\" for certain fields like addLabels, branchName, extractVersionTemplate, labels.

Renovate's templates use handlebars under the hood. You can recognize templates when you see strings like {{depName}} in configuration fields.

Below you can find lists of fields/values that you can use in templates. Some are configuration options passed through, while others are generated as part of Renovate's run.

logJSON and releases are only allowed in commitBody template.

"},{"location":"templates/#options-that-support-templating","title":"Options that support templating","text":"

The following configuration options accept Handlebars template syntax in their values:

"},{"location":"templates/#exposed-config-options","title":"Exposed config options","text":"

The following configuration options are passed through for templating:

"},{"location":"templates/#other-available-fields","title":"Other available fields","text":"

The following runtime values are passed through for templating:

"},{"location":"templates/#additional-handlebars-helpers","title":"Additional Handlebars helpers","text":""},{"location":"templates/#add","title":"add","text":"

Returns the sum of the fields.

{{add major 1}}

In the example above, it will add 1 to the major of current version and return the value.

"},{"location":"templates/#and","title":"and","text":"

Returns true only if all expressions are true.

{{#if (and isMajor hasReleaseNotes)}}Backwards Incompatible release! Check out the Release notes.{{/if}}

In the example above, it will only show a text if isMajor=true and hasReleaseNotes=true.

"},{"location":"templates/#containsstring","title":"containsString","text":"

Returns true if a given string is a substring.

{{#if (containsString depName 'python')}}Python{{else}}Other{{/if}}

"},{"location":"templates/#decodebase64","title":"decodeBase64","text":"

If you want to convert a Base64 value to a string, use the built-in function decodeBase64 like this:

{{{decodeBase64 body}}}

In the example above body is the base64 encoded value you want to decode.

"},{"location":"templates/#decodeuricomponent","title":"decodeURIComponent","text":"

If you want to decode a percent-encoded string, use the built-in function decodeURIComponent like this:

{{{decodeURIComponent depName}}}

In the example above depName is the string you want to decode.

Read the MDN Web Docs, decodeURIComponent() to learn more.

"},{"location":"templates/#distinct","title":"distinct","text":"

Removes duplicate elements from an array.

{{#each (distinct (lookupArray (lookupArray upgrades \"prBodyDefinitions\") \"Issue\"))}} {{{.}}}{{/each}}

"},{"location":"templates/#encodebase64","title":"encodeBase64","text":"

If you want to convert a string to Base64, use the built-in function encodeBase64 like this:

{{{encodeBase64 body}}}

In the example above body is the string you want to transform into a Base64-encoded value.

"},{"location":"templates/#encodeuricomponent","title":"encodeURIComponent","text":"

If you want to convert a string to a valid URI, use the built-in function encodeURIComponent like this:

{{{encodeURIComponent baseDir}}}

In the example above baseDir is the string you want to transform into a valid URI.

Read the MDN Web Docs, encodeURIComponent() to learn more.

"},{"location":"templates/#equals","title":"equals","text":"

Returns true if two values are equal (checks strict equality, i.e. ===).

{{#if (equals datasource 'git-refs')}}git-refs{{else}}Other{{/if}}

"},{"location":"templates/#includes","title":"includes","text":"

Returns true if an array contains a given string element.

{{#if (includes labels 'ci')}}Has CI label{{else}}No CI label{{/if}}

"},{"location":"templates/#lookuparray","title":"lookupArray","text":"

Similar to the built-in lookup helper, but performs lookups in every element of an array, instead of just one object.

For example:

{{#each (lookupArray upgrades \"prBodyDefinitions\")}} {{{Issue}}}{{/each}}

will produce the same output as:

{{#each upgrades}}{{#with prBodyDefinitions}} {{{Issue}}}{{/with}}{{/each}}.

The return value of lookupArray can be passed to other helpers - for example, to distinct.

"},{"location":"templates/#lowercase","title":"lowercase","text":"

The lowercase helper converts a given string to lower case.

{{{ lowercase depName }}}

"},{"location":"templates/#or","title":"or","text":"

Returns true if at least one expression is true.

{{#if (or isPatch isSingleVersion}}Small update, safer to merge and release.{{else}}Check out the changelog for all versions before merging!{{/if}}

"},{"location":"templates/#replace","title":"replace","text":"

The replace helper replaces all found strings matching the given regex with the replacement string. If you want to replace some characters in a string, use the built-in function replace like this:

{{{replace '[a-z]+\\\\.github\\\\.com' 'ghc' depName}}}

In the example above all matches of the regex [a-z]+\\.github\\.com will be replaced by ghc in depName.

Read the MDN Web Docs, String.prototype.replace() to learn more.

"},{"location":"templates/#split","title":"split","text":"

Splits a string into an array of substrings.

This example splits a package name by - and gets the second part: {{ lookup (split packageName '-') 1 }} An input of foo-bar-test therefore would return bar.

"},{"location":"templates/#stringtoprettyjson","title":"stringToPrettyJSON","text":"

If you want to print pretty JSON with Handlebars you can use the built-in function stringToPrettyJSON like this:

{{{stringToPrettyJSON myvar}}}

In the example above myvar is a variable/field, that has valid JSON.

"},{"location":"templates/#toarray","title":"toArray","text":"

If you want to convert elements to an array, use toArray, e.g.,

{{{ toJSON (toArray 'value1' 'value2' 'value3') }}} will render [\"value1\",\"value2\",\"value3\"].

"},{"location":"templates/#tojson","title":"toJSON","text":"

If you want to convert an object to a JSON string, you can use the built-in function toJSON like this:

{{{ toJSON upgrades }}}

"},{"location":"templates/#toobject","title":"toObject","text":"

If you want to convert key-value pairs to an object, use toObject, e.g.,

{{{ toJSON (toObject 'key1' 'value1' 'key2' 'value2') }}} will render {\"key1\":\"value1\",\"key2\":\"value2\"}.

"},{"location":"templates/#uppercase","title":"uppercase","text":"

The uppercase helper converts a given string to upper case.

{{{ uppercase depName }}}

"},{"location":"templates/#environment-variables","title":"Environment variables","text":"

By default, templates can only access a subset of environment variables like HOME or PATH. This is for security reasons.

You can reference environment variables like so:

HOME is {{env.HOME}}

If you're self-hosting Renovate, you can expose more variables with the customEnvVariables config option, which will also be available to all child processes.

See also: environment variable handling.

Warning

It is possible to use the exposeAllEnv config option to allow all environment variables in templates, but make sure to consider the security implications of giving the scripts unrestricted access to all variables.

"},{"location":"troubleshooting/","title":"Troubleshooting Renovate","text":"

Learn how to troubleshoot problems with Renovate, where to find the logging output, and how to get help if needed.

"},{"location":"troubleshooting/#getting-the-logs","title":"Getting the logs","text":"

Renovate's debug-level logs are usually enough to help troubleshoot most problems. Where you can find the logs depends on how you're running Renovate.

"},{"location":"troubleshooting/#the-mend-renovate-app","title":"The Mend Renovate App","text":"

Each pull request from the Mend Renovate App has a link to the Mend Developer Portal in the PR body text.

The text you're looking for is:

This PR was generated by Mend Renovate CLI. View the repository job log.

Select the blue text \"repository job log\" to go to the Recent jobs page in the Mend Developer Portal. Sign in with your GitHub account. Once you're logged in, you can see the logs for the Renovate jobs on your repository. You should have access to any repository which you have write access to and which has Renovate installed.

The Mend Renovate App provides logs for the most recent 2 weeks of logs, for each repository.

After selecting a recent job, you can select the debug level that you care about. For a full overview, select the DEBUG log level.

"},{"location":"troubleshooting/#self-hosted","title":"Self-hosted","text":"

The easiest way to gather logs from Renovate for any platform is to use the default logging to stdout/console. By default, Renovate will log in a human-readable format at INFO level.

For troubleshooting it's recommended to increase logging to DEBUG level by adding LOG_LEVEL=debug to your environment variables before invoking Renovate.

If your Renovate logs are being processed by a log service before you access them, you may find it better to have Renovate output logs in JSON format instead so that they can be reliably parsed and filtered. This can be achieved by adding LOG_FORMAT=json to your environment variables before invoking Renovate.

"},{"location":"troubleshooting/#log-debug-levels","title":"Log debug levels","text":"

There are different severity levels for the log output. From least severe to most severe:

To check for problems, look for WARN or ERROR logs (level 40 or 50 if in JSON format). To troubleshoot further, you usually need to look at DEBUG logs.

"},{"location":"troubleshooting/#resolving-problems-using-logs","title":"Resolving problems using logs","text":"

We recommend you follow this process:

  1. Try to narrow in on the problem area e.g. by looking for relevant branches or WARN or ERROR messages
  2. Find all relevant DEBUG or INFO messages from before and after the problem occurred
  3. Copy/paste the relevant parts of the logs into your discussion post or bug report

If you cannot fix the problem yourself after reading the logs, and reading - or searching through - our documentation, search the renovatebot/renovate discussion forum to see if somebody has asked a similar or related question.

If none of these steps have helped you, then create a new discussion post to get help from the Renovate maintainers.

Please locate the relevant parts of the logs as described earlier before asking for help or posting a bug report. Do not expect the Renovate maintainers to read through the full logs when trying to help you, as that takes a lot of time on our part. If later it turns out that the full logs are necessary, you will be asked for them then.

"},{"location":"troubleshooting/#validating-configuration-changes","title":"Validating configuration changes","text":"

Sometimes you will have to change your Renovate configuration to solve a problem. The renovate-config-validator program helps validate such configuration changes without committing them to your repository.

"},{"location":"updating-rebasing/","title":"Updating and rebasing branches","text":"

There are many situations in which Renovate must update/rebase a branch.

Here is a list of the most common cases where Renovate must update/rebase the branch:

Renovate uses its own version of \"rebasing\", which is not the same as doing a git rebase with Git. Instead, Renovate reapplies all updates into a new commit based off of the head of the base branch.

"},{"location":"updating-rebasing/#no-rebasing-if-you-have-made-edits","title":"No rebasing if you have made edits","text":"

First of all, here is the one time when Renovate won't update branches. If you push a new commit to a Renovate branch, for example to fix your code so the tests pass, then Renovate stops all updates of that branch. It is up to you to either finish the job and merge the PR, or rename it and close it so that Renovate can take over again.

Warning

Do not amend Renovate's commits, because Renovate will rebase over your amended commit. Keep your work safe and always push your own new commit to any Renovate branch.

"},{"location":"updating-rebasing/#rebasing-conflicted-prs","title":"Rebasing conflicted PRs","text":"

If new commits to the base branch - such as merging another Renovate PR - result in an open Renovate PR having merge conflicts, then Renovate will recreate (\"rebase\") any conflicted PRs. This applies both to commits to dependency files such as package.json as well as lock files such as yarn.lock. You should not ever need to resolve such conflicts manually. You can disable this functionality by configuring \"rebaseWhen\": \"never\" (not recommended).

"},{"location":"updating-rebasing/#rebasing-out-of-date-branches","title":"Rebasing out-of-date branches","text":"

There are multiple cases where Renovate will rebase its branches off the base branch every time they are out of date:

  1. If you configure \"rebaseWhen\": \"behind-base-branch\"
  2. If you use the default configuration \"rebaseWhen\": \"auto\" and the repository has a requirement that branches must be up-to-date before merging (e.g. \"Require branches to be up to date before merging\" on GitHub, or fast-forward-only settings on Bitbucket Server or GitLab)
  3. If you use the default configuration \"rebaseWhen\" : \"auto\" and configure \"automerge\" : true

In that case Renovate PRs will be rebased off the repository's base branch whenever they are behind the base branch, even if the PRs are not conflicted.

"},{"location":"updating-rebasing/#newer-dependency-versions","title":"Newer dependency versions","text":"

If an existing PR is open to upgrade dependency \"foo\" to v1.1.0 and then v1.1.1 is released, then Renovate will regenerate the branch again. This way:

"},{"location":"updating-rebasing/#manual-rebasing","title":"Manual rebasing","text":"

You can request that Renovate rebase a PR by selecting the rebase/retry checkbox on GitHub or GitLab. Or you can add a \"rebase\" label to the PR. The label name is configurable via the rebaseLabel option.

If you apply a rebase label then Renovate will regenerate its commit for the branch, even if the branch has been modified. The rebase label is useful in situations like:

"},{"location":"upgrade-best-practices/","title":"Upgrade best practices","text":"

This page explains what we (the Renovate maintainers) recommend you do to update your dependencies.

"},{"location":"upgrade-best-practices/#general-recommendations","title":"General recommendations","text":"

In general, you should:

If Renovate is too noisy for you, read the noise reduction docs.

"},{"location":"upgrade-best-practices/#use-the-configbest-practices-preset","title":"Use the config:best-practices preset","text":"

The config:recommended preset is the recommended configuration for most Renovate users. Renovate also has a config:best-practices preset that includes our upgrade best practices.

You should extend from the config:best-practices preset:

{\n  \"extends\": [\"config:best-practices\"]\n}\n

If you're using config:recommended now, replace it with config:best-practices:

- \"extends\": [\"config:recommended\"]\n+ \"extends\": [\"config:best-practices\"]\n
"},{"location":"upgrade-best-practices/#whats-in-the-configbest-practices-preset","title":"What's in the config:best-practices preset?","text":"

The config:best-practices preset has this configuration:

{\n  \"extends\": [\n    \"config:recommended\",\n    \"docker:pinDigests\",\n    \"helpers:pinGitHubActionDigests\",\n    \":configMigration\",\n    \":pinDevDependencies\",\n    \"abandonments:recommended\",\n    \"security:minimumReleaseAgeNpm\",\n    \":maintainLockFilesWeekly\"\n  ]\n}\n

The next sections explain what each part of the preset does.

"},{"location":"upgrade-best-practices/#config-migration","title":"Config migration","text":"

Renovate creates a config migration PR to replace old config option names with their new replacements. This way your configuration file and the Renovate docs always use the same terms.

You'll get config migration PRs no matter how you run Renovate: self-hosting or the Mend Renovate app.

"},{"location":"upgrade-best-practices/#extends-configrecommended","title":"Extends config:recommended","text":"

The config:recommended preset is a good base to start from. That's why we extend from it.

"},{"location":"upgrade-best-practices/#extends-dockerpindigests","title":"Extends docker:pinDigests","text":"

The Renovate docs, Docker Digest pinning section explains why you should pin your Docker containers to an exact digest.

"},{"location":"upgrade-best-practices/#extends-helperspingithubactiondigests","title":"Extends helpers:pinGitHubActionDigests","text":"

The GitHub Docs, using third-party actions recommend that you pin third-party GitHub Actions to a full-length commit SHA.

We recommend pinning all Actions. That's why the helpers:pinGitHubActionDigests preset pins all GitHub Actions.

For an in-depth explanation why you should pin your Github Actions, read the Palo Alto Networks blog post about the GitHub Actions worm.

"},{"location":"upgrade-best-practices/#extends-pindevdependencies","title":"Extends :pinDevDependencies","text":"

Pinning your development dependencies means you, and your team, are using the same versions of development tools. This makes the developer-tool side of your builds reproducible. Debugging faulty versions of your tools is easier, because you can use Git to check out different versions of the tools.

"},{"location":"upgrade-best-practices/#why-updating-often-is-easier-faster-and-safer","title":"Why updating often is easier, faster and safer","text":"

You may think that updating takes too much time. But updating regularly actually saves you time, because:

"},{"location":"upgrade-best-practices/#regular-updates-tend-to-be-small","title":"Regular updates tend to be small","text":"

Firstly, when you update regularly updates tend to be small. The update's changelogs are small, quick to read, and easy to understand. You probably only need to make changes in a few places (if at all) to merge the PR and get going again. Because you're reading the changelogs regularly, you'll get a feel for the direction of the upstream project.

"},{"location":"upgrade-best-practices/#applying-major-updates-is-easier","title":"Applying major updates is easier","text":"

Secondly, when you're current with upstream, major updates are easier. This is because you already:

"},{"location":"upgrade-best-practices/#youll-be-ready-for-cve-patches","title":"You'll be ready for CVE patches","text":"

Thirdly, you'll be ready when a upstream package releases a patch for a critical CVE. If you're current, you can review and merge Renovate's PR quickly.

When you're behind on updates, you'll have a bad time, because you must read more changelogs and make more changes before you can merge the critical patch.

"},{"location":"upgrade-best-practices/#youll-look-for-ways-to-automate-the-updates","title":"You'll look for ways to automate the updates","text":"

Finally, when you're updating often, you'll start looking for ways to automate the updates. You may start to automerge development dependencies like Prettier, or ESLint when the linter passes. Or you may decide to automerge any patch type upgrades, by using the default:automergePatch preset.

"},{"location":"upgrade-best-practices/#wait-two-weeks-before-automerging-third-party-dependencies","title":"Wait two weeks before automerging third-party dependencies","text":"

If you automerge third-party dependencies, we recommend setting minimumReleaseAge to \"14 days\". By waiting two weeks before automerging the dependencies, you give the upstream registries time to pull malicious dependencies, before Renovate merges them. If you want a third-party dependency update now, instead of waiting two weeks, you can request the update from the Dependency Dashboard.

"},{"location":"upgrade-best-practices/#use-github-pull-request-merge-queues","title":"Use GitHub Pull Request Merge Queues","text":"

You may also start using GitHub's pull request merge queues to speed up the merge process. On GitLab projects with merge trains enabled, Renovate adds automerged MRs to the merge train automatically (requires GitLab 17.11 or later).

"},{"location":"upgrade-best-practices/#starting-from-a-new-project","title":"Starting from a new project","text":"

Let's assume you're starting a new project. You created a new Git repository, installed the latest frameworks, libraries and development tools. After pushing the initial commit, you should enable and onboard Renovate.

Now you'll have to stay on the \"update often\" train.

"},{"location":"upgrade-best-practices/#project-with-one-year-old-dependencies","title":"Project with one year old dependencies","text":"

If you have a project that's a year behind on dependencies, you'll need to do some work. Let's assume that most dependencies need a patch or minor update, and at least one dependency needs a major update.

Start small, and get the patch and minor updates first. Read the changelogs for your updates. You may have to make small changes to get things working again.

When you have the latest patch and minor versions, you are ready for major updates. Start with major version updates for tools like Prettier or ESLint.

Then work on major updates for your framework or library. Take your time, read the changelogs, and make the necessary changes. Let multiple team members review your work before merging, it's easy to miss something.

Finally, update your development tools.

Now you're up to date, you should think how to make updating a regular habit.

"},{"location":"upgrade-best-practices/#project-with-five-year-old-dependencies","title":"Project with five year old dependencies","text":"

Let's assume your Dependency Dashboard lists more than 50 updates, and you have a few major version updates pending. If your project is this badly behind on updates, you have two problems:

"},{"location":"upgrade-best-practices/#focus-on-critical-updates-first","title":"Focus on critical updates first","text":"

Fix the easier problem first: getting back up to date. Update any dependencies that have critical updates for CVEs or other security related improvements.

If you're on the GitHub platform: follow the steps listed in the vulnerabilityAlerts docs to make sure Renovate is reading GitHub's Vulnerability Alerts.

You may want to enable the experimental osvVulnerabilityAlerts config option, to get OSV-based vulnerability alerts for direct dependencies. Read the osvVulnerabilityAlerts config option docs to learn more.

"},{"location":"upgrade-best-practices/#fix-blocking-updates","title":"Fix blocking updates","text":"

Next, update any dependency that's blocking another update. You may need to update dependency A before you can update dependency B or C. In that case, update dependency A first.

"},{"location":"upgrade-best-practices/#update-to-latest-minor-or-patch-of-current-version","title":"Update to latest minor or patch of current version","text":"

Then update all dependencies to their latest minor or patch version, to prepare for the major updates.

"},{"location":"upgrade-best-practices/#take-major-updates-in-sequence","title":"Take major updates in sequence","text":"

Take major updates in sequence. This way you'll read the changelogs for each major version, and learn why upstream made certain breaking changes.

Say you're on version 1 of a dependency, and the latest major version is at 4. You should update to 2, then 3 and finally 4. Avoid updating from 1 directly to 4.

Use the :separateMultipleMajorReleases preset to get separate major updates.

"},{"location":"upgrade-best-practices/#update-development-tools","title":"Update development tools","text":"

Finally update development tools like Prettier, ESLint, TSLint, Cypress, and so on.

"},{"location":"upgrade-best-practices/#improve-the-human-side","title":"Improve the human side","text":"

You're done with the technical side. Now comes the harder part, fixing the human side. There are probably a number of reasons why the project got this badly out of date.

When working on the human side, focus on the process, rules, and habits. Avoid blaming developers for not updating often.

"},{"location":"upgrade-best-practices/#why-developers-avoid-updating","title":"Why developers avoid updating","text":"

Let's assume most developers want a project that's up to date. So why are your developers avoiding updates? Some common reasons:

If updating is painful, or takes a lot of time, developers tend to avoid it. Make it easy and fast to update dependencies.

"},{"location":"upgrade-best-practices/#talk-with-your-team-about-the-update-process","title":"Talk with your team about the update process","text":"

Listen to your team, write down their problems. Then fix each problem as best as you can.

"},{"location":"upgrade-best-practices/#make-updating-easy-and-fast","title":"Make updating easy and fast","text":"

Respect your developer's time and brains:

"},{"location":"upgrade-best-practices/#ground-rules","title":"Ground rules","text":"

As a starting point:

"},{"location":"upgrade-best-practices/#how-we-use-renovate","title":"How we use Renovate","text":""},{"location":"upgrade-best-practices/#how-others-use-renovate","title":"How others use Renovate","text":"

Read the Swissquote user story to see how they use Renovate.

"},{"location":"upgrade-best-practices/#recommended-reading","title":"Recommended reading","text":"

There's a lot of good information out there, so we can only highlight a few resources.

Martin Fowler has two great resources:

The git bisect command can help you find the commit that introduced a bug, or other behavior change. Read the ProGit 2 book, section on binary search to learn more.

"},{"location":"examples/opentelemetry/","title":"OpenTelemetry","text":"

Requirements:

"},{"location":"examples/opentelemetry/#prepare-setup","title":"Prepare setup","text":"

Create a docker-compose.yaml and otel-collector-config.yml file as seen below in a folder.

docker-compose.yaml
name: renovate-otel-demo\n\nservices:\n  # Jaeger for storing traces\n  jaeger:\n    image: jaegertracing/jaeger:2.22.0\n    ports:\n      - '16686:16686' # Web UI\n      - '4317' # OTLP gRPC\n      - '4318' # OTLP HTTP\n\n  # Prometheus for storing metrics\n  prometheus:\n    image: prom/prometheus:v3.15.1\n    ports:\n      - '9090:9090' # Web UI\n      - '4318' # OTLP HTTP\n    command:\n      - --web.enable-otlp-receiver\n      # Mirror these flags from the Dockerfile, because `command` overwrites the default flags.\n      # https://github.com/prometheus/prometheus/blob/5b5fee08af4c73230b2dae35964816f7b3c29351/Dockerfile#L23-L24\n      - --config.file=/etc/prometheus/prometheus.yml\n      - --storage.tsdb.path=/prometheus\n\n  otel-collector:\n    # Using the Contrib version to access the spanmetrics connector.\n    # If you don't need the spanmetrics connector, you can use the standard version\n    image: otel/opentelemetry-collector-contrib:0.163.2\n    volumes:\n      - ./otel-collector-config.yml:/etc/otelcol-contrib/config.yaml\n    ports:\n      - '4318:4318' # OTLP HTTP ( exposed to the host )\n      - '4317:4317' # OTLP gRPC ( exposed to the host )\n    depends_on:\n      - jaeger\n      - prometheus\n
otel-collector-config.yml
receivers:\n  otlp:\n    protocols:\n      grpc:\n        endpoint: 0.0.0.0:4317\n      http:\n        endpoint: 0.0.0.0:4318\n\nexporters:\n  otlp/jaeger:\n    endpoint: jaeger:4317\n    tls:\n      insecure: true\n  otlphttp/prometheus:\n    endpoint: http://prometheus:9090/api/v1/otlp\n  debug:\n  # verbosity: normal\n\nconnectors:\n  spanmetrics:\n    histogram:\n      exponential:\n    dimensions:\n      - name: http.method\n        default: GET\n      - name: http.status_code\n      - name: http.host\n    dimensions_cache_size: 1000\n    aggregation_temporality: 'AGGREGATION_TEMPORALITY_CUMULATIVE'\n    exemplars:\n      enabled: true\n\nprocessors:\n  batch:\n\nextensions:\n  health_check:\n  pprof:\n  zpages:\n\nservice:\n  extensions: [pprof, zpages, health_check]\n  pipelines:\n    traces:\n      receivers: [otlp]\n      exporters:\n        - otlp/jaeger\n        # Send traces to connector for metrics calculation\n        - spanmetrics\n        # Enable debug exporter to see traces in the logs\n        #- debug\n      processors: [batch]\n\n    metrics:\n      receivers:\n        - otlp # Receive metrics from Renovate.\n        - spanmetrics # Receive metrics calculated by the spanmetrics connector.\n      processors: [batch]\n      exporters:\n        - otlphttp/prometheus\n        # Enable debug exporter to see metrics in the logs\n        # - debug\n

Start setup using this command inside the folder containing the files created in the earlier steps:

docker-compose up\n

This command will start:

Jaeger will be now reachable under http://localhost:16686.

"},{"location":"examples/opentelemetry/#run-renovate-with-opentelemetry","title":"Run Renovate with OpenTelemetry","text":"

To start Renovate with OpenTelemetry enabled run following command, after pointing to your config.js config file:

docker run \\\n  --rm \\\n  --network renovate-otel-demo_default \\\n  -e OTEL_EXPORTER_OTLP_ENDPOINT=http://otel-collector:4318 \\\n  -v \"/path/to/your/config.js:/usr/src/app/config.js\" \\\n  renovate/renovate:latest\n

You should now see trace_id and span_id fields in the logs.

 INFO: Repository finished (repository=org/example)\n       \"durationMs\": 5574,\n       \"trace_id\": \"f9a4c33852333fc2a0fbdc163100c987\",\n       \"span_id\": \"4ac1323eeaee\n
"},{"location":"examples/opentelemetry/#traces","title":"Traces","text":"

Open now Jaeger under http://localhost:16686.

You should now be able to pick renovate under in the field service field.

Select Find Traces to search for all Renovate traces and then select one of the found traces to open the trace view.

You should be able to see now the full trace view which shows more information about what is happening, such as HTTP requests, execution of commands or Git operations, and how long Renovate takes to process a given branch:

"},{"location":"examples/opentelemetry/#metrics","title":"Metrics","text":"

Additional to the received traces some metrics are calculated. This is achieved using the spanmetrics connector. The previously implemented setup will produce following metrics, which pushed to Prometheus:

### Example of internal spans\ntraces_span_metrics_calls_total{http_method=\"GET\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 2\ntraces_span_metrics_calls_total{http_method=\"GET\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"run\", status_code=\"STATUS_CODE_UNSET\"} 2\n\n### Example of http calls from Renovate to external services\ntraces_span_metrics_calls_total{http_host=\"api.github.com:443\", http_method=\"POST\", http_status_code=\"200\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_CLIENT\", span_name=\"POST\", status_code=\"STATUS_CODE_UNSET\"} 4\n\n\n### Example histogram metrics\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"8\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 0\n...\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"2000\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 0\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"5000\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"15000\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"10000\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_method=\"GET\", job=\"renovatebot.com/renovate\", le=\"+Inf\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 1\n\ntraces_span_metrics_duration_milliseconds_sum{http_method=\"GET\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 4190.694209\ntraces_span_metrics_duration_milliseconds_count{http_method=\"GET\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_INTERNAL\", span_name=\"repository\", status_code=\"STATUS_CODE_UNSET\"} 1\n

The spanmetrics connector creates two sets of metrics.

"},{"location":"examples/opentelemetry/#calls-metric","title":"Calls metric","text":"

At first there are the traces_span_metrics_calls_total metrics. These metrics show how often specific trace spans have been observed.

For example:

If we combine this using the PrometheusQueryLanguage ( PromQL ), we can calculate the average count of repositories each Renovate run handles.

traces_span_metrics_calls_total{span_name=\"repository\",service_name=\"renovate\"} / traces_span_metrics_calls_total{span_name=\"run\",service_name=\"renovate\"}\n

These metrics are generated for HTTP call spans too:

traces_span_metrics_calls_total{http_host=\"prometheus-community.github.io:443\", http_method=\"GET\", http_status_code=\"200\", job=\"renovatebot.com/renovate\", service_name=\"renovate\", span_kind=\"SPAN_KIND_CLIENT\", span_name=\"GET\", status_code=\"STATUS_CODE_UNSET\"} 5\n
"},{"location":"examples/opentelemetry/#latency-buckets","title":"Latency buckets","text":"

The second class of metrics exposed are the latency-focused buckets, that allow creating heatmaps. A request is added to a backed if the latency is bigger than the bucket value (le). request_duration => le

As an example if we receive a request which need 1.533s to complete get following metrics:

traces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"0.1\"} 0\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"1\"} 0\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"2\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"6\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"10\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"100\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"250\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"9.223372036854775e+12\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"+Inf\"} 1\ntraces_span_metrics_duration_milliseconds_sum{http_host=\"api.github.com:443\"} 1.533\ntraces_span_metrics_duration_milliseconds_count{http_host=\"api.github.com:443\"} 1\n

Now we have another request which this time takes 10s to complete:

traces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"0.1\"} 0\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"1\"} 0\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"2\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"6\"} 1\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"10\"} 2\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"100\"} 2\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"250\"} 2\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"9.223372036854775e+12\"} 2\ntraces_span_metrics_duration_milliseconds_bucket{http_host=\"api.github.com:443\",le=\"+Inf\"} 2\ntraces_span_metrics_duration_milliseconds_sum{http_host=\"api.github.com:443\"} 11.533\ntraces_span_metrics_duration_milliseconds_count{http_host=\"api.github.com:443\"} 2\n

More about the functionality can be found on the Prometheus page for metric types.

"},{"location":"examples/self-hosting/","title":"Self-Hosting Examples","text":"

Warning

All self-hosted Renovate instances must operate under a trust relationship with the developers of the monitored repositories. Because of this, there are security implications when running a self-hosted Renovate instance, which you must consider carefully.

Warning

Most Open Source packages are hosted on github.com, including a number of tools that Renovate may pull at run-time. GitHub greatly rate limits unauthenticated API requests, so you need to configure credentials for github.com or your deployment will get rate limited quickly. \u00a0 Read Running Renovate, GitHub.com token for changelogs to learn more.

"},{"location":"examples/self-hosting/#installing-renovate-oss-cli","title":"Installing Renovate OSS CLI","text":""},{"location":"examples/self-hosting/#npmjs","title":"npmjs","text":"
npm install -g renovate\n

Renovate does not embed npm, pnpm and yarn as its own dependencies. If you want to use these package managers to update your lockfiles, you must ensure that the correct versions are installed globally.

npm install -g yarn pnpm\n

The same goes for any other third-party binary tool like gradle or poetry - you need to make sure it is installed and the correct version before running Renovate.

"},{"location":"examples/self-hosting/#docker","title":"Docker","text":"

Renovate is available for Docker via an automated build at renovate/renovate on Docker Hub. It builds latest based on the main branch and all SemVer tags are published too.

Example of valid tags
docker run --rm renovate/renovate\ndocker run --rm renovate/renovate:44\ndocker run --rm renovate/renovate:44.133\ndocker run --rm renovate/renovate:44.133.0\n

Warning

Do not use the example tags listed above, as they will be out-of-date. Go to the renovate/renovate tags on DockerHub to grab the latest tagged release from Renovate.

If you want to configure Renovate using a config.js file then map it to /usr/src/app/config.js using Docker volumes. For example:

docker run --rm -v \"/path/to/your/config.js:/usr/src/app/config.js\" renovate/renovate\n
"},{"location":"examples/self-hosting/#kubernetes","title":"Kubernetes","text":"

Renovate's official Docker image is compatible with Kubernetes. The following is an example manifest of running Renovate against a GitHub Enterprise server.

Kubernetes manifest
apiVersion: batch/v1\nkind: CronJob\nmetadata:\n  name: renovate\nspec:\n  schedule: '@hourly'\n  concurrencyPolicy: Forbid\n  jobTemplate:\n    spec:\n      template:\n        spec:\n          containers:\n            - name: renovate\n              # Update this to the latest available and then enable Renovate on\n              # the manifest\n              image: renovate/renovate:44.133.0\n              args:\n                - user/repo\n              # Environment Variables\n              env:\n                - name: LOG_LEVEL\n                  value: debug\n              envFrom:\n                - secretRef:\n                    name: renovate-env\n          restartPolicy: Never\n

And the secret.yaml that goes with it:

secret.yaml
apiVersion: v1\nkind: Secret\nmetadata:\n  name: renovate-env\ntype: Opaque\nstringData:\n  RENOVATE_GITHUB_COM_TOKEN: 'any-personal-user-token-for-github-com-for-fetching-changelogs'\n  # You can set RENOVATE_AUTODISCOVER to true to run Renovate on all repos you have push access to\n  RENOVATE_AUTODISCOVER: 'false'\n  RENOVATE_ENDPOINT: 'https://github.company.com/api/v3'\n  RENOVATE_GIT_AUTHOR: 'Renovate <bot@renovateapp.com>'\n  RENOVATE_PLATFORM: 'github'\n  RENOVATE_TOKEN: 'your-github-enterprise-renovate-user-token'\n

A config.json file can be added to the manifest using a ConfigMap as shown in the following example (using a \"dry run\" in github.com):

Adding a config.json file to the manifest with configMap
---\napiVersion: v1\nkind: ConfigMap\nmetadata:\n  name: renovate-config\ndata:\n  config.json: |-\n    {\n      \"repositories\": [\"orgname/repo\",\"username/repo\"],\n      \"dryRun\" : \"full\"\n    }\n\n---\napiVersion: batch/v1\nkind: CronJob\nmetadata:\n  name: renovate-bot\nspec:\n  schedule: '@hourly'\n  concurrencyPolicy: Forbid\n  jobTemplate:\n    spec:\n      template:\n        spec:\n          containers:\n            - image: renovate/renovate:44.133.0\n              name: renovate-bot\n              env: # For illustration purposes, please use secrets.\n                - name: RENOVATE_PLATFORM\n                  value: 'github'\n                - name: RENOVATE_TOKEN\n                  value: 'some-token'\n                - name: RENOVATE_AUTODISCOVER\n                  value: 'false'\n                - name: RENOVATE_BASE_DIR\n                  value: '/tmp/renovate/'\n                - name: RENOVATE_CONFIG_FILE\n                  value: '/opt/renovate/config.json'\n                - name: LOG_LEVEL\n                  value: debug\n              volumeMounts:\n                - name: config-volume\n                  mountPath: /opt/renovate/\n                - name: work-volume\n                  mountPath: /tmp/renovate/\n          restartPolicy: Never\n          volumes:\n            - name: config-volume\n              configMap:\n                name: renovate-config\n            - name: work-volume\n              emptyDir: {}\n
"},{"location":"examples/self-hosting/#circleci","title":"CircleCI","text":"

Warning

The CircleCI configuration examples are for version 2 of daniel-shuy/renovate, which is outdated. Do you know how to get daniel-shuy/renovate version 3 working? Then please open a pull request to update the docs and close Renovate issue #13428.

If you are using CircleCI, you can use the third-party daniel-shuy/renovate orb to run a self-hosted instance of Renovate on CircleCI.

By default, the orb looks for the self-hosted configuration file in the project root, but you can specify another path to the configuration file with the config_file_path parameter.

Secrets should be configured using environment variables (e.g. RENOVATE_TOKEN, RENOVATE_GITHUB_COM_TOKEN).

Configure environment variables in CircleCI Project Settings. To share environment variables across projects, use CircleCI Contexts.

This runs Renovate hourly, and looks for the self-hosted config file at renovate-config.js
version: '2.1'\norbs:\n  renovate: daniel-shuy/renovate@2.2.0\nworkflows:\n  renovate:\n    jobs:\n      - renovate/self-hosted:\n          config_file_path: renovate-config.js\n    nightly:\n      triggers:\n        - schedule:\n            cron: 0 * * * *\n            filters:\n              branches:\n                only:\n                  - main\n
"},{"location":"examples/self-hosting/#renovate-config-file-validation-when-using-circleci","title":"Renovate config file validation when using CircleCI","text":"Validate your config as part of your workflow
version: '2.1'\norbs:\n  renovate: daniel-shuy/renovate@2.2.0\nworkflows:\n  lint:\n    jobs:\n      - renovate/validate-config\n
"},{"location":"examples/self-hosting/#gitlab-cicd-pipeline","title":"GitLab CI/CD pipeline","text":"

For GitLab pipelines we recommend you use the renovate-runner project on GitLab. We created some pipeline templates to help you run Renovate on pipeline schedules. You can also find the configuration steps there.

For self-hosted GitLab clone/import the renovate-runner project on GitLab project to your instance.

"},{"location":"examples/self-hosting/#filedirectory-usage","title":"File/directory usage","text":"

By default, Renovate stores all files in the renovate/ subdirectory of the operating system's temporary directory, e.g. /tmp/renovate/.

Repository data is copied or cloned into unique subdirectories under repos/, e.g. /tmp/renovate/repos/github/owner1/repo-a/.

Renovate's cache, and the caches(s) for npm, Yarn, Composer, and so on, are stored in /tmp/renovate/cache.

"},{"location":"examples/self-hosting/#overriding-the-default-directory","title":"Overriding the default directory","text":"

If you don't want to use the default tmp/renovate directory you can:

"},{"location":"examples/self-hosting/#overriding-the-default-cache-directory","title":"Overriding the default cache directory","text":"

If you want to override the cache directory then set your own value for cacheDir.

"},{"location":"examples/self-hosting/#usage","title":"Usage","text":"

The following example uses the Renovate CLI tool, which you can install by running npm i -g renovate.

If running your own Renovate deployment, then you will need a user account that Renovate will run as. We recommend you create and use a dedicated account for the bot, e.g. name it renovate-bot if on your own instance. Create and save a PAT for this account.

Create a Renovate config file, for example:

module.exports = {\n  endpoint: 'https://self-hosted.gitlab/api/v4/',\n  token: '**gitlab_token**',\n  platform: 'gitlab',\n  onboardingConfig: {\n    extends: ['config:recommended'],\n  },\n  repositories: ['username/repo', 'orgname/repo'],\n};\n

Here change the repositories to something appropriate. Also replace gitlab-token value with the one created during the previous step.

If you're running against GitHub Enterprise Server, then change the gitlab values in the example to the equivalent GitHub ones.

You can save this file as anything you want and then use the RENOVATE_CONFIG_FILE environment variable to tell Renovate where to find it.

Most people use cron to schedule when Renovate runs, usually on an hourly schedule.

Example bash script that you can point cron to
#!/bin/bash\n\nexport PATH=\"/home/user/.yarn/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:$PATH\"\nexport RENOVATE_CONFIG_FILE=\"/home/user/renovate-config.js\"\nexport RENOVATE_TOKEN=\"**some-token**\" # GitHub, GitLab, Azure DevOps\nexport RENOVATE_GITHUB_COM_TOKEN=\"**github-token**\" # Delete this if using github.com\n\n# Renovate\nrenovate\n

Save the script file, and run the script manually. Only add the script to cron after you checked it works.

Note

The GitHub.com token as an environment variable is needed to fetch changelogs that are usually hosted on github.com. You don't need to add it if you are already running Renovate against github.com, but you do need to add it if you're using GitHub Enterprise Server, GitLab, Azure DevOps, or Bitbucket.

"},{"location":"examples/self-hosting/#kubernetes-for-gitlab-using-git-over-ssh","title":"Kubernetes for GitLab, using Git over SSH","text":"

This section describes how to use a Git binary with SSH for GitLab, to avoid API shortcomings.

You need to first create a SSH key, then add the public part to GitLab (see this guide).

Then, you need to create the secret to add the SSH key, and the following config to your container:

host gitlab.com\n  HostName gitlab.com\n  StrictHostKeyChecking no\n  IdentityFile ~/.ssh/id_rsa\n  User git\n

To easily create the secret, you can do the following (see docs).

kubectl create secret generic ssh-key-secret --from-file=config=/path/to/config --from-file=id_rsa=/path/to/.ssh/id_rsa --from-file=id_rsa.pub=/path/to/.ssh/id_rsa.pub\n

It creates something like this:

apiVersion: v1\ndata:\n  config: aG9zdCBnaXRsYWIuY29tCiAgSG9zdE5hbWUgZ2l0bGFiLmNvbQogIFN0cmljdEhvc3RLZXlDaGVja2luZyBubwogIElkZW50aXR5RmlsZSB+Ly5zc2gvaWRfcnNhCiAgVXNlciBnaXQ=\n  id_rsa: <base64String>\n  id_rsa.pub: <base64String>\nkind: Secret\nmetadata:\n  name: ssh-key-secret\n  namespace: <namespace>\n

Then you need to add a Git author, and configure the mount volumes. The final configuration should look something like this:

---\napiVersion: v1\nkind: Namespace\nmetadata:\n  name: <namespace, for example renovate>\n\n---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: renovate-env\n  namespace: <namespace>\ntype: Opaque\nstringData:\n  RENOVATE_GITHUB_COM_TOKEN: 'any-personal-user-token-for-github-com-for-fetching-changelogs'\n  RENOVATE_AUTODISCOVER: 'false'\n  RENOVATE_ENDPOINT: 'https://github.company.com/api/v3'\n  RENOVATE_GIT_AUTHOR: 'Renovate <bot@renovateapp.com>'\n  RENOVATE_PLATFORM: 'github'\n  RENOVATE_TOKEN: 'your-github-enterprise-renovate-user-token'\n---\napiVersion: v1\ndata:\n  config: aG9zdCBnaXRsYWIuY29tCiAgSG9zdE5hbWUgZ2l0bGFiLmNvbQogIFN0cmljdEhvc3RLZXlDaGVja2luZyBubwogIElkZW50aXR5RmlsZSB+Ly5zc2gvaWRfcnNhCiAgVXNlciBnaXQ=\n  id_rsa: <base64String>\n  id_rsa.pub: <base64String>\nkind: Secret\nmetadata:\n  name: ssh-key-secret\n  namespace: <namespace>\n---\napiVersion: batch/v1beta1\nkind: CronJob\nmetadata:\n  name: renovate\n  namespace: <namespace>\nspec:\n  schedule: '@hourly'\n  concurrencyPolicy: Forbid\n  jobTemplate:\n    spec:\n      template:\n        spec:\n          volumes:\n            - name: ssh-key-volume\n              secret:\n                secretName: ssh-key-secret\n          containers:\n            - name: renovate\n              # Update this to the latest available and then enable Renovate on the manifest\n              image: renovate/renovate:44.133.0\n              volumeMounts:\n                - name: ssh-key-volume\n                  readOnly: true\n                  mountPath: '/home/ubuntu/.ssh'\n              args:\n                - <repository>\n              # Environment Variables\n              envFrom:\n                - secretRef:\n                    name: renovate-env\n          restartPolicy: Never\n
"},{"location":"examples/self-hosting/#logging","title":"Logging","text":"

If you're ingesting/parsing logs into another system then we recommend you set LOG_LEVEL=debug and LOG_FORMAT=json in your environment variables. Debug logging is usually needed for any debugging, while JSON format will mean that the output is parsable.

"},{"location":"examples/self-hosting/#about-the-log-level-numbers","title":"About the log level numbers","text":"

When you use LOG_LEVEL=debug and LOG_FORMAT=json, Renovate uses numbers in the level field.

The logging level output is controlled by the Bunyan logging library.

Level Meaning 10 trace 20 debug 30 info 40 warn 50 error 60 fatal"},{"location":"examples/self-hosting/#self-signed-tlsssl-certificates","title":"Self-signed TLS/SSL certificates","text":"

Renovate and invoked helper programs (like Git, or npm) use a secure TLS connection (e.g. HTTPS) to connect to remote source code and dependency hosts. If the remote hosts uses self-signed certificates or certificate authorities then Renovate must be told to trust them.

"},{"location":"examples/self-hosting/#renovate-nodejs-app","title":"Renovate Node.js app","text":"

For the main Renovate Node.js application set the environment variable NODE_EXTRA_CA_CERTS=/usr/local/share/ca-certificates/self-signed-certificate.crt. The Renovate application now trusts the self-signed-certificate.crt file. This means Renovate can safely connect to systems using that certificate or certificates signed by this certificate authority.

"},{"location":"examples/self-hosting/#helper-programs-like-git-or-npm","title":"Helper programs like Git or npm","text":"

Helper programs like Git and npm use the system trust store. For those programs to trust a self-signed certificate you must add it to the systems trust store. On Ubuntu/Debian and many Linux-based systems, this can be done by:

  1. copying the self-signed certificate (e.g. self-signed-certificate.crt) to /usr/local/share/ca-certificates/
  2. and running update-ca-certificates to update the system trust store afterwards
"},{"location":"examples/self-hosting/#renovate-docker-image","title":"Renovate Docker image","text":"

If you're using the official Renovate Docker image then we recommend you add the self-signed certificate and build your own modified Docker image.

Example of a Dockerfile that uses a self-signed certificate
FROM renovate/renovate\n\n# Changes to the certificate authority require root permissions\nUSER root\n\n# Copy and install the self signed certificate\nCOPY self-signed-certificate.crt /usr/local/share/ca-certificates/\nRUN update-ca-certificates\n\n# Change back to the Ubuntu user\nUSER 12021\n\n# OpenSSL\nENV SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crt\n
"},{"location":"examples/self-hosting/#proxy-environment-variable-configuration","title":"Proxy Environment Variable Configuration","text":"

If your environment uses an HTTP proxy configured via environment variables (HTTP_PROXY, HTTPS_PROXY, NO_PROXY, and their lowercase variants), Renovate inherits these settings and prefers the lowercase variant.

In some cases, you may need to adjust the NO_PROXY variable if Renovate encounters network or TLS errors when accessing internal or excluded domains.

Renovate uses the global-agent library to manage proxy connections.

To exclude a domain and all its subdomains, you must use a wildcard \u2014 for example:

NO_PROXY=*.example.org\n

This configuration ensures that both example.org and www.example.org are accessed directly, bypassing the proxy for Renovate.

If a tool that Renovate runs (such as git) still has proxy-related issues, note that different tools interpret NO_PROXY formats differently. See GitLab\u2019s detailed explanation for guidance on tool-specific behavior.

To debug the proxy configuration behavior you can set the environment variable ROARR_LOG=true to enable log printing to stdout.

"},{"location":"getting-started/installing-onboarding/","title":"Installing and onboarding Renovate into repositories","text":""},{"location":"getting-started/installing-onboarding/#about-the-security-and-privacy-of-installing-renovate","title":"About the security and privacy of installing Renovate","text":"

Read the Security and Permissions page to learn more about:

"},{"location":"getting-started/installing-onboarding/#repository-installation","title":"Repository installation","text":"

Renovate administrators can configure Renovate to either \"autodiscover\" installed repositories, or configure a fixed list of repository names to operate on.

If the administrator has configured a fixed list of repositories then the only way to \"install\" Renovate on a extra repository is for it to be manually added for the next run or restart.

Otherwise, the process for adding new repositories to a Renovate installation can vary:

"},{"location":"getting-started/installing-onboarding/#hosted-githubcom-app","title":"Hosted GitHub.com App","text":"

Follow these steps to install and enable the Mend Renovate App:

First, navigate to https://github.com/apps/renovate and select the Install button:

The only choice you need to make is whether to run Renovate on all repositories or on selected repositories:

Renovate will ignore any repositories that don't have known package files, as well as any forks, so you can enable Renovate for all your repositories with no problems. That said, most people run Renovate on selected repositories. Unfortunately GitHub doesn't offer a \"select all except X, Y, Z\" option, so you must select each repository where you want Renovate to run.

Once you're done selecting repositories for Renovate to run on, select the green Install button at the bottom of the page and Renovate will be enabled for those repositories and start the onboarding process.

Note

If you are using the Mend Renovate App then it has a custom behavior for forked repositories. If you choose \"All repositories\" when installing then forked repositories will be skipped by default, while if you choose \"Select repositories\" then they will be processed by Renovate even if they're a fork.

"},{"location":"getting-started/installing-onboarding/#hosted-gitlabcom-app","title":"Hosted GitLab.com App","text":"

Mend relaunched its hosted Renovate app for GitLab.com in July 2026, using a more secure architecture than the original version.

You can set it up by following these instructions when logging into the Mend Developer Platform.

We currently only support installing the app on a Group on GitLab.com. We do have plans to support User installations, but we do not have any planned timelines.

"},{"location":"getting-started/installing-onboarding/#self-hosting-on-windows","title":"Self-hosting on Windows","text":"

We recommend you set core.autocrlf = input in your Git config. You can do this by running this Git command:

git config --global core.autocrlf input\n

This prevents the carriage return \\r\\n which may confuse Renovate. You can also set the line endings in your repository by adding * text=auto eol=lf to your .gitattributes file.

"},{"location":"getting-started/installing-onboarding/#repository-onboarding","title":"Repository onboarding","text":"

Once you have enabled Renovate on a repository, you will get a \"Configure Renovate\" Pull Request looking something like this:

Note

If you self-host Renovate, and want to add the rebase/retry checkbox to Renovate's onboarding PRs: enable the onboardingRebaseCheckbox config option first.

"},{"location":"getting-started/installing-onboarding/#no-risk-onboarding","title":"No risk onboarding","text":"

Conveniently, Renovate will not make any changes to your repository or raise any further Pull Requests until after you merge the onboarding Pull Request. If there is anything about the Pull Request that you don't like or understand, take your time to read the documentation or ask questions on the discussions forum on GitHub and merge the PR only once you're satisfied with the result.

You can edit your Renovate configuration within the renovate/configure branch and Renovate will keep updating the description in the PR to match, so you can work on the config until you're satisfied with the results.

If you wish to opt-out of having Renovate run for your repo, simply close the onboarding Pull Request without merging it. This action is reversible - you can re-request an onboarding PR by renaming the (closed) onboarding PR, or you can commit a Renovate configuration file to your default branch to manually onboard.

"},{"location":"getting-started/installing-onboarding/#check-for-warnings","title":"Check for warnings","text":"

If you have any Warnings or Errors listed, see if you need or want to make any changes to fix them. Warnings and errors should be fixed on the base branch (e.g. main) so that Renovate can recreate its Configure Renovate PR on its next cycle.

"},{"location":"getting-started/installing-onboarding/#configuration-location","title":"Configuration location","text":"

The \"Configure Renovate\" PR will include a renovate.json file in the root directory, with suggested default settings. If you don't want a renovate.json file in your repository you can use one of the following files instead:

Or in a custom file present within the configFileNames. Renovate first checks all the files in the configFileNames array before checking from the above file list.

"},{"location":"getting-started/installing-onboarding/#packagejson","title":"package.json","text":"

Warning

This approach has been deprecated and will be removed in a future release.

You can add the same settings to a \"renovate\" section in your package.json file instead. The package.json file must be located at the root of your repository. This is handy if you are already using a package.json file anyway, e.g. when you're working on a JavaScript project. The configuration in your package.json will apply to the whole project (this includes other, nested package.json files).

"},{"location":"getting-started/installing-onboarding/#customized-defaults","title":"Customized defaults","text":"

Renovate provides a renovate.json file, with default settings that will work for most cases. Sometimes Renovate detects that an override to these defaults is needed, and will add this override automatically, such as:

"},{"location":"getting-started/installing-onboarding/#common-overrides","title":"Common overrides","text":"

Please check the docs on this website for an exhaustive Configuration Reference. To help you get started, here are some of the most commonly changed (overridden) configuration settings:

Renovate will update your PR description each time it finds changes.

"},{"location":"getting-started/installing-onboarding/#merge","title":"Merge","text":"

Once you're done checking and configuring in your Configure Renovate PR, it's time to merge it to enable the real Pull Requests to begin.

"},{"location":"getting-started/installing-onboarding/#repository-re-configuration","title":"Repository re-configuration","text":"

There will be times when you need to change your Renovate config. There are two recommended approaches:

"},{"location":"getting-started/installing-onboarding/#reconfigure-via-pr","title":"Reconfigure via PR","text":"

If you want to make config edits directly, follow these steps:

  1. Create a new branch named renovate/reconfigure
  2. Edit your Renovate configuration file
  3. Create a pull request from the renovate/reconfigure branch
  4. Run renovate on your repository(if self-hosted), or wait for the hosted app to process the changes
  5. Renovate will comment on your PR, outlining the expected changes from your modified configuration
  6. You can continue to edit the configuration file in the same PR, and Renovate will update its comment accordingly
  7. If you only want to validate your configuration changes, check out: Validate your config

Note

The reconfigure branch is only meant for changes to your Renovate configuration. Renovate reads the config from the reconfigure branch, but extracts dependencies from your default branch. Any other file changes in the reconfigure branch, like new package files or dependency versions, are not extracted and do not show in the comment.

"},{"location":"getting-started/installing-onboarding/#nuke-config-and-re-onboard","title":"Nuke config and re-onboard","text":"

Perhaps you really liked the interactive onboarding PR and want to use it again. You can follow the steps below to nuke the config and get a new PR. Any existing Renovate PRs will be closed after you've completed these steps.

  1. Find your original Configure Renovate PR
  2. Rename the original PR to something else, e.g. Configure Renovate - old
  3. Remove the current Renovate configuration file (e.g. renovate.json) from your mainline branch

Following these steps will trick Renovate into thinking that your repository was never onboarded, and will trigger a new \"Configure Renovate\" PR. If you're using the Mend Renovate App and you don't get a new onboarding PR within a few hours, then please create a Discussions post to request staff trigger it manually.

"},{"location":"getting-started/private-packages/","title":"Private package support","text":"

It's a very common requirement to be able to support private module/dependency lookups. This page describes Renovate's approach to authentication.

First, a quick note on terminology:

"},{"location":"getting-started/private-packages/#when-does-renovate-need-credentials","title":"When does Renovate need credentials?","text":"

By default, the only credentials Renovate has are those for the \"platform\", i.e. GitHub, GitLab, etc. If the token used has sufficient permissions, this will enable Renovate to lookup dependencies located in alternative repositories on the same host or any hosted on any embedded package registry on the same host.

It's also quite common to need to look up packages on other protected hosts, including npmjs, Docker Hub, or private registries like Nexus or Artifactory. Any time you need Renovate to access such registries with credentials then you will need to provision them as part of your config.

There are four times in Renovate's behavior when it may need credentials:

Note

If you self-host Renovate, and have a self-hosted registry which doesn't require authentication to access, then such modules/packages are not considered \"private\" to Renovate.

"},{"location":"getting-started/private-packages/#private-config-presets","title":"Private Config Presets","text":"

Renovate supports config presets, including those which are private.

Although npm presets were the first type supported, they are now deprecated and it is recommend that all users migrate to git-hosted \"local\" presets instead. However if you do still use them, private modules should work if you configure hostRules (recommended) or npmrc including token credentials in your global self-hosted config. It is strongly recommended not to use private modules on a private registry and a warning will be logged if that is found. Credentials stored on disk (e.g. in ~/.npmrc) are no longer supported.

The recommended way of using local presets is to configure them using \"local\" presets, e.g. \"extends\": [\"local>myorg/renovate-config\"], and ensure that the platform token has access to that repo.

It's not recommended that you use a private repository to host your config while then extending it from a public repository. If your preset doesn't have secrets then you should make it public, while if it does have secrets then it's better to split your preset between a public one which all repos extend, and a private one with secrets which only other private repos extend.

In summary, the recommended approach to private presets is:

"},{"location":"getting-started/private-packages/#dependency-version-lookups","title":"Dependency Version Lookups","text":"

Whenever Renovate detects that a project uses a particular dependency, it tries to look up that dependency to see if any new versions exist. If such a package is private, then Renovate must be configured with the relevant credentials. Renovate does not use any package managers for this step and performs all HTTP(S) lookups itself, including insertion of authentication headers.

Configuring Renovate with credentials requires hostRules. Each host rule consists of a hostType value and/or a way to match against hosts using matchHost.

hostType is not particularly important at this step unless you have different credentials for the same host, but it is sometimes useful in later steps so is good to include if you can. It can be either a \"platform\" name (e.g. github, azure, etc) or a \"datasource\" name (e.g. npm, maven, github-tags, etc).

If you want to apply credentials only for a nested path within a host then write matchHost as a base URL like https://registry.company.com/nested/path/. If the same credentials apply to all paths on a host and not on any subdomains of it then configure matchHost with a protocol like https://registry.company.com. Finally, to apply credentials to all hosts within the domain, use a matchHost value with no https:// prefix, e.g. company.com or registry.company.com, both of which would apply to a host like beta.registry.company.com.

In addition to the above options to match against a host, you need to add the credentials. Typically they are either token, or username + password. Other credential terms are not supported yet.

Example host rules
{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"registry.npmjs.org\",\n      \"token\": \"abc123\"\n    },\n    {\n      \"matchHost\": \"https://registry.company.com/pypi-simple/\",\n      \"username\": \"engineering\",\n      \"password\": \"abc123\"\n    }\n  ]\n}\n

Renovate applies these hostRules to every HTTP(s) request which is sent, so they are largely independent of any platform or datasource logic. With hostRules in place, private package lookups should all work.

"},{"location":"getting-started/private-packages/#github-and-enterprise-repo-scoped-credentials","title":"GitHub (and Enterprise) repo scoped credentials","text":"

If you need to use different credentials for a specific GitHub repo, then you can configure hostRules like one of the following:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://api.github.com/repos/org/repo\",\n      \"token\": \"abc123\"\n    },\n    {\n      \"matchHost\": \"https://github.domain.com/api/v3/repos/org/repo\",\n      \"token\": \"abc123\"\n    }\n  ]\n}\n

Renovate will use those credentials for all requests to org/repo.

"},{"location":"getting-started/private-packages/#example-for-gomod","title":"Example for gomod","text":"

Here's an example for gomod with private github.com repos. Assume this config is used on the github.com/some-other-org repo:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"dependencyDashboard\": true,\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://gitlab.com\",\n      \"token\": \"glpat-token_for_different_git_platform\",\n      \"hostType\": \"gitlab\"\n    },\n    {\n      \"matchHost\": \"https://github.com/some-org\",\n      \"token\": \"ghp_token_for_different_org\",\n      \"hostType\": \"go\"\n    },\n    {\n      \"matchHost\": \"https://api.github.com/repos/some-org\",\n      \"token\": \"ghp_token_for_different_org\",\n      \"hostType\": \"github\"\n    }\n  ],\n  \"customEnvVariables\": {\n    \"GOPRIVATE\": \"github.com/some-org,github.com/some-other-org,gitlab.com/some-org\",\n    \"GONOSUMDB\": \"github.com/some-org,github.com/some-other-org,gitlab.com/some-org\",\n    \"GONOPROXY\": \"github.com/some-org,github.com/some-other-org,gitlab.com/some-org\"\n  },\n  \"postUpdateOptions\": [\"gomodTidy\"]\n}\n

If you use private Go modules hosted on GitLab, read private Go modules hosted on GitLab to learn how to authenticate the module resolution requests.

"},{"location":"getting-started/private-packages/#looking-up-changelogs","title":"Looking up changelogs","text":"

When Renovate creates Pull Requests, its default behavior is to locate and embed release notes/changelogs of packages. These release notes are fetched from the source repository of packages and not from the registries themselves, so if they are private then they will require different credentials.

When it comes to open source, most packages host their source on github.com in public repositories. GitHub greatly rate limits unauthenticated API requests, so you need to configure credentials for github.com or your deployment will get rate limited quickly. It can be confusing for people who host their own source code privately to be asked to configure a github.com token but without it changelogs for most open source packages will be blocked.

Currently the preferred way to configure github.com credentials for self-hosted Renovate is:

Note

GITHUB_COM_TOKEN is still parsed and takes precedence over RENOVATE_GITHUB_COM_TOKEN, but is considered deprecated and will be removed in a future major update.

"},{"location":"getting-started/private-packages/#package-manager-credentials-for-artifact-updating","title":"Package Manager Credentials for Artifact Updating","text":"

In Renovate terminology, \"artifacts\" includes lock files, checksum files, and vendored dependencies. One way of understanding artifacts is: \"everything else that needs to be updated when the dependency version changes\".

Not all package managers supported by Renovate require artifact updating, because not all use lock or checksum files. But when such files need updating, Renovate does so by using the package managers themselves instead of trying to \"reverse engineer\" each package manager's file formats and behavior. Importantly, such package managers are run via shell commands and do not understand Renovate's hostRules objects, so Renovate needs to reformat the credentials into formats (such as environment variables or configuration files) which the package manager understands.

Because of this need to convert hostRules credentials into a format which package managers understand, sometimes artifact updating can fail due to missing credentials. Sometimes this can be resolved by changing Renovate configuration, but other times it may be due to a feature gap. The following details the most common/popular manager artifacts updating and how credentials are passed:

"},{"location":"getting-started/private-packages/#bundler","title":"bundler","text":"

hostRules with hostType=rubygems are converted into environment variables which Bundler supports.

"},{"location":"getting-started/private-packages/#composer","title":"composer","text":"

Any hostRules token for github.com or gitlab.com are found and written out to COMPOSER_AUTH in env for Composer to parse. Any hostRules with hostType=packagist are also included. For dependencies on github.com without a Packagist server: use a Personal Access Token for hostRule with hostType=git-tags, do not use an application token. Avoid adding a hostRule with hostType=github because:

The repository in composer.json should have the vcs type with a https URL. For example:

{\n  \"repositories\": [\n    {\n      \"type\": \"vcs\",\n      \"url\": \"https://github.com/organization/private-repository\"\n    }\n  ]\n}\n
"},{"location":"getting-started/private-packages/#gomod","title":"gomod","text":"

If a github.com token is found in hostRules, then it is written out to local GIT_CONFIG_ variables prior to running go commands. The environment variables used are: GIT_CONFIG_KEY_0=url.https://x-access-token:${token}@github.com/.insteadOf GIT_CONFIG_VALUE_0=https://github.com/ GIT_CONFIG_COUNT=1.

For git hosts that Renovate doesn't recognise, a token-only host rule is sent as the username without a password. Some git and curl versions don't send such credentials again after a redirect, so configure username and password instead.

"},{"location":"getting-started/private-packages/#helm","title":"helm","text":"

Maybe you're running your own ChartMuseum server to host your private Helm Charts. This is how you connect to a private Helm repository:

Connecting to a private Helm repository
module.exports = {\n  hostRules: [\n    {\n      matchHost: 'your.host.io',\n      hostType: 'helm',\n      username: '<your-username>',\n      password: process.env.SELF_HOSTED_HELM_CHARTS_PASSWORD,\n    },\n  ],\n};\n

If you need to configure per-repository credentials then you can also configure the above within a repository's Renovate config (e.g. renovate.json).

"},{"location":"getting-started/private-packages/#npm","title":"npm","text":"

The recommended approaches in order of preference are:

  1. Self-hosted hostRules: Configure a hostRules entry in your self-hosted config.js with the hostType, matchHost and token specified
  2. The Mend Renovate App with private modules from npmjs.org: Add an encrypted npmToken to your Renovate config
  3. The Mend Renovate App with a private registry: Add an plaintext npmrc plus an encrypted npmToken in config

These approaches are described in full below.

"},{"location":"getting-started/private-packages/#add-hostrule-to-self-hosted-config","title":"Add hostRule to self-hosted config","text":"

Define hostRules like this:

module.exports = {\n  hostRules: [\n    {\n      hostType: 'npm',\n      matchHost: 'registry.npmjs.org',\n      token: process.env.NPMJS_TOKEN,\n    },\n    {\n      hostType: 'npm',\n      matchHost:\n        'https://pkgs.dev.azure.com/{organization}/{project}/_packaging/{feed}/npm/registry/',\n      username: 'VssSessionToken',\n      password: process.env.AZURE_NPM_TOKEN,\n    },\n    {\n      // https://www.jfrog.com/confluence/display/JFROG/npm+Registry\n      // Will be passed as `//artifactory.my-company.com/artifactory/api/npm/npm:_auth=<TOKEN>` to `.npmrc`\n      hostType: 'npm',\n      matchHost: 'https://artifactory.my-company.com/artifactory/api/npm/npm/',\n      token: process.env.ARTIFACTORY_NPM_TOKEN,\n      authType: 'Basic',\n    },\n  ],\n};\n

Tip

Remember to put a trailing slash at the end of your matchHost URL.

"},{"location":"getting-started/private-packages/#add-npmrc-string-to-renovate-config","title":"Add npmrc string to Renovate config","text":"

You can add an .npmrc authentication line to your Renovate config under the field npmrc. e.g. a renovate.json might look like this:

{\n  \"npmrc\": \"//some.registry.com/:_authToken=abcdefghi-1234-jklmno-aac6-12345567889\"\n}\n

If configured like this, Renovate will use this to authenticate with npm and will ignore any .npmrc files(s) it finds checked into the repository. If you wish for the values in your config.npmrc to be merged (prepended) with any values found in repos then also set config.npmrcMerge=true. This merge approach is similar to how npm itself behaves if .npmrc is found in both the user home directory as well as a project.

"},{"location":"getting-started/private-packages/#add-npmtoken-to-renovate-config","title":"Add npmToken to Renovate config","text":"

If you are using the main npmjs registry then you can configure only the npmToken instead:

{\n  \"npmToken\": \"abcdefghi-1234-jklmno-aac6-12345567889\"\n}\n
"},{"location":"getting-started/private-packages/#add-an-encrypted-npm-token-to-renovate-config","title":"Add an encrypted npm token to Renovate config","text":"

If you don't want all users of the repository to see the plaintext token, you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it.

Go to https://app.renovatebot.com/encrypt, paste in your npm token, select \"Encrypt\", then copy the encrypted result.

Paste the encrypted result inside an encrypted object like this:

{\n  \"encrypted\": {\n    \"npmToken\": \"xxT19RIdhAh09lkhdrK39HzKNBn3etoLZAwHdeJ25cX+5y52a9kAC7flXmdw5JrkciN08aQuRNqDaKxp53IVptB5AYOnQPrt8MCT+x0zHgp4A1zv1QOV84I6uugdWpFSjPUkmLGMgULudEZJMlY/dAn/IVwf/IImqwazY8eHyJAA4vyUqKkL9SXzHjvS+OBonQ/9/AHYYKmDJwT8vLSRCKrXxJCdUfH7ZnikZbFqjnURJ9nGUHP44rlYJ7PFl05RZ+X5WuZG/A27S5LuBvguyQGcw8A2AZilHSDta9S/4eG6kb22jX87jXTrT6orUkxh2WHI/xvNUEout0gxwWMDkA==\"\n  }\n}\n

If you have no .npmrc file then Renovate creates one for you, pointing to the default npmjs registry. If instead you use an alternative registry or need an .npmrc file for some other reason, you should configure it too and substitute the npm token with ${NPM_TOKEN} for it to be replaced. e.g.

{\n  \"encrypted\": {\n    \"npmToken\": \"xxT19RIdhAh09lkhdrK39HzKNBn3etoLZAwHdeJ25cX+5y52a9kAC7flXmdw5JrkciN08aQuRNqDaKxp53IVptB5AYOnQPrt8MCT+x0zHgp4A1zv1QOV84I6uugdWpFSjPUkmLGMgULudEZJMlY/dAn/IVwf/IImqwazY8eHyJAA4vyUqKkL9SXzHjvS+OBonQ/9/AHYYKmDJwT8vLSRCKrXxJCdUfH7ZnikZbFqjnURJ9nGUHP44rlYJ7PFl05RZ+X5WuZG/A27S5LuBvguyQGcw8A2AZilHSDta9S/4eG6kb22jX87jXTrT6orUkxh2WHI/xvNUEout0gxwWMDkA==\"\n  },\n  \"npmrc\": \"registry=https://my.custom.registry/npm\\n//my.custom.registry/npm:_authToken=${NPM_TOKEN}\"\n}\n

Renovate will then use the following logic:

  1. If no npmrc string is present in config then one will be created with the _authToken pointing to the default npmjs registry
  2. If an npmrc string is present and has a ${NPM_TOKEN} then that placeholder will be replaced with the decrypted token
  3. If an npmrc string is present but doesn't have a ${NPM_TOKEN} then the file will have _authToken=<token> appended to it
"},{"location":"getting-started/private-packages/#encrypted-entire-npmrc-file-into-config","title":"Encrypted entire .npmrc file into config","text":"

Copy the entire .npmrc, replace newlines with \\n characters , and then try encrypting it at https://app.renovatebot.com/encrypt.

You will then get an encrypted string that you can substitute into your renovate.json instead. The end-result looks like this:

{\n  \"encrypted\": {\n    \"npmrc\": \"WOTWu+jliBtXYz3CU2eI7dDyMIvSJKS2N5PEHZmLB3XKT3vLaaYTGCU6m92Q9FgdaM/q2wLYun2JrTP4GPaW8eGZ3iiG1cm7lgOR5xPnkCzz0DUmSf6Cc/6geeVeSFdJ0zqlEAhdNMyJ4pUW6iQxC3WJKgM/ADvFtme077Acvc0fhCXv0XvbNSbtUwHF/gD6OJ0r2qlIzUMGJk/eI254xo5SwWVctc1iZS9LW+L0/CKjqhWh4SbyglP3lKE5shg3q7mzWDZepa/nJmAnNmXdoVO2aPPeQCG3BKqCtCfvLUUU/0LvnJ2SbQ1obyzL7vhh2OF/VsATS5cxbHvoX/hxWQ==\"\n  }\n}\n
"},{"location":"getting-started/private-packages/#automatically-authenticate-for-npm-package-stored-in-private-github-npm-repository","title":"Automatically authenticate for npm package stored in private GitHub npm repository","text":"
{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://npm.pkg.github.com/\",\n      \"hostType\": \"npm\",\n      \"encrypted\": {\n        \"token\": \"<Encrypted PAT Token>\"\n      }\n    }\n  ],\n  \"npmrc\": \"@organizationName:registry=https://npm.pkg.github.com/\"\n}\n
"},{"location":"getting-started/private-packages/#yarn-2","title":"Yarn 2+","text":"

Renovate doesn't support reading npmRegistries and npmScopes from .yarnrc.yml, so hostRules (or npmToken) and npmrc should be configured like above. Renovate updates npmRegistries in .yarnrc.yml with resolved hostRules before running Yarn. For Renovate to overwrite existing npmRegistries entry, the key should match the matchHost minus the protocol (http: or https:) plus the trailing slash.

For example, the Renovate configuration:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://npm.pkg.github.com/\",\n      \"hostType\": \"npm\",\n      \"encrypted\": {\n        \"token\": \"<Encrypted PAT Token>\"\n      }\n    }\n  ]\n}\n

will update .yarnrc.yml as following:

If no registry currently set

npmRegistries:\n  //npm.pkg.github.com/:\n    npmAuthToken: <Decrypted PAT Token>\n

If current registry key has protocol set:

npmRegistries:\n  https://npm.pkg.github.com:\n    npmAuthToken: <Decrypted PAT Token>\n
"},{"location":"getting-started/private-packages/#pnpm","title":"pnpm","text":"

Renovate reads private registries declared in pnpm-workspace.yaml (supported by pnpm v11+): the top-level registry key and the registries map, including its default key and scoped keys like @my-org.

registry: https://registry.npmjs.org/\nregistries:\n  default: https://registry.npmjs.org/\n  '@my-org': https://private.example.com/\n

These registries are applied to dependencies in member package.json files as well as to catalog/catalogs and overrides entries in the workspace file itself. Registries set this way take precedence over registry=/@scope:registry= lines in .npmrc.

Renovate does not read namedRegistries. Authentication is still read from .npmrc/hostRules (pnpm does not store auth in pnpm-workspace.yaml), so configure tokens as described above. Registry values that contain a ${...} placeholder are ignored, matching pnpm's own behavior since v11.5.3.

"},{"location":"getting-started/private-packages/#maven","title":"maven","text":"

GitLab package registry can be authorized using Authorization: Bearer <token>. In GitLab Pipelines authorization can be achieved using following config:

hostRules: [\n  {\n    hostType: 'maven',\n    matchHost: 'https://gitlab.host.com/api/v4',\n    token: process.env.CI_JOB_TOKEN,\n  },\n];\n
"},{"location":"getting-started/private-packages/#nuget","title":"nuget","text":"

For each known NuGet registry, Renovate searches for hostRules with hostType=nuget and matching host. For those found, a command like the following is run: dotnet nuget add source ${registryInfo.feedUrl} --configfile ${nugetConfigFile} --username ${username} --password ${password} --store-password-in-clear-text.

hostRules: [\n  {\n    matchHost: 'https://pkgs.dev.azure.com/<org>/',\n    hostType: 'nuget',\n    username: 'user', // doesn't matter for azure\n    password: '<PAT>',\n  },\n];\n
"},{"location":"getting-started/private-packages/#pip","title":"pip","text":"

If a requirements.txt file has an index-url then Renovate follows that link, instead of following any link set in the registryUrls array. To override the URL found in requirements.txt, you must create a custom packageRules setting. This is because packageRules are applied after package file extraction.

For example:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"pip_requirements\"],\n      \"registryUrls\": [\"https://docker.mycompany.domain\"]\n    }\n  ]\n}\n
"},{"location":"getting-started/private-packages/#pipenv","title":"pipenv","text":"

If a Pipfile contains a source with USERNAME or PASSWORD environment variables and there is a hostRules entry with a matching host plus username and password fields, then these variables would be passed to pipenv lock.

For example:

[[source]]\nurl = \"https://$USERNAME:${PASSWORD}@mypypi.example.com/simple\"\nverify_ssl = true\nname = \"pypi\"\n
"},{"location":"getting-started/private-packages/#pip-compile","title":"pip-compile","text":"

The pip-compile manager can extract these directives from the input file given to Renovate:

Renovate matches those URLs with credentials from matching hostRules blocks in the Renovate configuration. Then Renovate passes the information to pip-compile via environment variables.

Put directives in the .in file, avoid the lockfile

You must put the --[extra-]index-url directive(s) in the .in file, for pip-compile to use during Renovate jobs. Do not put the directive(s) in the lockfile, as this is not supported.

requirements.in
--extra-index-url https://pypi.my.domain/simple\n\nprivate-package==1.2.3\n
{\n  \"pip-compile\": {\n    \"managerFilePatterns\": [\"requirements.txt\"]\n  },\n  \"hostRules\": [\n    {\n      \"matchHost\": \"pypi.my.domain\",\n      \"username\": \"myuser\",\n      \"password\": \"mypassword\"\n    }\n  ]\n}\n
"},{"location":"getting-started/private-packages/#packages-that-renovate-needs","title":"Packages that Renovate needs","text":"

Renovate relies on pip's integration with the Python keyring package along with the keyrings.envvars backend for this.

"},{"location":"getting-started/private-packages/#self-hosting-renovate","title":"Self-hosting Renovate","text":"

This section only applies to users who self-host Renovate. If you self-host and use Containerbase, or our Docker sidecar container, then Renovate can already access the packages it needs.

But if you are self-hosting Renovate and:

Then you must install the Python keyring package and the keyrings.envvars package into your self-hosted environment.

"},{"location":"getting-started/private-packages/#poetry","title":"poetry","text":"

For every Poetry source, a hostRules search is done and then any found credentials are added to env like POETRY_HTTP_BASIC_X_USERNAME and POETRY_HTTP_BASIC_X_PASSWORD, where X represents the normalized name of the source in pyproject.toml.

module.exports = {\n  hostRules: [\n    {\n      matchHost: 'pypi.example.com',\n      hostType: 'pypi',\n      username: process.env.PYPI_USERNAME,\n      password: process.env.PYPI_PASSWORD,\n    },\n  ],\n};\n

If you're self-hosting Renovate via the GitLab Runner and want to access packages from private GitLab registries, you can use the GitLab CI job token for authentication:

module.exports = {\n  hostRules: [\n    {\n      matchHost: 'gitlab.example.com',\n      hostType: 'pypi',\n      username: 'gitlab-ci-token',\n      password: process.env.CI_JOB_TOKEN,\n    },\n  ],\n};\n
"},{"location":"getting-started/private-packages/#automatic-hostrules-credentials-for-platform-hosted-registries","title":"Automatic hostRules credentials for platform-hosted registries","text":""},{"location":"getting-started/private-packages/#github-packages","title":"GitHub Packages","text":"

For GitHub Packages, Renovate will automatically provision hostRules for both ghcr.io (containers) and *.pkg.github.com (maven, npm, nuget, rubygems) using the GitHub platform token. This means that any private packages hosted on GitHub will be automatically authenticated if they are accessible using the same token by Renovate.

If you wish to override this authentication by providing a different token, then your rule must be at least as specific as the automatic rule that Renovate generates. For example:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"npm.pkg.github.com\",\n      \"hostType\": \"npm\",\n      \"token\": \"some-personal-access-token\"\n    }\n  ]\n}\n
"},{"location":"getting-started/private-packages/#encryption-and-the-mend-renovate-app","title":"Encryption and the Mend Renovate App","text":"

Many users use the Mend Renovate App, which is hosted by Mend. If you are a user of this app, and have private modules, then the following is applicable.

"},{"location":"getting-started/private-packages/#private-presets-with-public-repositories","title":"Private presets with public repositories","text":"

If you have a preset in a private repo but reference (\"extend\") it from a public repository then it won't work. This is because public repositories are provided with a token scoped to only that particular repository, and not for all repositories within the organization. This is a security measure so that if a the token is accidentally leaked publicly, the damage is limited to the public repository it leaked to and not to every repository within the organization.

The solution to this is that you should break your presets into public and private ones, and reference only the public ones from public repositories.

"},{"location":"getting-started/private-packages/#encrypting-secrets","title":"Encrypting secrets","text":"

It is strongly recommended that you avoid committing secrets to repositories, including private ones, and this includes secrets needed by Renovate to access private modules. The preferred approach to secrets is that the administrator configures them as hostRules which are then applied to all repositories which Renovate accesses.

Store secrets for your Mend-hosted app via the web UI

Mend no longer supports putting encrypted secrets in the Renovate config file on your repository. Going forward, all secrets must be stored in the App settings via the web UI. If you have encrypted secrets in your Renovate config, you must migrate them to the web UI. Read Migrating Secrets from Repo Config to App Settings to learn how.

If you need to provide credentials to the Mend Renovate App, please do this:

  1. Add each secret string in the Credentials section of Organisation or Repository settings in the web UI at http://developer.mend.io.

  2. Reference secrets inside your Renovate config files with notation: {{ secrets.YOUR_SECRET }}.

    {\n  \"hostRules\": [\n    {\n      \"matchHost\": \"github.com\",\n      \"token\": \"{{ secrets.RENOVATE_GITHUB_COM_TOKEN }}\"\n    }\n  ]\n}\n

For more details, see Using Secrets with Mend Cloud Apps.

"},{"location":"getting-started/private-packages/#access-to-github-actions-secrets","title":"Access to GitHub Actions Secrets","text":"

The Mend Renovate App does not run using GitHub Actions, but such secrets would be a bad fit for the app anyway for the following reasons:

"},{"location":"getting-started/private-packages/#admin-config-vs-userrepository-config-for-self-hosted-users","title":"Admin config vs User/Repository config for Self-hosted users","text":"

\"Admin config\" refers to the config which the Renovate administrator provides at startup, e.g. using environment variables, CLI parameters, or the config.js configuration file. User/Repository config refers to the in-repository config file which defaults to renovate.json but has a large number of alternative filenames supported.

If there is a need to supply custom rules for certain repository, it can still be done using the config.js file and the repositories array.

If per-repository config must be done within the repository, it is still recommended against committing secrets directly (including e.g. .npmrc files with tokens) and instead encrypting them with a custom public key first. For instructions on this, see the above section on encrypting secrets for the Mend Renovate App but instead:

Note

Encrypted values can't be used in the \"Admin config\".

"},{"location":"getting-started/private-packages/#hostrules-configuration-using-environment-variables","title":"hostRules configuration using environment variables","text":"

Self-hosted users can enable the option detectHostRulesFromEnv to configure the most common types of hostRules via environment variables.

"},{"location":"getting-started/running/","title":"Running Renovate","text":"

As end user, you can choose from these ways to run Renovate:

If you're using the Mend Renovate App, or if someone else is hosting Renovate for you, skip ahead to the installing & onboarding page.

"},{"location":"getting-started/running/#self-hosting-renovate","title":"Self-Hosting Renovate","text":"

When self-hosting Renovate you're the \"administrator\" of that deployment, this means you:

If you're self-hosting Renovate on Windows, read Self-hosting on Windows to prevent line endings from confusing Renovate.

If you're running Renovate Community Edition or Renovate Enterprise Edition, refer to the documentation on the mend/renovate-ce-ee GitHub repository.

"},{"location":"getting-started/running/#available-distributions","title":"Available distributions","text":""},{"location":"getting-started/running/#npm-package-cli","title":"npm package (CLI)","text":"

Renovate's Open Source CLI is built and distributed as the npm package renovate. You can run this package in any Node.js environment - even via npx - and it will process all the repositories it is configured with, before exiting.

When installing Renovate via npm you are responsible for installing any third-party tools or languages like Ruby, Python, Composer, Bundler, Poetry, etc.

The renovate npm package is compatible with all of Renovate's supported platforms.

"},{"location":"getting-started/running/#docker-images","title":"Docker images","text":"

Renovate is also distributed as Docker images on Docker Hub (renovate/renovate) and GitHub container registry (ghcr.io/renovatebot/renovate). These Docker images work on all the hosting platforms that Renovate supports.

Both linux/amd64 and linux/arm64 architectures are supported, but you may still find some bugs in the arm64 image. You can't run the Docker images in a Windows or macOS container.

In general, you can run Renovate natively on Windows as long as you have all tools it will need (e.g. npm, pipenv, etc.) preinstalled before you run Renovate.

There are two Docker image flavors:

"},{"location":"getting-started/running/#the-default-image-formerly-slim","title":"The default image (formerly slim)","text":"

The default image only comes with the Node.js environment. Renovate will then install any needed tools when it runs. Read the binarySource=install documentation for more details. We recommend this default image for most users.

Renovate supports a persistent cache for downloaded tools, so that it only needs to unpack the tools on later runs. Use the containerbaseDir config option to control where Renovate stores its containerbase cache.

Warning

The usage of binarySource=docker is deprecated, and will be removed in the future.

If you want, you can map the Docker socket into the container so that Renovate can dynamically invoke \"sidecar\" images when needed. You'll need to set binarySource=docker for this to work. Read the binarySource config option docs for more information.

"},{"location":"getting-started/running/#the-full-image","title":"The full image","text":"

The -full image comes with most package managers that Renovate supports, but not all package managers. Update your Docker images regularly to keep the pre-installed tools up-to-date.

The full image is for users who don't want to download or install things at runtime. This image has some downsides, because it:

"},{"location":"getting-started/running/#github-action","title":"GitHub Action","text":"

Renovate's npm tool is also provided as a GitHub Action on renovatebot/github-action. Details on how to use it can be found in the repository.

"},{"location":"getting-started/running/#gitlab-runner","title":"GitLab Runner","text":"

The Renovate team provide a \"Renovate Runner\" project to make it easier to run Renovate as a CI pipeline job. This supports both gitlab.com and self-hosted GitLab. Details for how it works can be found in the project.

"},{"location":"getting-started/running/#mend-renovate-self-hosted-community-edition-enterprise-edition","title":"Mend Renovate Self-Hosted (Community Edition / Enterprise Edition)","text":"

Mend Renovate Self-Hosted Community Edition (sometimes \"Renovate CE\"/\"CE\") and Enterprise Edition (sometimes \"Renovate EE\"/\"EE\") are closed-source offerings of Renovate for self-hosted users.

It is built similarly to the default \"full\" Renovate image described above, but with these differences:

Plus, the Enterprise Edition has:

Mend Renovate Self-Hosted CE and EE have support for GitHub.com, GitHub Enterprise Server, GitLab.com, GitLab Self-Managed, and Bitbucket Data Center.

Go to the Mend.io website to learn more about Renovate Enterprise Edition.

To learn how to configure Renovate CE or Renovate EE, read the documentation on the public GitHub repository mend/renovate-ce-ee.

"},{"location":"getting-started/running/#mend-remediate","title":"Mend Remediate","text":"

Mend Remediate is part of Mend's Classic Repository Integrations product which is for Mend commercial customers, with full enterprise support.

It is integrated with Mend's vulnerability detection capabilities and additionally supports the capability of \"horizontal\" scalability - the ability to configure many Renovate \"worker\" containers which share a common job queue in order to not conflict with each other.

Mend Remediate supports GitHub Enterprise Server, GitLab self-hosted, and Bitbucket Server.

"},{"location":"getting-started/running/#forking-renovate-app","title":"Forking Renovate app","text":"

\"Forking Renovate\" is the sister app to the Mend Renovate App. The difference is that Forking Renovate does not need write permissions to create branches within the repo, and instead submits PRs from its own fork. Because of how it works, it functions on public repositories only and additionally cannot support automerge capabilities.

Install Forking Renovate from GitHub App store.

"},{"location":"getting-started/running/#benefits","title":"Benefits","text":"

Forking Renovate needs only read level access to the code of any repository it runs on.

"},{"location":"getting-started/running/#drawbacks","title":"Drawbacks","text":"

If you use Forking Renovate, you'll miss out on these features of the regular Renovate app:

"},{"location":"getting-started/running/#hosting-renovate","title":"Hosting Renovate","text":"

After deciding on a Renovate distribution, you need to decide where and how to run it.

For the GitHub Action and GitLab Runner approaches, they will naturally run on their respective CI infrastructure. For the npm package approach or Docker images, you will need some form of VM or container infrastructure to run Renovate on.

In all the above cases you must make sure that some form of cron-like capability exists to schedule when Renovate runs. We recommend that you run Renovate hourly, if possible.

Mend Renovate On-Premises and Mend Remediate both run as long-lived containers, so they do not need any cron-like concept as it is built-in.

"},{"location":"getting-started/running/#global-config","title":"Global config","text":"

Renovate's server-side/admin config is referred to as its \"global\" config, and can be set by using either:

By default Renovate checks if a file named config.js is present. Any other (*.js, *.ts, *.json, *.json5, *.yaml or *.yml) file is supported, when you reference it with the RENOVATE_CONFIG_FILE environment variable (for example: RENOVATE_CONFIG_FILE=config.yaml).

Renovate checks for the additional config file only if the RENOVATE_ADDITIONAL_CONFIG_FILE is set. Behaviour wise this config is similar to the file config, except that it has higher priority than the default config file.

Some config is global-only, meaning that either it is only applicable to the administrator or it can only be controlled by the administrator and not repository users. Those are documented in Self-hosted Configuration. Your global config can include both global as well as non-global configuration options, while user/repo config can only include non-global options. We recommend that you keep as much of the non-global config as possible in repository config files. This way the Renovate end users can see as much of the configuration as possible.

If you are configuring Renovate using environment variables, there are two possibilities:

If you combine both of the above then any single config option in the environment variable will override what's in RENOVATE_CONFIG. Mergeable options, like hostRules or packageRules, are combined instead: lists are appended and objects are merged.

Note

It's also possible to change the default prefix from RENOVATE_ using ENV_PREFIX. For example: ENV_PREFIX=RNV_ RNV_TOKEN=abc123 renovate.

"},{"location":"getting-started/running/#using-configjs","title":"Using config.js","text":"

If you use a config.js, it will be expected to export a configuration via module.exports. The value can be either a plain JavaScript object like in this example where config.js exports a plain object:

module.exports = {\n  token: 'abcdefg',\n};\n

config.js may also export a Promise of such an object, or a function that will return either a plain JavaScript object or a Promise of such an object. This allows one to include the results of asynchronous operations in the exported value. An example of a config.js that exports an async function (which is a function that returns a Promise) can be seen in a comment for #10011: Allow autodiscover filtering for repo topic and more examples can be seen in file.spec.ts.

"},{"location":"getting-started/running/#using-typescript-config-files","title":"Using TypeScript config files","text":"

Renovate supports TypeScript config files (.ts, .mts, .cts) via Node.js's built-in type stripping. Set the RENOVATE_CONFIG_FILE environment variable to point to your TypeScript config file:

RENOVATE_CONFIG_FILE=config.ts renovate\n

An example config.ts:

import type { AllConfig } from 'renovate/dist/config/types';\n\nconst config: AllConfig = {\n  platform: 'github',\n  token: process.env.RENOVATE_TOKEN,\n  repositories: ['my-org/my-repo'],\n};\n\nexport default config;\n

TypeScript config files follow the same rules as JavaScript config files: they can export a plain object, a Promise, or a function. The .mts extension is always treated as an ES module, and .cts is always treated as CommonJS.

"},{"location":"getting-started/running/#authentication","title":"Authentication","text":"

Regardless of platform, you need to select a user account for renovate to assume the identity of, and generate a Personal Access Token. We recommend you use @renovate-bot as username if you're on a self-hosted server where you can set all usernames. We also recommend you configure config.gitAuthor with the same identity as your Renovate user, for example: \"gitAuthor\": \"Renovate <renovate@some.domain.test>\".

Warning

We recommend you use a single, dedicated username for your Renovate. Never share the Renovate username with your other bots, as this can cause flip-flopping.

"},{"location":"getting-started/running/#docs","title":"Docs","text":"

Read the platform-specific docs to learn how to setup authentication on your platform:

"},{"location":"getting-started/running/#githubcom-token-for-changelogs-and-tools","title":"GitHub.com token for changelogs (and tools)","text":"

If you are running on any platform except github.com, you should also set the environment variable RENOVATE_GITHUB_COM_TOKEN and put the Personal Access Token for github.com in it. This account can be any account on GitHub, and needs only read-only access. It's used when fetching changelogs for repositories, as well as some Renovate-specific tools at runtime, in order to increase the hourly API limit. It's also OK to configure the same as a host rule instead, if you prefer that.

Note

If you're using Renovate in a project where dependencies are loaded from github.com (such as Go modules hosted on GitHub), we highly recommend that you add a github.com PAT (classic). Otherwise you will exceed the rate limit for the github.com API, which will lead to Renovate closing and reopening PRs because it could not get reliable info on updated dependencies.

"},{"location":"getting-started/running/#self-hosting-examples","title":"Self-hosting examples","text":"

For more examples on running Renovate self-hosted, read our Self-hosted examples page.

"},{"location":"getting-started/running/#community-tools","title":"Community tools","text":"

There are also some community-maintained tools which may help running Renovate.

"},{"location":"getting-started/use-cases/","title":"Use Cases","text":"

This page describes common use cases for Renovate.

"},{"location":"getting-started/use-cases/#development-dependency-updates","title":"Development dependency updates","text":"

The original use case, and the most popular one, is for developers to automate dependency updating in their software projects.

"},{"location":"getting-started/use-cases/#updating-of-package-files","title":"Updating of package files","text":"

We use the term \"package file\" to describe files which reference dependencies. Package files are managed by a \"package manager\".

Example package files include:

"},{"location":"getting-started/use-cases/#how-renovate-updates-a-package-file","title":"How Renovate updates a package file","text":"

Renovate:

  1. Scans your repositories to find package files and their dependencies
  2. Checks if any newer versions exist
  3. Raises Pull Requests for available updates

The Pull Requests patch the package files directly, and include changelogs for the newer versions (if they are available).

By default:

"},{"location":"getting-started/use-cases/#package-managers-with-lock-files","title":"Package managers with lock files","text":"

Many package managers support \"lock files\", which \"freeze\" the entire dependency tree including transitive dependencies. npm, Yarn, Bundler, Composer, Poetry, Pipenv, and Cargo all support or use lock files.

If you use a lock file then changes to your package file must come with a compatible change to the lock file. Renovate can patch/update package files directly, but can't \"reverse engineer\" lock files. This is why Renovate lets the package manager do the lock file update. A simplified example:

  1. The repository has a package.json and package-lock.json with version 1.0.0 of a dependency
  2. Renovate sees that version 1.1.0 is available
  3. Renovate patches the package.json to change the dependency's version from 1.0.0 to 1.1.0
  4. Renovate runs npm install to let npm update the package-lock.json
  5. Renovate commits the package.json and package-lock.json
  6. Renovate creates the PR
"},{"location":"getting-started/use-cases/#custom-dependency-extraction","title":"Custom dependency extraction","text":"

Renovate supports 90+ types of package files. By default, Renovate finds most dependencies, but there are exceptions. This can be because:

If your dependencies are not found by default, you can use our custom manager to set your own custom patterns to extract dependencies. You configure the custom manager by telling it:

The end result is that Renovate can keep dependencies in custom file formats up-to-date as long as the dependency datasource is known to Renovate.

"},{"location":"getting-started/use-cases/#devops-tooling","title":"DevOps tooling","text":"

Renovate is increasingly used for purposes which are traditionally described as DevOps instead of Developer.

"},{"location":"getting-started/use-cases/#devops-infrastructure-as-code-updates","title":"DevOps / Infrastructure as Code updates","text":"

It's common for repositories to have DevOps-related files like CI/CD configs, or \"Infrastructure as Code\" (IaC) files. Examples of IaC files are Docker, Kubernetes or Terraform files. Renovate handles IaC files as \"package managers\" and \"package files\" and can find and update them.

"},{"location":"getting-started/use-cases/#docker-compatible-images","title":"Docker-compatible images","text":"

Docker-compatible images are a key building block of modern software. These images are commonly found in CI/CD pipeline configs or referenced in IaC files. Renovate finds these IaC files and then searches Docker registries to see if there are newer tags or digests.

"},{"location":"getting-started/use-cases/#tag-based-updating","title":"Tag-based updating","text":"

An example of tag-based updating are node images from Docker Hub. The node images use these tag formats:

Renovate understands both formats and raises updates like these:

"},{"location":"getting-started/use-cases/#docker-digests","title":"Docker digests","text":"

You can check and update versions like 14.17.4 yourself. But looking up image digests like 341976f40d963a425d627a349a9b0034e1eafffbf4c82a173c1465ee403878d9 and updating them yourself doesn't scale. So let Renovate update your Docker digests.

You can even configure Renovate to \"pin\" your Docker digests. When you're using tag+digest based images, you'll have immutable builds.

"},{"location":"getting-started/use-cases/#internal-package-updates","title":"Internal package updates","text":"

Your company typically has dozens of repositories, if not hundreds or thousands. These repositories often rely on other repositories and may have upstream or downstream internal dependencies. In such cases, it is best practice to:

You can use Renovate to follow this best practice. Renovate finds and updates internal dependencies just like external or Open Source dependencies.

"},{"location":"getting-started/use-cases/#automerge-internal-dependencies","title":"Automerge internal dependencies","text":"

Renovate's automerge feature is really useful for internal dependencies where you can say \"if it passes tests let's merge it\".

To learn more about \"automerge\" read the key concepts, automerge documentation.

"},{"location":"getting-started/use-cases/#example-of-automerging-internal-dependencies","title":"Example of automerging internal dependencies","text":"

We use these Renovate features to automerge an internal dependency:

"},{"location":"getting-started/use-cases/#background-information","title":"Background information","text":"

We split our work over two repositories:

  1. The renovatebot/renovate repository, which has the Renovate code, and most of the Markdown documentation files
  2. The renovatebot/renovatebot.github.io repository, which has a submodule link to the renovatebot/renovate repository
"},{"location":"getting-started/use-cases/#update-process","title":"Update process","text":"
  1. We edit our documentation files on the main Renovate repository renovatebot/renovate
  2. Renovate sees the change(s) to the renovatebot/renovate Git submodule, and creates an update branch on the documentation build repository
  3. If the tests pass Renovate automerges the update branch into the main branch.
  4. A GitHub Actions workflow runs on main to build the documentation site and push the build live on our GitHub Pages domain
"},{"location":"getting-started/use-cases/#benefits","title":"Benefits","text":"

The way we've set things up means we avoid:

In fact we don't even get the update PR anymore!

"},{"location":"getting-started/use-cases/#advanced-configuration","title":"Advanced configuration","text":"

The capabilities listed below are commonly needed for all the above use cases.

"},{"location":"getting-started/use-cases/#batched-updates","title":"Batched updates","text":"

Renovate defaults to separating each dependency update into its own PR. But you may want to batch or \"group\" updates together. For example, group all patch updates into one PR or even all non-major updates together (patches and minor updates).

You can configure batched updates by setting a groupName as part of packageRules.

To learn more about batched updates, see Package grouping.

"},{"location":"getting-started/use-cases/#scheduled-updates","title":"Scheduled updates","text":"

You may want to limit the times when Renovate is allowed to raise updates. This reduces \"noise\" during your working hours, and reduces the chance of CI contention. You can tell Renovate to \"not bother you\" during times when you're using the CI resources, or want to focus on your work.

You can set the time ranges during which Renovate creates updates in the schedule field.

"},{"location":"getting-started/use-cases/#on-demand-updates-via-dependency-dashboard","title":"On-demand updates via Dependency Dashboard","text":"

You can use Renovate's \"Dependency Dashboard\" on platforms which support dynamic Markdown checkboxes:

When you enable the Dependency Dashboard, Renovate creates a \"Dependency Dashboard\" issue. This issue lists all updates which are pending, in progress, or were previously closed ignored.

If you want to get an update ahead of schedule, or want to retry a previously closed update: select the update's checkbox in the Dependency Dashboard.

"},{"location":"getting-started/use-cases/#dependency-dashboard-approval","title":"Dependency Dashboard Approval","text":"

If you enable the Dependency Dashboard you can opt-in to a different workflow for some, or even all of your packages. We call this the \"Dependency Dashboard Approval\" workflow.

Here's how it works:

"},{"location":"getting-started/use-cases/#benefits-of-using-dependency-dashboard-approval","title":"Benefits of using Dependency Dashboard Approval","text":"

When you use the Dependency Dashboard Approval workflow you have full visibility and control over your updates.

"},{"location":"getting-started/use-cases/#configuration-presets","title":"Configuration presets","text":"

You may run Renovate on many, or even all your repositories. This also means that you might want a similar config for all of your repositories. You can use configuration \"presets\" to avoid duplicating your configuration across your repositories.

Configuration presets are JSON configuration files which are committed to repositories and then referenced from others. Renovate includes over 100 built-in presets, like the default recommended config:recommended preset.

The typical workflow for a company is:

This means that repositories get the centralized config by default, and any changes made to the centralized config repository are propagated to other repositories immediately.

"},{"location":"getting-started/use-cases/#how-others-use-renovate","title":"How others use Renovate","text":"

You can learn a lot by seeing how others use Renovate. Check out the Swissquote user story.

"},{"location":"key-concepts/automerge/","title":"Introduction","text":"

You can choose to automate some dependency updates by letting Renovate automerge its PR. Renovate will wait for the required tests to pass before it automerges.

"},{"location":"key-concepts/automerge/#renovate-automerges-take-time","title":"Renovate automerges take time","text":"

Renovate automerges take time, so Renovate can't automerge a PR the second it passes your required tests. Before you start troubleshooting, wait! Give Renovate about two hours, so Renovate can run in a state where your tests have passed, and the PR branch is up-to-date with the base branch. If you or others keep committing to the default branch then Renovate cannot find a suitable gap to automerge into!

After Renovate automerges a branch, Renovate must calculate the \"Git state\" again, for all remaining branches. Merging one branch may result in another branch's updates being changed, or even removed as no longer needed. Renovate requires automerging branches to be up-to-date with their target branch, before automerging. As merging more than one branch in a row does not work reliably, Renovate will only automerge one branch/PR, per target branch, per run. Then you'll have to wait for the next time Renovate runs.

"},{"location":"key-concepts/automerge/#recommendations-from-the-renovate-maintainers","title":"Recommendations from the Renovate maintainers","text":"

In general, we recommend you enable automerge for any dependency update where you would select \"merge\" anyway. Keep automerge disabled for updates where you want to read the changelogs or code before the merge.

Automerge often works well for devDependencies. It can work for production dependencies too, but your project should have good test coverage.

For example, if you have Jest or Mocha as a development dependency, and it has an upgrade with passing tests... automerge them! If you have a linter like ESLint or TSLint and its update passes... automerge them! If you have an API with 100% test coverage and Express is updated... automerge it!

"},{"location":"key-concepts/automerge/#configuration-examples","title":"Configuration examples","text":""},{"location":"key-concepts/automerge/#automerge-lock-file-maintenance","title":"Automerge lock file maintenance","text":"

The lowest risk type of update to automerge is probably lockFileMaintenance. When Renovate performs lock file maintenance, it leaves the project dependency definitions unchanged, but refreshes the lock file completely. This means Renovate installs the latest versions, that match the package file constraints.

Example of automerging lock file maintenance
{\n  \"lockFileMaintenance\": {\n    \"enabled\": true,\n    \"automerge\": true\n  }\n}\n
"},{"location":"key-concepts/automerge/#automerge-lint-tool-updates","title":"Automerge lint tool updates","text":"

Automerging lint tool updates can be a real time-saver. Often a new lint tool version pass the updated tests, without any code changes on your end. If the tests pass you may as well automerge the PR.

In cases where you need to make changes to your code, the Renovate PR will fail the linter check. You can then make the necessary code changes directly in the Renovate branch for that PR, confirm the tests pass with your changes, and manually merge the PR.

Example of automerging lint and Prettier development packages
{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"matchPackageNames\": [\"lint\", \"prettier\"],\n      \"automerge\": true\n    }\n  ]\n}\n
"},{"location":"key-concepts/automerge/#automerge-non-major-updates","title":"Automerge non-major updates","text":"

Non-major updates in SemVer ecosystems shouldn't have breaking changes (if they follow the spec), so many users enable automerge for these too:

Example of automerging non-major updates in SemVer ecosystem
{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"minor\", \"patch\"],\n      \"matchCurrentVersion\": \"!/^0/\",\n      \"automerge\": true\n    }\n  ]\n}\n

The matchCurrentVersion setting above is a rule to exclude any dependencies which are pre-1.0.0 because those can make breaking changes at any time according to the SemVer spec.

"},{"location":"key-concepts/automerge/#automerge-monorepo-prs","title":"Automerge monorepo PRs","text":"

Say you want to automerge patch and minor updates for packages in the group:ionic-nativeMonorepo preset:

Example of automerging patch and minor updates in a group from a preset
{\n  \"packageRules\": [\n    {\n      \"extends\": [\"monorepo:ionic-native\"],\n      \"matchUpdateTypes\": [\"patch\", \"minor\"],\n      \"automerge\": true\n    }\n  ]\n}\n
"},{"location":"key-concepts/automerge/#faster-merges-with-platform-native-automerge","title":"Faster merges with platform-native automerge","text":"

By default, Renovate uses platform-native automerge to speed up automerging. If you don't want Renovate to use the platform-native automerge, then set platformAutomerge to false.

Example of disabling platform-native automerge
{\n  \"lockFileMaintenance\": {\n    \"enabled\": true,\n    \"automerge\": true,\n    \"automergeType\": \"pr\",\n    \"platformAutomerge\": false\n  }\n}\n

For more information read platformAutomerge.

"},{"location":"key-concepts/automerge/#github-merge-queue","title":"GitHub Merge Queue","text":"

Renovate supports GitHub's Merge Queue.

Read the GitHub Docs, managing a merge queue first.

The steps to enable GitHub's Merge Queue differ based on whether you use GitHub Actions or another CI provider.

With platformAutomerge enabled (which is the default), GitHub's auto-merge takes care of adding the PR to the merge queue. This requires the \"Allow auto-merge\" checkbox in the repository settings to be enabled, as described in the steps below.

Merge queues also work with platformAutomerge=false: Renovate first attempts to merge the PR directly, which succeeds when Renovate is on the merge queue's bypass list. If that merge is refused and the base branch has a merge queue, configured via classic branch protection or repository rulesets, Renovate adds the PR to the merge queue itself once all checks have passed. In that case the \"Allow auto-merge\" checkbox is not needed. PRs that are already waiting in the merge queue are left untouched on later runs. We recommend enabling the \"Automatically delete head branches\" repository setting, so branches get cleaned up after the merge queue merges the PR.

Warning

Branch automerge (automergeType=branch) only works if the base branch has a merge queue when Renovate is on the merge queue's bypass list, because pushing directly to the base branch is not possible otherwise. Renovate logs a warning and creates a PR instead if the merge queue rejects the push. Configure automergeType=pr in such repositories, or add Renovate to the bypass list.

GitHub Merge Queue overview page

GitHub has a page that shows all the PRs in the Merge Queue. The page link follows this pattern: https://github.com/organization-name/repository-name/queue/base-branch-name. For example, here's Renovate's main repository's Merge Queue overview.

"},{"location":"key-concepts/automerge/#if-you-use-github-actions","title":"If you use GitHub Actions","text":"

If you use GitHub Actions as your CI provider, follow these steps:

Add the on.merge_group event to your GitHub Action .yaml files, for example:

on:\n  pull_request:\n  merge_group:\n

On github.com, go to your repository's \"homepage\", click on Settings, scroll down to the Pull Requests section and enable the \"Allow auto-merge\" checkbox.

Then go to your repository's branch protection rules for your base branch (usually main) and enable the \"Require merge queue\" setting. Confirm you've set the correct \"required checks\" for your base branch.

Finally, allow Renovate to automerge by setting automerge=true in your Renovate config file, for example:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Automerge non-major updates\",\n      \"matchUpdateTypes\": [\"minor\", \"patch\"],\n      \"automerge\": true\n    }\n  ]\n}\n
"},{"location":"key-concepts/automerge/#if-you-dont-use-github-actions","title":"If you don't use GitHub Actions","text":"

If you don't use GitHub Actions as your CI provider, follow these steps:

Update your CI provider's configuration so it also runs tests on the temporary gh-readonly-queue/{base_branch} branches, read your CI providers's documentation to learn how to do this.

On github.com, go to your repository's \"homepage\", click on Settings, scroll down to the Pull Requests section and enable the \"Allow auto-merge\" checkbox. Go to your repository's branch protection rules for your base branch (usually main) and enable the \"Require merge queue\" setting. Confirm you've set the correct \"required checks\" for your base branch.

Finally, allow Renovate to automerge by setting automerge=true in your Renovate config file (see earlier example).

"},{"location":"key-concepts/automerge/#gitlab-merge-trains","title":"GitLab Merge Trains","text":"

Renovate supports GitLab's merge trains. Renovate detects whether merge trains are enabled on the project and then:

Warning

Branch automerge (automergeType=branch) only works with merge trains if Renovate is allowed to push to the protected target branch. If the push is rejected, Renovate logs a warning and creates a MR instead. Configure automergeType=pr in such projects, or allow Renovate to push to the target branch.

"},{"location":"key-concepts/automerge/#automerging-and-scheduling","title":"Automerging and scheduling","text":"

Automerging is particularly beneficial if you have configured a schedule, because Renovate on its own may be able to automerge the majority of your updates. And this is especially so if your repository needs rebasing, like when you use lock files. Let's say you have dependencies abc and xyz with upgrades, and you use a yarn.lock file.

This is a lot better than you waking up to two PRs and then having to deal with conflicts yourself after you merge the first one.

"},{"location":"key-concepts/automerge/#branch-vs-pr-automerging","title":"Branch vs PR automerging","text":"

Even if you automerge PRs, you are likely to still get notification noise - one when the PR is created and another when it is merged. For this reason we recommend you consider setting automergeType=branch which will mean:

Add the renovate/** branch to your testing workflow files, or Renovate will not work properly with the automergeType=branch setting.

The result is that passing updates are essentially \"silent\" - the only sign of them are the commits Renovate pushes to your base branch. If you have enabled branch protection which prevents Renovate from automerging directly to the base branch, then this won't work and you should stick with the default PR-based automerging instead.

"},{"location":"key-concepts/automerge/#assignees-and-reviewers","title":"Assignees and Reviewers","text":"

When automerge is enabled on a PR, Renovate will not add assignees or reviewers at PR creation time, in order to decrease notifications noise a little. If tests subsequently fail, making automerge not possible, then Renovate will add the configured assignees and/or reviewers.

Note: Renovate won't add assignees and reviewers to a PR with failing checks if the PR already has assignees or reviewers present. If there are accounts you wish to ignore (i.e. add assignees and reviewers regardless) then add them to ignoreReviewers to specify those which should be filtered out in such consideration.

If you want Renovate to always add assigness and reviewers to a PR regardless of automerge configuration, activate the assignAutomerge option.

"},{"location":"key-concepts/automerge/#frequent-problems-and-how-to-resolve-them","title":"Frequent problems and how to resolve them","text":""},{"location":"key-concepts/automerge/#automerge-not-enabled-correctly-in-config","title":"Automerge not enabled correctly in config","text":"

Sometimes, the reason Renovate is not automerging a PR is because of a configuration mistake. You can confirm that Renovate knows you want it to automerge by checking if the PR body includes the text \"Automerge: Enabled\". If you see \"Automerge: Disabled by config\" it means you need to make a config change for automerge to work.

"},{"location":"key-concepts/automerge/#absence-of-tests","title":"Absence of tests","text":"

By default, Renovate will not automerge until it sees passing status checks / check runs for the branch. If you have no tests but still want Renovate to automerge, you need to add \"ignoreTests\": true to your configuration.

Tip

We strongly recommend you have tests in any project where you are regularly updating dependencies.

"},{"location":"key-concepts/automerge/#committer-restrictions","title":"Committer restrictions","text":"

If you have protected your base branch with a list of allowed committers, and Renovate is not on that list, then naturally automerge can't work.

"},{"location":"key-concepts/automerge/#pull-requests-required","title":"Pull Requests Required","text":"

If you have configured your project to require Pull Requests before merging, it means that branch automerging is not possible, even if Renovate has rights to commit to the base branch.

"},{"location":"key-concepts/automerge/#required-pull-request-reviews","title":"Required Pull Request reviews","text":"

If you have mandatory Pull Request reviews then it means Renovate can't automerge its own PR until such a review has happened.

If you're on github.com or GitHub Enterprise Server (>=3.4) you can let Renovate bypass the mandatory Pull Request reviews using the \"Allow specified actors to bypass required pull requests\" option in your branch protection rules.

Alternatively, if you use the Mend Renovate App, you can also install the helper apps renovate-approve and renovate-approve-2 and they will mark all automerging Pull Requests by Renovate as approved. These approval helper apps are only available for GitHub.

On Azure/Gerrit/Gitlab, you can activate the autoApprove option.

"},{"location":"key-concepts/automerge/#codeowners","title":"Codeowners","text":"

Depending on the platform, having a CODEOWNERS file could block automerging, because it means a code owner must review the PR.

"},{"location":"key-concepts/automerge/#overriding-global-automerge","title":"Overriding global automerge","text":"

You might have setup a global configuration in a .github repository, that has a renovate.json file that turns on automerge for certain dependencies. It does not matter where you've put the global config, the important point in this example is that you're extending from a global config that's somewhere else. For this example we'll assume you put your config in a repository on GitHub, called .github.

Repositories in the organization all extend from this global configuration, and so they \"inherit\" the automerge settings as well.

To turn off automerge for all dependencies of a selected repository, you need to make a config that overrides all packageRules in the repository's renovate.json file, like this:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"extends\": [\"local>org-name/.github:renovate-config\"],\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"*\"],\n      \"automerge\": false\n    }\n  ]\n}\n
"},{"location":"key-concepts/changelogs/","title":"Renovate and changelogs","text":"

This page explains how Renovate fetches changelogs, when it can display them, and more.

"},{"location":"key-concepts/changelogs/#how-renovate-detects-changelogs","title":"How Renovate detects changelogs","text":"

Renovate detects and populates changelogs by:

  1. Identifying a source URL from the datasource response for a package, and saving that internally as sourceUrl if found
  2. Checking if Renovate's internal sourceUrl data for the package includes a source URL
  3. Looking up the source URL, if it resides on a supported platform (e.g. GitHub)
  4. Checking for both \"Releases\" metadata in the repository and any commonly known \"changelog\" file names
  5. Filtering the found releases to only include those versions being updated by the current PR
  6. Formatting and embedding the results into the PR body
"},{"location":"key-concepts/changelogs/#changelogs-for-private-packages","title":"Changelogs for private packages","text":"

For private packages, the algorithm is mostly the same as described above, with the additional considerations:

For more details, see Private packages, looking up changelogs.

"},{"location":"key-concepts/changelogs/#relevant-configuration-options","title":"Relevant configuration options","text":""},{"location":"key-concepts/changelogs/#fetchchangelogs","title":"fetchChangeLogs","text":"

Top-level configuration that controls when to fetch changelogs for addition to pull-request and branch commit-messages. If you want more finely-grained control over changelog fetching (disabling for specific packages, source repositories, etc), use packageRules to override the fetchChangeLogs value for matching packages.

Set to off if changelog fetching is causing a problem.

Set to branch if you have an advanced use case where you're embedding changelogs in the Git commit itself, we don't recommend this due to its potential size.

"},{"location":"key-concepts/changelogs/#changelogurl","title":"changelogUrl","text":"

This doesn't help with fetching the changelogs, but if you configure it then Renovate will include a link to this URL in the PR body, so users can click through to read the changelog.

"},{"location":"key-concepts/changelogs/#platforms-that-renovate-can-fetch-changelogs-from","title":"Platforms that Renovate can fetch changelogs from","text":"

See the list of platforms in the fetchChangeLogs config option docs.

"},{"location":"key-concepts/changelogs/#running-renovate-on-a-non-github-platform","title":"Running Renovate on a non-GitHub platform","text":"

Most Open Source packages are hosted on github.com, which means most changelogs are hosted there too. Fetching changelogs from github.com requires a GitHub token because GitHub blocks unauthenticated GraphQL API use.

This means that if you run Renovate on self-hosted GitHub Enterprise Server, or any non-GitHub platform which Renovate supports, then you need to configure a github.com Personal Access Token in Renovate in order to fetch changelogs.

Read Running Renovate, GitHub.com token for changelogs to learn more.

"},{"location":"key-concepts/changelogs/#troubleshooting-missing-changelogs","title":"Troubleshooting missing changelogs","text":"

Follow these steps to find out why Renovate does not find a changelog:

  1. The datasource for this package does not support sourceUrls.
  2. The package was published without source URL information being included.
  3. Renovate cannot access the source repository
  4. Renovate cannot detect the file names or release name convention within the repository
  5. Renovate cannot detect the release version in the changelog file

If none of this helps, search the Renovate issues and discussions to see if this is a known problem.

"},{"location":"key-concepts/changelogs/#advice-for-package-maintainers","title":"Advice for package maintainers","text":"

This section is for package maintainers that want to make sure Renovate can see their changelogs.

There isn't much information to add other than what's already written above.

Make sure that you have the required source URL in your package metadata, not just in your repository but also in the final data which the registry returns. For example, we have seen cases where the repository field in npm's package.json is populated correctly in the repository, but stripped out as part of the publishing process.

"},{"location":"key-concepts/changelogs/#let-renovate-understand-your-versioning-and-changelogs","title":"Let Renovate understand your versioning and changelogs","text":"

In general, Renovate can understand your versions and changelogs best when you:

Try to avoid things like:

"},{"location":"key-concepts/changelogs/#npm-package-maintainers","title":"npm package maintainers","text":"

As maintainer, make sure the package.json has a filled in repository field, read the npm Docs, configuring npm repository field to learn more. If your repository uses the monorepo pattern make sure each package.json file has a repository field.

"},{"location":"key-concepts/changelogs/#maven-package-maintainers","title":"maven package maintainers","text":"

Read maven datasource, making your changelogs fetchable.

"},{"location":"key-concepts/changelogs/#docker-image-maintainers","title":"Docker image maintainers","text":"

Read the Docker datasource docs.

"},{"location":"key-concepts/changelogs/#nuget-package-maintainers","title":"NuGet package maintainers","text":"

See Renovate issue #14128 about using NuGet's changelogs.

"},{"location":"key-concepts/dashboard/","title":"Introduction","text":"

Renovate has a Dependency Dashboard that shows an overview of the state of your repositories' dependencies.

When the Dependency Dashboard is enabled, Renovate will create a new issue in the repository. This issue has a \"dashboard\" where you can get an overview of the status of all updates.

Having the Dependency Dashboard also enables the concept of an \"approval\" workflow for new upgrades, either for selected dependencies (recommended) or even for all.

"},{"location":"key-concepts/dashboard/#supported-platforms","title":"Supported platforms","text":"

The Dependency Dashboard requires that the host platforms supports the concept of issues with dynamic Markdown checkboxes. Read our FAQ, Renovate core features not supported on all platforms to see if your platform can use the Dependency Dashboard feature.

"},{"location":"key-concepts/dashboard/#how-to-enable-the-dashboard","title":"How to enable the dashboard","text":"

To turn on the Dashboard manually, add the :dependencyDashboard preset to your extends array in the Renovate configuration file:

{\n  \"extends\": [\"schedule:automergeDaily\", \":dependencyDashboard\"]\n}\n

Or set dependencyDashboard to true:

{\n  \"dependencyDashboard\": true\n}\n
"},{"location":"key-concepts/dashboard/#how-to-disable-the-dashboard","title":"How to disable the dashboard","text":"

To disable the Dependency Dashboard, add the preset :disableDependencyDashboard or set dependencyDashboard to false.

{\n  \"extends\": [\"config:recommended\", \":disableDependencyDashboard\"]\n}\n
"},{"location":"key-concepts/dashboard/#use-cases","title":"Use cases","text":"

This section explains some common use cases where having the Dependency Dashboard can help.

"},{"location":"key-concepts/dashboard/#warnings-for-deprecated-dependencies","title":"Warnings for deprecated dependencies","text":"

If Renovate finds:

Then Renovate adds a prominent warning about these packages near the top of the Dependency Dashboard. Here is an example of how this can look:

The following dependencies are deprecated:

Datasource Name Replacement? npm airbnb-prop-types npm left-pad"},{"location":"key-concepts/dashboard/#abandonment-detection","title":"Abandonment detection","text":"

Renovate includes the abandonments:recommended preset (automatically included in config:best-practices) to help identify potentially abandoned packages. This preset:

Usage:

{\n  \"extends\": [\"abandonments:recommended\"]\n}\n

You can contribute additional overrides by updating the abandonments.json file.

"},{"location":"key-concepts/dashboard/#visibility-into-rejecteddeferred-updates","title":"Visibility into rejected/deferred updates","text":"

Renovate's Dependency Dashboard shows an overview of all updates that are still \"to do\".

If you close an update PR from Renovate without merging, the Dashboard will list this update in the Closed/Ignored section. If you later change your mind about the update, you can get a new PR by selecting the corresponding checkbox on the dashboard.

"},{"location":"key-concepts/dashboard/#dependency-dashboard-approval-workflow","title":"Dependency Dashboard Approval workflow","text":"

Sometimes you want Renovate to wait for your approval before creating an update PR. You can customize this \"wait for approval\" behavior however you like best.

At a high level the options are:

You can mix and match these options as well.

"},{"location":"key-concepts/dashboard/#require-approval-for-all-updates","title":"Require approval for all updates","text":"

We do not recommend that you require approval for all updates. When you require prior approval, you need to check the dashboard issue regularly to check for important updates. You'll probably forget to check often enough, and out of sight means out of mind!

Maybe you find Renovate too noisy, and want to opt-out of getting automatic updates whenever they're ready.

In this case, you can tell Renovate to wait for your approval before making any pull requests. This means that you have full control over when you get updates.

But vulnerability remediation PRs will still get created immediately without requiring approval.

To require manual approval for all updates, add the :dependencyDashboardApproval presets to the extends array in your Renovate configuration file:

{\n  \"extends\": [\"config:recommended\", \":dependencyDashboardApproval\"]\n}\n
"},{"location":"key-concepts/dashboard/#require-approval-for-major-updates","title":"Require approval for major updates","text":"

Major updates often have breaking changes which require manual changes in your code before they can be merged. So maybe you only want to get major updates when you have sufficient time to check them carefully.

Dependency Dashboard Approval is far superior to disabling major updates because at least you can fully see what's pending on the dashboard, instead of updates being totally invisible.

If you want to require approval for major updates, set dependencyDashboardApproval to true within a major object:

{\n  \"major\": {\n    \"dependencyDashboardApproval\": true\n  }\n}\n
"},{"location":"key-concepts/dashboard/#require-approval-for-specific-packages","title":"Require approval for specific packages","text":"

Sometimes you only want to update specific packages when you say so.

Maybe a package doesn't follow Semantic Versioning, and has breaking changes on every new release, so you want to update on your terms.

Or maybe you have a package that updates too rapidly for you to keep up with, and you want to update once in a while manually.

If you want to approve specific packages, set dependencyDashboardApproval to true within a packageRules entry where you have defined a specific package or pattern.

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"@somescope/**\"],\n      \"dependencyDashboardApproval\": true\n    }\n  ]\n}\n
"},{"location":"key-concepts/how-renovate-works/","title":"Introduction","text":"

Renovate usually performs these steps:

Because Renovate must support a lot of dependency naming and versioning conventions, it has modules for each known convention. You can contribute your own modules, if you want.

"},{"location":"key-concepts/how-renovate-works/#modules","title":"Modules","text":"

Renovate's modules are:

Renovate uses these modules in order:

  1. The platform module interacts with the source control platform and clones the repository
  2. The manager module looks for files based on their name and extracts the dependencies (each dependency has a datasource)
  3. The datasource module looks up versions of the dependency
  4. The versioning module validates and sorts the returned versions

For example:

  1. The gitlabci manager finds a dependency: python:3.10-alpine which has the docker datasource
  2. The docker datasource looks for versions and finds: [python:3.9,python:3.9-alpine,python:3.10,python:3.10-alpine,python:3.11,python:3.11-alpine]
  3. The docker versioning returns python:3.11-alpine, because that version is compatible with python:3.10-alpine
"},{"location":"key-concepts/how-renovate-works/#workflow","title":"Workflow","text":"

Here's an overview of the workflow:

flowchart TB\n    subgraph INITIALIZATION\n        direction TB\n        MC[Merge configurations <br> most important to least: <br> cli > env > file > default]\n        MC --> IP[Initialize platform]\n        IP --> AD[Query the platform for repositories]\n        AD --> NFIL[Narrow the list with filters]\n    end\n\n    subgraph REPOSITORY\n       direction TB\n       FER{{For each repository}}\n\n      subgraph EXTRACTD[EXTRACT DEPENDENCIES]\n          direction TB\n          CLBRANCH[Extract base branches]\n          CLBRANCH --> VULN[Check for vulnerabilities]\n          VULN --> CC{{For each manager}}\n          CC -->|manager A| CD[\"...\"]\n          CC -->|manager B| CCF[\"match files\"]\n          CCF --> CFEF{{For each file}}\n          CFEF -->|file 1| CCD1[Extract dependency]\n          CFEF -->|file 2| CCD2[...]\n      end\n\n      subgraph LOOKUP[LOOK UP UPDATES]\n          direction TB\n          UC{{For each manager}}\n          UC -->|manager A| UD[\"...\"]\n          UC -->|manager B| UFEF{{For each file}}\n          UFEF -->|file 1| FED{{For each dependency}}\n          UFEF -->|file 2| FED2[...]\n          FED -->|dep 1| D1[...]\n          D1 -..-> CU\n          FED -->|dep 2| D2[use datasource to <br> fetch versions]\n          D2 --> J[use versioning to find <br> next valid update]\n          FED2 -...-> CU\n          UD -....-> CU\n          J --> CU[Look up updates]\n      end\n\n      subgraph WRITEU[WRITE UPDATES]\n        direction TB\n        FEU{{For each update}}\n        FEU --> AUCOND[Check if branch needed: <br> existing/rebase/concurrent amount]\n        AUCOND --> AU[Create branch<br>Apply update<br>Create PR]\n      end\n\n      subgraph FINALIZE[FINALIZE]\n      direction TB\n        CM[Check for config migration]\n        CM --> CSB[Clean stale branches]\n\n      end\n\n      FER --> IRPO[Initialize repository]\n\n      IRPO --> EXTRACTD\n      EXTRACTD --> LOOKUP\n\n      LOOKUP --> WRITEU\n\n      WRITEU --> FINALIZE\n\n    end\n\n    INITIALIZATION --> REPOSITORY
"},{"location":"key-concepts/minimum-release-age/","title":"Minimum Release Age","text":""},{"location":"key-concepts/minimum-release-age/#what-is-minimum-release-age","title":"What is Minimum Release Age?","text":"

minimumReleaseAge is a feature that requires Renovate to wait for a specified amount of time before suggesting a dependency update.

The use of minimumReleaseAge is not to slow down fast releasing project updates, but to provide a means to reduce risk supply chain security risks.

In other ecosystems and package managers, this may be referred to as a \"dependency cooldown\".

For example, minimumReleaseAge=14 days would ensure that a package update is not suggested by Renovate until 14 days after its release, which allows plenty of time to allow security researchers and automated security tools to catch malicious intent in packages.

Note: Renovate will wait for the set duration to pass for each separate version. Renovate does not wait until the package has seen no releases for x time-duration(minimumReleaseAge).

When the time passed since the release is less than the set minimumReleaseAge: Renovate adds a \"pending\" status check to that update's branch. After enough days have passed: Renovate replaces the \"pending\" status with a \"passing\" status check.

"},{"location":"key-concepts/minimum-release-age/#configuration-options","title":"Configuration options","text":"

The following configuration options can be used to enable and tune the functionality of Minimum Release Age:

"},{"location":"key-concepts/minimum-release-age/#minimumreleaseagebehaviourtimestamp-optional-warning","title":"minimumReleaseAgeBehaviour=timestamp-optional warning","text":"

When Renovate runs with minimumReleaseAgeBehaviour=timestamp-optional, Renovate will log a warning, which is then also shown on the Dependency Dashboard.

This warning serves to inform users about at least one dependency not being able to adhere to the minimum release age due to the configuration.

In cases where this is not desired, you can remap the warning to a lower log level with logLevelRemap:

{\n  \"logLevelRemap\": [\n    {\n      \"matchMessage\": \"/Some .+ did not have a releaseTimestamp, but as we're running with minimumReleaseAgeBehaviour=timestamp-optional, proceeding/\",\n      \"newLogLevel\": \"info\"\n    }\n  ]\n}\n
"},{"location":"key-concepts/minimum-release-age/#faqs","title":"FAQs","text":""},{"location":"key-concepts/minimum-release-age/#where-does-the-release-timestamp-need-to-be-set","title":"Where does the release timestamp need to be set?","text":"

To prevent supply-chain attacks, Renovate requires that the registry/datasource provides the timestamp.

This ensures that a package maintainer cannot specify (maliciously or accidentally) a different timestamp to when the package was actually published.

Warning

For instance, a suggestion for the Docker ecosystem is to use the org.opencontainers.image.created image annotation. Unfortunately, the publisher controls this annotation, so could allow a maintainer to say that their image was published earlier than it had been to bypass Minimum Release Age restrictions.

As long as the registry/datasource provides the release timestamp, Renovate will add support for it.

"},{"location":"key-concepts/minimum-release-age/#my-package-manager-has-support-for-minimum-release-age-how-does-renovate-work-with-that-do-i-need-to-set-it-in-both","title":"My package manager has support for minimum release age, how does Renovate work with that? Do I need to set it in both?","text":"

We recommend specifying minimum release age in both your Renovate and package manager configuration.

Renovate's concept of minimumReleaseAge is set independently to your package manager's configuration, and is used by Renovate to decide whether to suggest dependency updates. A manager may read the minimum release age from the configuration of your package manager. If it does, Renovate uses the larger of that value and minimumReleaseAge. Setting minimumReleaseAge to null does not turn off the value from the configuration of your package manager.

When Renovate performs a dependency update, it may delegate to your package manager to update artifacts, such as the lockfile. In some cases, this can lead to a transitive dependency being introduced, which Renovate is not aware of, and so could lead to a dependency being introduced without Renovate's minimumReleaseAge check being followed.

To protect against this, it's recommended to ensure that your package manager configuration includes the relevant minimum release age checks, too.

There is ongoing work to integrate more closely with package manager checks to make sure that Renovate's minimum release age configuration is specified when calling package managers that support it. If you have a package manager you'd like supported, please raise a Suggest an Idea Discussion.

The table below lists the managers with a known integration, per package manager. Managers that are not listed do not integrate with the minimum release age of their package manager.

Manager Package manager Passed to the package manager Reads its setting Enforced in lock file maintenance Notes mise-en-place mise \u274c \u274c \u274c mise has its own minimum_release_age setting, which Renovate does not read yet. npm npm \u2705 \u274c \u274c Passes --before. Uses the older date if the repository .npmrc has a before setting. Skipped if the .npmrc has min-release-age. npm pnpm \u274c \u274c \u274c npm yarn \u274c \u274c \u274c PEP 621 pdm \u274c \u274c \u274c PEP 621 uv \u274c \u274c \u274c Poetry poetry \u2705>=2.4.0 \u274c \u274c Sets POETRY_SOLVER_MIN_RELEASE_AGE, rounded up to whole days. Older Poetry versions ignore it."},{"location":"key-concepts/minimum-release-age/#npm","title":"npm","text":"

When minimumReleaseAge is configured, Renovate passes --before=<date> to npm commands during lock file generation. This ensures that npm only resolves package versions that were available before the cooldown threshold, protecting against newly published (and potentially malicious) transitive dependencies.

The --before date is calculated as now - minimumReleaseAge. If a before=<date> or min-release-age=<days> setting already exists in the project's .npmrc, Renovate uses the stricter (older) of the two dates.

If the existing lock file contains packages published after the --before cutoff (for example, from dependencies merged before minimumReleaseAge was configured), npm will fail with an ETARGET error. In this case, Renovate automatically retries without --before and logs a warning. This ensures existing lock files are never broken by the --before flag.

After the next lock file maintenance run (which regenerates the lock file from scratch with --before), subsequent updates will fully enforce the minimumReleaseAge constraint.

"},{"location":"key-concepts/minimum-release-age/#poetry","title":"Poetry","text":"

When minimumReleaseAge is configured, Renovate sets the POETRY_SOLVER_MIN_RELEASE_AGE environment variable when running poetry update --lock. This ensures that Poetry only resolves package versions that are at least as old as the cooldown threshold. Poetry added this setting in v2.4.0, and older versions ignore it.

The value is calculated as ceil(minimumReleaseAge / 1 day) and passed as an integer number of days.

"},{"location":"key-concepts/minimum-release-age/#what-happens-if-the-datasource-andor-registry-does-not-provide-a-release-timestamp-when-using-minimumreleaseage","title":"What happens if the datasource and/or registry does not provide a release timestamp, when using minimumReleaseAge?","text":"

Warning

Renovate 42 changed the behaviour detailed below. In Renovate 42, the absence of a release timestamp will be treated as if the release is not yet past the timestamp, which provides a safer default. Prior to Renovate 42, we would treat the dependency without a release timestamp as if it has passed the minimumReleaseAge, and will immediately suggest that dependency update. If using Renovate prior you can opt into the more secure behaviour (which is default in Renovate 42) by using minimumReleaseAgeBehaviour=timestamp-required (added in 41.150.0)

Consider that:

Renovate will create a PR for the 1 dependency update that has passed the release timestamp, and the others will be marked as \"Pending Status Checks\" on the Dependency Dashboard. As time goes on, if the 2 updates with a release timestamp are now passed the minimum release age, Renovate will add them to the PR (or create a new one).

"},{"location":"key-concepts/minimum-release-age/#what-happens-when-an-update-is-not-yet-passing-the-minimum-release-age-checks","title":"What happens when an update is not yet passing the minimum release age checks?","text":"

Renovate will decide whether it will create a branch for a dependency update using internalChecksFilter.

"},{"location":"key-concepts/minimum-release-age/#internalchecksfilterstrict","title":"internalChecksFilter=strict","text":"

If you have not configured internalChecksFilter, Renovate will use internalChecksFilter=strict as the default.

This will make sure that branches are not created if the minimumReleaseAge status check, renovate/stability-days, does not pass.

Debug logs example when internalChecksFilter=strict 
DEBUG: Branch renovate/actions-checkout-5.x creation is disabled because internalChecksFilter was not met (repository=..., branch=renovate/actions-checkout-5.x)\n

In this case, no branch is created.

If you have a Dependency Dashboard enabled, it will be found in the Dependency Dashboard in the \"Pending Status Checks\".

You can force the dependency update by requesting it via the Dependency Dashboard, or if you are self-hosting, you can use the checkedBranches to force the branch creation.

Note

A previous version of the documentation (up until Renovate 42.19.9) recommended configuring prCreation. This is no longer the case.

If no branch is created, Renovate will not raise a PR, regardless of prCreation's settings.

"},{"location":"key-concepts/minimum-release-age/#recommended-settings","title":"Recommended settings","text":"

The recommendation is to set internalChecksFilter=strict when using minimumReleaseAge, so Renovate will create neither branches (nor PRs) on updates that haven't yet met minimum release age checks.

"},{"location":"key-concepts/minimum-release-age/#which-update-types-take-minimumreleaseage-into-account","title":"Which update types take minimumReleaseAge into account?","text":"

Depending on your manager, datasource and the given package(s), it may be that some updates provide a release timestamp that can have minimumReleaseAge enforced.

Update Type Supports minimumReleaseAge? Notes major \u2705 Depends on the Manager, Datasource, and package(s) minor \u2705 Depends on the Manager, Datasource, and package(s) patch \u2705 Depends on the Manager, Datasource, and package(s) pin \u274c Not yet supported digest \ud83d\udfe1 Depends on the Manager, Datasource, and package(s). See below for more info. pinDigest \ud83d\udfe1 Depends on the Manager, Datasource, and package(s). See below for more info. lockFileMaintenance \u274c It can only be enforced by your package manager. See below for more info. lockfileUpdate \u274c rollback \u274c bump \u274c replacement \u274c Not yet supported

You can validate which update types may have release timestamps by following something similar to how verify if the registry you're using.

"},{"location":"key-concepts/minimum-release-age/#digest-updates","title":"digest updates","text":"

A digest update repoints an existing digest - usually a sha256:... Docker image digest, or the commit a floating tag like v7 points to - at whatever the current version resolves to now.

For instance:

   steps:\n-    - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7\n+    - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7\n

In this case, the version v7 is not updated, but the digest is. When Renovate resolves this update, it looks for the newest version matching the current value (which would be the v7.0.1 version in this case), and then ages the update against the release timestamp for this new version.

Warning

Most registries do not expose when a digest itself was published, so to determine the Minimum Release Age cutoff, we age against the release timestamp of the matched version. The strength of the guarantee depends on what that timestamp means for your datasource.

What this means in practice:

"},{"location":"key-concepts/minimum-release-age/#pindigest-updates","title":"pinDigest updates","text":"

A pinDigest update (enabled via pinDigests) pins an existing versioned tag to its currently resolved digest, without changing the tag itself.

For instance:

-    - uses: actions/checkout@v7\n+    - uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7\n

Unlike a digest update, pinDigest doesn't repoint the reference to a different value - it freezes whatever the current value already resolves to. The reference itself (e.g. the v7 major tag above) is floating though, so what it resolves to right now may not be what currentVersion would resolve to under your configured rangeStrategy (for example, rangeStrategy=bump resolves currentVersion to the oldest matching release). So, like digest, a pinDigest update is aged against the release timestamp of the newest version matching the current value, not whatever currentVersion resolves to.

Unlike digest updates, an unversioned current value (such as latest) is exempt from minimumReleaseAge entirely, rather than being held indefinitely: pinning a reference which already floats to the latest content is strictly safer than leaving it unpinned, so holding it back would only prolong the less-safe, unpinned state.

If the current value does resolve to a version, but that version's datasource doesn't expose a release timestamp (for example GHCR, Quay or ECR), the same caveats as digest updates apply: the update is held indefinitely under the default minimumReleaseAgeBehaviour=timestamp-required, and needs minimumReleaseAgeBehaviour=timestamp-optional configured to raise it without an age check.

"},{"location":"key-concepts/minimum-release-age/#avoiding-pindigest-updates-not-being-raised-due-to-frequently-releasing-packages","title":"Avoiding pinDigest updates not being raised due to frequently-releasing packages","text":"

Because a pinDigest update ages against the newest matching version, a reference that releases faster than your configured minimumReleaseAge may never clear the check - leaving it perpetually unpinned, which is less safe than pinning to a slightly-stale release.

In particular, because Renovate raises a pinDigest PR across all applicable dependencies (by grouping them together), this can lead to the whole pinDigest update group being delayed.

Renovate does not fall back to pinning an older, already-aged release instead: doing so would mean the pin no longer reflects what the reference currently, genuinely points to, which is the property pinDigest exists to preserve.

If you want Renovate to raise pinDigest updates sooner than your regular version/digest updates, scope a shorter (or disabled) minimumReleaseAge to it specifically, using packageRules and matchUpdateTypes:

{\n  \"packageRules\": [\n    {\n      \"matchUpdateTypes\": [\"pinDigest\"],\n      \"minimumReleaseAge\": null\n    }\n  ]\n}\n

This decouples \"how fresh must a release be before I trust it enough to upgrade to it\" (your regular minimumReleaseAge) from \"how long to wait before freezing whatever's already there\" (the pinDigest-scoped override) - the same idea as using digest.minimumReleaseAge:

{\n  \"digest\": {\n    \"minimumReleaseAge\": null\n  }\n}\n

These are functionally identical options.

"},{"location":"key-concepts/minimum-release-age/#lockfilemaintenance-updates","title":"lockFileMaintenance updates","text":"

Lock file maintenance delegates to the package manager to update package(s), so the updated packages have no release timestamp for Renovate to check.

A manager can tell Renovate that its package manager enforces the minimum release age itself while it regenerates the lock file. In that case, Renovate does not wait for a release timestamp, and the renovate/stability-days status check of the lock file maintenance branch passes straight away.

For all other managers, lock file maintenance is treated like any other update without a release timestamp. With the default minimumReleaseAgeBehaviour=timestamp-required, the renovate/stability-days status check stays pending while minimumReleaseAge is set. The security:minimumReleaseAge* presets set minimumReleaseAge=null for lock file maintenance, so these branches are not held back.

"},{"location":"key-concepts/minimum-release-age/#what-happens-to-security-updates","title":"What happens to security updates?","text":"

Security updates bypass any minimumReleaseAge checks, and so will be raised as soon as Renovate detects them.

"},{"location":"key-concepts/minimum-release-age/#what-happens-if-a-package-has-multiple-updates-available","title":"What happens if a package has multiple updates available?","text":"

Note

This is based on the recommended settings above

Renovate waits for the set duration to pass for each separate version.

If Renovate sees that a package has multiple updates available, it will only raise update(s) that are passing the minimumReleaseAge check.

Let us consider a repository with minimumReleaseAge=1 hour, and with the following timeline:

"},{"location":"key-concepts/minimum-release-age/#what-happens-to-transitive-dependencies","title":"What happens to transitive dependencies?","text":"

Renovate does not currently manage any transitive dependencies - instead leaving that to package managers and lockFileMaintenance.

"},{"location":"key-concepts/minimum-release-age/#how-do-i-opt-out-dependencies-from-minimum-release-age-checks","title":"How do I opt out dependencies from minimum release age checks?","text":"

To opt out a dependency from minimum release age checks, create a package rule with minimumReleaseAge=null:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"extends\": [\n    // for instance\n    \"security:minimumReleaseAgeNpm\",\n  ],\n  \"packageRules\": [\n    {\n      \"description\": \"Disable minimum release age checks for internal dependencies\",\n      \"matchPackageNames\": [\"@super-secret-organisation/*\"],\n      \"minimumReleaseAge\": null,\n    },\n  ],\n}\n

Note

As of Renovate 42.19.5, using minimumReleaseAge=0 days is treated the same as minimumReleaseAge=null.

"},{"location":"key-concepts/minimum-release-age/#which-datasources-support-release-timestamps","title":"Which datasources support release timestamps?","text":"

The datasource that Renovate uses must have a release timestamp for the minimumReleaseAge config option to work. Some datasources may have a release timestamp, but in a format Renovate does not support. In those cases a feature request needs to be implemented.

The table below lists every datasource Renovate supports, and whether it provides a release timestamp.

Datasource Supports release timestamp? Notes Apk \ud83d\udfe0Maybe1 The release timestamp is determined from the buildDate field in the results. Artifactory \ud83d\udfe0Maybe1 The release timestamp is determined from the date-like text, next to the version hyperlink tag in the results. Aws Eks Addon \u274c Aws Machine Image \ud83d\udfe0Maybe1 The release timestamp is determined from the CreationDate field in the results. Aws Rds \u274c Azure Bicep Resource \u274c Azure Pipelines Tasks \u274c Azure Tags \u274c Bazel \u274c Bitbucket Server Tags \u274c Bitbucket Tags \ud83d\udfe0Maybe1 The release timestamp is determined from the date field in the results. Bitrise \ud83d\udfe0Maybe1 The release timestamp is determined from the published_at field in the results. Buildpacks Registry \ud83d\udfe0Maybe1 The release timestamp is determined from the published_at field in the results. Cdnjs \u274c Clojure \ud83d\udfe0Maybe1 The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Conan \u274c Conda \ud83d\udfe0Maybe1 The release timestamp is determined from the upload_time field of the files of a version when using the Anaconda.org API, or from the createdAt field of the variants of a version when using prefix.dev. All files of a version are assumed to be published at roughly the same time. Cpan \ud83d\udfe0Maybe1 The release timestamp is determined from the date field in the results. Crate \ud83d\udfe0Maybe1 The release timestamp is determined from pubtime field from crates.io index if available, or version.created_at field from crates.io API otherwise. Custom \u274c Dart \ud83d\udfe0Maybe1 The release timestamp is determined from the published field in the results. Dart Version \u274c Deb \u274c Deno \ud83d\udfe0Maybe1 The release timestamp is determined from the uploaded_at field in the results. Devbox \ud83d\udfe0Maybe1 Docker \ud83d\udfe0Maybe1 Only supported on Docker Hub: The release timestamp is determined from the tag_last_pushed field in the results. NOTE: Currently, digests will receive the same release timestamp as the tag_last_pushed, which means that digests may appear newer than they are - see https://github.com/renovatebot/renovate/issues/38659 Dotnet Version \ud83d\udfe0Maybe1 The release timestamp is determined from the release-date field in the results. Elm Package \ud83d\udfe0Maybe1 The release timestamp is determined from the Unix timestamp in the results. Endoflife Date \ud83d\udfe0Maybe1 The release timestamp is determined from the releaseDate field in the results. Flutter Version \ud83d\udfe0Maybe1 The release timestamp is determined from the release_date field in the results. Forgejo Releases \ud83d\udfe0Maybe1 The release timestamp is determined from the published_at field in the results. Forgejo Tags \ud83d\udfe0Maybe1 The release timestamp is determined from the created field in the results. Galaxy \ud83d\udfe0Maybe1 The release timestamp is determined from the created field in the results. Galaxy Collection \ud83d\udfe0Maybe1 The release timestamp is determined from the created_at field in the results. Git Refs \u274c Git Tags \u274c Gitea Releases \ud83d\udfe0Maybe1 The release timestamp is determined from the published_at field in the results. Gitea Tags \ud83d\udfe0Maybe1 The release timestamp is determined from the created field in the results. Github Digest \ud83d\udfe0Maybe1 The release timestamp is determined from the commit date. Github Release Attachments \ud83d\udfe0Maybe1 The release timestamp is determined from the releaseTimestamp field from the response. Github Releases \ud83d\udfe0Maybe1 The release timestamp is determined from the releaseTimestamp field from the response. Github Runners \ud83d\udfe0Maybe1 The release timestamp is manually specified in Renovate's code, based on the date GitHub announced the runner image as generally available on their changelog Github Tags \ud83d\udfe0Maybe1 The get release timestamp is determined from the releaseTimestamp field in the results. Gitlab Packages \ud83d\udfe0Maybe1 The release timestamp is determined from the created_at field in the results. Gitlab Releases \ud83d\udfe0Maybe1 The release timestamp is determined from the released_at field in the results. Gitlab Tags \ud83d\udfe0Maybe1 To get release timestamp we use the created_at field from the response. Glasskube Packages \u274c Go \ud83d\udfe0Maybe1 If the release timestamp is not returned from the respective datasoure used to fetch the releases, then Renovate uses the Time field in the results instead. For modules hosted on GitHub, a later GitHub Release publication time or git tag creation time takes precedence over both. Golang Version \ud83d\udfe0Maybe1 The release timestamp is determined from the Date field in the results. Gradle Version \ud83d\udfe0Maybe1 The release timestamp is determined from the buildTime field in the results. Hackage \u274c Helm \ud83d\udfe0Maybe1 The release timstamp is determined from the created field in the results. Hermit \u274c Hex \ud83d\udfe0Maybe1 The release timestamp is determined the inserted_at field in the results. Hexpm Bob \ud83d\udfe0Maybe1 The release timestamp is determined from the buildDate field in the results. Java Version \u274c Jenkins Plugins \ud83d\udfe0Maybe1 The releaseTimestamp is determined from the releaseTimestamp or buildDate field in the results. Jsr \ud83d\udfe0Maybe1 The release timestamp is determined from the createdAt field in the results. For packages without explicit timestamps, defaults to 2025-09-18. Julia General Metadata \ud83d\udfe0Maybe1 The release timestamp is determined from the registered field in the results. Kubernetes Api \u274c Maven \ud83d\udfe0Maybe1 The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Nextcloud \u274c Node Version \ud83d\udfe0Maybe1 The release timestamp is determined from the date field. Npm \ud83d\udfe0Maybe1 The release timestamp is determined from the time field in the results. Nuget \ud83d\udfe0Maybe1 For the v2 API, the release timestamp is determined from the Published tag. And, for the v3 API, the release timestamp is determined from the published field in the results. Orb \ud83d\udfe0Maybe1 The release timestamp is determined from the created_at field in the results. Packagist \ud83d\udfe0Maybe1 The release timestamp is determined from the time field in the results. Pod \u274c Puppet Forge \ud83d\udfe0Maybe1 The release timestamp is determined from the created_at field from the response. Pypi \ud83d\udfe0Maybe1 The release timestamp is determined from the earliest upload_time field of the files of a version. When using the Simple API, timestamps are available if the server supports the JSON-based Simple API (PEP 691). Python Version \u274c Repology \u274c Rpm \u274c Ruby Version \ud83d\udfe0Maybe1 The release timestamp is determined from the release-list table in the results. Rubygems \ud83d\udfe0Maybe1 The release timestamp is determined from the created_at field in the results. Rust Version \ud83d\udfe0Maybe1 The release timestamp is parsed from the release manifest URL. Sbt Package \ud83d\udfe0Maybe1 The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Sbt Plugin \u274c Terraform Module \ud83d\udfe0Maybe1 For registry.terraform.io and registry.opentofu.org (via api.opentofu.org), release timestamps are available for all versions. For app.terraform.io, only the latest version is annotated, using the published_at field from the extended module endpoint. Terraform Provider \ud83d\udfe0Maybe1 The release timestamp is only available for registry.terraform.io (v2 API) and registry.opentofu.org (via api.opentofu.org). Other registries using the Provider Registry Protocol do not provide timestamps. Typst \u274c Unity3d \ud83d\udfe0Maybe1 The release timestamp is determined from the releaseDate field in the results. Unity3d Packages \u274c

1 Whether release timestamps are actually available depends on the registry you use - check Which registries support release timestamps?.

"},{"location":"key-concepts/minimum-release-age/#which-registries-support-release-timestamps","title":"Which registries support release timestamps?","text":"

The below is a non-exhaustive list of public registries which support release timestamps:

Datasource Registry URL Supported Notes crate https://crates.io \u2705 rubygems https://rubygems.org \u2705 docker https://index.docker.io \u2705 docker (not Docker Hub) \u274c Issue docker https://ghcr.io \u274c Issue docker https://quay.io \u274c Issue github-releases https://github.com \u2705 terraform-module https://registry.terraform.io \u2705 terraform-module https://registry.opentofu.org \u2705 Queries api.opentofu.org for release timestamps terraform-provider https://registry.terraform.io \u2705 terraform-provider https://registry.opentofu.org \u2705 Queries api.opentofu.org for release timestamps github-tags https://github.com \u2705 go https://proxy.golang.org, \u2705 golang-version https://raw.githubusercontent.com/golang/website \u2705 maven https://repo1.maven.org/maven2 \u2705 node-version https://nodejs.org/dist \u2705 npm https://registry.npmjs.org \u2705 nuget https://api.nuget.org/v3/index.json \u2705 pypi https://pypi.org/pypi/ \u2705 ruby-version https://www.ruby-lang.org \u2705 jsr https://jsr.io \u2705 For packages without explicit timestamps, defaults to 2025-09-18

It is likely that if you are using a public registry (i.e. registry.npmjs.org, repo1.maven.org, etc) the release timestamp data will be present. We welcome user contributions to this table.

If you use a custom registry, for instance as a pull-through cache, additional configuration may be required.

If you are using a custom registry, or unsure about a public registry, you can confirm this using Renovate's debug logs by looking for the packageFiles with updates debug log line, which may contain a releaseTimestamp field in dependency updates:

packageFiles with updates debug log example 
DEBUG: packageFiles with updates\n{\n  \"baseBranch\": \"main\",\n  \"config\": {\n    \"dockerfile\": [\n      {\n        \"deps\": [\n          // NOTE that we're not seeing a release timestamp for this Docker digest\n          {\n            \"depName\": \"ghcr.io/renovatebot/base-image\",\n            \"packageName\": \"ghcr.io/renovatebot/base-image\",\n            \"currentValue\": \"10.67.5\",\n            \"currentDigest\": \"sha256:d67e849707f38e11c8674a59d3fffef1ea6977757f3a65d9d1a3a198bdd160cf\",\n            \"replaceString\": \"ghcr.io/renovatebot/base-image:10.67.5@sha256:d67e849707f38e11c8674a59d3fffef1ea6977757f3a65d9d1a3a198bdd160cf\",\n            \"autoReplaceStringTemplate\": \"{{depName}}{{#if newValue}}:{{newValue}}{{/if}}{{#if newDigest}}@{{newDigest}}{{/if}}\",\n            \"datasource\": \"docker\",\n            \"depType\": \"stage\",\n            \"updates\": [\n              {\n                \"bucket\": \"major\",\n                \"newVersion\": \"11.40.5\",\n                \"newValue\": \"11.40.5\",\n                \"newMajor\": 11,\n                \"newMinor\": 40,\n                \"newPatch\": 5,\n                \"updateType\": \"major\",\n                \"isBreaking\": true,\n                \"newDigest\": \"sha256:81bbc8c8c561f6c4c2d059a5bcdfc95ef837682a41ac45bfbc1380d8d07dc941\",\n                \"branchName\": \"renovate/main-ghcr.io-renovatebot-base-image-11.x\"\n              }\n            ],\n          }\n      // ...\n    ],\n    \"github-actions\": [\n      {\n        \"deps\": [\n          // NOTE that we get a release timestamp for this GitHub Action major version bump, as well as the current version's timestamp\n          {\n            \"depName\": \"actions/setup-node\",\n            \"commitMessageTopic\": \"{{{depName}}} action\",\n            \"datasource\": \"github-tags\",\n            \"versioning\": \"docker\",\n            \"depType\": \"action\",\n            \"replaceString\": \"actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0\",\n            \"autoReplaceStringTemplate\": \"{{depName}}@{{#if newDigest}}{{newDigest}}{{#if newValue}} # {{newValue}}{{/if}}{{/if}}{{#unless newDigest}}{{newValue}}{{/unless}}\",\n            \"currentValue\": \"v4.4.0\",\n            \"currentDigest\": \"49933ea5288caeca8642d1e84afbd3f7d6820020\",\n            \"updates\": [\n              {\n                \"bucket\": \"major\",\n                \"newVersion\": \"v6.0.0\",\n                \"newValue\": \"v6.0.0\",\n                \"newDigest\": \"2028fbc5c25fe9cf00d9f06a71cc4710d4507903\",\n                \"releaseTimestamp\": \"2025-10-14T02:37:06.000Z\",\n                \"newVersionAgeInDays\": 10,\n                \"newMajor\": 6,\n                \"newMinor\": 0,\n                \"newPatch\": 0,\n                \"updateType\": \"major\",\n                \"isBreaking\": true,\n                \"libYears\": 0.5323368531202435,\n                \"branchName\": \"renovate/main-actions-setup-node-6.x\"\n              }\n            ],\n            \"packageName\": \"actions/setup-node\",\n            \"warnings\": [],\n            \"sourceUrl\": \"https://github.com/actions/setup-node\",\n            \"registryUrl\": \"https://github.com\",\n            \"mostRecentTimestamp\": \"2025-10-14T02:37:06.000Z\",\n            \"isAbandoned\": false,\n            \"currentVersion\": \"v4.4.0\",\n            \"currentVersionTimestamp\": \"2025-04-02T19:20:51.000Z\",\n            \"currentVersionAgeInDays\": 204,\n            \"isSingleVersion\": true,\n            \"fixedVersion\": \"v4.4.0\"\n          },\n

Given a log line such as \u261d\ufe0f you can also use the following jq query to identify any dependencies (or their updates) that are missing the currentVersionTimestamp or releaseTimestamp fields like so:

jq query 
# Code snippet licensed under the Apache-2.0, and co-authored-by: gpt-oss:20b\njq '\n{\n  # -------- missing currentVersionTimestamp ----------\n  missingCurrentVersionTimestamps: [\n    .config\n    | to_entries[] as $ent\n    | $ent.value[] as $group\n    | $group.deps[] as $dep\n    | select($dep.currentVersionTimestamp == null)\n    | {\n        manager: $ent.key,\n        depName: $dep.depName,\n        packageFile: $group.packageFile,\n        datasource: $dep.datasource,\n        registryUrls: (\n          ($dep.registryUrl? | if . != null then [.] else [] end)\n          + ($dep.registryUrls // [])\n        )\n      }\n  ],\n  # -------- missing releaseTimestamp in updates ----------\n  missingReleaseTimestamps: [\n    .config\n    | to_entries[] as $ent\n    | $ent.value[] as $group\n    | $group.deps[] as $dep\n    | select(any($dep.updates[]?; .releaseTimestamp == null))\n    | {\n        manager: $ent.key,\n        depName: $dep.depName,\n        packageFile: $group.packageFile,\n        datasource: $dep.datasource,\n        registryUrls: (\n          ($dep.registryUrl? | if . != null then [.] else [] end)\n          + ($dep.registryUrls // [])\n        ),\n        missingUpdates: [\n          $dep.updates[]?\n          | select(.releaseTimestamp == null)\n          | . + {\n              dependencyCurrentVersionTimestamp: $dep.currentVersionTimestamp,\n              datasource: $dep.datasource\n            }\n        ]\n      }\n  ]\n}\n' debug-log.txt\n

Will then output:

jq query output 
{\n  \"missingCurrentVersionTimestamps\": [\n    {\n      \"manager\": \"dockerfile\",\n      \"datasource\": \"docker\",\n      \"depName\": \"ghcr.io/containerbase/devcontainer\",\n      \"packageFile\": \".devcontainer/Dockerfile\",\n      \"registryUrls\": [\"https://ghcr.io\"]\n    },\n    {\n      \"manager\": \"renovate-config\",\n      \"datasource\": null,\n      \"depName\": \"renovatebot/.github\",\n      \"packageFile\": \"renovate.json\",\n      \"registryUrls\": []\n    },\n    {\n      \"manager\": \"regex\",\n      \"datasource\": \"docker\",\n      \"depName\": \"ghcr.io/renovatebot/base-image\",\n      \"packageFile\": \"lib/config/options/index.ts\",\n      \"registryUrls\": [\"https://ghcr.io\"]\n    }\n  ],\n  \"missingReleaseTimestamps\": [\n    {\n      \"manager\": \"dockerfile\",\n      \"datasource\": \"docker\",\n      \"depName\": \"ghcr.io/renovatebot/base-image\",\n      \"packageFile\": \"tools/docker/Dockerfile\",\n      \"registryUrls\": [\"https://ghcr.io\"],\n      \"missingUpdates\": [\n        {\n          \"bucket\": \"major\",\n          \"newVersion\": \"11.40.5\",\n          \"newValue\": \"11.40.5\",\n          \"newMajor\": 11,\n          \"newMinor\": 40,\n          \"newPatch\": 5,\n          \"updateType\": \"major\",\n          \"isBreaking\": true,\n          \"newDigest\": \"sha256:81bbc8c8c561f6c4c2d059a5bcdfc95ef837682a41ac45bfbc1380d8d07dc941\",\n          \"branchName\": \"renovate/main-ghcr.io-renovatebot-base-image-11.x\",\n          \"dependencyCurrentVersionTimestamp\": null,\n          \"dependencyDatasource\": \"docker\"\n        }\n      ]\n    },\n    {\n      \"manager\": \"dockerfile\",\n      \"datasource\": \"docker\",\n      \"depName\": \"ghcr.io/renovatebot/base-image\",\n      \"packageFile\": \"tools/docker/Dockerfile\",\n      \"registryUrls\": [\"https://ghcr.io\"],\n      \"missingUpdates\": [\n        {\n          \"bucket\": \"major\",\n          \"newVersion\": \"11.40.5\",\n          \"newValue\": \"11.40.5-full\",\n          \"newMajor\": 11,\n          \"newMinor\": 40,\n          \"newPatch\": 5,\n          \"updateType\": \"major\",\n          \"isBreaking\": true,\n          \"newDigest\": \"sha256:824737973a79d8c280f8ab1928017780fb936396dc83075a4f7770610eda37bd\",\n          \"branchName\": \"renovate/main-ghcr.io-renovatebot-base-image-11.x\",\n          \"dependencyCurrentVersionTimestamp\": null,\n          \"dependencyDatasource\": \"docker\"\n        }\n      ]\n    },\n    {\n      \"manager\": \"dockerfile\",\n      \"datasource\": \"docker\",\n      \"depName\": \"ghcr.io/renovatebot/base-image\",\n      \"packageFile\": \"tools/docker/Dockerfile\",\n      \"registryUrls\": [\"https://ghcr.io\"],\n      \"missingUpdates\": [\n        {\n          \"bucket\": \"major\",\n          \"newVersion\": \"11.40.5\",\n          \"newValue\": \"11.40.5\",\n          \"newMajor\": 11,\n          \"newMinor\": 40,\n          \"newPatch\": 5,\n          \"updateType\": \"major\",\n          \"isBreaking\": true,\n          \"newDigest\": \"sha256:81bbc8c8c561f6c4c2d059a5bcdfc95ef837682a41ac45bfbc1380d8d07dc941\",\n          \"branchName\": \"renovate/main-ghcr.io-renovatebot-base-image-11.x\",\n          \"dependencyCurrentVersionTimestamp\": null,\n          \"dependencyDatasource\": \"docker\"\n        }\n      ]\n    }\n  ]\n}\n

Notice that this indicates that:

"},{"location":"key-concepts/minimum-release-age/#how-do-i-add-timestamp-data-to-custom-registries","title":"How do I add timestamp data to custom registries?","text":"

Renovate requires release timestamp to be provided by the registry.

A common solution is to point Renovate to a registry that does have the release timestamp in the form that Renovate is expecting. You can achieve this by using packageRules to prepend the public registry's URL to the registryUrls.

You can see exact examples below:

"},{"location":"key-concepts/minimum-release-age/#maven-datasource","title":"Maven datasource","text":"

For minimumReleaseAge to work, the Maven source must return reliable last-modified headers.

If your custom Maven source registry is pull-through and does not support the last-modified header, like GAR (Google Artifact Registry's Maven implementation) then you can extend the Maven source registry URL with https://repo1.maven.org/maven2 as the first item. Then the currentVersionTimestamp via last-modified will be taken from Maven central for public dependencies.

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"maven\"],\n      \"registryUrls\": [\n        \"https://repo1.maven.org/maven2\",\n        \"https://europe-maven.pkg.dev/org-artifacts/maven-virtual\"\n      ]\n    }\n  ]\n}\n
"},{"location":"key-concepts/minimum-release-age/#pypi-datasource","title":"Pypi datasource","text":"
{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"pypi\"],\n      \"registryUrls\": [\n        \"https://pypi.org/pypi/\",\n        \"https://custom-registry.example.com/pypi/some-repo/simple/\"\n      ]\n    }\n  ]\n}\n
"},{"location":"key-concepts/presets/","title":"Presets","text":"

Renovate presets are reusable bits of configuration, stored in JSON, JSON5 or JSONC format.

Presets that are included with Renovate are referenced by their name, like :dependencyDashboard and security:minimumReleaseAgeNpm.

Custom presets are referenced by repository location. To learn how to create and host them, read the Shareable Config Presets page.

"},{"location":"key-concepts/presets/#why-you-should-use-presets","title":"Why you should use presets","text":"

Use presets to:

"},{"location":"key-concepts/presets/#how-to-use-presets","title":"How to use presets","text":"

Say you're using the config:recommended preset, and want to pin your GitHub Action digests. Instead of writing your own Renovate config, you search the docs, and find the helpers:pinGitHubActionDigests preset. Then you add the preset to the \"extends\" array in your Renovate configuration file:

{\n  \"extends\": [\"config:recommended\", \"helpers:pinGitHubActionDigests\"]\n}\n

In the example above, Renovate follows the rules from the config:recommended preset, plus the rules for helpers:pinGitHubActionDigests.

Tip

If there is a logical conflict between presets, then the last preset in the \"extends\" array \"wins\".

"},{"location":"key-concepts/presets/#managing-config-for-many-repositories","title":"Managing config for many repositories","text":"

If you manage the Renovate configuration for many repositories, we recommend that you:

  1. Create a global preset configuration
  2. Extend from the global preset in all of the repositories that should use your global preset as base

This way, when you want to change your global Renovate configuration, you only need to edit the global preset file.

"},{"location":"key-concepts/presets/#presets-are-modular","title":"Presets are modular","text":"

Preset configs are modular: a preset can be as small or large as you need. A preset can even extend from other presets.

"},{"location":"key-concepts/presets/#built-in-presets","title":"Built-in presets","text":"

Renovate comes with many built-in presets. We recommend you browse Renovate's default presets. Again, to use the preset: add it to the \"extends\" array in your Renovate config file.

"},{"location":"key-concepts/presets/#contributing-a-new-built-in-preset","title":"Contributing a new built-in preset","text":"

If you have a Renovate config that may help others, you can put it into Renovate's built-in presets. Read Contributing to presets to learn how.

"},{"location":"key-concepts/presets/#summary","title":"Summary","text":"

In short:

"},{"location":"key-concepts/pull-requests/","title":"Pull requests","text":"

This page describes how Renovate pull requests work.

"},{"location":"key-concepts/pull-requests/#how-renovate-finds-existing-prs","title":"How Renovate finds existing PRs","text":"

Renovate does not need to maintain any database/state about open or closed Pull Requests. Instead, it uses the code platform's APIs to search and find such PRs.

Renovate finds existing PRs (open or closed) by matching both:

In cases like the above, there is typically one existing PR with a matching branch name and PR title. But if you group PRs and use titles like \"All non-major updates\", then multiple past PRs may match.

"},{"location":"key-concepts/pull-requests/#normal-prs","title":"Normal PRs","text":"

As explained above, Renovate PRs normally have some \"uniqueness\" in their title relating to the version in the upgrade. When you close a \"unique\" PR, Renovate assumes you don't want to see that PR again in future, for example:

  1. You ignored lodash@4.17.21 by closing Renovate's PR
  2. Renovate assumes you don't want any updates to 4.17.21 of lodash
  3. Renovate creates a new PR when the branch + title \"uniqueness\" exists again, like when lodash@4.17.22 releases

Renovate behaves similarly for major updates, for example:

  1. You ignored a major update for Lodash (pr title: \"Update lodash to v4\") by closing Renovate's PR
  2. Renovate assumes you don't want any updates to v4 of lodash
  3. Renovate won't create any update PRs for v4 of lodash, even if there are newer versions of v4
"},{"location":"key-concepts/pull-requests/#immortal-prs","title":"Immortal PRs","text":"

Some Renovate pull requests have a section like this:

\ud83d\udc7b Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

An immortal PR keeps popping up again after you close it.

This document explains why we have immortal PRs, and how you can fix them.

"},{"location":"key-concepts/pull-requests/#why-we-have-immortal-prs","title":"Why we have immortal PRs","text":"

First off, we don't have immortal PRs for some philosophical reason like: \"don't ignore this update, it's good for you!\". We have no good way to ignore some PRs after they're closed.

"},{"location":"key-concepts/pull-requests/#branch-name-and-pr-title-are-cache-keys","title":"Branch name and PR title are cache keys","text":"

Renovate uses the branch name and PR title like a cache key. If the same key exists and the PR was closed, then we ignore the PR.

"},{"location":"key-concepts/pull-requests/#cache-keys-can-cause-problems","title":"Cache keys can cause problems","text":"

Let's say you have an \"All non-major updates\" PR. If you close the PR, and Renovate ignores it based on the PR title, then you would never get a non-major update again.

"},{"location":"key-concepts/pull-requests/#only-unique-version-prs-can-be-ignored","title":"Only unique version PRs can be ignored","text":"

Renovate can only ignore PRs if they have a unique version, like \"to v16.1.2\" or \"to v16\" in the title.

"},{"location":"key-concepts/pull-requests/#grouped-updates-with-different-versions","title":"Grouped updates with different versions","text":"

The problem comes when there are groups of updates which have different versions. Then the update becomes \"Update react (major)\", which is not safely ignorable, instead of \"Update react to v16\".

"},{"location":"key-concepts/pull-requests/#future-plans-for-immortal-prs","title":"Future plans for immortal PRs","text":"

In the future we may embed metadata in each PR identifying the exact files and packages + versions that PR contains. Then we could allow such PRs to be closed/ignored but then as soon as there's any chance to files/packages/versions being updated then we'd be cache busted and create a new PR. If you regularly wish to close immortal PRs, it's an indication that you may be grouping too widely.

"},{"location":"key-concepts/pull-requests/#how-to-fix-immortal-prs","title":"How to fix immortal PRs","text":"

Avoid grouping dependencies together which have different versions, or which you have a high chance of wanting to ignore. If you have immortal PRs which you want to keep closed, then set \"recreateWhen\": \"never\".

"},{"location":"key-concepts/pull-requests/#major-updates-require-dependency-dashboard-approval","title":"Major updates require Dependency Dashboard approval","text":"

Avoid grouping major upgrades together unless they are related dependencies. Instead, set \"dependencyDashboardApproval\": true for major updates so that you have control about when they are created.

"},{"location":"key-concepts/pull-requests/#abandoned-prs","title":"Abandoned PRs","text":"

Renovate normally cleans up its own branches and PRs once it decides they are no longer needed, for example after you merge or close a PR. Depending on the state of the branch, Renovate either autocloses the PR and deletes the branch, or, if the branch has been modified, flags the PR as abandoned.

If someone other than Renovate modified the branch, Renovate will not destroy that work by autoclosing the PR and deleting the branch.

Instead, Renovate flags the PR as abandoned by:

This tells you that Renovate no longer considers the branch or PR its own, and will not autoclose or delete it.

"},{"location":"key-concepts/pull-requests/#recommended-actions-for-abandoned-prs","title":"Recommended actions for abandoned PRs","text":"

Renovate will not rebase, update, or close an abandoned PR again, so you need to deal with it manually:

Related config option: pruneStaleBranches.

"},{"location":"key-concepts/pull-requests/#ignoring-prs","title":"Ignoring PRs","text":"

Close a Renovate PR to ignore it.

Note

Renovate re-creates any PRs that are marked \"immortal\". This means that any immortal PR you close, pops up again the next time Renovate runs. To ignore immortal PRs, follow the advice in the How to fix immortal PRs section.

"},{"location":"key-concepts/scheduling/","title":"Renovate scheduling","text":"

This document describes Renovate's scheduling.

"},{"location":"key-concepts/scheduling/#default-behavior","title":"Default behavior","text":"

On the backend side, Renovate runs as often as its administrator has configured Renovate to run. For example, the administrator configure Renovate to begin its runs hourly, daily, or outside office hours only. How often Renovate runs per-repository subsequently depends on how many repositories there are to check, and how many updates are pending for each repository at the time. If the backend configuration for Renovate means it runs scheduled jobs per-repo approximately every X hours, it is not possible for repository configuration to reduce that to less than X, or to force Renovate to run at exact times on specific repos.

"},{"location":"key-concepts/scheduling/#default-timezone","title":"Default timezone","text":"

By default, Renovate schedules use the UTC timezone. But you can set your own timezone with the timezone config option.

"},{"location":"key-concepts/scheduling/#how-long-renovate-takes-to-run-when-scheduled","title":"How long Renovate takes to run when scheduled","text":"

How often Renovate processes individual repositories depends on:

The table below shows how the number of dependencies and repositories affect Renovate run times.

Dependencies to update Repositories with the dependencies Run time 1 1 Very fast 1 10 Fast 1 100 Slow 50 1 Slow 100 100 Very slow"},{"location":"key-concepts/scheduling/#global-schedule-vs-specific-schedule","title":"Global schedule vs specific schedule","text":"

At a high level, you have two ways to schedule Renovate, a \"global way\" and a \"specific way\":

Way to schedule Renovate What this does Notes Global Decides when Renovate runs. This schedule is usually controlled by your organization's administrator. For the Mend Renovate app, Mend decides when Renovate runs. Specific When Renovate runs it checks the schedule to see if it should look for updates to a specific dependency. Usually set in the renovate.json config file, or similar config file.

Renovate can only update a dependency if both of these conditions are true:

"},{"location":"key-concepts/scheduling/#managing-update-frequency","title":"Managing update frequency","text":"

Because Renovate defaults to \"always on\" and \"open PRs right away\" it can overwhelm you with \"new PR\" notifications. Use the schedule to control when Renovate looks for updates, for example:

"},{"location":"key-concepts/scheduling/#scheduling-use-cases","title":"Scheduling use cases","text":"

You can use the scheduling tools to:

"},{"location":"key-concepts/scheduling/#customizing-the-schedule","title":"Customizing the schedule","text":"

Use the timezone and schedule configuration options to control when Renovate runs.

At a high level you need to follow these steps:

  1. Tell Renovate what timezone you want to use
  2. Learn about the scheduling syntax
  3. Optional set an \"in-repository schedule\"
  4. Optional set packageRules with a custom schedule for a package, or group of packages
"},{"location":"key-concepts/scheduling/#setting-your-timezone","title":"Setting your timezone","text":"

By default, Renovate's schedules use the UTC timezone.

If you want Renovate to use your local time, use the timezone configuration option. You must use a valid IANA time zone!

Setting a specific timezone in your local config file
{\n  \"timezone\": \"America/Los_Angeles\"\n}\n

Also read the timezone config option docs.

"},{"location":"key-concepts/scheduling/#scheduling-syntax","title":"Scheduling syntax","text":"

After you've set your local timezone, you can set \"days of the week\" or \"hours of the day\" in which Renovate is allowed to make changes.

"},{"location":"key-concepts/scheduling/#recommended-cron-syntax","title":"Recommended cron syntax","text":"

We recommend you use the cron syntax in your Renovate schedules.

Description Cron syntax every weekend * * * * 0,6 before 5:00am * 0-4 * * * after 10pm and before 5am every weekday * 22-23,0-4 * * 1-5 on friday and saturday * * * * 5,6 every 3 months on the first day of the month * * 1 */3 *

Note

For Cron schedules, you must use the * wildcard for the minutes value, as Renovate doesn't support minute granularity. And the cron schedule must have five parts.

"},{"location":"key-concepts/scheduling/#deprecated-breejslater-syntax","title":"Deprecated breejs/later syntax","text":"

This section explains the deprecated @breejs/later syntax. We plan to remove the @breejs/later library in a future major Renovate release if we can find a way to migrate all valid schedules to cron syntax. Due to this upcoming change, we strongly recommend you use cron schedules.

Renovate uses the @breejs/later library to parse the text. For Renovate to understand the schedule, you must use valid @breejs/later syntax. Read the @breejs/later parses docs at breejs.github.io for more details. The @breejs/later library also controls the interpretation of \"days\", time_before\", and \"time_after\" keywords.

Valid, but deprecated later syntax Cron syntax every weekend * * * * 0,6 before 5:00am * 0-4 * * * after 10pm and before 5am every weekday * 22-23,0-4 * * 1-5 on friday and saturday * * * * 5,6 every 3 months on the first day of the month * * 1 */3 *

Warning

Renovate does not support scheduled minutes or \"at an exact time\" granularity. Granularity must be at least one hour.

"},{"location":"key-concepts/scheduling/#in-repository-schedule-configuration","title":"In-repository schedule configuration","text":"

Important: when the Renovate process runs is usually controlled by the administrator, using tools such as cron. For the Mend Renovate App, the Mend maintainers control when the Renovate process runs, usually hourly.

If you control the hardware that Renovate runs on, we recommend you:

Some config examples:

Renovate should run each day before 4 am
{\n  \"description\": \"Schedule daily before 4 AM\",\n  \"schedule\": [\"* 0-3 * * *\"]\n}\n
Renovate should run outside of common office hours
{\n  \"description\": \"Schedule during typical non-office hours on weekdays (i.e., 10 PM - 5 AM) and anytime on weekends\",\n  \"schedule\": [\"* 0-4,22-23 * * 1-5\", \"* * * * 0,6\"]\n}\n
"},{"location":"key-concepts/scheduling/#schedule-presets","title":"Schedule presets","text":"

Renovate has built-in presets for common schedules, like \"once a week\", \"outside office hours\" and so on. Before you create your own custom schedule, check if the Schedule Presets has what you need.

The preset schedules only decide when Renovate looks for updates, and do not affect any specific dependencies/packages.

"},{"location":"key-concepts/scheduling/#schedule-when-to-update-specific-dependencies","title":"Schedule when to update specific dependencies","text":"

With Renovate's scheduling features you can \"limit the noise\" from frequently updating dependencies, like the AWS SDK:

Restrict AWS SDK to weekly updates
{\n  \"packageRules\": [\n    {\n      \"description\": \"Schedule AWS SDK updates on Sunday nights (9 PM - 12 AM)\",\n      \"matchPackageNames\": [\"@aws-sdk/*\"],\n      \"schedule\": [\"* 21-23 * * 0\"]\n    }\n  ]\n}\n

Important tips for the \"schedule\" property:

Read the schedule config option documentation to learn more.

"},{"location":"mend-hosted/credentials/","title":"Using secrets with Mend cloud Apps","text":"

The information on this page is for the Mend-hosted cloud apps:

If you self-host, you can skip reading this page.

"},{"location":"mend-hosted/credentials/#migrate-secrets-in-your-renovate-config-file","title":"Migrate secrets in your Renovate config file","text":"

The Mend Renovate cloud apps no longer read encrypted secrets from Renovate config files in your repositories. You must migrate any secrets you currently keep in a Renovate config file, and upload them as secrets to org or repo settings pages on developer.mend.io. To add secrets you must have admin-level rights.

Read Migrating encrypted secrets from Repo Config to App Settings to learn more.

"},{"location":"mend-hosted/credentials/#managing-secrets-via-the-web-ui","title":"Managing secrets via the Web UI","text":"

This section explains how to manage secrets for the Mend-hosted cloud apps via the Web UI.

Only administrators of an Org or Repo can manage the secrets for that Org or Repo.

"},{"location":"mend-hosted/credentials/#adding-a-secret-through-the-ui","title":"Adding a secret through the UI","text":"

To add a secret for the Mend cloud app:

  1. Go to the web UI at developer.mend.io.
  2. Open your organization/repository settings.

  3. Put the secret in the Credentials section:

  4. Reference the secret from Renovate config files inside the repo. Alternatively, you can use the Host Rules UI (see below).

    {\n  \"hostRules\": [\n    {\n      \"matchHost\": \"github.com\",\n      \"token\": \"{{ secrets.MY_ORG_SECRET }}\"\n    }\n  ]\n}\n
"},{"location":"mend-hosted/credentials/#adding-a-host-rule-through-the-ui","title":"Adding a host rule through the UI","text":"

You can centrally add/configure Host Rules through the Mend UI as an alternative to including them in Renovate presets.

  1. Open the Credentials section of the settings page for the relevant Org or Repo.

  2. Select ADD HOST RULE to open the \"Add a Host Rule\" dialog box.

  3. Fill out the details for your host rule.

    As an example, if you are a Bitbucket or Azure DevOps user, and you want to specify a github.com token to fetch release notes and enable github-based datasources, you could create a host rule like this:

"},{"location":"mend-hosted/credentials/#organization-secrets-vs-repository-secrets","title":"Organization secrets vs repository secrets","text":""},{"location":"mend-hosted/credentials/#secret-scope","title":"Secret scope","text":"

Secrets can be scoped to your organization or to your repository:

Secret scoped to your What will happen? Organization Secrets are inherited by all repositories in your organization Repository Secrets are referenced by that repository only"},{"location":"mend-hosted/credentials/#make-changes-on-the-right-page","title":"Make changes on the right page","text":"

The web UI has two settings pages. One page is for the organization, and the other page is for the repository.

Make sure you're making the changes on the right page!

"},{"location":"mend-hosted/credentials/#example","title":"Example","text":"

The screenshot shows inherited organization secrets and specific repository secrets.

"},{"location":"mend-hosted/credentials/#managing-organization-level-secrets","title":"Managing organization-level secrets","text":"

The Installed Repositories table means you are on your organization's page. Select the Settings button to manage your organization secrets:

"},{"location":"mend-hosted/credentials/#managing-repository-level-secrets","title":"Managing repository-level secrets","text":"

The Recent jobs table means you are on your repository's page. Select the Settings button to manage your repository secrets:

"},{"location":"mend-hosted/credentials/#automating-secrets-via-apis-github-only","title":"Automating secrets via APIs (GitHub only)","text":"

Administrators of GitHub organizations and repositories can use the Developer Platform APIs to manage secrets.

See the Developer Platform API documentation for details.

"},{"location":"mend-hosted/credentials/#authenticating-the-apis","title":"Authenticating the APIs","text":"

Calls to the APIs require authentication with a personal access token from the GitHub user making the request. The token must be included in the request header as the authorization property.

You can use a classic token or a fine-grained token. Mend recommends the use of fine-grained tokens for enhanced security.

"},{"location":"mend-hosted/credentials/#scopes-and-permissions-for-tokens","title":"Scopes and permissions for tokens","text":"

No additional scopes or permissions need to be added when calling APIs on public repositories. When calling APIs on private repositories, the following scopes and permissions are required:

"},{"location":"mend-hosted/credentials/#fine-grained-token-example","title":"Fine-grained token example","text":"

To create a fine-grained token for the APIs, follow these steps:

"},{"location":"mend-hosted/credentials/#known-issues","title":"Known Issues","text":""},{"location":"mend-hosted/credentials/#error-deleting-host-rule-from-developer-portal","title":"Error deleting host rule from Developer Portal","text":"

Problem: When deleting a host rule from the Developer Portal, an error is shown \"Error deleting host rule\".

Workaround: Update the host rule to point to a valid host that you are not using in your repo. This way, the host rule will have no effect.

"},{"location":"mend-hosted/environment-variables/","title":"Environment Variables","text":"

There are per-plan differences on what can be specified which you can see below.

"},{"location":"mend-hosted/environment-variables/#community-free-users-environment-variables","title":"Community (Free) users' environment variables","text":"

Community (Free) users can control anything that is repository config, via environment variables.

This, for instance, allows a more straightforward way to default minimumReleaseAge

"},{"location":"mend-hosted/environment-variables/#community-oss-users-environment-variables","title":"Community (OSS) users' environment variables","text":"

Community (OSS) projects have the same access as Community (Free) users.

"},{"location":"mend-hosted/environment-variables/#enterprise-and-mend-appsec-users-environment-variables","title":"Enterprise and Mend AppSec users' environment variables","text":"

If you are a paying Mend customer, in addition to being able to control repository config, you also have access to control the following environment variables:

Variable Config option RENOVATE_ALLOWED_COMMANDS allowedCommands RENOVATE_ALLOWED_ENV allowedEnv RENOVATE_ALLOWED_HEADERS allowedHeaders RENOVATE_ALLOWED_UNSAFE_EXECUTIONS allowedUnsafeExecutions RENOVATE_ALLOW_PLUGINS allowPlugins RENOVATE_ALLOW_SCRIPTS allowScripts RENOVATE_ALLOW_SHELL_EXECUTOR_FOR_POST_UPGRADE_COMMANDS allowShellExecutorForPostUpgradeCommands RENOVATE_CUSTOM_ENV_VARIABLES customEnvVariables RENOVATE_FORK_PROCESSING forkProcessing RENOVATE_INHERIT_CONFIG inheritConfig RENOVATE_INHERIT_CONFIG_FILE_NAME inheritConfigFileName RENOVATE_INHERIT_CONFIG_REPO_NAME inheritConfigRepoName RENOVATE_INHERIT_CONFIG_STRICT inheritConfigStrict RENOVATE_ONBOARDING_NO_DEPS onboardingNoDeps"},{"location":"mend-hosted/faq/","title":"Frequently Asked Questions","text":""},{"location":"mend-hosted/faq/#im-hitting-a-timeout-kernel-out-of-memory-limit-with-a-pnpmyarn-project","title":"I'm hitting a timeout / kernel-out-of-memory limit with a pnpm/yarn project","text":"

If you're seeing that your jobs are regularly hitting a timeout / kernel-out-of-memory, this might be due to a package manager trying to update a large set of dependencies.

On Mend-hosted apps, it is recommended to use the repo-level configuration, toolSettings.nodeMaxMemory, to tune the maximum memory available for the pnpm/yarn commands to use this.

Mend-hosted apps don't set a maximum allowed nodeMaxMemory, so you can use the upper limit of memory from your plan as the maximum limit.

It is recommended to set this between 1.5GB and 2.5GB but may require tweaking according to your repository.

Note

It is at the discretion of Mend to raise the memory limit for repositories, in a similar way to how there are increased resources for Open Source projects on Renovate Cloud.

"},{"location":"mend-hosted/faq/#how-can-i-run-arbitrary-commands-through-postupgradetasks","title":"How can I run arbitrary commands through postUpgradeTasks?","text":"

As noted in the postUpgradeTasks documentation, a self-hosted administrator must allowlist any arbitrary commands that can run on their deployment. This is to prevent both an \"insider attack\" and an \"outsider attack\" that may occur when arbitrary commands execute. ../configuration-options.md#toolsettingsnodemaxmemory

Often, Renovate is a central service within a company, where there is some level of trust in its users. However, with Mend-hosted Renovate we're hosting a mix of users on the public Internet that we can't necessarily trust.

Although we harden Mend-hosted infrastructure more than a typical Renovate deployment, we still do not allow arbitrary command execution through postUpgradeTasks. Depending on which plan of Renovate Cloud you're using, we may make it possible to allowlist command(s) you wish to run.

"},{"location":"mend-hosted/faq/#community-free-users","title":"Community (Free) users","text":"

Free users cannot modify nor request arbitrary commands for postUpgradeTasks.

"},{"location":"mend-hosted/faq/#community-oss-users","title":"Community (OSS) users","text":"

Trusted Open Source projects on the Community (OSS) plan can raise a Mend Hosted Request on our GitHub Discussions, requesting the allowlisting of a given command.

Acceptance is at the discretion of Mend.

"},{"location":"mend-hosted/faq/#enterprise-and-mend-appsec-users","title":"Enterprise and Mend AppSec users","text":"

If you are a paying Mend customer, you have access to control a number of self-hosted configuration options for Renovate.

One such variable is RENOVATE_ALLOWED_COMMANDS, which allows controlling the allowedCommands that a repository can run. By configuring this, you can allow commands to run in your repository.

These variables can be managed by a repository administrator, and can also be set on the organisation level.

There is a balance between ease of use and security - remember that allowlisting commands can lead to a malicious dependency then executing within your project (an \"outsider attack\").

We recommend you restrict this to a subset of commands that need to run:

RENOVATE_ALLOWED_COMMANDS=[\"^make tidy$\"]\n

However, note that by calling a make task, other arbitrary command execution can occur.

Tip

There is currently no validation pre-save to confirm if you're entering values that are valid Renovate configuration. After making a change to variable(s), we recommend triggering a new job to ensure that the job does not fail with config-validation.

"},{"location":"mend-hosted/faq/#what-environment-variables-can-i-set","title":"What environment variables can I set?","text":"

In June 2026, Mend allowed all repositories to be able to set environment variables, separate from repository secrets.

For more details, see the separate Environment Variables documentation page.

"},{"location":"mend-hosted/faq/#what-ip-addresses-are-used-by-mend-renovate-cloud","title":"What IP Addresses are used by Mend Renovate Cloud?","text":"

If you are looking at restricting access to your source code via IP allowlisting, you will need to know which public IPs Mend's Developer Platform accesses from.

These can be found documented on the Mend docs site under the developer-platform section.

"},{"location":"mend-hosted/github-com-token/","title":"Purpose of github.com Token","text":"

Users of Mend's Renovate apps on Bitbucket Cloud and Azure DevOps need to provide a github.com token to retrieve release notes and changelogs, plus some package files.

If github.com credentials are not provided, Renovate will continue to run, but with the following limitations:

"},{"location":"mend-hosted/github-com-token/#do-i-need-to-provide-a-githubcom-token","title":"Do I need to provide a github.com token?","text":""},{"location":"mend-hosted/github-com-token/#githubcom-cloud-users","title":"github.com (Cloud) users","text":"

If your repositories are hosted on github.com (Cloud) and you are using the Renovate App on GitHub, you do not need to provide a token for github.com because the Renovate App already has access to GitHub.

"},{"location":"mend-hosted/github-com-token/#bitbucket-and-azure-devops-users","title":"Bitbucket and Azure DevOps users","text":"

If your repositories are hosted on Bitbucket or Azure DevOps, you will need to provide a github.com token if you want your Renovate PRs to contain release notes and changelogs, or if you want updates on packages that live exclusively on github.com.

If the github.com token is not provided, a warning will be shown in the Developer Portal and in the Dependency Dashboard.

"},{"location":"mend-hosted/github-com-token/#how-to-provide-a-githubcom-token","title":"How to provide a github.com token","text":"

Renovate will accept a github.com token from any GitHub user. The token requires no special access or permissions.

"},{"location":"mend-hosted/github-com-token/#step-1-acquire-a-githubcom-token","title":"Step 1: Acquire a github.com token","text":"
  1. Log in to github.com (any user)
  2. Navigate to Personal access tokens in Developer settings
  3. Choose Generate new token (either fine-grained or classic)
  4. Provide a Token name (fine-grained) or Note (optional for classic token)
  5. Choose the expiration date. (No additional scopes or repository permissions are required.)
  6. Press Generate token
  7. Copy the token when it is presented on the screen

[!IMPORTANT]

Make sure to copy your personal access token now as you will not be able to see this again.

"},{"location":"mend-hosted/github-com-token/#step-2-add-the-token-to-the-orgrepo-credentials","title":"Step 2: Add the token to the Org/Repo credentials","text":"

Use the token generated in the previous step to provide a secret and host rule for the Org or Repos.

[!NOTE]

If a github.com token is added to the settings for an Org, Workspace or Project, the token will be inherited by all of its child repositories.

  1. Log in to Developer Portal
  2. Navigate to the Settings for an Org/Workspace/Project or a Repo
  3. Go to the Credentials settings page
  4. Choose ADD SECRET and create a secret to store the token
  5. Choose ADD HOST RULE and create a host rule for github

For more information about providing Secrets and Host Rules in the Developer Portal UI, see the documentation for Credentials.

"},{"location":"mend-hosted/hosted-apps-config/","title":"Mend-hosted Apps Configuration","text":"

This page:

Note

For general configuration of the Renovate CLI, read the main Configuration/Overview section.

"},{"location":"mend-hosted/hosted-apps-config/#finding-the-logs","title":"Finding the logs","text":"

The Renovate logs for the Mend-hosted apps are on the Mend Developer Portal.

Reading the logs can help you understand the configuration that Renovate used.

"},{"location":"mend-hosted/hosted-apps-config/#renovate-version","title":"Renovate Version","text":"

The Renovate version used by the Mend-hosted apps is updated manually by the maintainers of the app. The maintainers don't follow any release schedule or release cadence, but try to update at least once a week. This means the Mend Renovate App can lag a few hours to a week behind the open source version.

Major releases of Renovate are held back until the maintainers are reasonably certain it works for most users.

"},{"location":"mend-hosted/hosted-apps-config/#which-version-is-the-mend-renovate-app-using","title":"Which version is the Mend Renovate app using?","text":"

Follow these steps to see which version the Mend Renovate app used for a specific job:

  1. Sign in to the Mend Developer Portal with your GitHub or Bitbucket account
  2. Select your organization
  3. Select a installed repository
  4. Select a job from the Recent jobs overview
  5. Select the Info Log Level from the dropdown menu

  6. You should see something like this:

    INFO: Renovate started\n{\n  \"renovateVersion\": \"44.133.0\"\n}\n...\nINFO: Repository started\n{\n  \"renovateVersion\": \"44.133.0\"\n}\n

Tip

The PRs that Renovate creates have a link to the \"repository job log\" in the footer of the PR body text.

"},{"location":"mend-hosted/hosted-apps-config/#onboarding-behavior","title":"Onboarding behavior","text":""},{"location":"mend-hosted/hosted-apps-config/#installing-renovate-into-all-repositories-leads-to-silent-mode","title":"Installing Renovate into all repositories leads to silent mode","text":"

If an Organization installed Renovate with \"All repositories\" (instead of \"Selected repositories\"), then Renovate defaults to \"Silent\" mode (dryRun=lookup). We chose this behavior because:

"},{"location":"mend-hosted/hosted-apps-config/#why-we-call-this-silent-mode","title":"Why we call this silent mode","text":""},{"location":"mend-hosted/hosted-apps-config/#get-onboarding-prs-from-renovate-by-getting-out-of-silent-mode","title":"Get onboarding PRs from Renovate by getting out of silent mode","text":"

If Renovate is installed, and you can see a job log, but Renovate is not onboarding your repository: look for dryRun in the logs to confirm you are in Silent mode. To get a onboarding PR from Renovate, change to Interactive mode either at the Repository level or Organization level.

"},{"location":"mend-hosted/hosted-apps-config/#installing-renovate-into-selected-repositories-always-leads-to-onboarding-prs","title":"Installing Renovate into selected repositories always leads to onboarding PRs","text":"

Additionally, if an Organization is installed with \"Selected repositories\" then the app will change onboardingNoDeps to \"enabled\". This change causes Renovate to create an Onboarding PR, even if Renovate does not detect any dependencies.

"},{"location":"mend-hosted/hosted-apps-config/#fork-processing","title":"Fork Processing","text":"

If an Organization installs Renovate with the \"All repositories\" option, then forkProcessing will remain set to its default value disabled. This means forked repositories are not onboarded, Renovate ignores them. To change this behavior, push a renovate.json file to the repository with \"forkProcessing\": \"enabled\".

If an Organization installs Renovate with \"Selected repositories\", we assume the organization wants to onboard all of the selected repositories, even forked repositories. Therefore we set forkProcessing to \"enabled\".

"},{"location":"mend-hosted/hosted-apps-config/#inherited-config","title":"Inherited config","text":"

The Mend Renovate app automatically applies inherited config to all installed repositories in an organization, if these conditions are met:

  1. A repository called renovate-config exists in the same organization, and the organization has installed the Mend Renovate app. The repository does not need to be onboarded
  2. Renovate finds a file called org-inherited-config.json in the renovate-config repository

Tip

If you're an Enterprise customer on Mend-hosted apps, you can change these settings through their respective environment variables.

To avoid wasted API calls, Mend apps will enable inheritConfig in an org only when Renovate detects a commit for the inheritConfig file. This means the inheritConfig file will not be detected if the Mend Renovate app is not installed on the renovate-config repository at the time of adding or changing the file. If you have such a file but the Mend app has not enabled inheritConfig in your org, try pushing a commit to that file and wait a minute to see if Renovate detects the change.

"},{"location":"mend-hosted/hosted-apps-config/#default-presets","title":"Default presets","text":"

The Mend Renovate app automatically adds the mergeConfidence:all-badges preset to the extends array. If you do not want the Merge Confidence badges: add the mergeConfidence:all-badges preset to the ignorePresets array.

Additionally, the preset config:recommended is added to onboardingConfig.

"},{"location":"mend-hosted/hosted-apps-config/#allowed-post-upgrade-commands","title":"Allowed Post-upgrade commands","text":"

A limited set of approved postUpgradeTasks commands are allowed in the app. The commands are not documented, as they may change over time.

You can find the allowed postUpgradeTasks commands in Renovate's log output, when searching for a log line which references allowedCommands.

"},{"location":"mend-hosted/hosted-apps-config/#validating-configuration","title":"Validating configuration","text":"

As noted in Validation of Renovate config change PRs, Renovate will automagically validate your configuration changes when pushing to the \"reconfigure\" branch.

Tip

When using a Mend-hosted app, the \"reconfigure\" branch defaults to renovate/reconfigure.

When pushing to this specific branch name, Renovate will run its validation and report a status check to the Platform whether this passes/fails validation.

Note

The reconfigure branch must be pushed to the source repository that Renovate runs against, not a fork.

If you have a Pull Request open from this branch (including draft PRs), Renovate will comment on the PR to note:

For example, when failing validation:

And when the PR then passes validation:

"},{"location":"mend-hosted/job-scheduling/","title":"Job Scheduling & Renovate Status","text":"

Mend Renovate Cloud will automatically schedule Renovate jobs to be run on installed repos. When the scheduler runs, selected repositories are added to the Job Queue, and eventually executed by the job runners.

"},{"location":"mend-hosted/job-scheduling/#job-schedulers","title":"Job Schedulers","text":"

There are four types of job schedulers, each with a different frequency and selection of repositories.

Job Scheduler Frequency Renovate statuses Active jobs 4-hourly1 new, activated Inactive jobs Daily onboarded, onboarding, silent, failed Blocked Weekly timeout, resource-limit, kernel-out-of-memory, unknown All repos Monthly All installed repos (including disabled)

(1) Renovate Enterprise jobs are scheduled every hour for repositories on GitHub and Azure DevOps.

"},{"location":"mend-hosted/job-scheduling/#renovate-status","title":"Renovate Status","text":"

Each repository installed with Renovate Cloud has a Renovate Status. The Renovate Status is used by the job scheduler to determine which repositories will be selected. The status appears in the list of repositories shown on the Org page of the Developer Portal.

The table below describes all the Renovate statuses.

Renovate Status Description Schedule <-blank-> New repo. Renovate has never run on this repo. Hourly onboarding Onboarding PR has not been merged Daily onboarded Onboarding PR has been merged. No Renovate PRs merged Daily activated At least one Renovate PR has been merged Hourly silent Renovate will run, but not deliver PRs or issues Daily failed An error occurred while running the last job Daily timeout A timeout occurred while running the last job Weekly kernel-out-of-memory An OOM error occurred while running the last job Weekly resource-limit A resource limit was hit while running the last job Weekly unknown An unknown error occurred while running the last job Weekly disabled Renovate will not run on this repository Monthly 
flowchart TD\n    A[Installed Repository] --> B{Renovate Status}\n    B -->|<code>new</code>| C[Active jobs<br>4-hourly #40;1#41;]\n    B -->|<code>activated</code>| C\n    B -->|<code>onboarded</code>| D[Inactive jobs<br>Daily]\n    B -->|<code>onboarding</code>| D\n    B -->|<code>silent</code>| D\n    B -->|<code>failed</code>| D\n    B -->|<code>timeout</code>| E[Blocked jobs<br>Weekly]\n    B -->|<code>resource-limit</code>| E\n    B -->|<code>kernel-out-of-memory</code>| E\n    B -->|<code>unknown</code>| E\n    B -->|<code>disabled</code>| F[All repos<br>Monthly]\n    C --> G[Job Queue]\n    D --> G\n    E --> G\n    F --> G\n    G --> H[Job Runner]

1 Renovate Enterprise jobs are scheduled every hour for repositories on GitHub and Azure DevOps.

"},{"location":"mend-hosted/migrating-secrets/","title":"Migrating Secrets from Repo Config to App Settings","text":"

The Mend Renovate Cloud apps no longer read encrypted secrets from Renovate config files in your repositories. Previously, you could encrypt a secret with the Renovate encryption tool and then put it in your Renovate config file.

When using the Mend Renovate Cloud apps, all secrets must be stored in the App settings on the cloud. The secrets can be referenced from the Renovate config files inside the repo using {{ secrets.SECRET_NAME }} notation.

"},{"location":"mend-hosted/migrating-secrets/#old-method","title":"Old method","text":"

This method is deprecated:

Put encrypted secret in Renovate config
{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"github.com\",\n      \"encrypted\": {\n        \"token\": \"drsMDVf6M2hTZCN......+gQm/0Rpw\"\n      }\n    }\n  ]\n}\n
"},{"location":"mend-hosted/migrating-secrets/#new-method","title":"New method","text":"

This is the new method that you should start using:

Reference the app secret in the Renovate config
{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"github.com\",\n      \"token\": \"{{ secrets.GITHUB_COM_TOKEN }}\"\n    }\n  ]\n}\n
"},{"location":"mend-hosted/migrating-secrets/#tips","title":"Tips","text":""},{"location":"mend-hosted/migrating-secrets/#do-not-change-the-secret-during-migration","title":"Do not change the secret during migration","text":"

Mend recommends that you do not change the secret during the migration, as this introduces an extra point of failure. After the migration you can of course change/rotate the secret.

"},{"location":"mend-hosted/migrating-secrets/#migrate-your-secrets-in-the-raw-form-plain-text","title":"Migrate your secrets in the raw form (plain text)","text":"

When migrating secrets, DO NOT migrate the encrypted form of the secret. You must input the secret in the web UI from plain text. (The web UI will store the value securely.) If you do not have the original plain text form of the secret being migrated, you will need to create a new secret.

"},{"location":"mend-hosted/migrating-secrets/#how-to-migrate-secrets","title":"How to migrate secrets","text":""},{"location":"mend-hosted/migrating-secrets/#use-plain-text-values-not-encrypted-values","title":"Use Plain text values - not encrypted values","text":"

You must Migrate encrypted secrets using the PLAIN TEXT value. You can not use the encrypted version of the secret.

"},{"location":"mend-hosted/migrating-secrets/#add-the-secret-to-the-correct-org-or-repo","title":"Add the secret to the correct Org or Repo","text":"

When you migrate a secret from a repository, make sure you are adding the secret to the same organization or repository for which you generated the secret!

"},{"location":"mend-hosted/migrating-secrets/#steps-to-migrate-a-secret-to-the-renovate-cloud-app","title":"Steps to migrate a secret to the Renovate Cloud App","text":"

  1. Go to the correct settings page for your organization or repository in the web UI at developer.mend.io.

  2. On the Credentials page, select ADD SECRET to add the plaintext secret.

  3. Give a value for Secret name, paste the plaintext secret into the Secret Value field, and select SAVE.

  4. Wait for the confirmation dialog: \u201cSuccessfully stored secret\u201d.

"},{"location":"mend-hosted/migrating-secrets/#using-the-api","title":"Using the API","text":"

The Mend Developer Platform has an API, allowing programmatic management of repo secrets and org secrets.

"},{"location":"mend-hosted/migrating-secrets/#troubleshooting","title":"Troubleshooting","text":""},{"location":"mend-hosted/migrating-secrets/#secret-is-stored-successfully-but-it-doesnt-work-when-used-in-the-app","title":"Secret is stored successfully, but it doesn't work when used in the app","text":"

The secret might be wrong. Try uploading the secret again.

"},{"location":"mend-hosted/migrating-secrets/#related-links","title":"Related links","text":""},{"location":"mend-hosted/overview/","title":"Mend Renovate Cloud-hosted (Community and Enterprise)","text":"

Mend provides cloud hosting services for running Renovate in free and paid versions:

They are available for Git repositories hosted on the following cloud platforms:

Mend Renovate cloud will regularly schedule Renovate jobs against all installed repositories. It also listens to webhooks and enqueues a Renovate job when relevant changes occur in a repo, or when actions are triggered from the Renovate PRs or Dashboard issue. There is a web UI with functionality to view and interact with installed repositories, their jobs and job logs.

"},{"location":"mend-hosted/overview/#getting-started","title":"Getting started","text":"

To get started using Mend Renovate Cloud versions, access the Developer Portal at https://developer.mend.io/.

Developers can log in using the OAuth credentials from their cloud-based Git repository.

Features of the Developer Portal include:

"},{"location":"mend-hosted/overview/#plans","title":"Plans","text":""},{"location":"mend-hosted/overview/#mend-renovate-community-cloud","title":"Mend Renovate Community Cloud","text":"

A generous free tier, available for all across an unlimited number of public and private repositories.

"},{"location":"mend-hosted/overview/#mend-renovate-community-oss-cloud","title":"Mend Renovate Community (OSS) Cloud","text":"

As part of Mend's commitment to support the Open Source community, we provide an enhanced free offering for maintainers of the projects the ecosystem rely upon.

This offering provides increased resources and concurrency, as well as access to Merge Confidence Workflows to allow maintainers to more intelligently receive updates based on signals Mend collects from other projects.

Projects licensed under an Open Source Initiative (OSI) approved license can request increased resources on Mend Renovate Cloud under the Community (OSS) plan.

Tip

To request increased resources, create a Mend Hosted Request on the Renovate GitHub Discussions board. Acceptance is at the discretion of Mend.

"},{"location":"mend-hosted/overview/#mend-renovate-enterprise-cloud","title":"Mend Renovate Enterprise Cloud","text":"

Mend's premium offering for our Cloud product, with support, enhanced scalability and scheduling, and access to Merge Confidence Workflows.

Contact Mend at sales@mend.io for purchase details.

"},{"location":"mend-hosted/overview/#resources-and-scheduling","title":"Resources and Scheduling","text":"

The resources, scheduling and concurrency of Renovate jobs is determined by the Mend Renovate plan used by the Org, which can be seen below:

Mend Renovate Community Cloud Mend Renovate Community (OSS) Cloud Mend Renovate Enterprise Cloud Concurrent jobs per Org 1 2 16 Job scheduling (active repos) Every 4 hours Every 4 hours Hourly1 Job runner CPUs 1 vCPU 1 vCPU 2 vCPU Job runner Memory 3GB 6GB 8GB Job runner Disk space 15GB 25GB 40GB Job timeout 30 minutes 60 minutes 60 minutes Merge Confidence Workflows \u274c Not included \u2705 Included \u2705 Included Mend.io Helpdesk Support \u274c Not included \u274c Not included \u2705 Included

1 Bitbucket repositories running Mend Renovate Enterprise are scheduled to run every 4 hours, to avoid hitting rate limits on GitHub APIs.

"},{"location":"modules/","title":"Modules introduction","text":"

Renovate modules, please select a subsection.

"},{"location":"modules/#supported-modules","title":"Supported modules","text":""},{"location":"modules/datasource/","title":"Datasources","text":"

After Renovate's manager scanned the files and extracted the dependencies, it assigns a datasource to each extracted package file or dependency. The datasource tells Renovate how to search for new versions.

You don't need to configure or override datasources. But you may use datasources in a packageRules array to configure Renovate's behavior, for example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"npm\"],\n      \"matchPackageNames\": [\"lodash\"],\n      \"automerge\": true\n    }\n  ]\n}\n
"},{"location":"modules/datasource/#supported-datasources","title":"Supported Datasources","text":"

Supported values for datasource are:

"},{"location":"modules/datasource/apk/","title":"Apk Datasource","text":""},{"location":"modules/datasource/apk/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier apk Default versioning apk Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the buildDate field in the results. Source URL support No"},{"location":"modules/datasource/apk/#description","title":"Description","text":"

The APK datasource is designed to work with Alpine Linux package repositories. It can fetch package information from APK repositories and provide version updates for Alpine Linux packages.

Alpine Linux uses the APK package manager, and packages are distributed through repositories. Each repository contains an APKINDEX.tar.gz file that contains metadata about all available packages.

Files are typically located in this structure:

https://dl-cdn.alpinelinux.org/alpine/v3.19/main/x86_64/APKINDEX.tar.gz\nhttps://dl-cdn.alpinelinux.org/alpine/v3.19/community/x86_64/APKINDEX.tar.gz\n
"},{"location":"modules/datasource/apk/#set-url-when-using-an-apk-repository","title":"Set URL when using an APK repository","text":"

To use an APK repository with the datasource, you must set a properly formatted URL with specific query parameters as registryUrl:

Note

Renovate does not fetch the registryUrl as-is. It combines the base URL with these parameters to build the actual index URLs, for example <base>/<branch>/<component>/<arch>/APKINDEX.tar.gz. Only the parameters above are accepted, so that a typo fails loudly instead of being ignored.

Examples:

https://dl-cdn.alpinelinux.org/alpine?branch=v3.19&components=main,community&arch=x86_64\nhttps://packages.wolfi.dev/os?arch=x86_64\n

The first URL points to the v3.19 branch of the Alpine repository for the x86_64 architecture, including the main and community components. Renovate looks up the package in every component you list, and aggregates the releases it finds.

The second URL points to the Wolfi repository, which has no branch or component in its path.

"},{"location":"modules/datasource/apk/#how-renovate-builds-the-index-urls","title":"How Renovate builds the index URLs","text":"

Say you set this registryUrl in your Renovate config:

Set the apk registryUrl in renovate.json
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"apk\"],\n      \"registryUrls\": [\n        \"https://dl-cdn.alpinelinux.org/alpine?branch=v3.19&components=main,community&arch=x86_64\"\n      ]\n    }\n  ]\n}\n

Renovate then fetches one index per component:

https://dl-cdn.alpinelinux.org/alpine/v3.19/main/x86_64/APKINDEX.tar.gz\nhttps://dl-cdn.alpinelinux.org/alpine/v3.19/community/x86_64/APKINDEX.tar.gz\n
"},{"location":"modules/datasource/apk/#versioning","title":"Versioning","text":"

This datasource uses apk versioning by default, which follows Alpine's version format (3.2.1-r0, 2.39.0_rc1-r0, 6.5_p20250503-r0) and understands APK's version constraints.

This means a currentValue may be a constraint rather than a plain version, e.g. =~8.12.1 to accept any 8.12.1-rN. Read the apk versioning docs for the operators it supports.

Depending on which APK repository you are using, you may want to use the loose versioning scheme, like so:

Specify loose versioning for apk lookups
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"apk\"],\n      \"versioning\": \"loose\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/apk/#dockerfile-support","title":"Dockerfile support","text":"

When using distributions built on apk packages, it is common to use a version pin for your packages, like so:

FROM alpine:3.18\nRUN apk add --no-cache bash=5.2.37-r2\n

This provides reproducibility in the case that the upstream package updates under you.

The dockerfile manager extracts these packages, allowing updates to them directly, without needing a Custom Manager.

The dockerfile manager does not work out a registryUrl from your base image, so it skips these packages with skipReason: unknown-registry rather than look them up against a registry which may hold versions your image cannot install. Set the registryUrls which match your base image with a packageRules entry to have them looked up.

Override apk registryUrl with a packageRules entry
{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"Dockerfile\"],\n      \"matchDatasources\": [\"apk\"],\n      \"matchPackageNames\": [\"nginx\"],\n      \"registryUrls\": [\n        \"https://dl-cdn.alpinelinux.org/alpine?branch=v3.18&components=main,community&arch=x86_64\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/apk/#wolfi-and-chainguard-images-example","title":"Wolfi and Chainguard Images example","text":"

Wolfi serves its index directly below the repository root, so its registryUrl needs neither branch nor components - only arch:

Point apk lookups at the Wolfi repository
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"apk\"],\n      \"registryUrls\": [\"https://packages.wolfi.dev/os?arch=x86_64\"]\n    }\n  ]\n}\n

Renovate then fetches a single index:

https://packages.wolfi.dev/os/x86_64/APKINDEX.tar.gz\n

Use arch=aarch64 for an arm64 image.

"},{"location":"modules/datasource/apk/#pinning-packages-in-a-wolfi-image","title":"Pinning packages in a Wolfi image","text":"

As the Wolfi (un)distribution follows a rolling release cadence, it is common to pin the version of a package you depend on. Similarly, the package's revision (-rN) changes more often than its version.

For instance, you may have a Docker image like so:

FROM cgr.dev/chainguard/wolfi-base:latest@sha256:96ff486b326d15db16aa1fbd41a17043a557bebf76d2c0ac932e717534025940\n\nRUN apk add --no-cache \\\n      curl=~8.12.1 \\\n      jq=1.7.1-r4 \\\n      bash\n

In this case:

"},{"location":"modules/datasource/apk/#mixing-alpine-and-wolfi-in-one-repository","title":"Mixing Alpine and Wolfi in one repository","text":"

A registryUrl applies per lookup, so a repository holding both Alpine and Wolfi images needs the two scoped apart. Match on the file the dependency was found in:

Separate apk registries for Alpine and Wolfi Dockerfiles
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"apk\"],\n      \"registryUrls\": [\n        \"https://dl-cdn.alpinelinux.org/alpine?branch=v3.21&components=main,community&arch=x86_64\"\n      ]\n    },\n    {\n      \"matchDatasources\": [\"apk\"],\n      \"matchFileNames\": [\"**/*.wolfi\", \"**/Dockerfile.wolfi\"],\n      \"registryUrls\": [\"https://packages.wolfi.dev/os?arch=x86_64\"]\n    }\n  ]\n}\n

A later rule overrides an earlier one, so set the repository you use most as the first rule and narrow it with the rules after it. Putting the narrower rule first would let the broader one overwrite its registryUrls again.

"},{"location":"modules/datasource/apk/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageTopic\": \"{{{depName}}} APK package\",\n  \"commitMessageExtra\": \"to {{#if isMajor}}{{{prettyNewMajor}}}{{else}}{{{prettyNewVersion}}}{{/if}}\"\n}\n
"},{"location":"modules/datasource/artifactory/","title":"Artifactory Datasource","text":""},{"location":"modules/datasource/artifactory/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier artifactory Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the date-like text, next to the version hyperlink tag in the results. Source URL support No"},{"location":"modules/datasource/artifactory/#description","title":"Description","text":"

Artifactory is the recommended registry for Conan packages.

This datasource returns releases from given custom registryUrl(s).

The target URL is composed by the registryUrl and the packageName.

The release timestamp is taken from the date in the directory listing, and is assumed to be in UTC time.

Directory listings often contain file names instead of plain version numbers. Use extractVersion to get the version from the file name. For example, this custom manager updates a URL like https://artifactory.example.com/artifactory/my-repo/path/to/api/api-definition_v1.2.3.yaml:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^openapi\\\\.ts$/\"],\n      \"matchStrings\": [\n        \"'(?<registryUrl>https://[^'/]+/artifactory/[^'/]+/)(?<packageName>[^']+/)(?<filePrefix>[a-z-]+_)(?<currentValue>v?[0-9.]+)\\\\.yaml'\"\n      ],\n      \"datasourceTemplate\": \"artifactory\",\n      \"extractVersionTemplate\": \"^{{{filePrefix}}}(?<version>v?[0-9.]+)\\\\.yaml$\"\n    }\n  ]\n}\n

Here extractVersionTemplate turns the listed file api-definition_v1.2.3.yaml into the version v1.2.3. currentValue is captured as v1.2.3 directly, because extractVersion is not applied to it.

"},{"location":"modules/datasource/aws-eks-addon/","title":"Aws Eks Addon Datasource","text":""},{"location":"modules/datasource/aws-eks-addon/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier aws-eks-addon Default versioning aws-eks-addon Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/aws-eks-addon/#description","title":"Description","text":"

This datasource returns the addon versions available for use on AWS EKS via the AWS API.

AWS API configuration

See Calling AWS Services from Renovate for how to configure your credentials.

You can also provide credentials specifically for this datasource with a hostRules entry. Set hostType to aws-eks-addon, username to the access key ID, password to the secret access key, and optionally token to the session token:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"aws-eks-addon\",\n      \"username\": \"access-key-id\",\n      \"password\": \"secret-access-key\",\n      \"token\": \"session-token\"\n    }\n  ]\n}\n

These credentials only apply to AWS EKS Addon lookups. When this host rule is absent or incomplete, Renovate uses the default AWS credential provider chain.

You can also specify different region and profile for each addon.

The minimal IAM privileges required for this datasource are:

{\n  \"Sid\": \"AllowDescribeEKSAddonVersions\",\n  \"Effect\": \"Allow\",\n  \"Action\": [\"eks:DescribeAddonVersions\"],\n  \"Resource\": \"*\"\n}\n

Read the AWS EKS IAM reference for more information.

Usage

Because Renovate has no manager for the AWS EKS Addon datasource, you need to help Renovate by configuring the custom manager to identify the AWS EKS Addons you want updated.

When configuring the custom manager, you have to pass in the Kubernetes version and addon names as a minified JSON object as the packageName For example:

# Getting the vpc-cni version for Kubernetes 1.30\n{\n   \"kubernetesVersion\": \"1.30\",\n   \"addonName\": \"vpc-cni\"\n}\n\n# In order to use it with this datasource, you have to minify it:\n{\"kubernetesVersion\":\"1.30\",\"addonName\":\"vpc-cni\"}\n

Although it's unlikely that EKS might support different addon versions across regions, you can optionally specify the region and/or profile in the minified JSON object to discover the addon versions specific to this region.

# discover kube-proxy addon versions without specifying a cluster version.\nrenovate: eksAddonsFilter={\"addonName\":\"kube-proxy\"}\n\n# discover kube-proxy default addon versions\nrenovate: eksAddonsFilter={\"addonName\":\"kube-proxy\", \"default\":true}\n\n# discover vpc-cni addon versions on Kubernetes 1.30 in us-east-1 region using environmental AWS credentials.\nrenovate: eksAddonsFilter={\"kubernetesVersion\":\"1.30\",\"addonName\":\"vpc-cni\",\"region\":\"eu-west-1\"}\n\n# discover vpc-cni addon versions on Kubernetes 1.30 in us-east-1 region using AWS credentials from `renovate-east` profile.\nrenovate: eksAddonsFilter={\"kubernetesVersion\":\"1.30\",\"addonName\":\"vpc-cni\",\"region\":\"us-east-1\",\"profile\":\"renovate-east\"}\n

Here's an example of using the custom manager to configure this datasource:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"aws-eks-addon\"],\n      \"overrideDepName\": \"{{replace '.*\\\"addonName\\\":\\\"([^\\\"]+)\\\".*' '$1' depName}}\"\n    }\n  ],\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/.*\\\\.tf/\"],\n      \"matchStrings\": [\n        \".*# renovate: eksAddonsFilter=(?<packageName>.*?)\\n.*?[a-zA-Z0-9-_:]*[ ]*?[:|=][ ]*?[\\\"|']?(?<currentValue>[a-zA-Z0-9-_.]+)[\\\"|']?.*\"\n      ],\n      \"datasourceTemplate\": \"aws-eks-addon\",\n      \"versioningTemplate\": \"aws-eks-addon\" // Optional. Default value is 'aws-eks-addon'\n    }\n  ]\n}\n

The configuration above matches every terraform file, and recognizes these lines:

variable \"vpc_cni_version\" {\n  type        = string\n  description = \"EKS vpc-cni add-on version\"\n  # kubernetesVersion and addonName provided\n  # renovate: eksAddonsFilter={\"kubernetesVersion\":\"1.30\",\"addonName\":\"vpc-cni\"}\n  default     = \"v1.18.1-eksbuild.3\"\n}\n

or

addons:\n  - name: vpc-cni\n    # only addon name and the supported default version\n    # renovate: eksAddonsFilter={\"addonName\":\"vpc-cni\", \"default\":true}\n    version: v1.18.5-eksbuild.1\n
"},{"location":"modules/datasource/aws-machine-image/","title":"Aws Machine Image Datasource","text":""},{"location":"modules/datasource/aws-machine-image/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier aws-machine-image Default versioning aws-machine-image Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the CreationDate field in the results. Source URL support No"},{"location":"modules/datasource/aws-machine-image/#description","title":"Description","text":"

Warning

This datasource is experimental. Its syntax and behavior may change at any time!

This datasource returns the latest Amazon Machine Image via the AWS API.

See Calling AWS Services from Renovate for how to configure your credentials.

You can also provide credentials specifically for this datasource with a hostRules entry. Set hostType to aws-machine-image, username to the access key ID, password to the secret access key, and optionally token to the session token:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"aws-machine-image\",\n      \"username\": \"access-key-id\",\n      \"password\": \"secret-access-key\",\n      \"token\": \"session-token\"\n    }\n  ]\n}\n

These credentials only apply to Amazon Machine Image lookups. When this host rule is absent or incomplete, Renovate uses the default AWS credential provider chain.

Read the Developer guide for more information on configuration options.

The least IAM privileges required for this datasource are:

{\n  \"Sid\": \"AllowEc2ImageLookup\",\n  \"Effect\": \"Allow\",\n  \"Action\": [\"ec2:DescribeImages\"],\n  \"Resource\": \"*\"\n}\n

Read the AWS IAM Reference for more information.

Because there is no general packageName, you have to use the describe images filter as minified JSON as a packageName.

Example:

# Getting the latest official EKS image from AWS (account '602401143452' for eu-central-1) for EKS 1.21 (name matches 'amazon-eks-node-1.21-*') would look as a describe images filter like:\n\n[\n  {\n    \"Name\": \"owner-id\",\n    \"Values\": [ \"602401143452\" ]\n  },\n  {\n    \"Name\": \"name\",\n    \"Values\": [ \"amazon-eks-node-1.21-*\" ]\n  }\n]\n\n# In order to use it with this datasource, you have to minify it:\n\n[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.21-*\"]}]\n

At the moment, this datasource has no \"manager\". You have to use the custom manager for this.

Usage Example

Here's an example of using the custom manager:

module.exports = {\n  customManagers: [\n    {\n      customType: 'regex',\n      managerFilePatterns: ['/.*/'],\n      matchStrings: [\n        '.*amiFilter=(?<packageName>.*?)\\n(.*currentImageName=(?<currentDigest>.*?)\\n)?(.*\\n)?.*?(?<depName>[a-zA-Z0-9-_:]*)[ ]*?[:|=][ ]*?[\"|\\']?(?<currentValue>ami-[a-z0-9]{17})[\"|\\']?.*',\n      ],\n      datasourceTemplate: 'aws-machine-image',\n      versioningTemplate: 'aws-machine-image',\n    },\n  ],\n};\n

Or as JSON:

{\n  'customManagers':\n    [\n      {\n        'customType': 'regex',\n        'managerFilePatterns': ['/.*/'],\n        'matchStrings':\n          [\n            \".*amiFilter=(?<packageName>.*?)\\n(.*currentImageName=(?<currentDigest>.*?)\\n)?(.*\\n)?.*?(?<depName>[a-zA-Z0-9-_:]*)[ ]*?[:|=][ ]*?[\\\"|']?(?<currentValue>ami-[a-z0-9]{17})[\\\"|']?.*\",\n          ],\n        'datasourceTemplate': 'aws-machine-image',\n        'versioningTemplate': 'aws-machine-image',\n      },\n    ],\n}\n

Note about currentImageName:

The optional currentImageName comment is automatically updated by Renovate to track the actual AMI name corresponding to the AMI ID. This provides human-readable context about which image version is being used. When Renovate finds a newer AMI, it will update both the AMI ID and the currentImageName comment.

This would match every file, and would recognize the following lines:

# With AMI name mentioned in the comments\n# amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.21-*\"]}]\n# currentImageName=amazon-eks-node-1.21-v20240703\nmy_ami1: ami-02ce3d9008cab69cb\n\n# Only AMI, no name mentioned\n# amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.20-*\"]}]\n# currentImageName=amazon-eks-node-1.20-v20240615\nmy_ami2: ami-0083e9407e275acf2\n\n# Using custom aws profile and region\n# amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.20-*\"]},{\"profile\":\"test\",\"region\":\"eu-central-1\"}]\n# currentImageName=amazon-eks-node-1.20-v20240615\nami = \"ami-0083e9407e275acf2\"\n\n# Without currentImageName comment (also works!)\n# amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.19-*\"]}]\nmy_ami3: ami-0a1b2c3d4e5f6g7h8\n
const myConfigObject = {\n  // With AMI name mentioned in the comments\n  // amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.21-*\"]}]\n  // currentImageName=amazon-eks-node-1.21-v20240703\n  my_ami1: 'ami-02ce3d9008cab69cb',\n};\n\n/**\n * AMI with name tracked in comment\n * amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.20-*\"]}]\n * currentImageName=amazon-eks-node-1.20-v20240615\n */\nconst my_ami2 = 'ami-0083e9407e275acf2';\n\n/**\n * Without currentImageName comment\n * amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.19-*\"]}]\n */\nconst my_ami3 = 'ami-0a1b2c3d4e5f6g7h8';\n
resource \"aws_instance\" \"web\" {\n\n    # AMI with name tracked in comment\n    # amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.20-*\"]}]\n    # currentImageName=amazon-eks-node-1.20-v20240615\n    ami = \"ami-0083e9407e275acf2\"\n\n    count = 2\n    source_dest_check = false\n\n    connection {\n        user = \"root\"\n    }\n}\n\nresource \"aws_instance\" \"app\" {\n    # Without currentImageName comment\n    # amiFilter=[{\"Name\":\"owner-id\",\"Values\":[\"602401143452\"]},{\"Name\":\"name\",\"Values\":[\"amazon-eks-node-1.19-*\"]}]\n    ami = \"ami-0a1b2c3d4e5f6g7h8\"\n\n    count = 1\n}\n
"},{"location":"modules/datasource/aws-machine-image/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageExtra\": \"to {{{newVersion}}}\",\n  \"prBodyColumns\": [\n    \"Change\",\n    \"Image\"\n  ],\n  \"prBodyDefinitions\": {\n    \"Image\": \"```{{{newDigest}}}```\"\n  },\n  \"digest\": {\n    \"commitMessageExtra\": \"to {{{newDigest}}}\",\n    \"prBodyColumns\": [\n      \"Image\"\n    ],\n    \"prBodyDefinitions\": {\n      \"Image\": \"```{{{newDigest}}}```\"\n    }\n  }\n}\n
"},{"location":"modules/datasource/aws-rds/","title":"Aws Rds Datasource","text":""},{"location":"modules/datasource/aws-rds/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier aws-rds Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/aws-rds/#description","title":"Description","text":"

This datasource returns the database engine versions available for use on AWS RDS via the AWS API.

Generally speaking, all publicly released database versions are available for use on RDS. However, new versions may not be available on RDS for a few weeks or months after their release while AWS tests them. In addition, AWS may pull existing versions if serious problems arise during their use.

Warning

The default versioning of the aws-rds datasource is not compatible with AWS Aurora! If you use AWS Aurora, you must set your own custom versioning. Scroll down to see an example.

"},{"location":"modules/datasource/aws-rds/#aws-api-configuration","title":"AWS API configuration","text":"

See Calling AWS Services from Renovate for how to configure your credentials.

Minimal IAM privileges needed for this datasource
{\n  \"Sid\": \"AllowDBEngineVersionLookup\",\n  \"Effect\": \"Allow\",\n  \"Action\": [\"rds:DescribeDBEngineVersions\"],\n  \"Resource\": \"*\"\n}\n

Read the AWS RDS IAM reference for more information.

"},{"location":"modules/datasource/aws-rds/#usage","title":"Usage","text":"

Because Renovate has no manager for the AWS RDS datasource, you need to help Renovate by configuring the custom manager to identify the RDS dependencies you want updated.

When configuring the custom manager, you have to pass a filter as minified JSON as the packageName. For example:

# Getting the latest supported MySQL 5.7 version from RDS as a filter would look like:\n\n[\n  {\n    \"Name\": \"engine\",\n    \"Values\": [ \"mysql\" ]\n  },\n  {\n    \"Name\": \"engine-version\",\n    \"Values\": [ \"5.7\" ]\n  }\n]\n\n# In order to use it with this datasource, you have to minify it:\n\n[{\"Name\":\"engine\",\"Values\":[\"mysql\"]},{\"Name\":\"engine-version\",\"Values\":[\"5.7\"]}]\n
Using a custom manager to configure this datasource
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"**.yaml\"],\n      \"matchStrings\": [\n        \".*rdsFilter=(?<packageName>.+?)[ ]*\\n[ ]*(?<depName>[a-zA-Z0-9-_:]*)[ ]*?:[ ]*?[\\\"|']?(?<currentValue>[.\\\\d]+)[\\\"|']?.*\"\n      ],\n      \"datasourceTemplate\": \"aws-rds\"\n    }\n  ]\n}\n

The configuration above matches every YAML file, and recognizes these lines:

spec:\n  # rdsFilter=[{\"Name\":\"engine\",\"Values\":[\"mysql\"]},{\"Name\":\"engine-version\",\"Values\":[\"5.7\"]}]\n  engineVersion: 5.7.34\n
"},{"location":"modules/datasource/aws-rds/#using-terraform-aws-rds-datasource-and-aurora-mysql","title":"Using Terraform, aws-rds datasource and Aurora MySQL","text":"

Here is the Renovate configuration to use Terraform, aws-rds and Aurora MySQL:

{\n  \"customManagers\": [\n    {\n      \"description\": \"Update RDS\",\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/.+\\\\.tf$/\"],\n      \"matchStrings\": [\n        \"\\\\s*#\\\\s*renovate:\\\\s*rdsFilter=(?<packageName>.+?) depName=(?<depName>.*) versioning=(?<versioning>.*)\\\\s*.*_version\\\\s*=\\\\s*\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"datasourceTemplate\": \"aws-rds\"\n    }\n  ]\n}\n

The above configuration is an example of updating an AWS RDS version inside a Terraform file, using a custom manager.

# renovate:rdsFilter=[{\"Name\":\"engine\",\"Values\":[\"aurora-mysql\"]},{\"Name\":\"engine-version\",\"Values\":[\"8.0\"]}] depName=aurora-mysql versioning=loose\nengine_version = \"8.0.mysql_aurora.3.05.2\"\n
"},{"location":"modules/datasource/azure-bicep-resource/","title":"Azure Bicep Resource Datasource","text":""},{"location":"modules/datasource/azure-bicep-resource/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier azure-bicep-resource Default versioning azure-rest-api Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/azure-bicep-resource/#description","title":"Description","text":"

This data source returns available Bicep resource versions from the official index, which is also used by all Bicep tooling: https://github.com/Azure/bicep-types-az

"},{"location":"modules/datasource/azure-bicep-resource/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageTopic\": \"resource {{depName}}\",\n  \"commitMessageExtra\": \"to {{{newVersion}}}\",\n  \"prBodyColumns\": [\n    \"Resource\",\n    \"Change\"\n  ],\n  \"prBodyDefinitions\": {\n    \"Resource\": \"{{{depNameLinked}}}\"\n  }\n}\n
"},{"location":"modules/datasource/azure-pipelines-tasks/","title":"Azure Pipelines Tasks Datasource","text":""},{"location":"modules/datasource/azure-pipelines-tasks/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier azure-pipelines-tasks Default versioning loose Custom registry support No Release timestamp support No Source URL support No"},{"location":"modules/datasource/azure-pipelines-tasks/#description","title":"Description","text":"

This datasource returns versions of the built-in Azure Pipelines tasks and from all public extensions on the Visual Studio Marketplace.

"},{"location":"modules/datasource/azure-tags/","title":"Azure Tags Datasource","text":""},{"location":"modules/datasource/azure-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier azure-tags Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/bazel/","title":"Bazel Datasource","text":""},{"location":"modules/datasource/bazel/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier bazel Default versioning bazel-module Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/bazel/#description","title":"Description","text":"

The bazel datasource is designed to query one or more Bazel registries or file based BCR using the first successful result.

"},{"location":"modules/datasource/bitbucket-server-tags/","title":"Bitbucket Server Tags Datasource","text":""},{"location":"modules/datasource/bitbucket-server-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier bitbucket-server-tags Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/bitbucket-tags/","title":"Bitbucket Tags Datasource","text":""},{"location":"modules/datasource/bitbucket-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier bitbucket-tags Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the date field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/bitrise/","title":"Bitrise Datasource","text":""},{"location":"modules/datasource/bitrise/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier bitrise Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the published_at field in the results. Source URL support Yes The source URL is determined from the source_code_url field of the release object in the results."},{"location":"modules/datasource/bitrise/#description","title":"Description","text":"

Renovate uses this datasource to fetch Bitrise steps from GitHub repositories.

Renovate field What value to use? packageName Name of the Bitrise step registryUrl GitHub HTTP Git URL, as used by Bitrise

For example, in the YAML snippet below:

format_version: 11\ndefault_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git\nproject_type: android\napp:\n  envs:\n    - MY_NAME: My Name\nworkflows:\n  test:\n    steps:\n      - script@1.1.5:\n          inputs:\n            - content: echo \"Hello ${MY_NAME}!\"\n
"},{"location":"modules/datasource/buildpacks-registry/","title":"Buildpacks Registry Datasource","text":""},{"location":"modules/datasource/buildpacks-registry/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier buildpacks-registry Default versioning No default versioning Custom registry support No Release timestamp support Yes The release timestamp is determined from the published_at field in the results. Source URL support Yes The source URL is determined from the source_code_url field of the release object in the results."},{"location":"modules/datasource/cdnjs/","title":"Cdnjs Datasource","text":""},{"location":"modules/datasource/cdnjs/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier cdnjs Default versioning No default versioning Custom registry support No Release timestamp support No Source URL support Yes The source URL is determined from the repository field in the results."},{"location":"modules/datasource/clojure/","title":"Clojure Datasource","text":""},{"location":"modules/datasource/clojure/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier clojure Default versioning maven Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Source URL support Yes The source URL is determined from the scm tags in the results."},{"location":"modules/datasource/conan/","title":"Conan Datasource","text":""},{"location":"modules/datasource/conan/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier conan Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support Yes The source URL is supported only if the package is served from the Artifactory servers. In which case we determine it from the properties[conan.package.url] field in the results."},{"location":"modules/datasource/conda/","title":"Conda Datasource","text":""},{"location":"modules/datasource/conda/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier conda Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the upload_time field of the files of a version when using the Anaconda.org API, or from the createdAt field of the variants of a version when using prefix.dev. All files of a version are assumed to be published at roughly the same time. Source URL support Yes The source URL is determined from the dev_url field in the results."},{"location":"modules/datasource/conda/#description","title":"Description","text":"

This datasource returns releases for package from anaconda registry and prefix.dev. Other repositories are not supported currently.

This datasource support following cases:

Look up numpy in conda-forge channel on anaconda.

{\n  packageName: 'conda-forge/numpy',\n}\n

Look up numpy in conda-forge channel from prefix.dev using API https://prefix.dev/api/graphql.

{\n  packageName: 'numpy',\n  registryUrls: [\"https://prefix.dev/conda-forge/\"]\n}\n
"},{"location":"modules/datasource/conda/#multiple-channels-support","title":"Multiple channels support","text":"
{\n  packageName: 'some-package',\n  registryUrls: [\n    \"https://api.anaconda.org/package/conda-forge/\",\n    \"https://prefix.dev/conda-forge/\",\n  ]\n}\n

The above example will lookup try to find the package on anaconda first, if the package can not be found on prefix.dev.

"},{"location":"modules/datasource/cpan/","title":"Cpan Datasource","text":""},{"location":"modules/datasource/cpan/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier cpan Default versioning perl Custom registry support No Release timestamp support Yes The release timestamp is determined from the date field in the results. Source URL support No"},{"location":"modules/datasource/crate/","title":"Crate Datasource","text":""},{"location":"modules/datasource/crate/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier crate Default versioning cargo Custom registry support Yes Release timestamp support Yes The release timestamp is determined from pubtime field from crates.io index if available, or version.created_at field from crates.io API otherwise. Source URL support Yes The source URL is determined from the repository field in the results."},{"location":"modules/datasource/custom/","title":"Custom Datasource","text":""},{"location":"modules/datasource/custom/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier custom Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/custom/#description","title":"Description","text":"

This custom datasource allows requesting version data from generic HTTP(S) endpoints.

"},{"location":"modules/datasource/custom/#usage","title":"Usage","text":"

The customDatasources option takes a record of customDatasource configs. This example shows how to update the k3s.version file with a custom datasource and a regex custom manager:

Options:

option default description defaultRegistryUrlTemplate \"\" URL used if no registryUrl is provided when looking up new releases format \"json\" format used by the API. Available values are: html, json, plain, toml, yaml transformTemplates [] JSONata rules to transform the API output. Each rule will be evaluated after another and the result will be used as input to the next

Tip

Use JSONata Exerciser to test your JSONata rules.

Available template variables:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/k3s.version/\"],\n      \"matchStrings\": [\"(?<currentValue>\\\\S+)\"],\n      \"depNameTemplate\": \"k3s\",\n      \"versioningTemplate\": \"semver-coerced\",\n      \"datasourceTemplate\": \"custom.k3s\"\n    }\n  ],\n  \"customDatasources\": {\n    \"k3s\": {\n      \"defaultRegistryUrlTemplate\": \"https://update.k3s.io/v1-release/channels\",\n      \"transformTemplates\": [\n        \"{\\\"releases\\\":[{\\\"version\\\": $$.(data[id = 'stable'].latest),\\\"sourceUrl\\\":\\\"https://github.com/k3s-io/k3s\\\",\\\"changelogUrl\\\":$join([\\\"https://github.com/k3s-io/k3s/releases/tag/\\\",data[id = 'stable'].latest])}],\\\"sourceUrl\\\": \\\"https://github.com/k3s-io/k3s\\\",\\\"homepage\\\": \\\"https://k3s.io/\\\"}\"\n      ]\n    }\n  }\n}\n

After all transformations, the resulting JSON must match one of these formats:

Minimal-supported object:

{\n  \"releases\": [\n    {\n      \"version\": \"v1.1.0\"\n    },\n    {\n      \"version\": \"v1.2.0\"\n    }\n  ]\n}\n

All available options:

{\n  \"releases\": [\n    {\n      \"version\": \"v1.0.0\",\n      \"isDeprecated\": true,\n      \"releaseTimestamp\": \"2022-12-24T18:21Z\",\n      \"changelogUrl\": \"https://github.com/demo-org/demo/blob/main/CHANGELOG.md#v0710\",\n      \"sourceUrl\": \"https://github.com/demo-org/demo\",\n      \"sourceDirectory\": \"monorepo/folder\",\n      \"digest\": \"c667f758f9e46e1d8111698e8d3a181c0b10f430\",\n      \"isStable\": true\n    }\n  ],\n  \"sourceUrl\": \"https://github.com/demo-org/demo\",\n  \"sourceDirectory\": \"monorepo/folder\",\n  \"changelogUrl\": \"https://github.com/demo-org/demo/blob/main/CHANGELOG.md\",\n  \"homepage\": \"https://demo.org\"\n}\n
"},{"location":"modules/datasource/custom/#debugging","title":"Debugging","text":"

Renovate writes tracing logs entries before transformation. If Renovate finds an unexpected dataformat, it also writes a tracing log after transformation.

"},{"location":"modules/datasource/custom/#getting-trace-level-logs-on-hosted-app","title":"Getting trace level logs on hosted app","text":"

If you use the Mend Renovate app, use the logLevelRemap config option to get the trace log.

Getting trace logs from the Mend Renovate app
{\n  \"logLevelRemap\": [\n    {\n      \"matchMessage\": \"/^Custom datasource/\",\n      \"newLogLevel\": \"info\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/custom/#getting-trace-level-logs-when-self-hosting","title":"Getting trace level logs when self-hosting","text":"

If you self-host Renovate, follow these steps to get the trace logs:

  1. Set the LOG_FILE_LEVEL env var to trace
  2. Run Renovate in dryRun mode
"},{"location":"modules/datasource/custom/#formats","title":"Formats","text":""},{"location":"modules/datasource/custom/#json","title":"JSON","text":"

If json is used processing works as described above. The returned body will be directly interpreted as JSON and forwarded to the transformation rules.

"},{"location":"modules/datasource/custom/#plain","title":"Plain","text":"

If the format is set to plain, Renovate will call the HTTP endpoint with the Accept header value text/plain. The body of the response will be treated as plain text and will be converted into JSON.

Suppose the body of the HTTP response is as follows:

1.0.0\n2.0.0\n3.0.0\n

When Renovate receives this response with the plain format, it will convert it into the following:

{\n  \"releases\": [\n    {\n      \"version\": \"1.0.0\"\n    },\n    {\n      \"version\": \"2.0.0\"\n    },\n    {\n      \"version\": \"3.0.0\"\n    }\n  ]\n}\n

After the conversion, any jsonata rules defined in the transformTemplates section will be applied as usual to further process the JSON data.

"},{"location":"modules/datasource/custom/#yaml","title":"Yaml","text":"

If yaml is used, response is parsed and converted into JSON for further processing.

Suppose the body of the HTTP response is as follows:

releases:\n  - version: 1.0.0\n  - version: 2.0.0\n  - version: 3.0.0\n

When Renovate receives this response with the yaml format, it will convert it into the following:

{\n  \"releases\": [\n    {\n      \"version\": \"1.0.0\"\n    },\n    {\n      \"version\": \"2.0.0\"\n    },\n    {\n      \"version\": \"3.0.0\"\n    }\n  ]\n}\n

After the conversion, any jsonata rules defined in the transformTemplates section will be applied as usual to further process the JSON data.

"},{"location":"modules/datasource/custom/#toml","title":"TOML","text":"

If toml is used, response is parsed and converted into TOML for further processing.

The below TOML document

[[releases]]\nversion = \"1.0.0\"\n[[releases]]\nversion = \"2.0.0\"\n[[releases]]\nversion = \"3.0.0\"\n

Will convert applying any jsonata rules defined in the transformTemplates section will be applied.

{\n  \"releases\": [\n    {\n      \"version\": \"1.0.0\"\n    },\n    {\n      \"version\": \"2.0.0\"\n    },\n    {\n      \"version\": \"3.0.0\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/custom/#html","title":"HTML","text":"

If the format is set to html, Renovate will call the HTTP endpoint with the Accept header value text/html. The body of the response will be treated as a HTML document, and all hyperlinks will be converted to versions.

For the following HTML document:

<html>\n  <body>\n    <a href=\"package-1.0.tar.gz\">package-1.0.tar.gz</a>\n    <a href=\"package-2.0.tar.gz\">package-2.0.tar.gz</a>\n  </body>\n</html>\n

The following JSON will be generated:

{\n  \"releases\": [\n    {\n      \"version\": \"package-1.0.tar.gz\"\n    },\n    {\n      \"version\": \"package-1.0.tar.gz\"\n    }\n  ]\n}\n

After the conversion, any jsonata rules defined in the transformTemplates section will be applied to process the JSON data.

To extract the version number, you may use extractVersion or JSONata rules.

"},{"location":"modules/datasource/custom/#examples","title":"Examples","text":""},{"location":"modules/datasource/custom/#k3s","title":"K3s","text":"

You can use this configuration to request the newest version available to K3s

{\n  \"customDatasources\": {\n    \"k3s\": {\n      \"defaultRegistryUrlTemplate\": \"https://update.k3s.io/v1-release/channels\",\n      \"transformTemplates\": [\n        \"{\\\"releases\\\":[{\\\"version\\\": $$.(data[id = 'stable'].latest),\\\"sourceUrl\\\":\\\"https://github.com/k3s-io/k3s\\\",\\\"changelogUrl\\\":$join([\\\"https://github.com/k3s-io/k3s/releases/tag/\\\",data[id = 'stable'].latest])}],\\\"sourceUrl\\\": \\\"https://github.com/k3s-io/k3s\\\",\\\"homepage\\\": \\\"https://k3s.io/\\\"}\"\n      ]\n    }\n  }\n}\n
"},{"location":"modules/datasource/custom/#hashicorp","title":"Hashicorp","text":"

You can use this configuration to request the newest versions of the Hashicorp products:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/\\\\.yml$/\"],\n      \"datasourceTemplate\": \"custom.hashicorp\",\n      \"matchStrings\": [\n        \"#\\\\s*renovate:\\\\s*(datasource=(?<datasource>.*?) )?depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\\\s*\\\\w*:\\\\s*(?<currentValue>.*)\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ],\n  \"customDatasources\": {\n    \"hashicorp\": {\n      \"defaultRegistryUrlTemplate\": \"https://api.releases.hashicorp.com/v1/releases/{{packageName}}?license_class=oss\",\n      \"transformTemplates\": [\n        \"{ \\\"releases\\\": $map($, function($v) { { \\\"version\\\": $v.version, \\\"releaseTimestamp\\\": $v.timestamp_created, \\\"changelogUrl\\\": $v.url_changelog, \\\"sourceUrl\\\": $v.url_source_repository } }), \\\"homepage\\\": $[0].url_project_website, \\\"sourceUrl\\\": $[0].url_source_repository }\"\n      ]\n    }\n  }\n}\n

To have the latest Nomad version in your Ansible variables, use this snippet after adding the above configuration:

# renovate: depName=nomad\nnomad_version: 1.6.0\n
"},{"location":"modules/datasource/custom/#grafana-dashboard","title":"Grafana Dashboard","text":"

You can use the following configuration to upgrade the Grafana Dashboards versions in your Grafana Helm chart:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/\\\\.yml$/\"],\n      \"matchStrings\": [\n        \"#\\\\s+renovate:\\\\s+depName=\\\"(?<depName>.*)\\\"\\\\n\\\\s+gnetId:\\\\s+(?<packageName>.*?)\\\\n\\\\s+revision:\\\\s+(?<currentValue>.*)\"\n      ],\n      \"versioningTemplate\": \"regex:^(?<major>\\\\d+)$\",\n      \"datasourceTemplate\": \"custom.grafana-dashboards\"\n    }\n  ],\n  \"customDatasources\": {\n    \"grafana-dashboards\": {\n      \"defaultRegistryUrlTemplate\": \"https://grafana.com/api/dashboards/{{packageName}}\",\n      \"format\": \"json\",\n      \"transformTemplates\": [\n        \"{\\\"releases\\\":[{\\\"version\\\": $string(revision)}]}\"\n      ]\n    }\n  }\n}\n

Grafana Helm chart values.yaml snippet:

dashboards:\n  default:\n    1860-node-exporter-full:\n      # renovate: depName=\"Node Exporter Full\"\n      gnetId: 1860\n      revision: 31\n      datasource: Prometheus\n    15760-kubernetes-views-pods:\n      # renovate: depName=\"Kubernetes / Views / Pods\"\n      gnetId: 15760\n      revision: 20\n      datasource: Prometheus\n
"},{"location":"modules/datasource/custom/#custom-offline-dependencies","title":"Custom offline dependencies","text":"

Sometimes the \"dependency version source\" is not available via an API. To work around a missing API, you can create dependency \"files\". These files are served via HTTP(S), so that Renovate can access them. For example, imagine the following file versiontracker.json for the software something:

[\n  {\n    \"version\": \"77\"\n  },\n  {\n    \"version\": \"76\"\n  }\n]\n

By writing a custom datasource, Renovate can process the versiontracker.json file, see below. This example uses Nexus as the webserver.

{\n  \"customDatasources\": {\n    \"nexus_generic\": {\n      \"defaultRegistryUrlTemplate\": \"https://nexus.example.com/repository/versiontrackers/{{packageName}}/versiontracker.json\",\n      \"transformTemplates\": [\n        \"{ \\\"releases\\\": $map($, function($v) { { \\\"version\\\": $v.version, \\\"sourceUrl\\\": $v.filelink } }) }\"\n      ]\n    }\n  }\n}\n

This could be used to update Ansible YAML files with the latest version through a custom manager. For example, with the following Ansible content:

# renovate: datasource=custom.nexus_generic depName=something versioning=loose\nsomething_version: '77'\n

And the following custom manager:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/\\\\.yml$/\"],\n      \"datasourceTemplate\": \"custom.nexus_generic\",\n      \"matchStrings\": [\n        \"#\\\\s*renovate:\\\\s*(datasource=(?<datasource>.*?)\\\\s*)?depName=(?<depName>.*?)(\\\\s*versioning=(?<versioning>.*?))?\\\\s*\\\\w*:\\\\s*[\\\"']?(?<currentValue>.+?)[\\\"']?\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ]\n}\n

Or if you have the datasource locally, you can also define your local registry by prefixing it with file://:

{\n  \"customDatasources\": {\n    \"local_generic\": {\n      \"defaultRegistryUrlTemplate\": \"file://dependencies/{{packageName}}/versiontracker.json\",\n      \"transformTemplates\": [\n        \"{ \\\"releases\\\": $map($, function($v) { { \\\"version\\\": $v.version, \\\"sourceUrl\\\": $v.filelink } }) }\"\n      ]\n    }\n  }\n}\n

Renovate will then parse your file from your current folder to access it.

"},{"location":"modules/datasource/custom/#nginx-directory-listing","title":"nginx directory listing","text":"

Sometimes all you have is a directory with files, and a HTTP server that can generate directory listings.

Let's use nginx itself as an example:

{\n  \"customDatasources\": {\n    \"nginx\": {\n      \"defaultRegistryUrlTemplate\": \"https://nginx.org/download\",\n      \"format\": \"html\"\n    }\n  },\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"custom.nginx\"],\n      \"extractVersion\": \"^nginx-(?<version>.+)\\\\.tar\\\\.gz$\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/custom/#html-page","title":"HTML page","text":"

You can use the html format to extract versions from a typical \"Downloads\" page:

{\n  \"customDatasources\": {\n    \"curl\": {\n      \"defaultRegistryUrlTemplate\": \"https://curl.se/download.html\",\n      \"format\": \"html\"\n    }\n  },\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"custom.curl\"],\n      \"extractVersion\": \"/curl-(?<version>.+)\\\\.tar\\\\.gz$\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/dart/","title":"Dart Datasource","text":""},{"location":"modules/datasource/dart/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier dart Default versioning npm Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the published field in the results. Source URL support Yes The source URL is determined from the repository field of the latest release object in the results."},{"location":"modules/datasource/dart-version/","title":"Dart Version Datasource","text":""},{"location":"modules/datasource/dart-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier dart-version Default versioning No default versioning Custom registry support No Release timestamp support No Source URL support Yes We use the URL: https://github.com/dart-lang/sdk."},{"location":"modules/datasource/deb/","title":"Deb Datasource","text":""},{"location":"modules/datasource/deb/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier deb Default versioning deb Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/deb/#description","title":"Description","text":"

Renovate uses the Debian datasource to update packages from Debian repositories. The debian datasource is meant for projects that:

The dockerfile manager detects packages installed by apt install or apt-get install in a RUN instruction. Anywhere else, you must combine the Debian datasource with regex managers for Renovate to detect your dependencies.

"},{"location":"modules/datasource/deb/#set-url-when-using-a-debian-repository","title":"Set URL when using a Debian repository","text":"

To use a Debian repository with the datasource, you must set a properly formatted URL with specific query parameters as registryUrl:

Note

These parameters are used to give Renovate context and are not directly used to call the repository. Therefore, the registryUrl has not to be a valid URL for a repository.

Example:

https://deb.debian.org/debian?suite=stable&components=main,contrib,non-free&binaryArch=amd64\n

This URL points to the stable suite of the Debian repository for amd64 architecture, including main, contrib, and non-free components.

"},{"location":"modules/datasource/deb/#dockerfile-support","title":"Dockerfile support","text":"

When using Debian-based images, it is common to use a version pin for your packages, like so:

FROM debian:trixie\nRUN apt-get update \\\n  && apt-get install -y --no-install-recommends curl=8.14.1-2 \\\n  && rm -rf /var/lib/apt/lists/*\n

This provides reproducibility in the case that the upstream package updates under you.

The dockerfile manager extracts these packages, allowing updates to them directly, without needing a Custom Manager.

The dockerfile manager does not work out a registryUrl from your base image, so it skips these packages with skipReason: unknown-registry rather than look them up against a suite which may hold versions your image cannot install. Set the registryUrls which match your base image with a packageRules entry to have them looked up.

Point deb lookups at the Debian trixie repositories
{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"Dockerfile\"],\n      \"matchDatasources\": [\"deb\"],\n      \"registryUrls\": [\n        \"https://deb.debian.org/debian?suite=trixie&components=main,contrib,non-free&binaryArch=amd64\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/deb/#usage-example","title":"Usage Example","text":"

Where the version is not given to apt directly - say it is held in an environment variable - you can extract it with a custom manager.

First you would set a custom manager in your renovate.json file for Dockerfile:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^Dockerfile$/\"],\n      \"matchStrings\": [\n        \"#\\\\s*renovate:\\\\s*?(suite=(?<suite>.*?))?\\\\s*depName=(?<depName>.*?)?\\\\sENV .*?_VERSION=\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"registryUrlTemplate\": \"https://deb.debian.org/debian?suite={{#if suite }}{{suite}}{{else}}stable{{/if}}&components=main,contrib,non-free&binaryArch=amd64\",\n      \"datasourceTemplate\": \"deb\"\n    }\n  ]\n}\n

Then you would put comments in your Dockerfile, to tell Renovate where to find the updates:

FROM debian:bullseye\n\n# renovate: suite=bullseye depName=gcc-11\nENV GCC_VERSION=\"11.2.0-19\"\n\nRUN apt-get update && \\\n    apt-get install -y \\\n    gcc-11=\"${GCC_VERSION}\" && \\\n    apt-get clean\n

When the apt package for gcc is updated, Renovate updates the environment variable.

Override deb registryUrl with a packageRules entry
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"deb\"],\n      \"matchPackageNames\": [\"gcc-11\"],\n      \"registryUrls\": [\n        \"https://deb.debian.org/debian?suite=stable&components=main,contrib,non-free&binaryArch=amd64\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/deb/#artifactory","title":"Artifactory","text":"

The Debian datasource can be used with Artifactory.

"},{"location":"modules/datasource/deb/#supported-repository-types","title":"Supported repository types","text":"

The debian datasource supports these repository types:

"},{"location":"modules/datasource/deb/#set-a-registryurl","title":"Set a registryUrl","text":"

To use Artifactory, first configure the deb datasource by setting the registryUrl.

Example of valid registryUrl format
https://<host>:<port>/artifactory/<repository-slug>?suite=<suite>&components=<components>&binaryArch=<binaryArch>\nhttps://artifactory.example.com:443/artifactory/debian?suite=bookworm&components=main,contrib,non-free&binaryArch=amd64\n
"},{"location":"modules/datasource/deb/#authenticating-to-artifactory","title":"Authenticating to Artifactory","text":"

If Artifactory asks for authentication, you must set up a host rule. First, generate a password for Renovate with Artifactory's \"Set Me Up\" feature. Then, add the following configuration:

Example Artifactory host rule configuration, with username and password
{\n  \"hostRules\": [\n    {\n      \"hostType\": \"deb\",\n      \"matchHost\": \"https://artifactory.example.com:443/artifactory/debian\",\n      \"username\": \"myuser\",\n      \"password\": \"< the generated password >\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/deno/","title":"Deno Datasource","text":""},{"location":"modules/datasource/deno/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier deno Default versioning semver Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the uploaded_at field in the results. Source URL support Yes The source URL is determined from the repository field in the results."},{"location":"modules/datasource/deno/#description","title":"Description","text":"

This datasource extracts dependencies from a denoland/apiland compatible registry server.

By default, Renovate uses the official Deno registry. You can override this by setting your own registryUrl.

"},{"location":"modules/datasource/devbox/","title":"Devbox Datasource","text":""},{"location":"modules/datasource/devbox/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier devbox Default versioning devbox Custom registry support Yes Release timestamp support Yes Source URL support No"},{"location":"modules/datasource/docker/","title":"Docker Datasource","text":""},{"location":"modules/datasource/docker/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier docker Default versioning docker Custom registry support Yes Release timestamp support Yes Only supported on Docker Hub: The release timestamp is determined from the tag_last_pushed field in the results. NOTE: Currently, digests will receive the same release timestamp as the tag_last_pushed, which means that digests may appear newer than they are - see https://github.com/renovatebot/renovate/issues/38659 Source URL support Yes The source URL is determined from the org.opencontainers.image.source and org.label-schema.vcs-url labels present in the metadata of the latest stable image found on the Docker registry."},{"location":"modules/datasource/docker/#description","title":"Description","text":"

This datasource identifies an image's source repository according to the pre-defined annotation keys of the OCI Image Format Specification.

This datasource looks for the metadata of the latest stable image found on the Docker registry and uses the value of the label org.opencontainers.image.source and org.label-schema.vcs-url as the sourceUrl. Additionally, it uses the value of the label org.opencontainers.image.revision as the gitRef.

The Label Schema is superseded by OCI annotations, use the org.opencontainers.image.source label if possible.

If you maintain a Docker image and want Renovate to find your changelogs, add a org.opencontainers.image.source field to your Dockerfile. The link must point to your GitHub or GitLab repository. Here's an example from our renovate/renovate Dockerfile:

LABEL org.opencontainers.image.source=\"https://github.com/renovatebot/renovate\"\n

If you use Harbor as a proxy cache for Docker Hub, then you must use Harbor version 2.5.0 or higher.

"},{"location":"modules/datasource/docker/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageTopic\": \"{{{depName}}} Docker tag\",\n  \"commitMessageExtra\": \"to {{#if isPinDigest}}{{{newDigestShort}}}{{else}}{{#if isMajor}}{{{prettyNewMajor}}}{{else}}{{{prettyNewVersion}}}{{/if}}{{/if}}\",\n  \"digest\": {\n    \"branchTopic\": \"{{{depNameSanitized}}}-{{{currentValue}}}\",\n    \"commitMessageExtra\": \"to {{newDigestShort}}\",\n    \"commitMessageTopic\": \"{{{depName}}}{{#if currentValue}}:{{{currentValue}}}{{/if}} Docker digest\",\n    \"group\": {\n      \"commitMessageTopic\": \"{{{groupName}}}\",\n      \"commitMessageExtra\": \"\"\n    }\n  },\n  \"pin\": {\n    \"commitMessageExtra\": \"\",\n    \"groupName\": \"Docker digests\",\n    \"group\": {\n      \"commitMessageTopic\": \"{{{groupName}}}\",\n      \"branchTopic\": \"digests-pin\"\n    }\n  }\n}\n
"},{"location":"modules/datasource/dotnet-version/","title":"Dotnet Version Datasource","text":""},{"location":"modules/datasource/dotnet-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier dotnet-version Default versioning No default versioning Custom registry support No Release timestamp support Yes The release timestamp is determined from the release-date field in the results. Source URL support Yes We use the URL https://github.com/dotnet/sdk for the dotnet-sdk package and, the https://github.com/dotnet/runtime URL for the dotnet-runtime package."},{"location":"modules/datasource/dotnet-version/#description","title":"Description","text":"

This datasource returns releases of the .NET Runtime and SDK. It only accepts dependencies with the name dotnet-sdk or dotnet-runtime.

"},{"location":"modules/datasource/elm-package/","title":"Elm Package Datasource","text":""},{"location":"modules/datasource/elm-package/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier elm-package Default versioning elm Custom registry support No Release timestamp support Yes The release timestamp is determined from the Unix timestamp in the results. Source URL support Yes The source URL is determined from the package name using the GitHub pattern."},{"location":"modules/datasource/elm-package/#description","title":"Description","text":"

This datasource uses the Elm Package Registry API to fetch versions for published Elm packages.

Elm packages use strict semantic versioning. The datasource fetches release timestamps from the registry's per-package releases endpoint.

By design, all Elm packages must be published from GitHub repositories. The package name is the GitHub repository path (e.g., elm/core is published from github.com/elm/core). This is enforced by the elm publish command, which requires packages to be tagged and pushed to GitHub before publishing. Therefore, the source URL is reliably derived from the package name.

"},{"location":"modules/datasource/endoflife-date/","title":"Endoflife Date Datasource","text":""},{"location":"modules/datasource/endoflife-date/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier endoflife-date Default versioning loose Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the releaseDate field in the results. Source URL support No"},{"location":"modules/datasource/endoflife-date/#description","title":"Description","text":"

endoflife.date provides version and end-of-life information for different packages.

To find the right \"package\" name for the software you're trying to update, use the endoflife.date \"All packages\" API endpoint. You can find it in the endoflife.date API documentation.

By default, this datasource uses loose versioning. If possible, we recommend you use a stricter versioning like semver instead of loose.

Usage Example

Say you're using Amazon EKS and want Renovate to update the versions in a Terraform .tfvars file. For example, you have this .tfvars file:

# renovate: datasource=endoflife-date depName=amazon-eks versioning=loose\nkubernetes_version = \"1.26\"\n

Given the above .tfvars file, you put this in your renovate.json:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"description\": \"Update Kubernetes version for Amazon EKS in tfvars files\",\n      \"managerFilePatterns\": [\"/.+\\\\.tfvars$/\"],\n      \"matchStrings\": [\n        \"#\\\\s*renovate:\\\\s*datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\\\s.*?_version\\\\s*=\\\\s*\\\"(?<currentValue>.*)\\\"\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{/if}}\"\n    }\n  ],\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"endoflife-date\"],\n      \"matchPackageNames\": [\"amazon-eks\"],\n      \"extractVersion\": \"^(?<version>.*)-eks.+$\"\n    }\n  ]\n}\n

With this configuration, Renovate will parse all *.tfvars files in the repository. It will then update variables that end with _version and have the # renovate: datasource=endoflife-date depName=dependency-name versioning=versioning comment set in the line above when any new versions are available.

For amazon-eks, the defined packageRule above will also strip the -eks-${eks-release-version} suffix to only set the Kubernetes minor version.

"},{"location":"modules/datasource/flutter-version/","title":"Flutter Version Datasource","text":""},{"location":"modules/datasource/flutter-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier flutter-version Default versioning semver Custom registry support No Release timestamp support Yes The release timestamp is determined from the release_date field in the results. Source URL support Yes We use the URL: https://github.com/flutter/flutter."},{"location":"modules/datasource/forgejo-releases/","title":"Forgejo Releases Datasource","text":""},{"location":"modules/datasource/forgejo-releases/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier forgejo-releases Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the published_at field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/forgejo-releases/#description","title":"Description","text":"

This datasource allows to lookup releases from a Forgejo repositories.

By default it will use https://code.forgejo.org to lookup releases.

"},{"location":"modules/datasource/forgejo-tags/","title":"Forgejo Tags Datasource","text":""},{"location":"modules/datasource/forgejo-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier forgejo-tags Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/forgejo-tags/#description","title":"Description","text":"

This datasource allows to lookup git tags from a Forgejo repositories.

By default it will use https://code.forgejo.org to lookup tags.

"},{"location":"modules/datasource/galaxy/","title":"Galaxy Datasource","text":""},{"location":"modules/datasource/galaxy/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier galaxy Default versioning pep440 Custom registry support No Release timestamp support Yes The release timestamp is determined from the created field in the results. Source URL support Yes The source URL is determined from the github_user and github_repo fields in the results."},{"location":"modules/datasource/galaxy-collection/","title":"Galaxy Collection Datasource","text":""},{"location":"modules/datasource/galaxy-collection/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier galaxy-collection Default versioning pep440 Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created_at field in the results. Source URL support Yes The sourceUrl is determined from the repository field in the results."},{"location":"modules/datasource/galaxy-collection/#description","title":"Description","text":"

By default, the galaxy-collection datasource checks for dependencies on https://galaxy.ansible.com. But you can override the default if you want.

Set your own registries by:

Then you can use Renovate with a private automation hub or an ansible repository on artifactory.

Example config for requirements.yaml
---\ncollections:\n  - name: community.general\n    version: 3.0.0\n    source: https://hub.mydomain.com/api/galaxy/content/community/\n
Example config for renovate.json
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"galaxy-collection\"],\n      \"registryUrls\": [\n        \"https://hub.mydomain.com/api/galaxy/content/community/\",\n        \"https://hub.mydomain.com/api/galaxy/content/certified/\",\n        \"https://hub.mydomain.com/api/galaxy/content/myprivaterepo/\",\n        \"https://mydomain.com/artifactory/api/ansible/myrepository/\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/git-refs/","title":"Git Refs Datasource","text":""},{"location":"modules/datasource/git-refs/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier git-refs Default versioning No default versioning Custom registry support No Release timestamp support No Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/git-refs/#description","title":"Description","text":"

You can use this datasource plus regex managers to update git-based dependencies that are not natively supported by Renovate.

The git-refs datasource returns a reference from a Git repository.

The packageName must be a fully qualified domain name.

To fetch the latest digest of a reference instead of the named reference: put the named reference in currentValue and match on the currentDigest.

Usage example

Say you want to maintain the HEAD digest of the master branch of a repository. You would configure a custom manager in your Renovate config file for files named versions.ini:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^versions.ini$/\"],\n      \"matchStrings\": [\"GOOGLE_API_VERSION=(?<currentDigest>.*?)\\\\n\"],\n      \"currentValueTemplate\": \"master\",\n      \"depNameTemplate\": \"googleapis\",\n      \"packageNameTemplate\": \"https://github.com/googleapis/googleapis\",\n      \"datasourceTemplate\": \"git-refs\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/git-tags/","title":"Git Tags Datasource","text":""},{"location":"modules/datasource/git-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier git-tags Default versioning No default versioning Custom registry support No Release timestamp support No Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/gitea-releases/","title":"Gitea Releases Datasource","text":""},{"location":"modules/datasource/gitea-releases/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gitea-releases Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the published_at field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/gitea-releases/#description","title":"Description","text":"

This datasource allows to lookup releases from a Gitea repositories.

Note

Use forgejo-releases as the datasource if you are using Forgejo. Forgejo support will be removed from gitea-releases datasource in a future release.

By default it will use https://gitea.com to lookup releases.

"},{"location":"modules/datasource/gitea-tags/","title":"Gitea Tags Datasource","text":""},{"location":"modules/datasource/gitea-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gitea-tags Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/gitea-tags/#description","title":"Description","text":"

This datasource allows to lookup git tags from a Gitea repositories.

Note

Use forgejo-tags as the datasource if you are using Forgejo. Forgejo support will be removed from gitea-tags datasource in a future release.

By default it will use https://gitea.com to lookup tags.

"},{"location":"modules/datasource/github-digest/","title":"Github Digest Datasource","text":""},{"location":"modules/datasource/github-digest/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier github-digest Default versioning exact Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the commit date. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/github-digest/#description","title":"Description","text":"

This datasource fetches both tags and branches from GitHub repositories, prioritizing tags over branches when names conflict.

It's designed for GitHub Actions that reference non-semver refs like branch names (main, master) or commit SHAs. It uses exact versioning, meaning no version ordering is performed - only digest pinning updates are supported.

"},{"location":"modules/datasource/github-release-attachments/","title":"Github Release Attachments Datasource","text":""},{"location":"modules/datasource/github-release-attachments/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier github-release-attachments Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the releaseTimestamp field from the response. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/github-releases/","title":"Github Releases Datasource","text":""},{"location":"modules/datasource/github-releases/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier github-releases Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the releaseTimestamp field from the response. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/github-releases/#description","title":"Description","text":"

This datasource allows lookup releases from GitHub.com and GitHub Enterprise repositories.

"},{"location":"modules/datasource/github-runners/","title":"Github Runners Datasource","text":""},{"location":"modules/datasource/github-runners/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier github-runners Default versioning docker Custom registry support Yes Release timestamp support Yes The release timestamp is manually specified in Renovate's code, based on the date GitHub announced the runner image as generally available on their changelog Source URL support Yes We use the URL: https://github.com/actions/runner-images."},{"location":"modules/datasource/github-runners/#description","title":"Description","text":"

This datasource returns a list of all runners that are hosted by GitHub. The datasource is based on GitHub's runner-images and partner-runner-images repositories.

Examples: windows-2025 / ubuntu-24.04 / macos-15.

"},{"location":"modules/datasource/github-runners/#maintenance","title":"Maintenance","text":""},{"location":"modules/datasource/github-runners/#adding-a-new-version","title":"Adding a new version","text":"

New runner versions must be added to the datasource with a pull request.

"},{"location":"modules/datasource/github-runners/#unstable-runners","title":"Unstable runners","text":"

Unstable runners are tagged as [beta] in the runner-images repository's readme and should get the isStable:false property in our code.

"},{"location":"modules/datasource/github-runners/#promoting-a-version-to-stable","title":"Promoting a version to stable","text":"

Once a runner version becomes stable, the [beta] tag is removed and the suffix latest is added to its YAML label. We then remove the isStable:false property in our code.

"},{"location":"modules/datasource/github-runners/#deprecating-a-version","title":"Deprecating a version","text":"

Deprecated runners are tagged as [deprecated] in the runner-images repository's readme and we should give it the isDeprecated:true property. If a runner is very old, the readme may drop it completely, but we should still give it the isDeprecated:true property.

"},{"location":"modules/datasource/github-tags/","title":"Github Tags Datasource","text":""},{"location":"modules/datasource/github-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier github-tags Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The get release timestamp is determined from the releaseTimestamp field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/github-tags/#description","title":"Description","text":"

This datasource allows lookup Git tags from GitHub.com and GitHub Enterprise repositories.

"},{"location":"modules/datasource/gitlab-packages/","title":"Gitlab Packages Datasource","text":""},{"location":"modules/datasource/gitlab-packages/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gitlab-packages Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created_at field in the results. Source URL support No"},{"location":"modules/datasource/gitlab-packages/#description","title":"Description","text":"

GitLab Packages API supports looking up package versions from all types of packages registry supported by GitLab and can be used in combination with regex managers to keep dependencies up-to-date which are not specifically supported by Renovate.

To specify which specific repository should be queried when looking up a package, the packageName should be formed with the project path first, then a : and finally the package name.

As an example, gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list:@gitlab-org/nk-js would look for the@gitlab-org/nk-js packages in the generic packages repository of the gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list project.

To specify where to find a self-hosted GitLab instance, specify registryUrl. An example would be https://gitlab.company.com.

If you are using a self-hosted GitLab instance, please note the following requirements:

Usage Example

A real-world example for this specific datasource would be maintaining package versions in a config file. This can be achieved by configuring a custom manager in renovate.json for files named versions.ini:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^versions.ini$/\"],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\\\s.*?_VERSION=(?<currentValue>.*)\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ]\n}\n

Now you may use comments in your versions.ini files to automatically update dependencies, which could look like this:

# renovate: datasource=gitlab-packages depName=gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list:@gitlab-org/nk-js versioning=semver registryUrl=https://gitlab.com\nNKJS_VERSION=3.4.0\n

By default, gitlab-packages uses the docker versioning scheme.

"},{"location":"modules/datasource/gitlab-releases/","title":"Gitlab Releases Datasource","text":""},{"location":"modules/datasource/gitlab-releases/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gitlab-releases Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the released_at field in the results. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/gitlab-releases/#description","title":"Description","text":"

GitLab Releases API supports looking up releases supported by GitLab and can be used in combination with regex managers to keep dependencies up-to-date which are not specifically supported by Renovate.

To specify which specific repository should be queried when looking up a package, the packageName should be set to the project path.

As an example, gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list would look for releases in the gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list project.

To specify where to find a self-hosted GitLab instance, specify registryUrl. An example would be https://gitlab.company.com.

Please note the following requirements:

Usage Example

A real-world example for this specific datasource would be maintaining package versions in a config file. This can be achieved by configuring a custom manager in renovate.json for files named versions.ini:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^versions.ini$/\"],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\\\s.*?_VERSION=(?<currentValue>.*)\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ]\n}\n

Now you may use comments in your versions.ini files to automatically update dependencies, which could look like this:

# renovate: datasource=gitlab-releases depName=gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list versioning=semver registryUrl=https://gitlab.com\nNKJS_VERSION=3.4.0\n

By default, gitlab-releases uses the semver-coerced versioning scheme.

"},{"location":"modules/datasource/gitlab-tags/","title":"Gitlab Tags Datasource","text":""},{"location":"modules/datasource/gitlab-tags/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gitlab-tags Default versioning No default versioning Custom registry support Yes Release timestamp support Yes To get release timestamp we use the created_at field from the response. Source URL support Yes The source URL is determined by using the packageName and registryUrl."},{"location":"modules/datasource/gitlab-tags/#description","title":"Description","text":"

GitLab Tags API supports looking up Git tags and can be used in combination with regex managers to keep dependencies up-to-date which are not specifically supported by Renovate.

To specify which specific repository should be queried when looking up a package, the packageName should be set to the project path.

As an example, gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list would look for releases in the gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list project.

To specify where to find a self-hosted GitLab instance, specify registryUrl. An example would be https://gitlab.company.com.

Usage Example

A real-world example for this specific datasource would be maintaining package versions in a config file. This can be achieved by configuring a custom manager in renovate.json for files named versions.ini:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^versions.ini$/\"],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?( registryUrl=(?<registryUrl>.*?))?\\\\s.*?_VERSION=(?<currentValue>.*)\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ]\n}\n

Now you may use comments in your versions.ini files to automatically update dependencies, which could look like this:

# renovate: datasource=gitlab-tags depName=gitlab-org/ci-cd/package-stage/feature-testing/new-packages-list versioning=semver registryUrl=https://gitlab.com\nNKJS_VERSION=3.4.0\n

By default, gitlab-tags uses the semver-coerced versioning scheme.

"},{"location":"modules/datasource/glasskube-packages/","title":"Glasskube Packages Datasource","text":""},{"location":"modules/datasource/glasskube-packages/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier glasskube-packages Default versioning glasskube Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/go/","title":"Go Datasource","text":""},{"location":"modules/datasource/go/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier go Default versioning semver Custom registry support No Release timestamp support Yes If the release timestamp is not returned from the respective datasoure used to fetch the releases, then Renovate uses the Time field in the results instead. For modules hosted on GitHub, a later GitHub Release publication time or git tag creation time takes precedence over both. Source URL support Yes The source URL is determined from the packageName and registryUrl."},{"location":"modules/datasource/go/#description","title":"Description","text":"

The best way to lookup Go Modules is using Go proxies.

"},{"location":"modules/datasource/go/#goproxy-settings","title":"GOPROXY settings","text":"

This datasource will use default GOPROXY settings of https://proxy.golang.org,direct if the environment variable is unset.

To override this default and use a different proxy in self-hosted environments, configure GOPROXY to an alternative setting in env.

To override this default and stop using any proxy at all, set GOPROXY to the value direct.

"},{"location":"modules/datasource/go/#pseudo-versions","title":"Pseudo versions","text":"

Go proxies return an empty list of versions when queried (@v/list) for a package which uses pseudo versions, but return the latest pseudo-version when queried for @latest.

If the @latest endpoint returns a pseudo-version, and the release list is empty, then this datasource will return the latest pseudo-version as the only release/version for the package.

"},{"location":"modules/datasource/go/#checking-for-new-major-releases","title":"Checking for new major releases","text":"

When a Go proxy is queried for @v/list it returns only versions for v0 or v1 of a package. Therefore Renovate will also query @v2/list just in case there also exists a v2 of the package. Similarly, if the dependency is already on a higher version such as v5, Renovate will check in case higher major versions exist. You do not need to be worried about any 403/404 responses which result from such checks - they are the only way for Renovate to know if newer major releases exist.

"},{"location":"modules/datasource/go/#release-timestamps","title":"Release timestamps","text":"

A Go proxy reports the commit time of the tagged commit as a version's Time, which can be different to when the release first existed. This inconsistency can lead to minimumReleaseAge being applied incorrectly to the Go module's updates.

Note

For modules hosted on GitHub, Renovate will look up the repository's GitHub Releases and git tags, and use whichever of the Release's publication time or the tag's own creation time is later than the timestamp reported by the Go proxy. A Release's publication time takes precedence over a tag's creation time if both exist for the same version. This lookup needs a GitHub token to be configured, and is skipped if the lookup fails, leaving the timestamp reported by the Go proxy in place.

For example, this happens when:

Similarly, a lightweight git tag has no creation time of its own and always matches the commit it points to, but an annotated git tag carries its own, separate creation time that can be later than the commit it points to, even without a GitHub Release ever being published.

"},{"location":"modules/datasource/go/#fallback-to-direct-lookups","title":"Fallback to direct lookups","text":"

If no result is found from Go proxy lookups then Renovate will fall back to direct lookups. A direct lookup reports the datasource which served it, such as github-tags or git-tags, as effectiveDatasource, which templates and matchJsonata can read.

"},{"location":"modules/datasource/go/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageTopic\": \"module {{depName}}\"\n}\n
"},{"location":"modules/datasource/golang-version/","title":"Golang Version Datasource","text":""},{"location":"modules/datasource/golang-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier golang-version Default versioning semver Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the Date field in the results. Source URL support Yes We use the URL: https://github.com/golang/go."},{"location":"modules/datasource/gradle-version/","title":"Gradle Version Datasource","text":""},{"location":"modules/datasource/gradle-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier gradle-version Default versioning gradle Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the buildTime field in the results. Source URL support Yes We use the URL: https://github.com/gradle/gradle."},{"location":"modules/datasource/hackage/","title":"Hackage Datasource","text":""},{"location":"modules/datasource/hackage/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier hackage Default versioning pvp Custom registry support No Release timestamp support No Source URL support No"},{"location":"modules/datasource/hackage/#description","title":"Description","text":"

This datasource uses the Hackage JSON API to fetch versions for published Haskell packages.

While not all versions use PVP, the majority does. This manager assumes a default versioning set to PVP. Versioning can be overwritten using packageRules, e.g. with matchDatasources.

"},{"location":"modules/datasource/helm/","title":"Helm Datasource","text":""},{"location":"modules/datasource/helm/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier helm Default versioning helm Custom registry support Yes Release timestamp support Yes The release timstamp is determined from the created field in the results. Source URL support Yes The source URL is determined from the home field or the sources field in the results."},{"location":"modules/datasource/helm/#description","title":"Description","text":"

This datasource reads index.yaml from a Helm chart repository.

"},{"location":"modules/datasource/helm/#amazon-s3-repositories","title":"Amazon S3 repositories","text":"

In addition to HTTP(S) repositories, an s3:// registry URL is supported, so charts hosted in an Amazon S3 bucket (or an S3-compatible backend) can be looked up:

dependencies:\n  - name: my-chart\n    version: 1.0.0\n    repository: s3://my-bucket/charts\n

Renovate then reads s3://my-bucket/charts/index.yaml with the AWS SDK, which signs the request with AWS Signature Version 4. See Calling AWS Services from Renovate for how to configure your credentials.

For S3-compatible backends, set the self-hosted s3Endpoint and s3PathStyle configuration options.

You can also provide credentials specifically for a bucket with a hostRules entry. Set hostType to helm, matchHost to the bucket name, username to the access key ID, password to the secret access key, and optionally token to the session token:

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"helm\",\n      \"matchHost\": \"my-bucket\",\n      \"username\": \"AKIAIOSFODNN7EXAMPLE\",\n      \"password\": \"wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY\"\n    }\n  ]\n}\n

If no matching host rule provides both username and password, the default AWS credential provider chain is used.

"},{"location":"modules/datasource/helm/#default-configuration","title":"Default configuration","text":"
{\n  \"commitMessageTopic\": \"Helm release {{depName}}\"\n}\n
"},{"location":"modules/datasource/hermit/","title":"Hermit Datasource","text":""},{"location":"modules/datasource/hermit/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier hermit Default versioning hermit Custom registry support Yes Release timestamp support No Source URL support Yes The source URL is determined from the Repository field in the results."},{"location":"modules/datasource/hermit/#description","title":"Description","text":"

By default Hermit looks up packages from the open source project https://github.com/cashapp/hermit-packages.

Hermit supports private packages. To get Renovate to find your private packages, follow these steps:

  1. perform hermit search --json with your private Hermit distribution and save the file to index.json
  2. make a GitHub release in your private packages repository named index with the asset index.json generated in step 1.
  3. setup a CI pipeline to repeat step 1 & 2 on new commits to the private packages repository.

  4. Add a package rule for the Hermit manager, so that Renovate knows where to find your private packages:

    {\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"hermit\"],\n      \"defaultRegistryUrls\": [\n        \"https://github.com/your/private-hermit-packages\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/hex/","title":"Hex Datasource","text":""},{"location":"modules/datasource/hex/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier hex Default versioning hex Custom registry support Yes Release timestamp support Yes The release timestamp is determined the inserted_at field in the results. Source URL support Yes The source URL is determined from the Github field in the results."},{"location":"modules/datasource/hexpm-bob/","title":"Hexpm Bob Datasource","text":""},{"location":"modules/datasource/hexpm-bob/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier hexpm-bob Default versioning semver Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the buildDate field in the results. Source URL support Yes We use the URL https://github.com/elixir-lang/elixir.git for the elixir package and the https://github.com/erlang/otp.git URL for the erlang package."},{"location":"modules/datasource/hexpm-bob/#description","title":"Description","text":"

This datasource returns releases from Bob the builder.

Supported values for packageName:

Read the Bob the builder docs, Erlang builds for a list of supported operating systems and versions.

"},{"location":"modules/datasource/java-version/","title":"Java Version Datasource","text":""},{"location":"modules/datasource/java-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier java-version Default versioning No default versioning Custom registry support No Release timestamp support No Source URL support No"},{"location":"modules/datasource/java-version/#description","title":"Description","text":"

This datasource returns releases from the Adoptium API.

It uses image_type=<jre|jdk>&project=jdk&release_type=ga&sort_method=DATE&sort_order=DESC as filter parameters. This means that the datasource finds:

When Renovate contacts the Adoptium API, it fetches 50 pages. Each page has 50 items. So 2500 items are fetched from the API in total.

If you want to get releases which come with the JDK, set the packageName to java-jdk or java.

If you want to get releases which come with the JRE, set the packageName to java-jre. LTS releases of Java will have a version that comes with the JRE. Non-LTS releases may not always include the JRE.

Additionally you can filter by os and architecture. For example, to get only Linux x64 jre releases, you can pass java-jre?os=linux&architecture=x64 as packageName. See https://api.adoptium.net/q/swagger-ui/#/Release%20Info/getReleaseVersions for allowed values.

Use java?system=true to let renovate detect the current os and architecture.

"},{"location":"modules/datasource/jenkins-plugins/","title":"Jenkins Plugins Datasource","text":""},{"location":"modules/datasource/jenkins-plugins/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier jenkins-plugins Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The releaseTimestamp is determined from the releaseTimestamp or buildDate field in the results. Source URL support Yes The source URL is determined from the scm field in the results."},{"location":"modules/datasource/jenkins-plugins/#description","title":"Description","text":"

The jenkins-plugins datasource supports lookups from the Jenkins Update Center or custom registries.

When you define a custom registry with the registryUrl config option, you must follow Jenkins' update site layout.

The update-center.actual.json and plugin-versions.json files must be in the current path, so Renovate can find them. For example, the files could be put in the https://custom.registry.renovatebot.com/current directory.

"},{"location":"modules/datasource/jsr/","title":"Jsr Datasource","text":""},{"location":"modules/datasource/jsr/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier jsr Default versioning semver Custom registry support No Release timestamp support Yes The release timestamp is determined from the createdAt field in the results. For packages without explicit timestamps, defaults to 2025-09-18. Source URL support No"},{"location":"modules/datasource/julia-general-metadata/","title":"Julia General Metadata Datasource","text":""},{"location":"modules/datasource/julia-general-metadata/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier julia-general-metadata Default versioning julia Custom registry support No Release timestamp support Yes The release timestamp is determined from the registered field in the results. Source URL support No"},{"location":"modules/datasource/julia-general-metadata/#description","title":"Description","text":"

This datasource returns release information for Julia packages registered in the public General registry, via the GeneralMetadata.jl JSON API at https://juliaregistries.github.io/GeneralMetadata.jl/api/{Package}/versions.json.

Because the GeneralMetadata.jl API only offers information on packages registered in the General registry, this datasource does not support custom registry URLs. Private or alternative Julia registries (e.g. those managed via LocalRegistry.jl) need a different datasource.

The package name is the case-sensitive Julia package name, e.g. Example.

"},{"location":"modules/datasource/kubernetes-api/","title":"Kubernetes Api Datasource","text":""},{"location":"modules/datasource/kubernetes-api/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier kubernetes-api Default versioning kubernetes-api Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/kubernetes-api/#description","title":"Description","text":"

Kubernetes API upgrade versions are manually transcribed from the Kubernetes API deprecation guide. The Kubernetes API deprecation guide is updated regularly, so this list may be out of date. This also contains some flux custom resources which where also manually added from flux releases as well as external secrets custom resources.

"},{"location":"modules/datasource/maven/","title":"Maven Datasource","text":""},{"location":"modules/datasource/maven/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier maven Default versioning maven Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Source URL support Yes The source URL is determined from the scm tags in the results."},{"location":"modules/datasource/maven/#description","title":"Description","text":""},{"location":"modules/datasource/maven/#maven-central-rate-limiting-and-caching","title":"Maven Central rate limiting and caching","text":"

Maven Central, hosted by Sonatype, receives a very large number of requests and has implemented rate limiting measures to manage organizational overconsumption. If you're experiencing 429 (rate limited) responses from Maven Central, you may need to optimize your caching strategy.

Renovate includes Maven caching optimizations, but they rely on having a persistent datasource cache. By default, Renovate uses a file-based cache, which means:

To maximize caching effectiveness and reduce Maven Central requests:

  1. Use Redis for persistent caching: Configure a Redis instance for your Renovate datasource cache
  2. Ensure cache persistence: If using file-based caching, ensure the cache directory persists between Renovate runs
  3. Monitor rate limit warnings: Renovate will log warnings when receiving 429 responses from Maven Central

If you continue to experience rate limiting issues after implementing persistent caching, you may need to:

Note

Dependencies that appear to be Gradle plugins (where the groupId or artifactId ends with .gradle.plugin) will not be looked up in Maven Central.

"},{"location":"modules/datasource/maven/#making-your-changelogs-fetchable","title":"Making your changelogs fetchable","text":"

In case you are publishing artifacts and you want to ensure that your changelogs are fetchable by Renovate, you need to configure the scm section on their pom.xml file.

For example:

<scm>\n    <url>scm:git:https://github.com/path_to_repository</url>\n</scm>\n

This is what allows Renovate to determine the sourceUrl, that it then uses to fetch the changelogs.

Note

This also works for private repositories. It can leverage the same token that you had to configure in order to be able to reach the private Artifactory.

"},{"location":"modules/datasource/maven/#specifying-your-project-homepage","title":"Specifying your project homepage","text":"

When opening a Pull Request Renovate uses the top level url property to determine the homepage of your project and shows it inside the Pull Request. To customize you can set it inside your pom.xml.

For example:

<url>https://project.example.com</url>\n
"},{"location":"modules/datasource/maven/#latest-and-release-tags","title":"latest and release tags","text":"

When latest or release values are present in a package's maven-metadata.xml, Renovate will map these to its tags concept. This enables the use of Renovate's followTag feature.

However, Renovate will set respectLatest=false whenever the latest tag is found, because many Maven registries have been found to populate the tag unreliably. You should use packageRules to set respectLatest=true if you wish to use this feature.

"},{"location":"modules/datasource/nextcloud/","title":"Nextcloud Datasource","text":""},{"location":"modules/datasource/nextcloud/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier nextcloud Default versioning semver Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/nextcloud/#description","title":"Description","text":"

This datasource finds Nextcloud application updates from Nextcloud feeds.

By default, Renovate has no default registry url for this datasource. You need to override the default behavior with the registryUrls config option. For example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"nextcloud\"],\n      \"registryUrls\": [\n        \"https://apps.nextcloud.com/api/v1/platform/30.0.0/apps.json\"\n      ]\n    }\n  ]\n}\n

Additionally, if you want Renovate to automatically update the platform version, you can create a custom manager. For example:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/(^|/)renovate.json$/\"],\n      \"matchStrings\": [\n        \"https://apps.nextcloud.com/api/v1/platform/(?<currentValue>\\\\d+\\\\.\\\\d+\\\\.\\\\d+)/apps.json\"\n      ],\n      \"depNameTemplate\": \"nextcloud/server\",\n      \"datasourceTemplate\": \"github-releases\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/node-version/","title":"Node Version Datasource","text":""},{"location":"modules/datasource/node-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier node-version Default versioning node Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the date field. Source URL support Yes We use the URL: https://github.com/nodejs/node"},{"location":"modules/datasource/node-version/#description","title":"Description","text":"

This datasource returns NodeJS releases from nodejs.org API.

"},{"location":"modules/datasource/npm/","title":"Npm Datasource","text":""},{"location":"modules/datasource/npm/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier npm Default versioning npm Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the time field in the results. Source URL support Yes The source URL is determined from the repository field in the results."},{"location":"modules/datasource/nuget/","title":"Nuget Datasource","text":""},{"location":"modules/datasource/nuget/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier nuget Default versioning nuget Custom registry support Yes Release timestamp support Yes For the v2 API, the release timestamp is determined from the Published tag. And, for the v3 API, the release timestamp is determined from the published field in the results. Source URL support Yes For the v2 API, the source URL is determined from the ProjectUrl tag. And, for the v3 API, the source URL is determined from the metadata.repository@url field in the results."},{"location":"modules/datasource/orb/","title":"Orb Datasource","text":""},{"location":"modules/datasource/orb/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier orb Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created_at field in the results. Source URL support No"},{"location":"modules/datasource/packagist/","title":"Packagist Datasource","text":""},{"location":"modules/datasource/packagist/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier packagist Default versioning composer Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the time field in the results. Source URL support Yes The source URL is determined from source field in the results."},{"location":"modules/datasource/pod/","title":"Pod Datasource","text":""},{"location":"modules/datasource/pod/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier pod Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/puppet-forge/","title":"Puppet Forge Datasource","text":""},{"location":"modules/datasource/puppet-forge/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier puppet-forge Default versioning No default versioning Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created_at field from the response. Source URL support No"},{"location":"modules/datasource/pypi/","title":"Pypi Datasource","text":""},{"location":"modules/datasource/pypi/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier pypi Default versioning pep440 Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the earliest upload_time field of the files of a version. When using the Simple API, timestamps are available if the server supports the JSON-based Simple API (PEP 691). Source URL support Yes The source URL is determined from the homepage field if it is a github repository, else we use the project_urls field."},{"location":"modules/datasource/pypi/#description","title":"Description","text":"

This datasource uses the following logic to determine lookup URLs:

The Simple API supports both the HTML serialization (PEP 503) and the JSON serialization (PEP 691). Renovate uses content negotiation (an Accept header) to prefer the JSON serialization, falling back to HTML automatically if the registry does not support it. If the registry responds 406 because it cannot serve any of the negotiated types, Renovate retries the request without that header.

Renovate reads the release timestamp from the upload_time of a version's files, or the upload-time (PEP 700), which the Simple JSON API exposes, so minimumReleaseAge works against it.

If you are using Artifactory, you must explicitly enable the generation of upload-time metadata server-side.

"},{"location":"modules/datasource/python-version/","title":"Python Version Datasource","text":""},{"location":"modules/datasource/python-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier python-version Default versioning python Custom registry support No Release timestamp support No Source URL support No"},{"location":"modules/datasource/python-version/#description","title":"Description","text":"

This datasource returns Python releases from the python.org API.

It also fetches deprecated versions from the Endoflife Date datasource.

Because Renovate depends on containerbase/python-prebuild it will also fetch releases from the GitHub API.

"},{"location":"modules/datasource/python-version/#example-custom-manager","title":"Example custom manager","text":"

Below is a custom regex manager to update the Python versions in a Dockerfile. Python versions sometimes drop the dot that separate the major and minor number: so 3.11 becomes 311. The example below handles this case.

ARG PYTHON_VERSION=311\nFROM image-python${PYTHON_VERSION}-builder:1.0.0\n
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^Dockerfile$/\"],\n      \"matchStringsStrategy\": \"any\",\n      \"matchStrings\": [\n        \"ARG PYTHON_VERSION=\\\"?(?<currentValue>3(?<minor>\\\\d+))\\\"?\\\\s\"\n      ],\n      \"autoReplaceStringTemplate\": \"ARG PYTHON_VERSION={{{replace '\\\\.' '' newValue}}}\\n\",\n      \"currentValueTemplate\": \"3.{{{minor}}}\",\n      \"datasourceTemplate\": \"python-version\",\n      \"versioningTemplate\": \"python\",\n      \"depNameTemplate\": \"python\"\n    }\n  ]\n}\n
"},{"location":"modules/datasource/repology/","title":"Repology Datasource","text":""},{"location":"modules/datasource/repology/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier repology Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/repology/#description","title":"Description","text":"

With Repology you can look up package versions from many package repositories. You can combine Repology with regex managers to update dependencies which are not supported by Renovate.

The packageName field should be constructed using the repository identifier and the actual package name separated by a slash. For example: alpine_3_12/gcc would look for a binary (or source package) called gcc within the alpine_3_12 repository.

A list of all supported repositories can be found on the Repology homepage.

To find the correct identifier, select the repository you want and copy the identifier in the URL: https://repology.org/repository/<identifier>. For example, the Alpine Linux 3.12 repository has this URL: https://repology.org/repository/alpine_3_12 and has this repository identifier: alpine_3_12.

Usage Example

Say you're using system packages in a Dockerfile and want to update them with Repology. With the Repology datasource you can \"pin\" each dependency, and get automatic updates.

First you would set a custom manager in your renovate.json file for Dockerfile:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^Dockerfile$/\"],\n      \"matchStrings\": [\n        \"#\\\\s*renovate:\\\\s*datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\\\sENV .*?_VERSION=\\\"(?<currentValue>.*)\\\"\\\\s\"\n      ],\n      \"versioningTemplate\": \"{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}\"\n    }\n  ]\n}\n

Then you would put comments in your Dockerfile, to tell Renovate where to find the updates:

FROM alpine:3.12.0@sha256:a15790640a6690aa1730c38cf0a440e2aa44aaca9b0e8931a9f2b0d7cc90fd65\n\n# renovate: datasource=repology depName=alpine_3_12/gcc versioning=loose\nENV GCC_VERSION=\"9.3.0-r2\"\n# renovate: datasource=repology depName=alpine_3_12/musl-dev versioning=loose\nENV MUSL_DEV_VERSION=\"1.1.24-r8\"\n\nRUN apk add --no-cache \\\n    gcc=\"${GCC_VERSION}\" \\\n    musl-dev=\"${MUSL_DEV_VERSION}\"\n

When the operating system package for gcc of Alpine Linux 3.12 is updated, Renovate updates the environment variable.

Tip

We recommend you try loose or deb versioning for distribution packages first. This is because the version number usually doesn't match Renovate's default semver-coerced specification.

"},{"location":"modules/datasource/rpm/","title":"Rpm Datasource","text":""},{"location":"modules/datasource/rpm/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier rpm Default versioning No default versioning Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/rpm/#description","title":"Description","text":"

This datasource rpm returns releases of the RPM packages. It assumes the RPM repository is following the RPM standard and by default it has a repomd.xml in the directory provided by user in the registryUrl. According to this Pulp project doc, https://docs.pulpproject.org/en/2.10/plugins/pulp_rpm/tech-reference/rpm.html,

repomd.xml is the metadata file that clients use to discover what repository metadata files exist in the repository. It should always be located at repodata/repomd.xml relative to the root of the repository.

"},{"location":"modules/datasource/rpm/#set-url-when-using-an-rpm-repository","title":"Set URL when using an RPM repository","text":"

To use an RPM repository with the datasource, you must set a registryUrl with the directory that contains the repomd.xml and corresponding primary.xml.

Example:

If we have

Then the registryUrl should set as http://example.com/repo/repodata/ or http://example.com/repo/repodata.

"},{"location":"modules/datasource/rpm/#usage-example","title":"Usage Example","text":"

Say you're defining dnf/tdnf/yum packages in a manifest.json and you want Renovate to update them.

Assuming your manifest.json looks like this.

{\n  \"example-package1\": \"1.0.0-1.azl3\",\n  \"example-package2\": \"1.1.0\"\n}\n

where the versioning format could be <semantic version>-<revision or release>, or just <semantic version>

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\n        \"path_to_manifest_json\"\n      ],\n      \"registryUrlTemplate\": \"http://example.com/repo/repodata/\",\n      \"datasourceTemplate\": \"rpm\"\n    }\n  ]\n}\n

In an RPM repository, the <SHA256>-primary.xml looks like this:

`<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<metadata xmlns=\"http://linux.duke.edu/metadata/common\">\n  <package type=\"rpm\">\n    <name>example-package1</name>\n    <arch>x86_64</arch>\n    <version epoch=\"0\" ver=\"1.0\" rel=\"2.azl3\"/>\n  </package>\n  <package type=\"rpm\">\n    <name>example-package1</name>\n    <arch>x86_64</arch>\n    <version epoch=\"0\" ver=\"1.1\" rel=\"1.azl3\"/>\n  </package>\n  <package type=\"rpm\">\n    <name>example-package1</name>\n    <arch>x86_64</arch>\n    <version epoch=\"0\" ver=\"1.1\" rel=\"2.azl3\"/>\n  </package>\n  <package type=\"rpm\">\n    <name>example-package1</name>\n    <arch>x86_64</arch>\n    <version epoch=\"0\" ver=\"1.2\"/>\n  </package>\n...\n...\n</metadata>\n

You may also check the yum/dnf info for the package to find version and release:

# dnf info example-package1\nLast metadata expiration check: 18:34:13 ago on Tue Oct  7 13:58:36 2025.\nInstalled Packages\nName         : example-package1\nVersion      : 1.0.0\nRelease      : 1.azl3\nArchitecture : x86_64\n[...]\n

You can see that ver and rel (release/revision) is stored separately. The RPM datasource implementation will combine these together as ver-rel. That's why the version is defined as 1.0.0-1.az3, if rel (like example-package1) is available. Or just 1.1.0 if rel (like example-package2) is not available.

"},{"location":"modules/datasource/rpm/#limitation-and-consideration","title":"Limitation and Consideration","text":"

In real-world scenarios, the decompressed primary.xml file from an RPM repository can be extremely large. To handle this efficiently, this implementation uses streaming XML parsing, which processes the file incrementally and avoids loading the entire XML into memory.

Streaming XML parsing is a practical solution for large files in Node.js, but for extremely large or complex cases (e.g., files exceeding ~512MB), you may still encounter memory or performance issues. For such scenarios, consider using more robust approaches such as native modules, optimized SAX parsers, or external tools. Contributions and suggestions for further improving large file handling are welcome.

"},{"location":"modules/datasource/ruby-version/","title":"Ruby Version Datasource","text":""},{"location":"modules/datasource/ruby-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier ruby-version Default versioning ruby Custom registry support No Release timestamp support Yes The release timestamp is determined from the release-list table in the results. Source URL support Yes We use the URL: https://github.com/ruby/ruby."},{"location":"modules/datasource/rubygems/","title":"Rubygems Datasource","text":""},{"location":"modules/datasource/rubygems/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier rubygems Default versioning ruby Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the created_at field in the results. Source URL support Yes The source URL is determined from the source_code_uri field in the results."},{"location":"modules/datasource/rubygems/#description","title":"Description","text":""},{"location":"modules/datasource/rubygems/#rubygems-datasource_1","title":"Rubygems datasource","text":"

Datasource query order depends on the registry.

"},{"location":"modules/datasource/rubygems/#querying-rubygemsorg","title":"Querying rubygems.org","text":"

Rubygems rate limits are easy to hit, so we need to be careful with the queries. This is implemented with two-level cache:

"},{"location":"modules/datasource/rubygems/#querying-rubygemspkggithubcom-or-gitlabcom","title":"Querying rubygems.pkg.github.com or gitlab.com","text":"

These particular registries are queried using obsolete API

"},{"location":"modules/datasource/rubygems/#other-registries","title":"Other registries","text":""},{"location":"modules/datasource/rust-version/","title":"Rust Version Datasource","text":""},{"location":"modules/datasource/rust-version/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier rust-version Default versioning rust-release-channel Custom registry support No Release timestamp support Yes The release timestamp is parsed from the release manifest URL. Source URL support Yes"},{"location":"modules/datasource/rust-version/#description","title":"Description","text":"

This datasource fetches available Rust compiler versions from the official Rust distribution infrastructure at https://static.rust-lang.org/manifests.txt.

"},{"location":"modules/datasource/rust-version/#how-it-works","title":"How it works","text":"

The datasource retrieves version information from a single source file (manifests.txt) which contains chronological URLs to manifest files for all Rust releases. Rather than fetching each individual manifest TOML file, version information is extracted directly from the URL patterns using regex parsing.

"},{"location":"modules/datasource/rust-version/#supported-versions","title":"Supported Versions","text":"

The datasource only returns versions that correspond to specific Rust releases:

"},{"location":"modules/datasource/rust-version/#version-extraction","title":"Version Extraction","text":"

Manifest URLs follow this pattern:

static.rust-lang.org/dist/YYYY-MM-DD/channel-rust-{identifier}.toml\n

Examples:

"},{"location":"modules/datasource/rust-version/#release-timestamps","title":"Release Timestamps","text":"

Release timestamps are derived from the date in the manifest URL and set to midnight UTC (YYYY-MM-DDTHH:MM:SS.000Z). This provides day-level precision for release timing.

"},{"location":"modules/datasource/rust-version/#versioning-scheme","title":"Versioning Scheme","text":"

This datasource uses the rust-release-channel versioning scheme, which understands Rust's release channels, dated nightlies, and semantic versioning for stable and beta releases.

"},{"location":"modules/datasource/sbt-package/","title":"Sbt Package Datasource","text":""},{"location":"modules/datasource/sbt-package/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier sbt-package Default versioning ivy Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the Last-Modified header or the lastModified field in the results. Source URL support Yes The source URL is determined from the scm tags in the results."},{"location":"modules/datasource/sbt-package/#description","title":"Description","text":"

This datasource finds SBT package updates from Maven repositories.

By default, Renovate checks https://repo.maven.apache.org/maven2 for SBT packages. You can override the default behavior with the registryUrls config option. For example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"sbt-package\"],\n      \"registryUrls\": [\n        \"https://repo.maven.apache.org/maven2\",\n        \"https://oss.sonatype.org/content/repositories/snapshots\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/sbt-plugin/","title":"Sbt Plugin Datasource","text":""},{"location":"modules/datasource/sbt-plugin/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier sbt-plugin Default versioning ivy Custom registry support Yes Release timestamp support No Source URL support Yes The source URL is determined from the scm tags in the results."},{"location":"modules/datasource/sbt-plugin/#description","title":"Description","text":"

This datasource finds SBT plugin updates from Maven repositories.

By default, Renovate:

  1. Checks https://repo1.maven.org/maven2/ for SBT plugins
  2. If the above URL returns no results, then Renovate tries the legacy URL: https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases

You can override the default behavior with the registryUrls config option. For example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"sbt-plugin\"],\n      \"registryUrls\": [\n        \"https://repo1.maven.org/maven2/\",\n        \"https://oss.sonatype.org/content/repositories/snapshots\",\n        \"https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/datasource/terraform-module/","title":"Terraform Module Datasource","text":""},{"location":"modules/datasource/terraform-module/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier terraform-module Default versioning hashicorp Custom registry support Yes Release timestamp support Yes For registry.terraform.io and registry.opentofu.org (via api.opentofu.org), release timestamps are available for all versions. For app.terraform.io, only the latest version is annotated, using the published_at field from the extended module endpoint. Source URL support Yes For registry.terraform.io and app.terraform.io, the source URL is taken from the source field of the registry response. For registry.opentofu.org, it is derived from the package name following the OpenTofu registry policy of github.com/NAMESPACE/terraform-TARGETSYSTEM-NAME."},{"location":"modules/datasource/terraform-provider/","title":"Terraform Provider Datasource","text":""},{"location":"modules/datasource/terraform-provider/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier terraform-provider Default versioning hashicorp Custom registry support Yes Release timestamp support Yes The release timestamp is only available for registry.terraform.io (v2 API) and registry.opentofu.org (via api.opentofu.org). Other registries using the Provider Registry Protocol do not provide timestamps. Source URL support Yes For registry.terraform.io, the source URL is taken from the source field of the v2 API response. For registry.opentofu.org, it is derived from the package name following the OpenTofu registry policy of github.com/NAMESPACE/terraform-provider-NAME."},{"location":"modules/datasource/typst/","title":"Typst Datasource","text":""},{"location":"modules/datasource/typst/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier typst Default versioning semver-coerced Custom registry support No Release timestamp support No Source URL support No"},{"location":"modules/datasource/unity3d/","title":"Unity3d Datasource","text":""},{"location":"modules/datasource/unity3d/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier unity3d Default versioning unity3d Custom registry support Yes Release timestamp support Yes The release timestamp is determined from the releaseDate field in the results. Source URL support No"},{"location":"modules/datasource/unity3d-packages/","title":"Unity3d Packages Datasource","text":""},{"location":"modules/datasource/unity3d-packages/#table-of-values","title":"Table of values","text":"Name Value Notes Identifier unity3d-packages Default versioning unity3d-packages Custom registry support Yes Release timestamp support No Source URL support No"},{"location":"modules/datasource/unity3d-packages/#description","title":"Description","text":"

This datasource finds Unity package updates from Unity package feeds.

By default, Renovate checks https://packages.unity.com for Unity packages.

You can override the default behavior with the registryUrls config option. For example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"unity3d-packages\"],\n      \"registryUrls\": [\"https://package.openupm.com\"]\n    }\n  ]\n}\n
"},{"location":"modules/manager/","title":"Managers","text":"

Renovate is based around the concept of \"package managers\", or \"managers\" for short. These range from traditional package managers like npm, Bundler and Composer through to less traditional concepts like CircleCI or Travis config files.

The goal of Renovate is to detect and maintain all third-party dependencies in your repositories, through the use of managers.

"},{"location":"modules/manager/#supported-managers","title":"Supported Managers","text":"Group Category ID Managers Ansible ansible ansible, ansible-galaxy Batect batect batect, batect-wrapper Bazel bazel bazel, bazel-module, bazelisk C and C++ c conan Continuous Delivery cd argocd, buildpacks, cdnurl, fleet, flux, glasskube, helmfile, helmsman, html, sveltos, tekton Continuous Integration ci azure-pipelines, bitbucket-pipelines, bitrise, buildkite, buildpacks, circleci, cloudbuild, crow, droneci, github-actions, gitlabci, gitlabci-include, jenkins, tekton, travis, velaci, woodpecker Custom Managers custom regex, jsonata Dart dart fvm, pub Docker docker buildpacks, devcontainer, docker-compose, dockerfile, quadlet .NET dotnet cake, nuget, paket, unity3d Elixir elixir gleam, mix Go golang gomod, ocb Haskell haskell haskell-cabal Helm helm helm-requirements, helm-values, helmfile, helmsman, helmv3, vendir Infrastructure as Code iac ansible, ansible-galaxy, bicep, crossplane, puppet, terraform, terragrunt Java java ant, deps-edn, gradle, gradle-wrapper, kotlin-script, leiningen, maven, maven-wrapper, osgi, sbt, scalafmt, smithy JavaScript js bun, bun-version, deno, meteor, nodenv, npm, nvm Kubernetes kubernetes argocd, crossplane, fleet, flux, glasskube, helm-requirements, helm-values, helmfile, helmsman, helmv3, jsonnet-bundler, kubernetes, kustomize, sveltos, vendir Node.js node nodenv, nvm Perl perl cpanfile PHP php composer Python python copier, homeassistant-manifest, pep621, pep723, pip-compile, pip_requirements, pip_setup, pipenv, pixi, poetry, pyenv, runtime-version, setup-cfg Ruby ruby bundler, puppet, ruby-version Rust rust cargo, rust-toolchain Swift swift cocoapods, mint, swift, xcodegen Terraform terraform terraform, terraform-version, terragrunt, terragrunt-version, tflint-plugin No Category n/a apm, asdf, devbox, git-submodules, hermit, homebrew, mise, nix, pre-commit, proto, renovate-config, typst"},{"location":"modules/manager/#configuring-managers","title":"Configuring Managers","text":""},{"location":"modules/manager/#file-matching","title":"File Matching","text":"

Most Renovate managers have a default managerFilePatterns array. The managerFilePatterns array can hold a regular expression or glob pattern, that match against the repository file list.

"},{"location":"modules/manager/#managers-with-no-default-managerfilepatterns","title":"Managers with no default managerFilePatterns","text":"

Some managers have no default managerFilePatterns, because they have no filename convention that would let Renovate intelligently filter them. If there is no default filePattern, the manager is disabled. For the manager to work, you must create a managerFilePatterns regular expression, or glob pattern. For example:

{\n  \"kubernetes\": {\n    \"managerFilePatterns\": [\"/^config/.*\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/#extending-a-managers-default-managerfilepatterns","title":"Extending a manager's default managerFilePatterns","text":"

If the default managerFilePatterns for a manager does not match your file(s), you can extend the pattern. You extend the pattern by configuring the manager's managerFilePatterns. For example:

{\n  \"dockerfile\": {\n    \"managerFilePatterns\": [\"does-not-look-like-a-docker-file\"]\n  }\n}\n
"},{"location":"modules/manager/#ignoring-files-that-match-the-default-managerfilepatterns","title":"Ignoring files that match the default managerFilePatterns","text":"

Renovate will extend the existing managerFilePatterns, meaning you don't need to include the default patterns like Dockerfile in your own array. In other words, the patterns are \"additive\". If a manager matches a file that you don't want it to, ignore it using the ignorePaths configuration option. Also, if you ever find that Renovate is not matching a file name that you're certain it should, check your preset config isn't the cause of it. The config:recommended preset ignores common test and example directory names, for example.

"},{"location":"modules/manager/#enabling-and-disabling-managers","title":"Enabling and disabling managers","text":""},{"location":"modules/manager/#enabling-experimental-managers","title":"Enabling experimental managers","text":"

Most managers are enabled by default. For those that aren't, typically because they are considered experimental, you can opt-in manually. If there was a manager called some-new-manager you would enable it like this:

{\n  \"some-new-manager\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"modules/manager/#disabling-managers","title":"Disabling managers","text":"Example of disabling a specific manager (gradle)
{\n  \"gradle\": {\n    \"enabled\": false\n  }\n}\n

Please check the list of supported managers.

"},{"location":"modules/manager/#limiting-enabled-managers","title":"Limiting enabled managers","text":"

Say you only want to use Renovate for JavaScript packages, and to update your Dockerfile, and don't want any other updates. You can use the enabledManagers array, to list the managers you want to use (npm, dockerfile):

{\n  \"enabledManagers\": [\"npm\", \"dockerfile\"]\n}\n

Using the enabledManagers array disables all other managers, this includes Bundler, Composer, Docker Compose, etc.

"},{"location":"modules/manager/ansible/","title":"Automated Dependency Updates for Ansible","text":"

Categories: ansible, iac

Renovate supports updating Ansible dependencies.

"},{"location":"modules/manager/ansible/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)tasks/[^/]+\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/ansible/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/ansible/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/ansible/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)tasks/[^/]+\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/ansible/#additional-information","title":"Additional Information","text":"

Supports Docker-type dependency extraction from Ansible configuration files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/ansible-galaxy/","title":"Automated Dependency Updates for Ansible Galaxy","text":"

Categories: ansible, iac

Renovate supports updating Ansible Galaxy dependencies.

"},{"location":"modules/manager/ansible-galaxy/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)(galaxy|requirements)(\\.ansible)?\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/ansible-galaxy/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: galaxy-collection, git-tags, github-tags.

"},{"location":"modules/manager/ansible-galaxy/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description galaxy-collection Ansible Galaxy collection role Ansible role"},{"location":"modules/manager/ansible-galaxy/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)(galaxy|requirements)(\\\\.ansible)?\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/ansible-galaxy/#additional-information","title":"Additional Information","text":"

Extracts Ansible Galaxy dependencies from configuration files used by the ansible-galaxy CLI tool.

"},{"location":"modules/manager/ant/","title":"Automated Dependency Updates for Apache Ant","text":"

Categories: java

Renovate supports updating Apache Ant dependencies.

"},{"location":"modules/manager/ant/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: **/build.xml.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/ant/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/ant/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/ant/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/build.xml\"\n  ]\n}\n
"},{"location":"modules/manager/ant/#additional-information","title":"Additional Information","text":"

Extracts Apache Ant dependencies from build.xml files that use the maven-resolver-ant-tasks or maven-ant-tasks library. Dependencies are looked up using the Maven datasource.

"},{"location":"modules/manager/ant/#supported-syntax","title":"Supported syntax","text":"

Renovate extracts dependencies from <dependency> elements in two formats:

"},{"location":"modules/manager/ant/#property-resolution","title":"Property resolution","text":"

Version values can reference Ant properties defined via <property name=\"...\" value=\"...\"/> or loaded from external .properties files via <property file=\"...\"/>. Ant's first-definition-wins semantics are respected.

"},{"location":"modules/manager/ant/#file-traversal","title":"File traversal","text":"

Renovate follows <import file=\"...\"/> elements to extract dependencies from imported build files. Properties defined before an <import> are available in the imported file.

"},{"location":"modules/manager/ant/#registry-urls","title":"Registry URLs","text":"

Renovate discovers Maven registry URLs from:

Discovered registries are scoped to their dependency block.

"},{"location":"modules/manager/apm/","title":"Automated Dependency Updates for APM","text":"

Categories: no-category

Renovate supports updating APM dependencies.

"},{"location":"modules/manager/apm/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)apm\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/apm/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, gitlab-tags.

"},{"location":"modules/manager/apm/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/apm/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)apm\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/apm/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/apm/#additional-information","title":"Additional Information","text":"

The apm manager keeps APM (Agent Package Manager) dependencies up to date.

Renovate reads the apm.yml manifest and updates the git-pinned entries under dependencies.apm and devDependencies.apm. Each entry uses the form [host/]owner/repo[/subpath]#<ref>, for example:

name: your-project\nversion: 1.0.0\ndependencies:\n  apm:\n    - microsoft/apm-sample-package#v1.0.0\n    - gitlab.com/team/project#v2.3.0\ndevDependencies:\n  apm:\n    - owner/repo#v1.2.3\n

Only entries that pin an exact #<ref> are updated. Entries without a #<ref> are skipped because there is no version to bump.

APM also documents pinning to a commit SHA with the release tag kept as a trailing comment (owner/repo#<sha> # v2.0.0). With pinDigests enabled (part of the config:best-practices preset) Renovate keeps both the SHA and the tag comment current, the same way it does for github-actions (uses: owner/action@<sha> # v4). A SHA pin without a tag comment is skipped, as there is no version to track.

When an apm.lock.yaml lockfile is present, Renovate refreshes it by running apm install after updating the manifest. This requires the apm CLI to be available (for example, with binarySource=global).

"},{"location":"modules/manager/argocd/","title":"Automated Dependency Updates for Argo CD","text":"

Categories: kubernetes, cd

Renovate supports updating Argo CD dependencies.

"},{"location":"modules/manager/argocd/#file-matching","title":"File Matching","text":"

Because file names for argocd cannot be easily determined automatically, Renovate will not attempt to match any argocd files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/argocd/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, git-tags, helm.

"},{"location":"modules/manager/argocd/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/argocd/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/argocd/#additional-information","title":"Additional Information","text":"

To use the argocd manager you must set your own managerFilePatterns pattern. The argocd manager has no default managerFilePatterns pattern, because there is no common filename or directory name convention for Argo CD YAML files. By setting your own managerFilePatterns Renovate avoids having to check each *.yaml file in a repository for a Argo CD definition.

If you need to change the versioning format, read the versioning documentation to learn more.

Some configuration examples:

If most .yaml files in your repository are for Argo CD
{\n  \"argocd\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\"]\n  }\n}\n
Argo CD YAML files are in a argocd/ directory
{\n  \"argocd\": {\n    \"managerFilePatterns\": [\"/argocd/.+\\\\.yaml$/\"]\n  }\n}\n
One Argo CD file in a directory
{\n  \"argocd\": {\n    \"managerFilePatterns\": [\"/^config/applications\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/argocd/#oci-helm-charts","title":"OCI Helm charts","text":"

Renovate looks up Helm charts stored in OCI registries with the docker datasource. Use registryAliases to map a registry host, for example a pull-through cache, to the registry Renovate should query instead.

"},{"location":"modules/manager/asdf/","title":"Automated Dependency Updates for asdf","text":"

Categories: no-category

Renovate supports updating asdf dependencies.

"},{"location":"modules/manager/asdf/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.tool-versions$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/asdf/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: dart-version, docker, dotnet-version, flutter-version, github-releases, github-tags, hexpm-bob, java-version, node-version, npm, pypi, ruby-version, rust-version.

"},{"location":"modules/manager/asdf/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/asdf/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.tool-versions$/\"\n  ]\n}\n
"},{"location":"modules/manager/asdf/#additional-information","title":"Additional Information","text":"

Keeps the asdf .tool-versions file updated.

Because asdf supports versioning for many different tools, specific tool support must be added one-by-one. The following tools are currently supported:

Note

Only the first version entry for each supported tool is managed, this is because .tool-versions supports fallback versions.

"},{"location":"modules/manager/azure-pipelines/","title":"Automated Dependency Updates for Azure Pipelines","text":"

Categories: ci

Renovate supports updating Azure Pipelines dependencies.

"},{"location":"modules/manager/azure-pipelines/#enabling","title":"Enabling","text":"

Azure Pipelines functionality is currently in beta testing, so you must opt-in to test it. To enable it, add a configuration like this to either your self-hosted config or your renovate.json:

{\n  \"azure-pipelines\": {\n    \"enabled\": true\n  }\n}\n

If you find any bugs, please create a new discussion first. If you find that it works well, then let us know too.

"},{"location":"modules/manager/azure-pipelines/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/).azuredevops/.+\\.ya?ml$/\n/azure.*pipelines?.*\\.ya?ml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/azure-pipelines/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: azure-pipelines-tasks, git-tags.

"},{"location":"modules/manager/azure-pipelines/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description docker A Docker image reference in a container: field in Azure Pipelines gitTags A Git repository resource referenced by tag (e.g. refs/tags/v1.0.0)"},{"location":"modules/manager/azure-pipelines/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/).azuredevops/.+\\\\.ya?ml$/\",\n    \"/azure.*pipelines?.*\\\\.ya?ml$/\"\n  ],\n  \"enabled\": false\n}\n
"},{"location":"modules/manager/azure-pipelines/#additional-information","title":"Additional Information","text":"

The azure-pipelines manager is disabled by default. This is because there's no way for Renovate to know whether new task versions are yet available with the Azure DevOps environment, so new versions proposed by Renovate could fail.

To opt into running it, set the following:

{\n  \"azure-pipelines\": {\n    \"enabled\": true\n  }\n}\n

In most cases only major version numbers are specified in YAML when referencing a task version: NodeTool@0. By default, Renovate replaces these with the full version: NodeTool@0.216.0.

To use the standard convention for Azure Pipelines, add:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"azure-pipelines-tasks\"],\n      \"extractVersion\": \"^(?<version>\\\\d+)\"\n    }\n  ]\n}\n

Renovate now updates container and repository resources from the resources block, plus tasks from steps blocks.

For example:

resources:\n  repositories:\n    - type: github\n      name: renovate/renovate\n      ref: refs/heads/main\n    - type: github\n      name: user/repo\n      ref: refs/tags/v0.5.1\n  containers:\n    - container: linux\n      image: ubuntu:24.04\n    - container: python\n      image: python:3.14@sha256:90bdf58a84b9ed919c2942fddafd6c4c8256b22073cc95ecd2710ea255671eba\n\nstages:\n  - stage: StageOne\n    jobs:\n      - job: JobOne\n        steps:\n          - task: Bash@3\n            inputs:\n              script: 'echo Hello World'\n

Read the resources block and the tasks block Azure Pipelines documentation for more information.

The azure-pipelines manager can process these files:

Warning

Renovate can't update (root) container-element in containers jobs, see issue #21987. Renovate can't read Azure repositories defined in resource blocks, see issue #15028.

"},{"location":"modules/manager/batect/","title":"Automated Dependency Updates for Batect","text":"

Categories: batect

Renovate supports updating Batect dependencies.

"},{"location":"modules/manager/batect/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)batect(-bundle)?\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/batect/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, git-tags.

"},{"location":"modules/manager/batect/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/batect/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)batect(-bundle)?\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/batect/#additional-information","title":"Additional Information","text":"

Extracts all Docker images and Batect bundles from Batect configuration files.

For updates to Batect itself, see batect-wrapper.

"},{"location":"modules/manager/batect/#files-searched","title":"Files searched","text":"

By default, the manager searches for files called batect.yml or batect-bundle.yml.

If you keep your Batect configuration in other files, you'll need to tell Renovate where to find them. Files included in your main configuration file with include don't need to be listed.

You do this by creating a \"batect\" object in your renovate.json file. This object should have a managerFilePatterns array with regular expressions that match the configuration file names.

For example:

{\n  \"batect\": {\n    \"managerFilePatterns\": [\n      \"/(^|/)batect(-bundle)?\\\\.yml$/\",\n      \"/(^|/)my-other-batect-file\\\\.yml$/\",\n      \"/^a-directory/[^/]*\\\\.yml$/\"\n    ]\n  }\n}\n
"},{"location":"modules/manager/batect/#bundle-versioning","title":"Bundle versioning","text":"

This manager assumes that any bundles referenced use tags for versioning, and that these tags use SemVer. The implementation of SemVer is strict - versions must follow the X.Y.Z or vX.Y.Z format. Versions that don't match this format (eg. X.Y) will be ignored.

"},{"location":"modules/manager/batect-wrapper/","title":"Automated Dependency Updates for Batect Wrapper","text":"

Categories: batect

Renovate supports updating Batect Wrapper dependencies.

"},{"location":"modules/manager/batect-wrapper/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)batect$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/batect-wrapper/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/batect-wrapper/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/batect-wrapper/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)batect$/\"\n  ],\n  \"versioning\": \"semver\"\n}\n
"},{"location":"modules/manager/batect-wrapper/#additional-information","title":"Additional Information","text":"

Configuration for Batect wrapper updates. The default configuration will automatically update both batect and batect.cmd, similar to running ./batect --upgrade.

See also: Batect image reference updates

"},{"location":"modules/manager/bazel/","title":"Automated Dependency Updates for Bazel","text":"

Categories: bazel

Renovate supports updating Bazel dependencies.

"},{"location":"modules/manager/bazel/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)WORKSPACE(|\\.bazel|\\.bzlmod)$/\n/\\.WORKSPACE\\.bazel$/\n/\\.bzl$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bazel/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, github-releases, github-tags, go.

"},{"location":"modules/manager/bazel/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description container_pull A Docker container image pulled via container_pull _container_pull A Docker container image pulled via the private _container_pull rule git_repository A Git repository dependency via git_repository _git_repository A Git repository dependency via the private _git_repository rule new_git_repository A Git repository with a custom BUILD file via new_git_repository _new_git_repository A Git repository with a custom BUILD file via the private _new_git_repository rule go_repository A Go module dependency via go_repository _go_repository A Go module dependency via the private _go_repository rule http_archive An archive downloaded over HTTP via http_archive _http_archive An archive downloaded over HTTP via the private _http_archive rule http_file A file downloaded over HTTP via http_file _http_file A file downloaded over HTTP via the private _http_file rule oci_pull An OCI container image pulled via oci_pull _oci_pull An OCI container image pulled via the private _oci_pull rule maven_install A Maven artifact installed via maven_install _maven_install A Maven artifact installed via the private _maven_install rule"},{"location":"modules/manager/bazel/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)WORKSPACE(|\\\\.bazel|\\\\.bzlmod)$/\",\n    \"/\\\\.WORKSPACE\\\\.bazel$/\",\n    \"/\\\\.bzl$/\"\n  ]\n}\n
"},{"location":"modules/manager/bazel/#additional-information","title":"Additional Information","text":"

Bazel is quite unlike most other \"package managers\" that Renovate supports, which usually focus on a particular ecosystem like JavaScript, Ruby or Docker. Instead, Bazel is a build tool so supports a multitude of languages/datasources. Renovate does not support all possible Bazel references, although would like to, and feature requests are welcome.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/bazel-module/","title":"Automated Dependency Updates for Bazel Module","text":"

Categories: bazel

Renovate supports updating Bazel Module dependencies.

"},{"location":"modules/manager/bazel-module/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/|\\.)MODULE\\.bazel$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bazel-module/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bazel, crate, docker, github-tags, maven.

"},{"location":"modules/manager/bazel-module/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description bazel_dep A direct Bazel module dependency via bazel_dep git_override A Git-based override for a Bazel module dependency via git_override archive_override An archive-based override for a Bazel module dependency via archive_override local_path_override A local path override for a Bazel module dependency via local_path_override single_version_override A version or registry override for a Bazel module dependency via single_version_override git_repository A Git repository dependency via git_repository in a module extension new_git_repository A Git repository with a custom BUILD file via new_git_repository in a module extension oci_pull An OCI container image pulled via the oci.pull module extension tag maven_install A Maven artifact installed via the maven module extension crate_spec A Rust crate dependency via the crate.spec module extension tag rules_img_pull A container image pulled via a rules_img repo rule in a module extension"},{"location":"modules/manager/bazel-module/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/|\\\\.)MODULE\\\\.bazel$/\"\n  ]\n}\n
"},{"location":"modules/manager/bazel-module/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/bazel-module/#additional-information","title":"Additional Information","text":"

The bazel-module manager can update Bazel module (bzlmod) enabled workspaces.

"},{"location":"modules/manager/bazel-module/#maven","title":"Maven","text":"

It also takes care about maven artifacts initalized with bzlmod. For simplicity the name of extension variable is limited to maven*. E.g.:

maven = use_extension(\"@rules_jvm_external//:extensions.bzl\", \"maven\")\n
maven_1 = use_extension(\"@rules_jvm_external//:extensions.bzl\", \"maven\")\n

Both install and artifact methods are supported:

maven.install(\n    artifacts = [\n        \"org.seleniumhq.selenium:selenium-java:4.4.0\",\n    ],\n)\n\nmaven.artifact(\n    artifact = \"javapoet\",\n    group = \"com.squareup\",\n    neverlink = True,\n    version = \"1.11.1\",\n)\n
"},{"location":"modules/manager/bazel-module/#docker","title":"Docker","text":"

Similarly, it updates Docker / OCI images pulled with oci_pull.

Note that the extension must be called oci:

oci = use_extension(\"@rules_oci//oci:extensions.bzl\", \"oci\")\n\noci.pull(\n    name = \"nginx_image\",\n    digest = \"sha256:287ff321f9e3cde74b600cc26197424404157a72043226cbbf07ee8304a2c720\",\n    image = \"index.docker.io/library/nginx\",\n    platforms = [\"linux/amd64\"],\n    tag = \"1.27.1\",\n)\n

It also supports Docker images pulled with rules_img pull:

pull = use_repo_rule(\"@rules_img//img:pull.bzl\", \"pull\")\npull(\n    name = \"ubuntu\",\n    digest = \"sha256:1e622c5f9ac0c0144d577702ba5f2cce79fc8e3cf89ec88291739cd4eee3b7b9\",\n    registry = \"index.docker.io\",\n    repository = \"library/ubuntu\",\n    tag = \"24.04\",\n)\n
"},{"location":"modules/manager/bazel-module/#crate","title":"Crate","text":"

It also supports Rust crate dependencies initialized with rules_rust crate_universe. For simplicity the name of extension variable is limited to crate*. E.g.:

crate = use_extension(\"@rules_rust//crate_universe:extension.bzl\", \"crate\")\n
crate_1 = use_extension(\"@rules_rust//crate_universe:extension.bzl\", \"crate\")\n

The spec method is supported:

crate.spec(\n    package = \"axum\",\n    version = \"0.8.4\",\n)\n\ncrate.spec(\n    package = \"tokio\",\n    version = \"1.45.1\",\n    features = [\n        \"full\",\n    ],\n)\n\ncrate.spec(\n    package = \"custom_crate\",\n    git = \"https://github.com/example/custom_crate.git\",\n    tag = \"v1.0.0\",\n)\n
"},{"location":"modules/manager/bazel-module/#lockfile-support","title":"Lockfile support","text":"

The bazel-module manager updates the MODULE.bazel.lock file when dependencies change. After updating MODULE.bazel, Renovate runs bazel mod deps to regenerate the lockfile.

Requirements:

If no MODULE.bazel.lock file is found, the lockfile update step is skipped.

It will only run if the allowedUnsafeExecutions global option includes bazelModDeps.

"},{"location":"modules/manager/bazelisk/","title":"Automated Dependency Updates for Bazelisk","text":"

Categories: bazel

Renovate supports updating Bazelisk dependencies.

"},{"location":"modules/manager/bazelisk/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.bazelversion$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bazelisk/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/bazelisk/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bazelisk/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.bazelversion$/\"\n  ],\n  \"pinDigests\": false,\n  \"versioning\": \"semver\"\n}\n
"},{"location":"modules/manager/bazelisk/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/bazelisk/#additional-information","title":"Additional Information","text":"

Simply keeps the .bazelversion file updated.

"},{"location":"modules/manager/bazelisk/#lockfile-support","title":"Lockfile support","text":"

When a MODULE.bazel.lock file exists in the repository, updating the Bazel version also regenerates the lockfile. See the bazel-module manager docs for details.

It will only run if the allowedUnsafeExecutions global option includes bazelModDeps.

"},{"location":"modules/manager/bicep/","title":"Automated Dependency Updates for Bicep","text":"

Categories: iac

Renovate supports updating Bicep dependencies.

"},{"location":"modules/manager/bicep/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.bicep$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bicep/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: azure-bicep-resource.

"},{"location":"modules/manager/bicep/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bicep/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.bicep$/\"\n  ]\n}\n
"},{"location":"modules/manager/bicep/#additional-information","title":"Additional Information","text":"

Updates the Azure REST API version of resources in Bicep files.

"},{"location":"modules/manager/bitbucket-pipelines/","title":"Automated Dependency Updates for Bitbucket Pipelines","text":"

Categories: ci

Renovate supports updating Bitbucket Pipelines dependencies.

"},{"location":"modules/manager/bitbucket-pipelines/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: **/*-pipelines.yml.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bitbucket-pipelines/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/bitbucket-pipelines/#references","title":"References","text":""},{"location":"modules/manager/bitbucket-pipelines/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description bitbucket-tags A Bitbucket pipe reference resolved via Bitbucket tags docker A Docker image used as the build image or in a service definition"},{"location":"modules/manager/bitbucket-pipelines/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/*-pipelines.yml\"\n  ]\n}\n
"},{"location":"modules/manager/bitbucket-pipelines/#additional-information","title":"Additional Information","text":"

Extracts dependencies from Bitbucket Pipelines config files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/bitrise/","title":"Automated Dependency Updates for Bitrise","text":"

Categories: ci

Renovate supports updating Bitrise dependencies.

"},{"location":"modules/manager/bitrise/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)bitrise\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bitrise/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitrise, git-tags.

"},{"location":"modules/manager/bitrise/#references","title":"References","text":""},{"location":"modules/manager/bitrise/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bitrise/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)bitrise\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/bitrise/#additional-information","title":"Additional Information","text":"

Updates step references of bitrise.yml files.

"},{"location":"modules/manager/buildkite/","title":"Automated Dependency Updates for Buildkite","text":"

Categories: ci

Renovate supports updating Buildkite dependencies.

"},{"location":"modules/manager/buildkite/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/buildkite\\.ya?ml/\n/\\.buildkite/.+\\.ya?ml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/buildkite/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, github-tags.

"},{"location":"modules/manager/buildkite/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/buildkite/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/buildkite\\\\.ya?ml/\",\n    \"/\\\\.buildkite/.+\\\\.ya?ml$/\"\n  ],\n  \"commitMessageTopic\": \"buildkite plugin {{depName}}\",\n  \"commitMessageExtra\": \"to {{#if isMajor}}{{{prettyNewMajor}}}{{else}}{{{newValue}}}{{/if}}\"\n}\n
"},{"location":"modules/manager/buildkite/#additional-information","title":"Additional Information","text":"

Used for updating Docker dependencies in Buildkite configuration files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/buildpacks/","title":"Automated Dependency Updates for Buildpacks","text":"

Categories: docker, ci, cd

Renovate supports updating Buildpacks dependencies.

"},{"location":"modules/manager/buildpacks/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)project\\.toml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/buildpacks/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: buildpacks-registry, docker.

"},{"location":"modules/manager/buildpacks/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/buildpacks/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"buildpack {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)project\\\\.toml$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/buildpacks/#additional-information","title":"Additional Information","text":"

The buildpacks manager updates Cloud Native Buildpacks project descriptors in project.toml files. A project.toml file can reference builder / buildpack images by URIs. Renovate can update a project.toml file if:

Note: If you use buildpacks in the io.buildpacks.group array, then you must configure the Docker reference (uri) for Renovate to work.

Example of a project.toml file with Docker reference URIs
[_]\nschema-version = \"0.2\"\n\n[io.buildpacks]\nbuilder = \"registry.corp/builder/noble:1.1.1\"\n\n[[io.buildpacks.group]]\nuri = \"docker://buildpacks/java:2.2.2\"\n\n[[io.buildpacks.group]]\nuri = \"buildpacks/nodejs:3.3.3\"\n\n[[io.buildpacks.group]]\nuri = \"file://local.oci\" # will be ignored\n
"},{"location":"modules/manager/bun/","title":"Automated Dependency Updates for Bun","text":"

Categories: js

Renovate supports updating Bun dependencies.

"},{"location":"modules/manager/bun/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)bun\\.lockb?$/\n/(^|/)package\\.json$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bun/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-tags, npm.

"},{"location":"modules/manager/bun/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bun/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)bun\\\\.lockb?$/\",\n    \"/(^|/)package\\\\.json$/\"\n  ],\n  \"digest\": {\n    \"prBodyDefinitions\": {\n      \"Change\": \"{{#if displayFrom}}`{{{displayFrom}}}` \u2192 {{else}}{{#if currentValue}}`{{{currentValue}}}` \u2192 {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}\"\n    }\n  },\n  \"prBodyDefinitions\": {\n    \"Change\": \"[{{#if displayFrom}}`{{{displayFrom}}}` \u2192 {{else}}{{#if currentValue}}`{{{currentValue}}}` \u2192 {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}]({{#if depName}}https://renovatebot.com/diffs/npm/{{replace '/' '%2f' depName}}/{{{currentVersion}}}/{{{newVersion}}}{{/if}})\"\n  }\n}\n
"},{"location":"modules/manager/bun/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/bun/#additional-information","title":"Additional Information","text":"

Used for updating bun projects. Bun is a tool for JavaScript projects and therefore an alternative to managers like npm, pnpm and Yarn.

If a package.json is found to be part of bun manager results then the same file will be excluded from the npm manager results unless an npm/pnpm/Yarn lock file is also found.

"},{"location":"modules/manager/bun-version/","title":"Automated Dependency Updates for Bun Version","text":"

Categories: js

Renovate supports updating Bun Version dependencies.

"},{"location":"modules/manager/bun-version/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.bun-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bun-version/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: npm.

"},{"location":"modules/manager/bun-version/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bun-version/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.bun-version$/\"\n  ],\n  \"versioning\": \"npm\"\n}\n
"},{"location":"modules/manager/bun-version/#additional-information","title":"Additional Information","text":"

Simply keeps the .bun-version file updated.

"},{"location":"modules/manager/bundler/","title":"Automated Dependency Updates for Bundler","text":"

Categories: ruby

Renovate supports updating Bundler dependencies.

"},{"location":"modules/manager/bundler/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Gemfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/bundler/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: ruby-version, rubygems.

"},{"location":"modules/manager/bundler/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/bundler/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Gemfile$/\"\n  ],\n  \"versioning\": \"ruby\"\n}\n
"},{"location":"modules/manager/bundler/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/bundler/#additional-information","title":"Additional Information","text":"

Renovate uses the bundler manager to extract dependencies from Gemfile and Gemfile.lock files.

"},{"location":"modules/manager/bundler/#authenticating-private-registry","title":"Authenticating private registry","text":"

If:

Then you should authenticate Renovate with hostRules. For example:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"private-registry.company.com\",\n      \"hostType\": \"rubygems\",\n      \"token\": \"abc123\"\n    }\n  ]\n}\n

Important notes:

To avoid committing raw secrets to your repository, either:

"},{"location":"modules/manager/cake/","title":"Automated Dependency Updates for Cake","text":"

Categories: dotnet

Renovate supports updating Cake dependencies.

"},{"location":"modules/manager/cake/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.cake$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cake/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: nuget.

"},{"location":"modules/manager/cake/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/cake/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.cake$/\"\n  ]\n}\n
"},{"location":"modules/manager/cake/#additional-information","title":"Additional Information","text":"

Extracts dependencies from *.cake files.

It can also extract dotnet: tool packages when used in .NET single file builds, when they are used with the InstallTool or InstallTools method. Keep in mind that those files are usually not *.cake files but C# code files. Those are not included in the managerFilePatterns per default - make sure to include them manually in your configuration if you want to use this feature.#:packageor#:sdk directives are not handled by the cake manager as this is a dotnet feature. Those are separately handled by the nuget manager.

"},{"location":"modules/manager/cargo/","title":"Automated Dependency Updates for Cargo","text":"

Categories: rust

Renovate supports updating Cargo dependencies.

"},{"location":"modules/manager/cargo/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Cargo\\.toml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cargo/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: crate, git-refs, git-tags, github-tags, gitlab-tags.

"},{"location":"modules/manager/cargo/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/cargo/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"Rust crate {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)Cargo\\\\.toml$/\"\n  ]\n}\n
"},{"location":"modules/manager/cargo/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/cargo/#additional-information","title":"Additional Information","text":"

Extracts dependencies from Cargo.toml files, and also updates Cargo.lock files too if found.

When using the default rangeStrategy=auto:

The update-lockfile default means that most upgrades will update Cargo.lock files without the need to change the value in Cargo.toml.

"},{"location":"modules/manager/cargo/#private-modules-authentication","title":"Private Modules Authentication","text":"

Before running the cargo commands to update the cargo.lock, Renovate exports git insteadOf directives in environment variables.

Renovate uses this logic before it updates any \"artifacts\":

The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com. For those running against github.com, this token will be the default platform token.

Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.

Rules from this list are converted to environment variable directives if they match any of these characteristics:

"},{"location":"modules/manager/cargo/#git-index-registries","title":"Git index registries","text":"

When Renovate clones a git index registry over http(s) to look up versions, it exports the same insteadOf directives as for artifact updates, with hostType=crate in place of hostType=cargo. Because artifact updates accept hostType=crate rules too, a single crate rule covers both the lookup and the Cargo.lock update. Git uses the credentials of the directive whose URL matches the index URL. Cloning a git index registry other than the crates.io index (https://index.crates.io/) requires allowCustomCrateGitRegistries. Sparse registries (sparse+https://) are fetched over HTTP, and use hostRules like other datasources.

"},{"location":"modules/manager/cdnurl/","title":"Automated Dependency Updates for CDN URL","text":"

Categories: cd

Renovate supports updating CDN URL dependencies.

"},{"location":"modules/manager/cdnurl/#file-matching","title":"File Matching","text":"

Because file names for cdnurl cannot be easily determined automatically, Renovate will not attempt to match any cdnurl files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cdnurl/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: cdnjs.

"},{"location":"modules/manager/cdnurl/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/cdnurl/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [],\n  \"versioning\": \"semver\"\n}\n
"},{"location":"modules/manager/cdnurl/#additional-information","title":"Additional Information","text":"

To enable this manager, add the matching files to cdnurl.managerFilePatterns. For example:

{\n  \"cdnurl\": {\n    \"managerFilePatterns\": [\"/\\\\.html?$/\"]\n  }\n}\n

Warning

This manager does not read or update Subresource Integrity (SRI) hashes. It replaces any matching URL it finds, without adding or updating script integrity hashes. We recommend you use the html manager if you need SRI updating.

"},{"location":"modules/manager/circleci/","title":"Automated Dependency Updates for CircleCI","text":"

Categories: ci

Renovate supports updating CircleCI dependencies.

"},{"location":"modules/manager/circleci/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.circleci/.+\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/circleci/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, orb.

"},{"location":"modules/manager/circleci/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description orb CircleCI orb reference docker Docker image in executor/job configuration"},{"location":"modules/manager/circleci/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.circleci/.+\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/circleci/#additional-information","title":"Additional Information","text":"

The circleci manager extracts both docker as well as orb datasources from CircleCI config files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/circleci/#private-orbs","title":"Private orbs","text":"

To get private orbs working you should:

  1. Encrypt your CircleCI token with the Renovate encryption page
  2. Create a new hostRules entry in your Renovate config file
  3. Put the encrypted token in the token field

The end-result should look like this:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"circleci.com\",\n      \"authType\": \"Token-Only\",\n      \"encrypted\": {\n        \"token\": \"****\"\n      }\n    }\n  ]\n}\n

This config strips the Bearer/Basic prefix from the authorization header.

"},{"location":"modules/manager/cloudbuild/","title":"Automated Dependency Updates for Cloud Build","text":"

Categories: ci

Renovate supports updating Cloud Build dependencies.

"},{"location":"modules/manager/cloudbuild/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)cloudbuild\\.ya?ml/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cloudbuild/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/cloudbuild/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/cloudbuild/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)cloudbuild\\\\.ya?ml/\"\n  ]\n}\n
"},{"location":"modules/manager/cloudbuild/#additional-information","title":"Additional Information","text":"

The cloudbuild manager extracts docker datasources from Cloud Build config files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/cocoapods/","title":"Automated Dependency Updates for CocoaPods","text":"

Categories: swift

Renovate supports updating CocoaPods dependencies.

"},{"location":"modules/manager/cocoapods/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Podfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cocoapods/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, gitlab-tags, pod.

"},{"location":"modules/manager/cocoapods/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/cocoapods/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Podfile$/\"\n  ],\n  \"versioning\": \"ruby\"\n}\n
"},{"location":"modules/manager/cocoapods/#additional-information","title":"Additional Information","text":"

The cocoapods manager supports extracting both \"pod\" type references as well as dependencies on GitHub repositories that use versioned tags.

Whenever a Podfile is updated, Renovate will also update any associated Podfile.lock file. This is done using the cocoapods gem, which runs within the Ruby runtime.

"},{"location":"modules/manager/composer/","title":"Automated Dependency Updates for Composer","text":"

Categories: php

Renovate supports updating Composer dependencies.

"},{"location":"modules/manager/composer/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)([\\w-]*)composer\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/composer/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, git-tags, packagist.

"},{"location":"modules/manager/composer/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description require Production dependency from require section require-dev Development dependency from require-dev section"},{"location":"modules/manager/composer/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)([\\\\w-]*)composer\\\\.json$/\"\n  ],\n  \"versioning\": \"composer\"\n}\n
"},{"location":"modules/manager/composer/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/composer/#additional-information","title":"Additional Information","text":"

Extracts dependencies from composer.json files, and keeps the associated composer.lock file updated too.

If you use VCS repositories then Renovate needs a hint via the name property, which must match the relevant package. For example, the package acme/foo would need an entry in repositories similar to the following:

{\n  \"name\": \"acme/foo\",\n  \"type\": \"vcs\",\n  \"url\": \"http://vcs-of-acme.org/acme/foo.git\"\n}\n

By default, Renovate will invoke composer update with the --with-dependencies flag. Add composerWithAll to your postUpdateOptions array to use the --with-all-dependencies flag instead.

"},{"location":"modules/manager/conan/","title":"Automated Dependency Updates for Conan","text":"

Categories: c

Renovate supports updating Conan dependencies.

"},{"location":"modules/manager/conan/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)conanfile\\.(txt|py)$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/conan/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: conan.

"},{"location":"modules/manager/conan/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description build_requires A build-time dependency declared in [build_requires] or build_requirements() python_requires A Python-based Conan recipe dependency declared via python_requires requires A runtime dependency declared in [requires] or requirements()"},{"location":"modules/manager/conan/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)conanfile\\\\.(txt|py)$/\"\n  ],\n  \"datasource\": \"conan\",\n  \"versioning\": \"conan\"\n}\n
"},{"location":"modules/manager/conan/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/conan/#additional-information","title":"Additional Information","text":"

Renovate can upgrade dependencies in conanfile.txt or conanfile.py files and also updates conan.lock files too if found.

How it works:

  1. Renovate searches in each repository for any conanfile.txt or conanfile.py file
  2. Renovate extracts existing dependencies from:
  3. Renovate resolves the dependency's version using the Conan v2 API
  4. If Renovate finds an update, Renovate will update conanfile.txt or conanfile.py
  5. Renovate also updates conan.lock file if exists
"},{"location":"modules/manager/copier/","title":"Automated Dependency Updates for Copier","text":"

Categories: python

Renovate supports updating Copier dependencies.

"},{"location":"modules/manager/copier/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.copier-answers(\\..+)?\\.ya?ml/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/copier/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags.

"},{"location":"modules/manager/copier/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description template Copier project template source"},{"location":"modules/manager/copier/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.copier-answers(\\\\..+)?\\\\.ya?ml/\"\n  ],\n  \"versioning\": \"pep440\"\n}\n
"},{"location":"modules/manager/copier/#additional-information","title":"Additional Information","text":"

Keeps Copier templates up to date. Supports multiple .copier-answers(...).y(a)ml files in a single repository. If a template requires unsafe features, Copier must be invoked with the --trust flag. Enabling this behavior must be allowed in the self-hosted configuration via allowScripts. Actually enable it in the configuration by setting ignoreScripts to false.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/copier/#private-modules-authentication","title":"Private Modules Authentication","text":"

To look up new template versions, Renovate converts SSH-style _src_path URLs (like git+ssh://git@gitlab.com/some-org/some-template.git) to their HTTPS equivalent, the same way the git-submodules manager does. This way the lookup works with hostRules credentials on setups which access the Git host via HTTPS only. The answers file itself keeps the original URL.

Before running the copier command to update from the template, Renovate exports git insteadOf directives in environment variables.

Renovate uses this logic before it updates the template copy:

The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com. For those running against github.com, this token will be the default platform token.

Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.

Rules from this list are converted to environment variable directives if they match any of these characteristics:

"},{"location":"modules/manager/cpanfile/","title":"Automated Dependency Updates for cpanfile","text":"

Categories: perl

Renovate supports updating cpanfile dependencies.

"},{"location":"modules/manager/cpanfile/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)cpanfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/cpanfile/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: cpan, github-tags.

"},{"location":"modules/manager/cpanfile/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description configure Dependencies needed during the configure phase build Dependencies needed during the build phase test Dependencies needed during the test phase runtime Dependencies needed at runtime develop Dependencies needed during development (author_requires)"},{"location":"modules/manager/cpanfile/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)cpanfile$/\"\n  ]\n}\n
"},{"location":"modules/manager/cpanfile/#additional-information","title":"Additional Information","text":"

The cpanfile manager is used to extract dependencies from cpanfile.

"},{"location":"modules/manager/crossplane/","title":"Automated Dependency Updates for Crossplane","text":"

Categories: kubernetes, iac

Renovate supports updating Crossplane dependencies.

"},{"location":"modules/manager/crossplane/#file-matching","title":"File Matching","text":"

Because file names for crossplane cannot be easily determined automatically, Renovate will not attempt to match any crossplane files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/crossplane/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/crossplane/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description provider A Crossplane Provider package configuration A Crossplane Configuration package function A Crossplane Function package"},{"location":"modules/manager/crossplane/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/crossplane/#additional-information","title":"Additional Information","text":"

To use the crossplane manager you must set your own managerFilePatterns pattern. The crossplane manager has no default managerFilePatterns pattern, because there is no common filename or directory name convention for Crossplane YAML files. By setting your own managerFilePatterns Renovate avoids having to check each *.yaml file in a repository for a Crossplane Package definition.

The crossplane manager supports these depTypes:

You can use these depType's to control which dependencies Renovate will upgrade.

If you need to change the versioning format, read the versioning documentation to learn more.

Some configuration examples:

If most .yaml files are for Crossplane
{\n  \"crossplane\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\"]\n  }\n}\n
For Crossplane files in a packages/ directory
{\n  \"crossplane\": {\n    \"managerFilePatterns\": [\"/packages/.+\\\\.yaml$/\"]\n  }\n}\n
For a single Crossplane file
{\n  \"crossplane\": {\n    \"managerFilePatterns\": [\"/^config/provider\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/crow/","title":"Automated Dependency Updates for Crow","text":"

Categories: ci

Renovate supports updating Crow dependencies.

"},{"location":"modules/manager/crow/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /^\\.crow(?:/[^/]+)?\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/crow/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/crow/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/crow/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/^\\\\.crow(?:/[^/]+)?\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/crow/#additional-information","title":"Additional Information","text":"

Extracts all Docker images from Crow CI Pipeline YAML files.

"},{"location":"modules/manager/deno/","title":"Automated Dependency Updates for Deno","text":"

Categories: js

Renovate supports updating Deno dependencies.

"},{"location":"modules/manager/deno/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)deno\\.lock$/\n/(^|/)deno\\.(json|jsonc)$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/deno/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: deno, jsr, npm.

"},{"location":"modules/manager/deno/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/deno/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)deno\\\\.lock$/\",\n    \"/(^|/)deno\\\\.(json|jsonc)$/\"\n  ],\n  \"digest\": {\n    \"prBodyDefinitions\": {\n      \"Change\": \"{{#if displayFrom}}`{{{displayFrom}}}` -> {{else}}{{#if currentValue}}`{{{currentValue}}}` -> {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}\"\n    }\n  },\n  \"prBodyDefinitions\": {\n    \"Change\": \"{{#if (equals datasource \\\"npm\\\")}}[{{#if displayFrom}}`{{{displayFrom}}}` -> {{else}}{{#if currentValue}}`{{{currentValue}}}` -> {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}]({{#if depName}}https://renovatebot.com/diffs/npm/{{replace '/' '%2f' depName}}/{{{currentVersion}}}/{{{newVersion}}}{{/if}}){{else}}{{#if displayFrom}}`{{{displayFrom}}}` -> {{else}}{{#if currentValue}}`{{{currentValue}}}` -> {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}{{/if}}\"\n  }\n}\n
"},{"location":"modules/manager/deno/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/deno/#additional-information","title":"Additional Information","text":"

Extracts dependencies from the Deno's projects deno.json and deno.jsonc files. The deno manager also supports the package.json file for Deno's node-compat as long as a deno.lock file is placed next to the package.json file. It could support another lock filename that specified in deno.json or deno.jsonc.

"},{"location":"modules/manager/deno/#supported-dependency-types","title":"Supported Dependency Types","text":"

The following depTypes of deno.json or deno.jsonc are currently supported by the deno manager:

Additionally, an import map JSON file containing imports and scopes.<mapping>.<specifier> like the examples above is supported.

The deno manager also supports some depTypes that supported by npm manager.

Note

Deno cli supports private npm compatible registries itself, however the deno managaer is not yet ready to support Private npm module.

Note

In source dependencies are not supported.

import { assert } from 'jsr:@std/assert@1.0.0';\n
"},{"location":"modules/manager/deps-edn/","title":"Automated Dependency Updates for deps.edn","text":"

Categories: java

Renovate supports updating deps.edn dependencies.

"},{"location":"modules/manager/deps-edn/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)(?:deps|bb)\\.edn$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/deps-edn/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: clojure.

"},{"location":"modules/manager/deps-edn/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/deps-edn/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)(?:deps|bb)\\\\.edn$/\"\n  ],\n  \"versioning\": \"maven\"\n}\n
"},{"location":"modules/manager/deps-edn/#additional-information","title":"Additional Information","text":"

Extracts Maven dependencies from deps.edn files.

"},{"location":"modules/manager/devbox/","title":"Automated Dependency Updates for Devbox","text":"

Categories: no-category

Renovate supports updating Devbox dependencies.

"},{"location":"modules/manager/devbox/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)devbox\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/devbox/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: devbox.

"},{"location":"modules/manager/devbox/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/devbox/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)devbox\\\\.json$/\"\n  ]\n}\n
"},{"location":"modules/manager/devbox/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/devbox/#additional-information","title":"Additional Information","text":"

Used for updating devbox projects.

Devbox is a tool for creating isolated, reproducible development environments that run anywhere.

It uses nix packages sourced from the devbox package registry.

"},{"location":"modules/manager/devbox/#package-versioning","title":"Package versioning","text":"

Some packages in the devbox registry don't follow the basic versioning we have set up. We have allowed for defining an versioning API override within tool-versioning.ts.

"},{"location":"modules/manager/devcontainer/","title":"Automated Dependency Updates for Devcontainer","text":"

Categories: docker

Renovate supports updating Devcontainer dependencies.

"},{"location":"modules/manager/devcontainer/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/^.devcontainer/devcontainer.json$/\n/^.devcontainer.json$/\n/^.devcontainer/[^/]+/devcontainer.json$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/devcontainer/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, golang-version, node-version, python-version, ruby-version.

"},{"location":"modules/manager/devcontainer/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description feature A Dev Container Feature reference (e.g. ghcr.io/devcontainers/features/node:1) image The base Docker image specified in the image field of devcontainer.json"},{"location":"modules/manager/devcontainer/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/^.devcontainer/devcontainer.json$/\",\n    \"/^.devcontainer.json$/\",\n    \"/^.devcontainer/[^/]+/devcontainer.json$/\"\n  ]\n}\n
"},{"location":"modules/manager/devcontainer/#additional-information","title":"Additional Information","text":"

Extracts all Docker images from the image and features properties in these files:

It extracts some known versions of the features, like node and python.

The devcontainer manager does not support build.dockerFile or dockerComposeFile values as these are covered by the dockerfile and docker-compose managers respectively.

"},{"location":"modules/manager/docker-compose/","title":"Automated Dependency Updates for Docker Compose","text":"

Categories: docker

Renovate supports updating Docker Compose dependencies.

"},{"location":"modules/manager/docker-compose/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)(?:docker-)?compose[^/]*\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/docker-compose/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/docker-compose/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/docker-compose/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)(?:docker-)?compose[^/]*\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/docker-compose/#additional-information","title":"Additional Information","text":"

Extracts all Docker images from with Docker Compose YAML files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/docker-compose/#registry-aliases-with-variable-defaults","title":"Registry aliases with variable defaults","text":"

Docker Compose files often use environment variables with default values:

services:\n  foobar:\n    image: ${CI_REGISTRY:-}image:1.0\n

To handle these variables, configure registry aliases with the default value syntax:

{\n  \"registryAliases\": {\n    \"${CI_REGISTRY:-}\": \"my-registry.io\"\n  }\n}\n

Both image reference formats work:

The alias value works with or without a trailing slash.

"},{"location":"modules/manager/dockerfile/","title":"Automated Dependency Updates for Dockerfile","text":"

Categories: docker

Renovate supports updating Dockerfile dependencies.

"},{"location":"modules/manager/dockerfile/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/|\\.)([Dd]ocker|[Cc]ontainer)file$/\n/(^|/)([Dd]ocker|[Cc]ontainer)file[^/]*$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/dockerfile/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: apk, deb, docker.

"},{"location":"modules/manager/dockerfile/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description syntax The # syntax= parser directive at the top of the Dockerfile stage An intermediate FROM instruction in a multi-stage build final The last FROM instruction in the Dockerfile (the final build stage) install A system package manager was used to install a package, for instance via RUN apk add ..."},{"location":"modules/manager/dockerfile/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/|\\\\.)([Dd]ocker|[Cc]ontainer)file$/\",\n    \"/(^|/)([Dd]ocker|[Cc]ontainer)file[^/]*$/\"\n  ]\n}\n
"},{"location":"modules/manager/dockerfile/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/dockerfile/#supported-dependencies","title":"Supported dependencies","text":"

This manager extracts image references in a Dockerfile and/or Containerfile and supports:

"},{"location":"modules/manager/dockerfile/#from-support","title":"FROM support","text":"

Renovate can update images referenced in FROM directives. This even works for multi-stage builds with many FROM directives in one Dockerfile.

FROM node:20.9.0\n

Advanced FROM flags like --platform or AS <name> are also supported:

FROM --platform=linux/amd64 node:20.9.0 AS installer\n

Also, Renovate will automatically expand variables and ARG directives:

ARG TAG=3.19.4\nFROM alpine:${TAG}\n

Renovate supports variables with default values (using the :- syntax) when they are configured with registry aliases:

FROM ${CI_REGISTRY:-}alpine:3.19.4\n
{\n  \"registryAliases\": {\n    \"${CI_REGISTRY:-}\": \"my-registry.io\"\n  }\n}\n

Both image reference formats work:

The alias value works with or without a trailing slash.

"},{"location":"modules/manager/dockerfile/#copy-from-support","title":"COPY --from support","text":"

Renovate can update images referenced in COPY --from directives.

FROM node:20.9.0\nCOPY --from alpine:3.19.4 /bin/sh /usr/local/sh\n
"},{"location":"modules/manager/dockerfile/#run-mount-support","title":"RUN --mount support","text":"

Images referenced in RUN --mount directives are also supported.

FROM python:3.12\nRUN --mount=from=ghcr.io/astral-sh/uv:0.5,source=/uv,target=/bin/uv \\\n    uv venv\n
"},{"location":"modules/manager/dockerfile/#syntax-support","title":"syntax support","text":"

Renovate can update syntax references.

# syntax=docker/dockerfile:1.9.0\nFROM alpine:3.19.4\n
"},{"location":"modules/manager/dockerfile/#run-apk-add-support","title":"RUN apk add support","text":"

Renovate extracts Alpine packages installed via apk add, using the apk datasource.

FROM alpine:3.21\nRUN apk add --no-cache \\\n      bash=5.2.37-r2 \\\n      rsyslog=8.2412.0-r1\n

Renovate does not work out which Alpine release your base image installs from, and the apk datasource's default registry may not match it, so a lookup against that default would offer versions your image cannot install. Renovate therefore skips these packages with skipReason: unknown-registry until you say which repositories to read.

Give them a registryUrls with a packageRules entry to have them looked up:

Point apk lookups at the Alpine 3.21 repositories
{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"Dockerfile\"],\n      \"matchDatasources\": [\"apk\"],\n      \"registryUrls\": [\n        \"https://dl-cdn.alpinelinux.org/alpine?branch=v3.21&components=main,community&arch=x86_64\"\n      ]\n    }\n  ]\n}\n

Version constraints are read with apk versioning, so the fuzzy constraints which Wolfi and Chainguard images commonly pin with are supported too:

FROM cgr.dev/chainguard/wolfi-base\nRUN apk add --no-cache curl=~8.12.1\n

~8.12.1 matches every 8.12.1-rN, so Renovate only raises a PR once a version outside the constraint is released, and keeps the precision you wrote it with - curl=~8.13.0, not curl=~8.13.0-r0.

Renovate skips packages which it cannot update, and says why in the packageFiles with updates log line:

Renovate also proposes no new value for the <, <=, >, >=, >~ and <~ operators, as there is no single obvious new bound for them.

Local or remote .apk files, virtual packages (--virtual .build-deps) and provider dependencies (so:, cmd:, pc:) are ignored.

Packages installed by a system package manager use the install depType, so you can match them in a packageRules entry with matchDepTypes:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Disable APK package updates\",\n      \"matchDepTypes\": [\"install\"],\n      \"matchDatasources\": [\"apk\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/dockerfile/#run-apt-install-support","title":"RUN apt install support","text":"

Renovate extracts Debian packages installed via apt install or apt-get install, using the deb datasource.

FROM debian:trixie\nRUN apt-get update \\\n  && apt-get install -y --no-install-recommends \\\n       curl=8.14.1-2 \\\n       git=1:2.47.3-0+deb13u1 \\\n  && rm -rf /var/lib/apt/lists/*\n

The deb datasource needs a registryUrl which says which suite, components and architecture to look in, and Renovate does not work that out from your base image. Its default is the Debian stable suite for amd64, which may not match your base image, so a lookup against that default would offer versions your image cannot install. Renovate therefore skips these packages with skipReason: unknown-registry until you say which repositories to read.

Give them a registryUrls with a packageRules entry to have them looked up:

Point deb lookups at the Debian trixie repositories
{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"Dockerfile\"],\n      \"matchDatasources\": [\"deb\"],\n      \"registryUrls\": [\n        \"https://deb.debian.org/debian?suite=trixie&components=main,contrib,non-free&binaryArch=amd64\"\n      ]\n    }\n  ]\n}\n

Renovate skips packages which it cannot update, and says why in the packageFiles with updates log line:

Local or remote .deb files, removal markers like vim- and pattern matches like ^gnome are ignored. dpkg -i is not supported, because it installs a local file rather than a package from a repository.

Packages installed by a system package manager use the install depType, so you can match them in a packageRules entry with matchDepTypes:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Disable Debian package updates\",\n      \"matchDepTypes\": [\"install\"],\n      \"matchDatasources\": [\"deb\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/dockerfile/#versioning","title":"Versioning","text":"

Renovate's managers does not understand versioning, that's up to Renovate's versioning modules. The default docker versioning for container image datasources treats suffixes as \"compatibility\", for example: -alpine. Many container images are not SemVer compliant because they use such suffixes in their tags.

If Renovate does not update your container images correctly, you may need to tell Renovate what versioning it should use. For example, if you know that an image follows SemVer, you can tell Renovate to use \"semver\" versioning for that image:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"whitesource/renovate\"],\n      \"versioning\": \"semver\"\n    }\n  ]\n}\n

Read Renovate's Docker Versioning docs to learn more.

"},{"location":"modules/manager/droneci/","title":"Automated Dependency Updates for Droneci","text":"

Categories: ci

Renovate supports updating Droneci dependencies.

"},{"location":"modules/manager/droneci/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.drone\\.yml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/droneci/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/droneci/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description docker A Docker image used in a Drone CI pipeline step or service"},{"location":"modules/manager/droneci/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.drone\\\\.yml$/\"\n  ]\n}\n
"},{"location":"modules/manager/droneci/#additional-information","title":"Additional Information","text":"

Extracts Docker-type dependencies from DroneCI config files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/fleet/","title":"Automated Dependency Updates for Rancher Fleet","text":"

Categories: cd, kubernetes

Renovate supports updating Rancher Fleet dependencies.

"},{"location":"modules/manager/fleet/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)fleet\\.ya?ml/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/fleet/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, git-tags, helm.

"},{"location":"modules/manager/fleet/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description git_repo Git repository reference in a Fleet GitRepo manifest fleet Helm chart reference in a Fleet deployment"},{"location":"modules/manager/fleet/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)fleet\\\\.ya?ml/\"\n  ]\n}\n
"},{"location":"modules/manager/fleet/#additional-information","title":"Additional Information","text":"

Can upgrade bundle definitions and GitRepo YAML manifests of Rancher Fleet.

By default, only bundles with Helm references will be upgraded. To enable GitRepo updates you have to extend your managerFilePatterns configuration.

{\n  \"fleet\": {\n    \"managerFilePatterns\": [\"/(^|/)fleet.ya?ml/\", \"/myGitRepoManifests\\\\.yaml/\"]\n  }\n}\n

In case pull through cache configured via internal registry, it is possible to setup registryAlias to query package updates via upstream source

{\n  \"registryAliases\": {\n    \"https://registry.com/jetstack\": \"https://charts.jetstack.io\",\n    \"registry.com/docker-io\": \"registry-1.docker.io\"\n  }\n}\n
"},{"location":"modules/manager/flux/","title":"Automated Dependency Updates for Flux","text":"

Categories: cd, kubernetes

Renovate supports updating Flux dependencies.

"},{"location":"modules/manager/flux/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(?:^|/)gotk-components\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/flux/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, docker, git-refs, git-tags, github-releases, github-tags, gitlab-tags, helm.

"},{"location":"modules/manager/flux/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description HelmChart Helm chart from a HelmRelease or HelmChart resource, or an OCIRepository selecting the Helm chart layer"},{"location":"modules/manager/flux/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(?:^|/)gotk-components\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/flux/#additional-information","title":"Additional Information","text":"

This manager parses Flux YAML manifests and supports:

  1. HelmRelease resources
  2. GitRepository resources
  3. OCIRepository resources
  4. Flux system manifests
"},{"location":"modules/manager/flux/#helmrelease-support","title":"HelmRelease support","text":"

Extracts helm dependencies from HelmRelease resources.

The flux manager extracts helm dependencies for HelmRelease resources linked to HelmRepository or GitRepository sources. HelmRepository resources can be referenced via spec.chart or indirectly via a HelmChart when using spec.chartRef. Renovate supports OCI HelmRepository sources, those with type: oci. Renovate will then extract the docker dependencies for the referenced HelmRelease resources.

In addition, for the flux manager to properly link HelmRelease and HelmRepository resources, both of the following conditions must be met:

  1. The HelmRelease resource must either have its metadata.namespace property set or its spec.chart.spec.sourceRef.namespace property (when not using chartRef) set
  2. The referenced HelmRepository and HelmChart (when using chartRef) resources must have their metadata.namespace property set

Namespaces will not be inferred from the context (e.g. from the parent Kustomization).

Renovate updates HelmRelease resources coming from GitRepository by updating the GitRepository resource.

Renovate updates Docker dependencies inside HelmRelease values like the helm-values manager.

When a referenced HelmRepository resource is not present in the scanned manifests (for example, it is defined in another repository or as a cluster-global resource), you can statically map the sourceRef.name of the HelmRelease (or HelmChart) to a registry URL using registryAliases in your flux configuration:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"flux\"],\n      \"matchDatasources\": [\"helm\"],\n      \"registryAliases\": {\n        \"podinfo-repo\": \"https://stefanprodan.github.io/podinfo\"\n      }\n    }\n  ]\n}\n

In this example, a HelmRelease whose spec.chart.spec.sourceRef.name is podinfo-repo will be treated as if it were backed by a HelmRepository with URL https://stefanprodan.github.io/podinfo.

"},{"location":"modules/manager/flux/#gitrepository-support","title":"GitRepository support","text":"

Renovate can update git references from GitRepository resources.

The flux manager only updates GitRepository fields that have a tag or commit key. When commit is being updated, if a branch key is also present, only commits from that branch will be considered.

"},{"location":"modules/manager/flux/#kustomization-support","title":"Kustomization support","text":"

Renovate can update image^1 references from Kustomization resources.

"},{"location":"modules/manager/flux/#ocirepository-support","title":"OCIRepository support","text":"

Renovate can update oci references from OCIRepository resources.

The flux manager updates OCIRepository fields that have a digest, tag or both keys.

"},{"location":"modules/manager/flux/#helm-chart-deptype","title":"Helm chart depType","text":"

Renovate sets the HelmChart depType on the Helm charts it extracts from:

Other OCIRepository resources have no depType.

"},{"location":"modules/manager/flux/#flux-system-manifests-support","title":"Flux system manifests support","text":"

Renovate supports updating Flux system manifests generated during Flux installation. System manifests are identified via being named gotk-components.y(a)ml and containing comment headers as generated by flux bootstrap.

Warning

Renovate cannot identify the use of custom bootstrap flags, such as --cluster-domain. In such a scenario Renovate's PR will overwrite these values with the Flux defaults. See issue #13952 on GitHub for more information.

Updating system manifests requires that either:

  1. The flux tool is pre-installed, or
  2. You run a Docker image based on containerbase, such as the official Renovate images, and have binarySource=install configured
"},{"location":"modules/manager/flux/#default-managerfilepatterns","title":"Default managerFilePatterns","text":"

By default, the flux manager only matches **/gotk-components.y(a)ml. So it only checks system manifest files generated by the flux bootstrap command.

This is because there is no commonly accepted file/directory naming convention for Flux manifests and we don't want to check every single *.yaml file in repositories just in case some of them have Flux definitions.

If most .yaml files in your repository are Flux manifests, then you could add this to your config:

{\n  \"flux\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\"]\n  }\n}\n

If instead you have all your Flux manifests inside a flux/ directory, you would add this:

{\n  \"flux\": {\n    \"managerFilePatterns\": [\"/flux/.+\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/flux/#versioning","title":"Versioning","text":"

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/fvm/","title":"Automated Dependency Updates for FVM","text":"

Categories: dart

Renovate supports updating FVM dependencies.

"},{"location":"modules/manager/fvm/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)\\.fvm/fvm_config\\.json$/\n/(^|/)\\.fvmrc$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/fvm/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: flutter-version.

"},{"location":"modules/manager/fvm/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/fvm/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.fvm/fvm_config\\\\.json$/\",\n    \"/(^|/)\\\\.fvmrc$/\"\n  ],\n  \"versioning\": \"semver\"\n}\n
"},{"location":"modules/manager/fvm/#additional-information","title":"Additional Information","text":"

Keeps the .fvmrc file or older .fvm/fvm_config.json file updated.

"},{"location":"modules/manager/git-submodules/","title":"Automated Dependency Updates for Git Submodules","text":"

Categories: no-category

Renovate supports updating Git Submodules dependencies.

"},{"location":"modules/manager/git-submodules/#enabling","title":"Enabling","text":"

Git Submodules functionality is currently in beta testing, so you must opt-in to test it. To enable it, add a configuration like this to either your self-hosted config or your renovate.json:

{\n  \"git-submodules\": {\n    \"enabled\": true\n  }\n}\n

If you find any bugs, please create a new discussion first. If you find that it works well, then let us know too.

"},{"location":"modules/manager/git-submodules/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.gitmodules$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/git-submodules/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-refs.

"},{"location":"modules/manager/git-submodules/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/git-submodules/#default-config","title":"Default config","text":"
{\n  \"enabled\": false,\n  \"versioning\": \"git\",\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.gitmodules$/\"\n  ]\n}\n
"},{"location":"modules/manager/git-submodules/#additional-information","title":"Additional Information","text":"

Keeps Git submodules updated within a repository.

You can customize the per-submodule checks of the git-submodules manager like this:

{\n  \"ignoreDeps\": [\"path/to/submodule\", \"path/to/submodule2\"],\n  \"git-submodules\": {\n    \"enabled\": true\n  }\n}\n
"},{"location":"modules/manager/git-submodules/#updating-to-specific-tag-values","title":"Updating to Specific Tag Values","text":"

If you want to update your Git submodules to a specific tag, you can set the desired tag as the branch in your .gitmodules file. Renovate will then automatically update this version to the latest Git branch or tag which satisfies your versioning scheme.

[submodule \"renovate\"]\n  path = deps/renovate\n  url = https://github.com/renovatebot/renovate.git\n  branch = v0.0.1\n

Note: Using this approach will disrupt the native git submodule update experience when using git submodule update --remote. You may encounter an error like fatal: Unable to find refs/remotes/origin/v0.0.1 revision in submodule path... because Git can only update submodules when tracking a branch. To manually update the submodule, navigate to the submodule directory and run the following commands: git fetch && git checkout <new tag>.

"},{"location":"modules/manager/git-submodules/#private-modules-authentication","title":"Private Modules Authentication","text":"

Before running the git commands to update the submodules, Renovate exports git insteadOf directives in environment variables.

The following logic is executed prior to \"submodules\" updating:

The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com. For those running against github.com, this token will be the default platform token.

Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.

Rules from this list are converted to environment variable directives if they match any of the following characteristics:

"},{"location":"modules/manager/github-actions/","title":"Automated Dependency Updates for GitHub Actions","text":"

Categories: ci

Renovate supports updating GitHub Actions dependencies.

"},{"location":"modules/manager/github-actions/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)(workflow-templates|\\.(?:github|gitea|forgejo)/(?:workflows|actions))/.+\\.ya?ml$/\n/(^|/)action\\.ya?ml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/github-actions/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: gitea-tags, github-digest, github-runners, github-tags, rust-version.

"},{"location":"modules/manager/github-actions/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description action A repository-based action reference in a uses: field (e.g. actions/checkout@v4) workflow A reusable workflow referenced in a job-level uses: field (e.g. owner/repo/.github/workflows/release.yml@v1) docker A Docker image reference in a uses: field (e.g. uses: docker://alpine:3), or in the runs.image: field of a Docker container action (e.g. image: docker://alpine:3) container A Docker image specified in a job's container: field service A Docker image specified in a job's services: field github-runner A GitHub-hosted runner version in a runs-on: field (e.g. ubuntu-24.04) uses-with A language/runtime version passed as an input to a versioned action (e.g. node-version for actions/setup-node)"},{"location":"modules/manager/github-actions/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)(workflow-templates|\\\\.(?:github|gitea|forgejo)/(?:workflows|actions))/.+\\\\.ya?ml$/\",\n    \"/(^|/)action\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/github-actions/#additional-information","title":"Additional Information","text":"

The github-actions manager extracts dependencies from GitHub Actions workflow and workflow template files. It can also be used for Gitea and Forgejo Actions workflows as such are compatible with GitHub Actions workflows.

"},{"location":"modules/manager/github-actions/#digest-pinning-and-updating","title":"Digest pinning and updating","text":"

If you like to use digest pinning but want to follow the action version tag, you can use the sample below:

name: build\n\non: [push]\n\njobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@3df4ab11eba7bda6032a0b82a6bb43b11571feac # v4.0.0\n

Renovate will update the commit SHA according to the GitHub tag you specified. Renovate can update digests that use SHA1 and SHA256 algorithms. The GitHub tag is in the format of <PREFIX><SEPARATOR><VERSION>. PREFIX and SEPARATOR are optional. Valid separators are the ASCII hyphen (-) or forward slash (/). VERSION can include the major, minor, and patch components and may optionally include a v prefix. Here are the examples of valid GitHub tags: 1.0.1, 1.0, 1, v1.0.1, v1.0, v1, prefix-1.0.1, prefix-1.0, prefix-1, prefix-v1.0.1, prefix-v1.0, prefix-v1. prefix/1.0.1, prefix/1.0, prefix/1, prefix/v1.0.1, prefix/v1.0, prefix/v1.

If you want to automatically pin action digests add the helpers:pinGitHubActionDigests preset to the extends array:

{\n  \"extends\": [\"helpers:pinGitHubActionDigests\"]\n}\n

Actions pinned to a bare SHA without a version comment are disabled by default, because Renovate cannot determine which branch or tag the SHA belongs to. To enable updates, add a tag or branch name as a version comment, as shown above.

"},{"location":"modules/manager/github-actions/#reusable-workflows","title":"Reusable workflows","text":"

A job-level uses: which points at owner/repo/.github/workflows/<file>.yml@<ref> calls a reusable workflow instead of running an action, so Renovate gives it the workflow depType. Every other uses: reference to a repository keeps the action depType, including an action in a subdirectory such as github/codeql-action/init@v3.

Use matchDepTypes to configure the two separately. For example, to keep pinning action digests but leave reusable workflow calls on their tag:

{\n  \"extends\": [\"helpers:pinGitHubActionDigests\"],\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"workflow\"],\n      \"pinDigests\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/github-actions/#github-actions-lockfile-actionslock","title":"GitHub Actions lockfile (actions.lock)","text":"

This feature is flagged as experimental

Experimental features might be changed at any time. Due to GitHub classing this functionality as a \"public preview\", there may be changes to Renovate's functionality - in a possibly breaking manner - while GitHub work to stabilise the feature.

Renovate keeps the GitHub Actions dependency lockfile in sync. The lockfile is an alternative to inline digest pinning: your workflows keep readable tags like actions/checkout@v4.3.1, and .github/workflows/actions.lock records the commit each tag resolved to.

If the repository has a .github/workflows/actions.lock, then Renovate regenerates it whenever it updates an action. Renovate installs the gh-actions-lock extension for the gh CLI, and runs gh actions-lock once per branch, from the repository root, after writing every updated workflow:

gh extension install github/gh-actions-lock --pin <version> --force\ngh actions-lock --no-interactive --no-onboard --no-narrow --ignore-local-actions --json=findings\n

Renovate invokes gh actions-lock in a way that keeps the diff to the dependency being updated, by re-resolving only the refs which have changed, along with anything new they pull in transitively. Every other pin stays as locked, including floating refs (like @v4) which have since moved upstream. For a ghActionsLock constraint below v0.3.0, Renovate passes --relock (which also advances moved floating refs) and --no-migrate-local-actions instead of --ignore-local-actions. With binarySource=global, Renovate assumes the installed extension is v0.3.0 or later.

You do not need to configure anything: if there's no actions.lock file, then there's nothing to update. Workflows which are not onboarded to the lockfile are skipped. Local composite actions are still regenerated, as they can be transitive dependencies of a workflow which is onboarded.

Note

The lockfile is an alternative to inline digest pinning: your workflows keep readable tags like actions/checkout@v4.3.1, and .github/workflows/actions.lock records the commit each tag resolved to. When updating the lockfile, gh actions-lock replaces digest pinned GitHub Actions to the version reference:

-uses: actions/setup-java@1bcf9fb12cf4aa7d266a90ae39939e61372fe520 # v5.4.0\n+uses: actions/setup-java@v5.7.0\n

Digests that are already pinned will be updated by Renovate, until they are removed by gh actions-lock. This does not apply if your organization or repository enables the Require actions to be pinned to a full-length commit SHA policy, found in your Actions settings. If this is enabled, gh actions-lock leaves the digests in place, so your workflows stay digest pinned and Renovate carries on updating them.

Renovate pins the version of the actions-lock extension to provide deterministic updates, which is then bumped in a later Renovate release.

To use a different version, set the ghActionsLock constraint:

{\n  \"constraints\": {\n    \"ghActionsLock\": \"v0.4.0\"\n  }\n}\n

The version must be a full release tag, as in the example above.

Because constraints is mergeable, setting \"constraints\": {} does not remove the pin: set the value to an empty string to always install the latest extension.

{\n  \"constraints\": {\n    \"ghActionsLock\": \"\"\n  }\n}\n

You can also control the gh CLI version using constraints.gh.

Note

With binarySource=global, Renovate does not install or re-pin the extension, as Renovate uses the tools installed by your administrator's deployment. Both gh and the gh-actions-lock extension must already be available, and specifying ghActionsLock and gh in your repository's constraints will be ignored. Pin the extension when you provision your image:

gh extension install github/gh-actions-lock --pin v0.1.6\n

Note

gh actions-lock resolves refs and repository IDs through the GitHub API, so it needs a token. Renovate takes the token from the github host rule matching your platform endpoint, and passes it as GH_TOKEN. On GitHub Enterprise Server Renovate passes that token using GH_ENTERPRISE_TOKEN and GH_HOST, and additionally passes the token from your github.com host rule as GH_TOKEN, because public actions are still resolved against github.com.

"},{"location":"modules/manager/github-actions/#non-semver-refs-branches-and-feature-tags","title":"Non-semver refs (branches and feature tags)","text":"

Renovate supports GitHub Actions that reference non-semver refs like branch names (main, master) or feature-oriented tags (cargo-llvm-cov).

When the action reference doesn't look like a version number (i.e., doesn't match /^v?\\d+/), Renovate routes to the github-digest datasource which fetches both tags and branches. Since these refs have no version ordering, only digest pinning updates are supported.

Routing logic:

When pinning, Renovate adds a comment to preserve the original ref:

- uses: taiki-e/install-action@d8c10dae823f48238abff23fee4146b448aed2f1 # cargo-llvm-cov\n

Non-semver ref support is currently limited to GitHub-hosted actions. Gitea and Forgejo support the same ref types, but Renovate does not yet handle them for these platforms.

"},{"location":"modules/manager/github-actions/#steps-nested-in-parallel-blocks","title":"Steps nested in parallel: blocks","text":"

Renovate extracts dependencies from steps nested inside a parallel: block, just as it does for regular sequential steps. This includes both the action reference itself and any supported with: version inputs.

jobs:\n  build:\n    runs-on: ubuntu-latest\n    steps:\n      - uses: actions/checkout@v4\n      - parallel:\n          - uses: actions/setup-node@v5\n            with:\n              node-version: '20.0.0'\n          - uses: actions/setup-go@v5\n            with:\n              go-version: '1.23'\n
"},{"location":"modules/manager/github-actions/#docker-container-actions","title":"Docker container actions","text":"

For a Docker container action, Renovate extracts the image from runs.image:

runs:\n  using: 'docker'\n  image: 'docker://ghcr.io/ossf/scorecard-action:v2.5.0'\n

Renovate can also pin and update the image's digest:

runs:\n  using: 'docker'\n  image: 'docker://ghcr.io/ossf/scorecard-action:v2.5.0@sha256:1e1481c65fc2407d3fd6ab18a23c741eb4d1c0d9359ebafc4b3ab13aa61d8627'\n

Renovate ignores a runs.image which points at a local Dockerfile.

"},{"location":"modules/manager/github-actions/#non-support-of-variables","title":"Non-support of Variables","text":"

Renovate ignores any GitHub runners which are configured in variables. For example, Renovate ignores the runner configured in the RUNNER variable:

name: build\non: [push]\n\nenv:\n  RUNNER: ubuntu-22.04\n\njobs:\n  build:\n    runs-on: ${{ env.RUNNER }}\n
"},{"location":"modules/manager/github-actions/#ratchet-support","title":"Ratchet support","text":"

The github-action manager understands ratchet comments, like # ratchet:actions/checkout@v2.1.0. This means that Renovate will:

"},{"location":"modules/manager/github-actions/#updating-with-values-in-github-actions","title":"Updating with: values in GitHub Actions","text":"

Both GitHub's own first-party Actions and Actions maintained by the wider community will commonly specify a version of a given tool using a with: block, such as:

steps:\n  - uses: actions/setup-node@v5\n    with:\n      node-version: '22.0.0'\n\n- uses: astral-sh/setup-uv@v10.3.2\n  with:\n    version: '0.4.x'\n

Renovate supports extracting some of these input(s) from the following Actions, and performing automagic dependency updates accordingly.

A single step can yield more than one dependency. For example, pnpm/setup declares both the pnpm version and the JavaScript runtime to install:

steps:\n  - uses: pnpm/setup@v1\n    with:\n      version: '12.0.0'\n      runtime: 'node@24.1.0'\n

The following 90 Actions have support for their with: blocks:

Action with input(s) used Dependency Default versioning zizmorcore/zizmor-action version ghcr.io/zizmorcore/zizmor (Default)1 aws-actions/amazon-ecs-render-task-definition image (determined from with input(s)) (Default)1 renovatebot/github-action renovate-version, renovate-image (determined from with input(s)) (Default)1 dart-lang/setup-dart sdk dart (Default)1 actions/setup-dotnet dotnet-version dotnet-sdk npm actions/setup-go go-version go npm actions/setup-node node-version node node actions/setup-python python-version python npm aquaproj/aqua-installer aqua_version aqua (Default)1 aquasecurity/setup-trivy version aquasecurity/trivy (Default)1 aquasecurity/trivy-action version aquasecurity/trivy (Default)1 astral-sh/ruff-action version ruff (Default)1 astral-sh/setup-uv version astral-sh/uv npm azure/setup-helm version helm (Default)1 azure/setup-kubectl version kubectl (Default)1 bufbuild/buf-setup-action version buf (Default)1 cargo-bins/cargo-binstall version cargo-bins/cargo-binstall (Default)1 cue-lang/setup-cue version cue (Default)1 dagger/dagger-for-github version dagger (Default)1 denoland/setup-deno deno-version deno npm docker/setup-buildx-action version buildx (Default)1 docker/setup-compose-action version docker/compose (Default)1 docker/setup-docker-action version docker (Default)1 extractions/setup-just just-version just (Default)1 fluxcd/flux-mirror/actions/setup version flux-mirror (Default)1 foundry-rs/foundry-toolchain version foundry (Default)1 github/gh-aw-actions/setup-cli version github/gh-aw (Default)1 GitTools/actions/gitversion/setup versionSpec gitversion npm golangci/golangci-lint-action version golangci/golangci-lint (Default)1 goreleaser/goreleaser-action version goreleaser/goreleaser npm hashicorp/setup-packer version packer (Default)1 hashicorp/setup-terraform terraform_version terraform npm helm/chart-releaser-action version chart-releaser (Default)1 helm/chart-testing-action version chart-testing (Default)1 j178/prek-action prek-version prek npm jfrog/setup-jfrog-cli version jfrog-cli (Default)1 julia-actions/setup-julia version julia npm jwlawson/actions-setup-cmake cmake-version cmake npm mozilla-actions/sccache-action version sccache (Default)1 opentofu/setup-opentofu tofu_version opentofu npm peaceiris/actions-hugo hugo-version hugo (Default)1 prefix-dev/setup-pixi pixi-version prefix-dev/pixi semver pulumi/actions pulumi-version pulumi (Default)1 pypa/hatch version pypa/hatch (Default)1 raven-actions/actionlint version actionlint (Default)1 reviewdog/action-setup reviewdog_version reviewdog (Default)1 sigstore/cosign-installer cosign-release sigstore/cosign (Default)1 slsa-framework/actions/attest/actions version slsa-framework/attester (Default)1 slsa-framework/actions/slsa_with_provenance version slsa-framework/source-tool (Default)1 stCarolas/setup-maven maven-version maven npm subosito/flutter-action flutter-version flutter npm superfly/flyctl-actions/setup-flyctl version flyctl (Default)1 swift-actions/setup-swift swift-version swift (Default)1 UpCloudLtd/upcloud-cli-action version UpCloudLtd/upcloud-cli (Default)1 WillAbides/setup-go-faster go-version go npm conda-incubator/setup-miniconda miniforge-version, python-version (determined from with input(s)) (Default)1 crystal-lang/install-crystal crystal, shards (determined from with input(s)) (Default)1 erlef/setup-beam otp-version, elixir-version, gleam-version, rebar3-version (determined from with input(s)) (Default)1 jaxxstorm/action-install-gh-release repo, tag (determined from with input(s)) (Default)1 moonrepo/setup-toolchain moon-version, proto-version (determined from with input(s)) (Default)1 sigoden/install-binary repo, tag (determined from with input(s)) (Default)1 slsa-framework/actions/install/verifier version, repo (determined from with input(s)) (Default)1 slsa-framework/actions/verify/build version, repo (determined from with input(s)) (Default)1 slsa-framework/actions/verify/source version, repo (determined from with input(s)) (Default)1 slsa-framework/actions/verify/vsa version, repo (determined from with input(s)) (Default)1 terraform-linters/setup-tflint tflint_version tflint (Default)1 jdx/mise-action version, sha256 jdx/mise (Default)1 gradle/actions/setup-gradle gradle-version gradle gradle actions/setup-java distribution, java-version, java-package (determined from with input(s)) (Default)1 biomejs/setup-biome version @biomejs/biome (Default)1 cloudflare/wrangler-action wranglerVersion wrangler (Default)1 cycjimmy/semantic-release-action semantic_version semantic-release npm expo/expo-github-action eas-version eas-cli (Default)1 jakebailey/pyright-action version pyright (Default)1 oven-sh/setup-bun bun-version bun (Default)1 pnpm/action-setup version pnpm (Default)1 supabase/setup-cli version supabase (Default)1 abatilo/actions-poetry poetry-version poetry (Default)1 pdm-project/setup-pdm version pdm (Default)1 PyO3/maturin-action maturin-version maturin (Default)1 snok/install-poetry version poetry (Default)1 ruby/setup-ruby ruby-version ruby (Default)1 dtolnay/rust-toolchain toolchain rust (Default)1 moonrepo/setup-rust channel rust (Default)1 actions-rust-lang/setup-rust-toolchain toolchain rust (Default)1 baptiste0928/cargo-install crate, version (determined from with input(s)) (Default)1 graalvm/setup-graalvm java-version, version (determined from with input(s)) (Default)1 helm/kind-action version, node_image, kubectl_version (determined from with input(s)) (Default)1 pnpm/setup version, runtime pnpm (Default)1 voidzero-dev/setup-vp version, node-version (determined from with input(s)) (Default)1

1 Default for the datasource used.

Depending on your use case, you may need to change versioning manually. If you find a use case which you think Renovate could/should automatically detect and support without manual configuration, please raise Suggest an Idea Discussion.

"},{"location":"modules/manager/gitlabci/","title":"Automated Dependency Updates for GitLab CI/CD","text":"

Categories: ci

Renovate supports updating GitLab CI/CD dependencies.

"},{"location":"modules/manager/gitlabci/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.gitlab-ci\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gitlabci/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, gitlab-tags.

"},{"location":"modules/manager/gitlabci/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description image Docker image specified as a string image-name Docker image specified via the name property service-image Docker image used as a service repository A GitLab CI/CD component reference"},{"location":"modules/manager/gitlabci/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.gitlab-ci\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/gitlabci/#additional-information","title":"Additional Information","text":"

Extracts Docker dependencies from gitlab-ci.yml files.

If you need to change the versioning format, read the versioning documentation to learn more.

If you use Gitlab Dependency Proxy then you can use these predefined variables as prefixes for your image:

If you use predefined GitLab CI variables like CI_REGISTRY or CI_SERVER_FQDN make sure to configure their value via registryAliases:

{\n  \"registryAliases\": {\n    \"$CI_REGISTRY\": \"registry.example.com\",\n    \"$CI_SERVER_FQDN\": \"gitlab.example.com\",\n    \"$CI_SERVER_HOST\": \"gitlab.example.com\"\n  }\n}\n

Variables with default values (using the :- syntax) are also supported:

{\n  \"registryAliases\": {\n    \"${CI_REGISTRY:-}\": \"registry.example.com\"\n  }\n}\n

Both image reference formats work:

The alias value works with or without a trailing slash.

"},{"location":"modules/manager/gitlabci-include/","title":"Automated Dependency Updates for GitLab CI/CD include","text":"

Categories: ci

Renovate supports updating GitLab CI/CD include dependencies.

"},{"location":"modules/manager/gitlabci-include/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.gitlab-ci\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gitlabci-include/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: gitlab-tags.

"},{"location":"modules/manager/gitlabci-include/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description repository GitLab project repository reference in a CI/CD include statement"},{"location":"modules/manager/gitlabci-include/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.gitlab-ci\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/gitlabci-include/#additional-information","title":"Additional Information","text":"

Extracts \"includes\" dependencies from gitlab-ci.yml files.

"},{"location":"modules/manager/glasskube/","title":"Automated Dependency Updates for Glasskube","text":"

Categories: kubernetes, cd

Renovate supports updating Glasskube dependencies.

"},{"location":"modules/manager/glasskube/#file-matching","title":"File Matching","text":"

Because file names for glasskube cannot be easily determined automatically, Renovate will not attempt to match any glasskube files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/glasskube/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: glasskube-packages.

"},{"location":"modules/manager/glasskube/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/glasskube/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/glasskube/#additional-information","title":"Additional Information","text":"

Extract version data from Packages/ClusterPackages and repository data from PackageRepositories.

To use the glasskube manager you must set your own managerFilePatterns pattern. The glasskube manager has no default managerFilePatterns pattern, because there is no common filename or directory name convention for Glasskube YAML files. By setting your own managerFilePatterns Renovate avoids having to check each *.yaml file in a repository for a Glasskube definition.

"},{"location":"modules/manager/gleam/","title":"Automated Dependency Updates for Gleam","text":"

Categories: elixir

Renovate supports updating Gleam dependencies.

"},{"location":"modules/manager/gleam/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)gleam.toml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gleam/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: hex.

"},{"location":"modules/manager/gleam/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description dependencies Listed under dependencies devDependencies Listed under dev-dependencies"},{"location":"modules/manager/gleam/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)gleam.toml$/\"\n  ],\n  \"versioning\": \"hex\"\n}\n
"},{"location":"modules/manager/gleam/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/gleam/#additional-information","title":"Additional Information","text":"

Renovate can update gleam.toml and/or manifest.toml files.

"},{"location":"modules/manager/gleam/#how-renovate-updates-gleamtoml-files","title":"How Renovate updates gleam.toml files","text":"

The gleam manager extracts dependencies for the hex datasource, and uses Renovate's implementation of Hex SemVer to evaluate gleam.toml updates.

"},{"location":"modules/manager/gleam/#how-renovate-updates-manifesttoml-files","title":"How Renovate updates manifest.toml files","text":"

The gleam manager uses the gleam program to update manifest.toml files.

"},{"location":"modules/manager/gleam/#enable-lockfilemaintenance","title":"Enable lockFileMaintenance","text":"

We recommend you set lockFileMaintenance to true for the gleam manager, in your Renovate config. This way Renovate can update all your dependencies, including those with in-range updates.

lockFileMaintenance=true periodically refreshes your manifest.toml files, ensuring all dependencies are updated to their latest allowed versions.

"},{"location":"modules/manager/gleam/#default-rangestrategyauto-behavior","title":"Default rangeStrategy=auto behavior","text":"

Renovate's default rangeStrategy is \"auto\". Here's how \"auto\" works with the gleam manager:

Version type New version Old range New range after update What Renovate does Complex range 0.16.0 >= 0.14.0 and < 0.15.0 >= 0.14.0 and < 0.16.1 Widen range to include the new version. Simple range 0.39.0 <= 0.38.0 <= 0.39.0 If update outside current range: widens range to include the new version. Exact version constraint 0.13.0 == 0.12.0 == 0.13.0 Replace old version with new version."},{"location":"modules/manager/gleam/#recommended-rangestrategy-for-apps-and-libraries","title":"Recommended rangeStrategy for apps and libraries","text":"

For applications, we recommend using rangeStrategy=pin. This pins your dependencies to exact versions, which is generally considered best practice for apps.

For libraries, use rangeStrategy=widen with version ranges in your gleam.toml. This allows for greater compatibility with other projects that may use your library as a dependency.

"},{"location":"modules/manager/gomod/","title":"Automated Dependency Updates for Go Modules","text":"

Categories: golang

Renovate supports updating Go Modules dependencies.

"},{"location":"modules/manager/gomod/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)go\\.mod$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gomod/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: go, golang-version.

"},{"location":"modules/manager/gomod/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description golang The go directive specifying the minimum version of Go that the code is source compatible with toolchain The toolchain directive specifying the Go toolchain version require A direct module dependency indirect An indirect (transitive) module dependency replace A module replacement directive tool A tool dependency using Go 1.24+'s tool directive"},{"location":"modules/manager/gomod/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)go\\\\.mod$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/gomod/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/gomod/#updating-of-go-mod-and-toolchain-directives","title":"Updating of Go mod and toolchain directives","text":"

In go.mod, the go directive essentially means \"Compatible with this version or later\". It is generally recommended for Go projects to not bump this version unless necessary, and therefore Renovate's default behavior is not to propose upgrades to it. If you need to update it once or irregularly, it's recommended to do it manually. If you are sure you want to always bump it to latest, then you need the following configuration:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"gomod\"],\n      \"matchDepNames\": [\"go\"],\n      \"matchDepTypes\": [\"golang\"],\n      \"rangeStrategy\": \"bump\"\n    }\n  ]\n}\n

In go.mod, the toolchain directive essentially means \"Use this exact version of go\". Unlike the go directive, it's valid to keep bumping this, and you should see updates to it proposed by default.

"},{"location":"modules/manager/gomod/#only-suggesting-updates-that-match-your-go-directive","title":"Only suggesting updates that match your go directive","text":"

In go.mod, the go directive essentially means \"Compatible with this version or later\". It is generally recommended for Go projects to not bump this version unless necessary.

As noted above, Renovate doesn't update this directly, but dependency updates can lead to a package you rely on bumping their go directive, which means you can't accept the proposed update without also bumping your go directive.

To make this simpler, you can use constraintsFiltering=strict to make sure that Renovate will only propose updates that match the constraints you specify.

For example, given the go.mod:

module example\n\ngo 1.24.0\n\nrequire golang.org/x/mod v0.32.0\n

We can then configure Renovate to set the same constraint when updating any Go dependencies:

{\n  \"$schema\": \"https://docs.renovatebot.com/renovate-schema.json\",\n  \"packageRules\": [\n    {\n      \"description\": \"Ensure source compatibility with Go version used by this project\",\n      \"matchManagers\": [\"gomod\"],\n      \"constraintsFiltering\": \"strict\"\n    }\n  ]\n}\n

In this case, Renovate would only propose an update to a version of golang.org/x/mod that supports Go 1.24.x.

Note

It is recommended to read the constraintsFiltering documentation and Language constraints and upgrading for more information about how the filtering works and how strict this can be.

"},{"location":"modules/manager/gomod/#post-update-options","title":"Post-Update Options","text":"

You might be interested in the following postUpdateOptions:

  1. gomodTidy - if you'd like Renovate to run go mod tidy after every update before raising the PR
  2. This is implicitly enabled for major updates if the user has enabled the option gomodUpdateImportPaths
  3. gomodTidy1.17 - if you'd like Renovate to run go mod tidy -compat=1.17 after every update before raising the PR
  4. gomodTidyE - if you'd like Renovate to run go mod tidy -e after every update before raising the PR
  5. gomodTidyAll - if you'd like Renovate to also run go mod tidy on every other module which depends on the updated one through a local replace directive
  6. gomodUpdateImportPaths - if you'd like Renovate to update your source import paths on major updates before raising the PR
  7. gomodMassage - to enable massaging of all replace statements prior to running go so that they will be ignored
  8. goGenerate - to run go generate ./... after vendoring.

When Renovate is running using binarySource=install (such as in the Mend Renovate App) then it will pick the latest compatible version of Go to run, i.e. the latest 1.x release. Even if the go.mod has a version like go 1.22, Renovate will treat it as a ^1.22 constraint and not =1.22.

Unless matching tool directives exist, indirect updates are disabled by default. To enable them, add a package rule such as:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"gomod\"],\n      \"matchDepTypes\": [\"indirect\"],\n      \"enabled\": true\n    }\n  ]\n}\n
"},{"location":"modules/manager/gomod/#private-modules-authentication","title":"Private Modules Authentication","text":"

Before running the go commands to update the go.sum, Renovate exports git insteadOf directives in environment variables.

The following logic is executed prior to \"artifacts\" updating:

The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com. For those running against github.com, this token will be the default platform token.

Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.

Rules from this list are converted to environment variable directives if they match any of the following characteristics:

"},{"location":"modules/manager/gomod/#major-upgrades-of-dependencies","title":"Major upgrades of dependencies","text":"

Major upgrades in Go are different from most other ecosystems, because both the version and module name need to be changed. It is very common that such upgrades require changes to application code, which Renovate doesn't do.

By default, Renovate will make such change in the go.mod files but nothing else - the rest is up to you. If you add gomodUpdateImportPaths to postUpdateOptions then Renovate will also use a third-party tool to migrate import paths within application code, but there may still be actual application logic which needs to be changed too.

Ultimately: it is known and unavoidable that the majority of major Go upgrades won't be immediately mergeable. You might prefer to configure such major updates with dependencyDashboardApproval=true so that you can request them on demand, on supported platforms.

"},{"location":"modules/manager/gradle/","title":"Automated Dependency Updates for Gradle","text":"

Categories: java

Renovate supports updating Gradle dependencies.

"},{"location":"modules/manager/gradle/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/\\.gradle(\\.kts)?$/\n/(^|/)gradle\\.properties$/\n/(^|/)gradle/.+\\.toml$/\n/(^|/)buildSrc/.+\\.kt$/\n/\\.versions\\.toml$/\n/(^|/)versions.props$/\n/(^|/)versions.lock$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gradle/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/gradle/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description plugin A Gradle plugin dependency dependencies A standard Gradle dependency devDependencies A dependency from a buildSrc project test A test dependency from the gradle-consistent-versions plugin lock file"},{"location":"modules/manager/gradle/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.gradle(\\\\.kts)?$/\",\n    \"/(^|/)gradle\\\\.properties$/\",\n    \"/(^|/)gradle/.+\\\\.toml$/\",\n    \"/(^|/)buildSrc/.+\\\\.kt$/\",\n    \"/\\\\.versions\\\\.toml$/\",\n    \"/(^|/)versions.props$/\",\n    \"/(^|/)versions.lock$/\"\n  ],\n  \"timeout\": 600,\n  \"versioning\": \"gradle\"\n}\n
"},{"location":"modules/manager/gradle/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/gradle/#additional-information","title":"Additional Information","text":"

The gradle manager uses a custom parser written in JavaScript, similar to many others managers. It does not call gradle directly in order to extract a list of dependencies.

"},{"location":"modules/manager/gradle/#executing-the-gradle-wrapper","title":"Executing the Gradle Wrapper","text":"

Renovate will only execute the Gradle Wrapper (via ./gradlew or gradlew.bat) if the self-hosted administrator configures allowedUnsafeExecutions to include the gradleWrapper option. This is required due to possible supply chain security attack vectors that can occur with the Gradle Wrapper being executed.

"},{"location":"modules/manager/gradle/#updating-lockfiles","title":"Updating lockfiles","text":"

The gradle manager supports gradle lock files in .lockfile artifacts, as well as lock files used by the gradle-consistent-versions plugin. During lock file maintenance, renovate calls ./gradlew :dependencies --write-locks on the root project and subprojects. For regular dependency updates, renovate automatically updates lock state entries via the --update-locks command line flag.

As the output of these commands can be very large, any text other than errors (in stderr) is discarded.

"},{"location":"modules/manager/gradle/#dependency-verification","title":"Dependency verification","text":"

Renovate supports Gradle's dependency verification functionality to ensure that checksums are calculated for your dependencies.

Note

This requires your self-hosted administrator to allow the Gradle Wrapper to execute.

If Renovate finds a gradle/verification-metadata.xml file and either <verify-metadata>true</verify-metadata> or <verify-signatures>true</verify-signatures> (or both), it updates the content by using the ./gradlew --write-verification-metadata <hashTypes> dependencies command. Renovate will check the file for existing hash types (like sha256) and use them as <hashTypes>.

Warning

Gradle allows verification metadata to use the md5 and sha1 algorithms. Because those algorithms are prone to collision attacks, Renovate ignores them. If Renovate encounters hashes that are generated with md5 or sha1 algorithms, Renovate uses sha256 instead.

"},{"location":"modules/manager/gradle/#rich-version-constraints","title":"Rich version constraints","text":"

Renovate extracts dependencies whose version comes from a Gradle rich version constraint declared in a version { ... } block, in both the Groovy and the Kotlin DSL:

dependencies {\n    implementation('org.slf4j:slf4j-api') {\n        version {\n            strictly '[1.7, 1.8['\n        }\n    }\n}\n

Renovate can only rewrite one version literal per dependency, so it picks a single constraint to update and records which one in managerData.versionConstraint:

Declared constraints What Renovate updates strictly strictly strictly + prefer strictly, if strictly is a single version require require require + prefer require, because prefer is only a hint prefer prefer require + strictly nothing, skipped as multiple-constraint-dep strictly range + prefer nothing, skipped as multiple-constraint-dep anything + reject or rejectAll nothing, skipped as unsupported-version

strictly and prefer pin a version on purpose, so Renovate disables those dependencies by default and only updates them for vulnerability alerts. If you disable them yourself with a package rule, Renovate skips their vulnerability fixes too. A require constraint means the same thing as a plain version declaration, so it is updated like any other dependency.

To also receive regular updates for strictly and prefer constraints, opt in with a package rule:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"gradle\"],\n      \"matchJsonata\": [\n        \"managerData.versionConstraint in ['strictly', 'prefer']\"\n      ],\n      \"enabled\": true\n    }\n  ]\n}\n

Note

Rich versions in version catalogs are extracted by the TOML parser instead, which updates a single require, prefer or strictly constraint without disabling it.

Note

A version { ... } block on a dependency that already spells out its version, such as implementation('org.slf4j:slf4j-api:1.7.25') { version { strictly '1.7.30' } }, is not valid Gradle. Renovate updates the version in the dependency string and ignores the block.

"},{"location":"modules/manager/gradle-wrapper/","title":"Automated Dependency Updates for Gradle Wrapper","text":"

Categories: java

Renovate supports updating Gradle Wrapper dependencies.

"},{"location":"modules/manager/gradle-wrapper/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)gradle/wrapper/gradle-wrapper\\.properties$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/gradle-wrapper/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: gradle-version.

"},{"location":"modules/manager/gradle-wrapper/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/gradle-wrapper/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)gradle/wrapper/gradle-wrapper\\\\.properties$/\"\n  ],\n  \"versioning\": \"gradle\"\n}\n
"},{"location":"modules/manager/gradle-wrapper/#additional-information","title":"Additional Information","text":"

Configuration for Gradle Wrapper updates. Changes here affect how Renovate updates the version of gradle in the wrapper, not how it uses the wrapper.

"},{"location":"modules/manager/haskell-cabal/","title":"Automated Dependency Updates for Haskell Cabal","text":"

Categories: haskell

Renovate supports updating Haskell Cabal dependencies.

"},{"location":"modules/manager/haskell-cabal/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.cabal$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/haskell-cabal/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: hackage.

"},{"location":"modules/manager/haskell-cabal/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/haskell-cabal/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.cabal$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/haskell-cabal/#additional-information","title":"Additional Information","text":"

Supports dependency extraction from build-depends fields in Cabal package description files. They use the extension .cabal, and are used with the Haskell programming language.

Limitations:

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/helm-requirements/","title":"Automated Dependency Updates for Helm v2 Chart Dependencies","text":"

Categories: helm, kubernetes

Renovate supports updating Helm v2 Chart Dependencies dependencies.

"},{"location":"modules/manager/helm-requirements/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)requirements\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/helm-requirements/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: helm.

"},{"location":"modules/manager/helm-requirements/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/helm-requirements/#default-config","title":"Default config","text":"
{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  },\n  \"commitMessageTopic\": \"helm chart {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)requirements\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/helm-requirements/#additional-information","title":"Additional Information","text":"

Renovate supports updating Helm Chart references within requirements.yaml files.

The helm-requirements manager defines this default registryAlias:

{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  }\n}\n

If your Helm charts make use of repository aliases then you will need to configure an registryAliases object in your config to tell Renovate where to look for them. Be aware that alias values must be properly formatted URIs.

If you need to change the versioning format, read the versioning documentation to learn more.

To learn how to use Helm with private packages, read private package support, Package Manager Credentials for Artifact Updating, helm.

"},{"location":"modules/manager/helm-values/","title":"Automated Dependency Updates for Helm Values","text":"

Categories: helm, kubernetes

Renovate supports updating Helm Values dependencies.

"},{"location":"modules/manager/helm-values/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)values\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/helm-values/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/helm-values/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/helm-values/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"helm values {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)values\\\\.ya?ml$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/helm-values/#additional-information","title":"Additional Information","text":"

Renovate supports updating of Docker dependencies within Helm Chart values.yaml files or other YAML files that use the same format (via managerFilePatterns configuration). Updates are performed if the files follow the conventional format used in most of the Helm charts:

image:\n  repository: 'some-docker/dependency'\n  tag: v1.0.0\n  registry: registry.example.com # optional key, will default to \"docker.io\"\n\nimage:\n  repository: 'some-docker/dependency'\n  version: v1.0.0\n\ncoreImage:\n  registry: docker.io\n  repository: bitnami/harbor-core\n  tag: 2.1.3-debian-10-r38\n\ncli:\n  image: 'some-docker/dependency'\n  tag: v1.0.0\n\ncli:\n  image: 'some-docker/dependency'\n  version: v1.0.0\n

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/helmfile/","title":"Automated Dependency Updates for Helmfile","text":"

Categories: cd, helm, kubernetes

Renovate supports updating Helmfile dependencies.

"},{"location":"modules/manager/helmfile/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)helmfile\\.ya?ml(?:\\.gotmpl)?$/\n/(^|/)helmfile\\.d/.+\\.ya?ml(?:\\.gotmpl)?$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/helmfile/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, helm.

"},{"location":"modules/manager/helmfile/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/helmfile/#default-config","title":"Default config","text":"
{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  },\n  \"commitMessageTopic\": \"helm chart {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)helmfile\\\\.ya?ml(?:\\\\.gotmpl)?$/\",\n    \"/(^|/)helmfile\\\\.d/.+\\\\.ya?ml(?:\\\\.gotmpl)?$/\"\n  ]\n}\n
"},{"location":"modules/manager/helmfile/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/helmfile/#additional-information","title":"Additional Information","text":"

Checks helmfile.yaml files and extracts dependencies for the helm datasource.

The helmfile manager defines this default registryAlias:

{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  }\n}\n

If your Helm charts make use of repository aliases then you will need to configure an registryAliases object in your config to tell Renovate where to look for them. Be aware that alias values must be properly formatted URIs.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/helmfile/#private-repositories-and-registries","title":"Private repositories and registries","text":"

To use private sources of Helm charts, you must set the password and username you use to authenticate to the private source. For this you use a custom hostRules array.

"},{"location":"modules/manager/helmfile/#classic-repositories","title":"Classic repositories","text":"

Renovate passes hostRules with hostType: 'helm' to helmfile deps for classic (non-OCI) repositories. It does so through the <NAME>_USERNAME and <NAME>_PASSWORD environment variables, where <NAME> is the repository name in upper case with dashes replaced by underscores. The hostRules entry must have both a username and a password, and its matchHost must match the repository url. Helmfile uses each variable only when the repository does not set that field itself.

For example, with this helmfile.yaml:

repositories:\n  - name: team-a-charts\n    url: https://charts.example.com/team-a\n  - name: public\n    url: https://public.example.com\nreleases:\n  - name: app\n    chart: team-a-charts/app\n    version: 1.0.0\n

and this Renovate config:

{\n  hostRules: [\n    {\n      matchHost: 'https://charts.example.com',\n      hostType: 'helm',\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n  ],\n}\n

Renovate runs helmfile deps with TEAM_A_CHARTS_USERNAME and TEAM_A_CHARTS_PASSWORD set. The public repository has no matching hostRules entry, so it gets no credentials.

"},{"location":"modules/manager/helmfile/#oci-registries","title":"OCI registries","text":"
{\n  hostRules: [\n    {\n      // global login\n      matchHost: 'ghcr.io',\n      hostType: 'docker',\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n    {\n      // login with encrypted password\n      matchHost: 'https://ghci.io',\n      hostType: 'docker',\n      username: '<some-username>',\n      encrypted: {\n        password: 'some-encrypted-password',\n      },\n    },\n  ],\n}\n
"},{"location":"modules/manager/helmsman/","title":"Automated Dependency Updates for Helmsman","text":"

Categories: cd, helm, kubernetes

Renovate supports updating Helmsman dependencies.

"},{"location":"modules/manager/helmsman/#file-matching","title":"File Matching","text":"

Because file names for helmsman cannot be easily determined automatically, Renovate will not attempt to match any helmsman files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/helmsman/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, helm.

"},{"location":"modules/manager/helmsman/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/helmsman/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/helmsman/#additional-information","title":"Additional Information","text":"

The helmsman manager is currently limited and does not support the full feature set of Helmsman, read about the limitations below.

"},{"location":"modules/manager/helmsman/#non-configured-managerfilepatterns","title":"Non-configured managerFilePatterns","text":"

By default the helmsman manager has an empty array for its managerFilePatterns configuration option, because there is no convention for file naming in practice. This means that helmsman won't search for any files, and you won't get any updates from the manager.

To enable the helmsman manager, provide a valid managerFilePatterns yourself, for example:

{\n  \"helmsman\": {\n    \"managerFilePatterns\": [\"/(^|/)desired_state\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/helmsman/#file-format","title":"File format","text":"

Currently, state files must be in the .yaml format. The .toml format is not supported.

"},{"location":"modules/manager/helmsman/#oci-helm-charts","title":"OCI Helm charts","text":"

Renovate looks up Helm charts stored in OCI registries with the docker datasource. Use registryAliases to map a registry host, for example a pull-through cache, to the registry Renovate should query instead.

"},{"location":"modules/manager/helmv3/","title":"Automated Dependency Updates for Helm v3","text":"

Categories: helm, kubernetes

Renovate supports updating Helm v3 dependencies.

"},{"location":"modules/manager/helmv3/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Chart\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/helmv3/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, helm.

"},{"location":"modules/manager/helmv3/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/helmv3/#default-config","title":"Default config","text":"
{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  },\n  \"commitMessageTopic\": \"helm chart {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)Chart\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/helmv3/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/helmv3/#additional-information","title":"Additional Information","text":"

Renovate supports updating Helm Chart references in:

The helmv3 manager defines this default registryAlias:

{\n  \"registryAliases\": {\n    \"stable\": \"https://charts.helm.sh/stable\"\n  }\n}\n

If you use repository aliases in your Helm charts then you must set an registryAliases object in your configuration file so Renovate knows where to find the repository. Alias values must be properly formatted URIs.

If you need to change the versioning format, read our versioning documentation to learn more.

"},{"location":"modules/manager/helmv3/#private-repositories-and-registries","title":"Private repositories and registries","text":"

To use private sources in your Helm charts, you must set the password and username you use to authenticate to the private source. For this you use a custom hostRules array.

"},{"location":"modules/manager/helmv3/#oci-registries","title":"OCI registries","text":"
{\n  hostRules: [\n    {\n      // Global login\n      matchHost: 'registry.gitlab.com',\n      hostType: 'docker',\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n    {\n      // For repository string oci://registry.gitlab.com/user/oci-helm-test\n      matchHost: 'https://registry.gitlab.com/user/oci-helm-test',\n      hostType: 'docker',\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n  ],\n}\n
"},{"location":"modules/manager/helmv3/#helm-repository","title":"Helm repository","text":"
{\n  hostRules: [\n    {\n      // Global login for 'gitlab.com' if using Helm\n      matchHost: 'gitlab.com',\n      hostType: 'helm', // this is optional, but else the credentials will be used for all requests matching `matchHost`\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n    {\n      // Specific repository\n      matchHost: 'https://gitlab.com/api/v4/projects/xxxxxxx/packages/helm/stable',\n      hostType: 'helm', // this is optional\n      username: '<some-username>',\n      password: '<some-password>',\n    },\n  ],\n}\n
"},{"location":"modules/manager/helmv3/#subchart-archives","title":"Subchart archives","text":"

To get updates for subchart archives put helmUpdateSubChartArchives in your postUpdateOptions configuration. Renovate now updates archives in the /charts folder.

{\n  \"postUpdateOptions\": [\"helmUpdateSubChartArchives\"]\n}\n
"},{"location":"modules/manager/helmv3/#oci-helm-charts","title":"OCI Helm charts","text":"

Renovate looks up Helm charts stored in OCI registries with the docker datasource. Use registryAliases to map a registry host, for example a pull-through cache, to the registry Renovate should query instead.

"},{"location":"modules/manager/hermit/","title":"Automated Dependency Updates for Hermit","text":"

Categories: no-category

Renovate supports updating Hermit dependencies.

"},{"location":"modules/manager/hermit/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)bin/hermit$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/hermit/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: hermit.

"},{"location":"modules/manager/hermit/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/hermit/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)bin/hermit$/\"\n  ],\n  \"excludeCommitPaths\": [\n    \"**/bin/hermit\"\n  ],\n  \"versioning\": \"hermit\"\n}\n
"},{"location":"modules/manager/hermit/#additional-information","title":"Additional Information","text":"

Hermit package installation token

When upgrading private packages through, Hermit manager will uses one of the following two tokens to download private packages.

HERMIT_GITHUB_TOKEN\nGITHUB_TOKEN\n

These environment variable could be passed on via setting it in customEnvironmentVariables.

Git credentials configured in hostRules are also automatically propagated to hermit install via GIT_CONFIG_* environment variables. This enables Hermit to fetch packages from private Git repositories without additional configuration.

Nested Hermit setup

Nested Hermit setup in a single repository is also supported. e.g.

\u251cbin\n\u251c\u2500hermit\n\u251c\u2500(other files)\n\u251c\n\u251cnested\n\u251c\u2500bin\n\u251c\u2500\u2500hermit\n\u251c\u2500\u2500(other files)\n
"},{"location":"modules/manager/homeassistant-manifest/","title":"Automated Dependency Updates for Home Assistant Manifest","text":"

Categories: python

Renovate supports updating Home Assistant Manifest dependencies.

"},{"location":"modules/manager/homeassistant-manifest/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)manifest\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/homeassistant-manifest/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, pypi.

"},{"location":"modules/manager/homeassistant-manifest/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/homeassistant-manifest/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)manifest\\\\.json$/\"\n  ]\n}\n
"},{"location":"modules/manager/homeassistant-manifest/#additional-information","title":"Additional Information","text":"

The Home Assistant Manifest manager updates the requirements field in Home Assistant integration manifest.json files.

Example manifest.json
{\n  \"domain\": \"my_integration\",\n  \"name\": \"My Integration\",\n  \"requirements\": [\"aiohttp==3.9.1\", \"pydantic>=2.5.0\"]\n}\n
"},{"location":"modules/manager/homebrew/","title":"Automated Dependency Updates for Homebrew","text":"

Categories: no-category

Renovate supports updating Homebrew dependencies.

"},{"location":"modules/manager/homebrew/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /^Formula/\\w*/?[^/]+[.]rb$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/homebrew/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases, github-tags, npm.

"},{"location":"modules/manager/homebrew/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/homebrew/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"Homebrew Formula {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/^Formula/\\\\w*/?[^/]+[.]rb$/\"\n  ]\n}\n
"},{"location":"modules/manager/homebrew/#additional-information","title":"Additional Information","text":"

The homebrew manager extracts dependencies from Homebrew Formula Ruby files.

"},{"location":"modules/manager/homebrew/#supported-files","title":"Supported Files","text":"

Renovate supports Formula files that follow the Homebrew naming convention:

"},{"location":"modules/manager/homebrew/#supported-dependencies","title":"Supported Dependencies","text":"

The manager extracts and updates:

"},{"location":"modules/manager/homebrew/#how-it-works","title":"How It Works","text":"

When a new version is available, Renovate:

  1. Downloads the new tarball from GitHub or NPM registry
  2. Calculates the SHA256 checksum
  3. Updates both the url and sha256 fields in the Formula file
"},{"location":"modules/manager/homebrew/#limitations","title":"Limitations","text":""},{"location":"modules/manager/homebrew/#example-formulas","title":"Example Formulas","text":""},{"location":"modules/manager/homebrew/#github-package","title":"GitHub Package","text":"
class MyPackage < Formula\n  desc \"My awesome package\"\n  homepage \"https://github.com/owner/repo\"\n  url \"https://github.com/owner/repo/releases/download/v1.2.3/repo-1.2.3.tar.gz\"\n  sha256 \"abc123def456...\"\n\n  def install\n    # installation steps\n  end\nend\n
"},{"location":"modules/manager/homebrew/#npm-package","title":"npm Package","text":"
class ClaudeCode < Formula\n  desc \"Anthropic's official CLI for Claude\"\n  homepage \"https://www.anthropic.com/claude-code\"\n  url \"https://registry.npmjs.org/@anthropic-ai/claude-code/-/claude-code-1.0.0.tgz\"\n  sha256 \"abc123def456...\"\n  license \"Proprietary\"\nend\n
"},{"location":"modules/manager/homebrew/#unsupported-formulas","title":"Unsupported Formulas","text":"

Formulas with the following characteristics will be skipped:

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/html/","title":"Automated Dependency Updates for HTML","text":"

Categories: cd

Renovate supports updating HTML dependencies.

"},{"location":"modules/manager/html/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.html?$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/html/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: cdnjs.

"},{"location":"modules/manager/html/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/html/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.html?$/\"\n  ],\n  \"versioning\": \"semver\",\n  \"digest\": {\n    \"enabled\": false\n  },\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/html/#additional-information","title":"Additional Information","text":"

The html manager updates <script> tags and CSS <link> tags that point to the cdnjs content delivery network. It also updates Subresource Integrity (SRI) hashes in integrity attributes.

Key differences between the cdnurl manager and the html manager:

"},{"location":"modules/manager/jenkins/","title":"Automated Dependency Updates for Jenkins","text":"

Categories: ci

Renovate supports updating Jenkins dependencies.

"},{"location":"modules/manager/jenkins/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)plugins\\.(txt|ya?ml)$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/jenkins/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: jenkins-plugins.

"},{"location":"modules/manager/jenkins/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/jenkins/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)plugins\\\\.(txt|ya?ml)$/\"\n  ]\n}\n
"},{"location":"modules/manager/jenkins/#additional-information","title":"Additional Information","text":"

The Jenkins manager supports a custom text or YAML format of the plugin list as described on their github page.

By default, Renovate gets the versions from the main Jenkins update center.

There are no strict filename rules, the convention is to name the file plugins.txt or plugins.yaml.

"},{"location":"modules/manager/jsonata/","title":"Custom Manager Support using JSONata","text":"

Categories: custom

With customManagers using JSONata queries you can configure Renovate so it finds dependencies in JSON, TOML and YAML files, that are not detected by its other built-in package managers.

Renovate uses the jsonata package to process the file content using the queries, after the content has been parsed into json format.

For more on the jsonata query language, read the jsonata query language site.

The JSONata manager is unique in Renovate, because:

If you have limited managers to run within enabledManagers config option, you need to add \"custom.jsonata\" to the list.

"},{"location":"modules/manager/jsonata/#required-fields","title":"Required Fields","text":"

The first two required fields are managerFilePatterns and matchStrings:

"},{"location":"modules/manager/jsonata/#information-that-renovate-needs-about-the-dependency","title":"Information that Renovate needs about the dependency","text":"

Before Renovate can look up a dependency and decide about updates, it must have this info about each dependency:

Info type Required Notes Docs Name of the dependency Yes datasource Yes Example datasources: npm, Docker, GitHub tags, and so on. Supported datasources Version scheme to use. Defaults to semver-coerced. Yes You may set another version scheme, like pep440. Supported versioning schemes fileFormat Yes Must be either json, yaml or toml. Configuration Options"},{"location":"modules/manager/jsonata/#required-fields-to-be-present-in-the-resulting-structure-returned-by-the-jsonata-query","title":"Required fields to be present in the resulting structure returned by the jsonata query","text":"

You must:

"},{"location":"modules/manager/jsonata/#optional-fields-you-can-include-in-the-resulting-structure","title":"Optional fields you can include in the resulting structure","text":"

You may use any of these items:

"},{"location":"modules/manager/jsonata/#usage","title":"Usage","text":"

When you configure a JSONata manager, use the following syntax:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"json\",\n      \"managerFilePatterns\": [\"<file match pattern>\"],\n      \"matchStrings\": [\"<query>\"],\n      ...\n    }\n  ]\n}\n

Overwrite the <query> placeholder text with your JSONata query. The JSONata query transforms the content to a JSON object, similar to this:

dependencies information extracted using a JSONata query
[\n  {\n    \"depName\": \"some_dep\",\n    \"currentValue\": \"1.0.0\",\n    \"datasource\": \"docker\",\n    \"versioning\": \"semver\"\n  }\n]\n

Creating your Renovate JSONata manager config is easier if you understand JSONata queries. We recommend you follow these steps:

  1. Read the official JSONata query language docs
  2. Check our example queries below
  3. You're ready to make your own config

Alternatively, you can use \"trial and error\" to a working config by adjusting our examples.

YAML files are parsed as multi-document files, even those that have only one document.

"},{"location":"modules/manager/jsonata/#yaml-parsing","title":"YAML parsing","text":"

To show how the JSONata manager parses YAML, below is an example YAML file and the corresponding parsing to JSON.

YAML:

Example multi document YAML file
production:\n  packages:\n    version: 1.2.3\n    package: foo\ntest:\n  metadata:\n    - version: 4.5.6\n      package: bar\n---\ndevelopment:\n  author: Renovate\n

JSON:

Example JSON parsing
[\n  {\n    \"production\": {\n      \"packages\": {\n        \"version\": \"1.2.3\",\n        \"package\": \"foo\"\n      }\n    },\n    \"test\": {\n      \"metadata\": [\n        {\n          \"version\": \"4.5.6\",\n          \"package\": \"bar\"\n        }\n      ]\n    }\n  },\n  {\n    \"development\": {\n      \"author\": \"Renovate\"\n    }\n  }\n]\n
"},{"location":"modules/manager/jsonata/#example-queries","title":"Example queries","text":"

Below are some example queries for the generic JSON manager. You can also use the JSONata test website to experiment with queries.

Dependencies spread in different nodes, and we want to limit the extraction to a particular node
{\n  \"production\": [\n    {\n      \"version\": \"1.2.3\",\n      \"package\": \"foo\"\n    }\n  ],\n  \"development\": [\n    {\n      \"version\": \"4.5.6\",\n      \"package\": \"bar\"\n    }\n  ]\n}\n

Query:

production.{ \"depName\": package, \"currentValue\": version }\n
Dependencies spread in different nodes, and we want to extract all of them as if they were in the same node
{\n  \"production\": [\n    {\n      \"version\": \"1.2.3\",\n      \"package\": \"foo\"\n    }\n  ],\n  \"development\": [\n    {\n      \"version\": \"4.5.6\",\n      \"package\": \"bar\"\n    }\n  ]\n}\n

Query:

*.{ \"depName\": package, \"currentValue\": version }\n
The dependency name is in a JSON node name, and the version is in a child leaf to that node
{\n  \"foo\": {\n    \"version\": \"1.2.3\"\n  },\n  \"bar\": {\n    \"version\": \"4.5.6\"\n  }\n}\n

Query:

$each(function($v, $n) { { \"depName\": $n, \"currentValue\": $v.version } })\n
The dependency name and its version are both value nodes of the same parent node
{\n  \"packages\": [\n    {\n      \"version\": \"1.2.3\",\n      \"package\": \"foo\"\n    },\n    {\n      \"version\": \"4.5.6\",\n      \"package\": \"bar\"\n    }\n  ]\n}\n

Query:

packages.{ \"depName\": package, \"currentValue\": version }\n
The dependency name and version are part of the same string
{\n  \"packages\": [\"foo@1.2.3\", \"bar@4.5.6\"]\n}\n

Query:

$map($map(packages, function ($v) { $split($v, \"@\") }), function ($v) { { \"depName\": $v[0], \"currentVersion\": $v[1] } })\n
JSONata manager config to extract deps from a package.json file in the Renovate repository
{\n  \"customManagers\": [\n    {\n      \"customType\": \"jsonata\",\n      \"fileFormat\": \"json\",\n      \"managerFilePatterns\": [\"/package.json/\"],\n      \"matchStrings\": [\n        \"$each(dependencies, function($v, $k) { {\\\"depName\\\":$k, \\\"currentValue\\\": $v, \\\"depType\\\": \\\"dependencies\\\"}})\",\n        \"$each(devDependencies, function($v, $k) { {\\\"depName\\\":$k, \\\"currentValue\\\": $v, \\\"depType\\\": \\\"devDependencies\\\"}})\",\n        \"$each(optionalDependencies, function($v, $k) { {\\\"depName\\\":$k, \\\"currentValue\\\": $v, \\\"depType\\\": \\\"optionalDependencies\\\"}})\",\n        \"{ \\\"depName\\\": \\\"pnpm\\\", \\\"currentValue\\\": $substring(packageManager, 5),  \\\"depType\\\": \\\"packageManager\\\"}\"\n      ],\n      \"datasourceTemplate\": \"npm\"\n    }\n  ]\n}\n
Dependencies in a single node, and we want to extract all of them
packages:\n  - version: 1.2.3\n    package: foo\n

Query:

packages.{ \"depName\": package, \"currentValue\": version }\n
Dependencies in a single node in a multi document yaml, and we want to extract all of them
packages:\n  - version: 1.2.3\n    package: foo\n---\npackages:\n  - version: 1.2.5\n    package: bar\n

Query:

packages.{ \"depName\": package, \"currentValue\": version }\n
JSONata manager config to extract deps from a toml file
[[packages]]\nversion = \"1.2.3\"\npackage = \"foo\"\n\n[[packages]]\nversion = \"1.2.2\"\npackage = \"bar\"\n

Query:

packages.{ \"depName\": package, \"currentValue\": version }\n
"},{"location":"modules/manager/jsonnet-bundler/","title":"Automated Dependency Updates for jsonnet-bundler","text":"

Categories: kubernetes

Renovate supports updating jsonnet-bundler dependencies.

"},{"location":"modules/manager/jsonnet-bundler/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)jsonnetfile\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/jsonnet-bundler/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags.

"},{"location":"modules/manager/jsonnet-bundler/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/jsonnet-bundler/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)jsonnetfile\\\\.json$/\"\n  ],\n  \"datasource\": \"git-tags\"\n}\n
"},{"location":"modules/manager/jsonnet-bundler/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/jsonnet-bundler/#additional-information","title":"Additional Information","text":"

Extracts dependencies from jsonnetfile.json files, updates jsonnetfile.lock.json and updates the vendor directory.

Supports lock file maintenance.

This plugin requires jsonnet-bundler >= v0.4.0 since previous versions don't support updating single dependencies.

"},{"location":"modules/manager/kotlin-script/","title":"Automated Dependency Updates for Kotlin Script","text":"

Categories: java

Renovate supports updating Kotlin Script dependencies.

"},{"location":"modules/manager/kotlin-script/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /^.+\\.main\\.kts$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/kotlin-script/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/kotlin-script/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/kotlin-script/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/^.+\\\\.main\\\\.kts$/\"\n  ]\n}\n
"},{"location":"modules/manager/kotlin-script/#additional-information","title":"Additional Information","text":"

Renovate supports upgrading dependencies in Kotlin Script files. Read the Kotlin Script docs to learn more. For example:

#!/usr/bin/env kotlin\n@file:Repository(\"https://jitpack.io\")\n@file:DependsOn(\"com.github.krzema12:github-actions-kotlin-dsl:main-SNAPSHOT\")\n@file:DependsOn(\"org.eclipse.jgit:org.eclipse.jgit:4.6.0.201612231935-r\")\n@file:DependsOn(\"org.jetbrains.lets-plot:lets-plot-kotlin-jvm:3.0.2\")\n\nprintln(\"Hello world!\")\n\n// ...\n

By default, Renovate only scans files with the .main.kts extension and not .kts. This way Renovate avoids ambiguity with Gradle config files that use the .gradle.kts extension.

If you want to manage other Kotlin Script files, you may use the managerFilePatterns config option to let Renovate update these files:

{\n  \"kotlin-script\": {\n    \"managerFilePatterns\": [\"/^.*\\\\.kts$/\"]\n  }\n}\n
"},{"location":"modules/manager/kubernetes/","title":"Automated Dependency Updates for Kubernetes","text":"

Categories: kubernetes

Renovate supports updating Kubernetes dependencies.

"},{"location":"modules/manager/kubernetes/#file-matching","title":"File Matching","text":"

Because file names for kubernetes cannot be easily determined automatically, Renovate will not attempt to match any kubernetes files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/kubernetes/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, kubernetes-api.

"},{"location":"modules/manager/kubernetes/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/kubernetes/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/kubernetes/#additional-information","title":"Additional Information","text":"

The kubernetes manager has no managerFilePatterns default patterns, so it won't match any files until you configure it with a pattern. This is because there is no commonly accepted file/directory naming convention for Kubernetes YAML files and we don't want to check every single *.yaml file in repositories just in case any of them have Kubernetes definitions.

If most .yaml files in your repository are Kubernetes ones, then you could add this to your config:

{\n  \"kubernetes\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\"]\n  }\n}\n

If instead you have them all inside a k8s/ directory, you would add this:

{\n  \"kubernetes\": {\n    \"managerFilePatterns\": [\"/k8s/.+\\\\.yaml$/\"]\n  }\n}\n

Or if it's only a single file then something like this:

{\n  \"kubernetes\": {\n    \"managerFilePatterns\": [\"/^config/k8s\\\\.yaml$/\"]\n  }\n}\n

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/kustomize/","title":"Automated Dependency Updates for Kustomize","text":"

Categories: kubernetes

Renovate supports updating Kustomize dependencies.

"},{"location":"modules/manager/kustomize/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)kustomization\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/kustomize/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, git-tags, github-tags, helm.

"},{"location":"modules/manager/kustomize/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description Kustomization Kustomization resource referencing remote bases or images Component Kustomize Component resource referencing remote bases or images HelmChart Helm chart embedded in a kustomization file via helmCharts"},{"location":"modules/manager/kustomize/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)kustomization\\\\.ya?ml$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/kustomize/#additional-information","title":"Additional Information","text":"

Renovate can manage these parts of the kustomization.yaml file:

  1. remote resources
  2. image tags
  3. components
  4. helm charts
  5. remote bases (deprecated since Kustomize v2.1.0)
"},{"location":"modules/manager/kustomize/#how-it-works","title":"How It Works","text":"
  1. Renovate searches in each repository for any kustomization.yaml files
  2. Dependencies are extracted from remote bases, image tags and Helm charts
  3. Renovate resolves the dependency's source repository and checks if there are SemVer tags
  4. If Renovate finds an update, then it updates the kustomization.yaml file

This manager uses three depTypes to allow fine-grained control of which dependencies are upgraded:

"},{"location":"modules/manager/kustomize/#helm-charts-inflation","title":"Helm charts inflation","text":"

Renovate will inflate helm charts referenced in a kustomization if any of the following is true:

  1. The version Renovate is upgrading from was inflated, OR
  2. The kustomizeInflateHelmCharts option in postUpdateOptions is enabled

To inflate charts from a private Helm repository, configure its credentials in a hostRules entry with hostType: helm and both a username and a password. Renovate passes them to helm pull. For charts from an OCI registry, Renovate logs in with helm registry login first, using the hostRules entry with hostType: docker for that registry.

{\n  \"hostRules\": [\n    {\n      \"hostType\": \"helm\",\n      \"matchHost\": \"https://charts.example.com\",\n      \"username\": \"user\",\n      \"password\": \"secret\"\n    }\n  ]\n}\n

Note: To prevent Renovate from updating dependencies in the expanded charts, you'll need to manually exclude the folders from Helm managers. For example:

{\n  \"packageRules\": [\n    {\n      \"matchFileNames\": [\"**/charts/**\"],\n      \"matchManagers\": [\"helmv3\", \"helm-values\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/kustomize/#limitations","title":"Limitations","text":" 
- name: image/name\n  newTag: v0.0.1\n# or\n- newTag: v0.0.1\n  name: image/name\n
- name: image/name\n  newTag: v0.0.1@sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n# without a version, digests are tracked as :latest\n- name: image/name\n  digest: sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n
- name: image/name\n  newName: custom-image/name:v0.0.1\n- name: image/name\n  newName: custom-image/name:v0.0.1@sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n- name: image/name\n  newName: custom-image/name@sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n- name: image/name\n  newName: custom-image/name\n  newTag: v0.0.1@sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n- name: image/name\n  newName: custom-image/name\n  digest: sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n
# bad: skipped because newTag: is ignored when digest: is set\n- name: image/name\n  newTag: v0.0.1\n  digest: sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n# good:\n- name: image/name\n  newTag: v0.0.1@sha256:3eeba3e2caa30d2aba0fd78a34c1bbeebaa1b96c7aa3c95ec9bac44163c5ca4f\n
"},{"location":"modules/manager/leiningen/","title":"Automated Dependency Updates for Leiningen","text":"

Categories: java

Renovate supports updating Leiningen dependencies.

"},{"location":"modules/manager/leiningen/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)project\\.clj$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/leiningen/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: clojure.

"},{"location":"modules/manager/leiningen/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description dependencies Listed under :dependencies managed-dependencies Listed under :managed-dependencies plugins Listed under :plugins pom-plugins Listed under :pom-plugins parent-project Listed under :parent-project (via lein-parent :coords)"},{"location":"modules/manager/leiningen/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)project\\\\.clj$/\"\n  ],\n  \"versioning\": \"maven\"\n}\n
"},{"location":"modules/manager/leiningen/#additional-information","title":"Additional Information","text":"

Extracts Maven-type dependencies.

"},{"location":"modules/manager/maven/","title":"Automated Dependency Updates for Maven","text":"

Categories: java

Renovate supports updating Maven dependencies.

"},{"location":"modules/manager/maven/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/|\\.)pom\\.xml$/\n/(^|/)pom\\.template\\.xml$/\n/^(((\\.mvn)|(\\.m2))/)?settings\\.xml$/\n/(^|/)\\.mvn/extensions\\.xml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/maven/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, maven.

"},{"location":"modules/manager/maven/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description compile Dependency with compile scope (default); available on all classpaths provided Dependency with provided scope; expected to be supplied by the JDK or container at runtime runtime Dependency with runtime scope; required at runtime but not for compilation test Dependency with test scope; only used for test compilation and execution system Dependency with system scope; similar to provided but the JAR is specified explicitly import Dependency with import scope; used to import dependency management from another POM (BOM) optional Optional dependency (declared with <optional>true</optional>) build A build plugin or extension (<plugin> or <extension> element) parent The parent POM (<parent> element) parent-root A parent POM that is itself a root POM or has an external parent; promoted from parent during multi-module resolution"},{"location":"modules/manager/maven/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/|\\\\.)pom\\\\.xml$/\",\n    \"/(^|/)pom\\\\.template\\\\.xml$/\",\n    \"/^(((\\\\.mvn)|(\\\\.m2))/)?settings\\\\.xml$/\",\n    \"/(^|/)\\\\.mvn/extensions\\\\.xml$/\"\n  ]\n}\n
"},{"location":"modules/manager/maven/#additional-information","title":"Additional Information","text":"

The maven manager focuses on extracting dependencies from pom.xml. It uses the official Maven versioning scheme. XML files must declare official namespaces to be parsed correctly (see Maven documentation on pom.xml, extensions.xml).

It also supports Image Customizations of spring-boot's OCI packaging. Usage of registryAliases is possible only for container image references.

"},{"location":"modules/manager/maven/#limitations","title":"Limitations","text":"

Currently maven properties are not supported for buildpack related dependencies.

"},{"location":"modules/manager/maven-wrapper/","title":"Automated Dependency Updates for Maven Wrapper","text":"

Categories: java

Renovate supports updating Maven Wrapper dependencies.

"},{"location":"modules/manager/maven-wrapper/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|\\/).mvn/wrapper/maven-wrapper.properties$/\n/(^|\\/)mvnw(.cmd)?$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/maven-wrapper/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/maven-wrapper/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/maven-wrapper/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|\\\\/).mvn/wrapper/maven-wrapper.properties$/\",\n    \"/(^|\\\\/)mvnw(.cmd)?$/\"\n  ]\n}\n
"},{"location":"modules/manager/maven-wrapper/#additional-information","title":"Additional Information","text":"

Configuration for Maven Wrapper updates. Changes here affect how Renovate updates the version of Maven in the wrapper, not how it uses the wrapper.

"},{"location":"modules/manager/maven-wrapper/#private-registry-authentication","title":"Private registry authentication","text":"

If the Maven wrapper downloads artifacts from a private registry, Renovate can pass credentials to the wrapper command automatically.

When Renovate finds a custom repository URL in the wrapper configuration, it looks for matching hostRules with hostType: \"maven\" and passes the credentials to the wrapper command.

Both username and password must be set in the host rule for authentication to apply.

Example hostRules configuration:

{\n  \"hostRules\": [\n    {\n      \"matchHost\": \"private-registry.example.com\",\n      \"hostType\": \"maven\",\n      \"username\": \"renovate-bot\",\n      \"password\": \"{{ secrets.MAVEN_PASSWORD }}\"\n    }\n  ]\n}\n

To learn more about how to securely provide credentials, see Private package support.

"},{"location":"modules/manager/meteor/","title":"Automated Dependency Updates for Meteor","text":"

Categories: js

Renovate supports updating Meteor dependencies.

"},{"location":"modules/manager/meteor/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)package\\.js$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/meteor/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: npm.

"},{"location":"modules/manager/meteor/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/meteor/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)package\\\\.js$/\"\n  ]\n}\n
"},{"location":"modules/manager/meteor/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/mint/","title":"Automated Dependency Updates for Mint","text":"

Categories: swift

Renovate supports updating Mint dependencies.

"},{"location":"modules/manager/mint/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Mintfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/mint/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags.

"},{"location":"modules/manager/mint/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/mint/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Mintfile$/\"\n  ]\n}\n
"},{"location":"modules/manager/mint/#additional-information","title":"Additional Information","text":"

Renovate supports updating Mintfiles.

Go to the yonaskolb/Mint repository on GitHub to learn more about the Mint package manager.

You must put the library version in the Mintfile:

// Good:\nSwiftGen/SwiftGen@6.6.1\nrealm/SwiftLint @ 0.48.0\n\n// Bad:\nyonaskolb/xcodegen\n
"},{"location":"modules/manager/mise/","title":"Automated Dependency Updates for mise-en-place","text":"

Categories: no-category

Renovate supports updating mise-en-place dependencies.

"},{"location":"modules/manager/mise/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

**/{,.}mise{,.*}.toml\n**/{,.}mise/config{,.*}.toml\n**/.config/mise{,.*}.toml\n**/.config/mise/{mise,config}{,.*}.toml\n**/.config/mise/conf.d/*.toml\n**/.rtx{,.*}.toml\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/mise/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, conda, crate, dart-version, docker, dotnet-version, flutter-version, git-refs, git-tags, github-digest, github-releases, github-tags, gitlab-releases, gitlab-tags, go, hexpm-bob, java-version, node-version, npm, nuget, pypi, ruby-version, rubygems, rust-version.

"},{"location":"modules/manager/mise/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description tools A tool defined under the top-level [tools] table include A remote configuration file (git:: or oci::) referenced in the top-level include array

Tools defined under tasks.<name>.tools produce dynamic depType values in the form task-<name>-tools, and remote git:: task files defined in tasks.<name>.file produce task-<name>-file, where <name> is the task name (e.g. task-lint-tools, task-build-file).

"},{"location":"modules/manager/mise/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/{,.}mise{,.*}.toml\",\n    \"**/{,.}mise/config{,.*}.toml\",\n    \"**/.config/mise{,.*}.toml\",\n    \"**/.config/mise/{mise,config}{,.*}.toml\",\n    \"**/.config/mise/conf.d/*.toml\",\n    \"**/.rtx{,.*}.toml\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/mise/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/mise/#additional-information","title":"Additional Information","text":"

Renovate can update mise configuration files.

"},{"location":"modules/manager/mise/#supported-configuration-files","title":"Supported configuration files","text":"

Renovate supports all standard mise configuration file patterns:

"},{"location":"modules/manager/mise/#supported-tool-locations","title":"Supported tool locations","text":"

Renovate supports top level tools and tasks.*.tools keys.

"},{"location":"modules/manager/mise/#remote-task-files","title":"Remote task files","text":"

Renovate supports remote git task files in tasks.<name>.file, using the same git:: forms as for remote include entries. The path may point to any file, not only to TOML files. ref handling, datasources and comment hints work like for remote include entries, and the dependencies have the depType task-<name>-file. Local paths and plain http(s):// URLs without the git:: prefix have no version and are ignored.

[tasks.build]\nfile = \"git::https://github.com/org/tasks.git//scripts/build.sh?ref=v1.0.0\"\n\n[tasks.lint]\nfile = \"git::ssh://git@gitlab.com/org/tasks.git//lint.sh?ref=0123456789abcdef0123456789abcdef01234567\" # v1.0.0\n
"},{"location":"modules/manager/mise/#remote-include-support","title":"Remote include support","text":"

Renovate supports the remote forms of the top level include key:

A tag ref is updated to the newest tag:

include = [\n  \"git::https://github.com/org/cfg.git//mise.toml?ref=v0.5.0\",\n  \"oci::ghcr.io/org/base:1.0\",\n]\n
"},{"location":"modules/manager/mise/#pinning-to-a-commit-sha","title":"Pinning to a commit sha","text":"

Optionally, a ref can be a full or short commit sha, if it has a trailing # <version> or # <branch> comment. Renovate updates the sha and the comment:

include = [\n  # tracks tags: the sha and the comment are bumped to the new tag\n  \"git::https://github.com/org/cfg.git//mise.toml?ref=0123456789abcdef0123456789abcdef01234567\", # v0.5.0\n  # tracks a branch: the sha is bumped to the head of the branch\n  \"git::https://gitlab.com/org/cfg.git//mise.toml?ref=0123456789abcdef0123456789abcdef01234567\", # main\n]\n

Renovate does not fetch the included files, so the tools they define are not updated. include entries are not locked by mise.lock.

"},{"location":"modules/manager/mise/#lock-file-support","title":"Lock file support","text":"

Renovate supports mise lock files (mise.lock). When a lock file is present:

When mise lock pins a tool's dependencies in a native dependency sidecar (for example .mise/locks/npm-prettier/3.3.3/aube-lock.yaml), Renovate commits the sidecar changes together with the lock file, including new sidecar directories and the removal of ones that mise lock deleted.

Renovate recognizes environment-specific lock files:

For more information about mise lock files, see the mise lock file documentation.

"},{"location":"modules/manager/mise/#trust-model-for-lock-file-updates","title":"Trust model for lock file updates","text":"

Running mise lock can execute repository-defined behavior, so Renovate treats mise lockfile refreshes as an unsafe execution.

Self-hosted administrators must explicitly allow this path by including mise in the global allowedUnsafeExecutions setting.

Because mise lock can execute repository-defined scripts, Renovate treats lockfile refreshes as an unsafe execution and attempts to run mise in safe mode.

If mise does not support safe mode or version detection fails, Renovate blocks all mise operations.

"},{"location":"modules/manager/mise/#allowing-unsafe-executions","title":"Allowing Unsafe Executions","text":"

Self-hosted administrators can permit these operations by adding \"mise\" to the global allowedUnsafeExecutions configuration.

Once allowed, Renovate runs mise trust before mise lock when a mise.lock file is present. This exposes the trust step in execution logs and defers trust rules to mise.

In particular:

"},{"location":"modules/manager/mise/#renovate-only-updates-primary-versions","title":"Renovate only updates primary versions","text":"

Renovate's mise manager is designed to automatically update the first (primary) version listed for each tool in the mise.toml file.

Secondary or fallback versions require manual updates.

"},{"location":"modules/manager/mise/#example","title":"Example","text":"

Given a mise.toml entry like:

[tools]\nerlang = [\"23.3\", \"22.0\"]\n

Renovate will update \"23.3\" (the primary version) but will not touch \"22.0\" (the fallback version).

The same applies when the array items are inline tables:

[tools]\nrust = [\n  { version = \"1.98.1\", components = \"clippy,rustfmt\" },\n  { version = \"nightly-2026-07-12\", profile = \"minimal\" },\n]\n

Renovate will update \"1.98.1\" and read backend options such as version_prefix or tag_regex from that first item only.

"},{"location":"modules/manager/mise/#why-can-renovate-only-update-primary-versions","title":"Why can Renovate only update primary versions?","text":"

To maintain consistency and reliability, Renovate opts to only manage the first listed version.

This follows the same workflow that Renovate's asdf manager uses.

"},{"location":"modules/manager/mise/#short-names-support","title":"Short names support","text":"

Renovate uses the mise registry to resolve tool short names to their appropriate datasource.

Where possible, Renovate will automagically support tools from the mise registry (via mise registry --json).

This means that any tool in the mise registry that has a supported backend (e.g. aqua, github, cargo) should be automatically supported by Renovate.

"},{"location":"modules/manager/mise/#adding-new-tool-support","title":"Adding new tool support","text":"

If a tool you need is not yet in the mise registry, add it upstream to mise. Once Renovate syncs its registry data, the tool will be supported automatically, as long as it is in a backend that Renovate supports.

For tools that need a custom datasource mapping (e.g. core tools like node, python), you can create a PR to extend Renovate's mise manager directly.

If you want to add support for other tools' short names to mise, you can create a PR to extend Renovate's asdf manager, which indirectly helps Renovate's mise manager as well. Even if the tool does not use the asdf backend in the registry, the short names added to the asdf manager will still be used in the mise manager.

This may no longer be necessary now we automagically add support via the tools that the mise registry advertises.

"},{"location":"modules/manager/mise/#backends-support","title":"Backends support","text":"

Renovate's mise manager supports the following backends:

"},{"location":"modules/manager/mise/#limitations","title":"Limitations","text":"

Renovate's mise manager does not support the following tool syntax:

"},{"location":"modules/manager/mise/#supported-default-registry-tool-short-names","title":"Supported default registry tool short names","text":"

Note

Renovate syncs the supported registry data with mise, and is periodically updated (currently using 2026.10.25 linux-x64 (2026-10-31).Over time, this support may change and short tool names may be added / removed as per upstream mise.

Renovate's mise manager can version the following tool short names. Out of 1100 known tools: 1078 supported, 4 possibly supported, 18 unsupported.

Name Source Supported 1password mise \u2705 1password-cli mise \u2705 7z mise \u2705 7zip mise \u2705 aapt2 mise \ud83e\udd14 Possibly unsupported due to backend(s): [\"vfox\"] acli mise \u2705 act asdf \u2705 action-validator mise \u2705 actionlint mise \u2705 actionlint asdf \u2705 adr-tools asdf \u2705 ag mise \u2705 age mise \u2705 age-plugin-yubikey mise \u2705 agebox mise \u2705 agent-browser mise \u2705 agy mise \u2705 aichat mise \u2705 air mise \u2705 aks-engine mise \u2705 allure mise \u2705 allurectl mise \u2705 alp mise \u2705 amass mise \u2705 amazon-ecr-credential-helper mise \u2705 amazon-ecs-cli mise \u2705 amp mise \u2705 amplify mise \u2705 android-cli mise \u274c android-sdk mise \ud83e\udd14 Possibly unsupported due to backend(s): [\"vfox\"] ansible mise \u2705 ansible-base mise \u2705 ansible-core mise \u2705 ant mise \ud83e\udd14 Possibly unsupported due to backend(s): [\"vfox\"] antigravity-cli mise \u2705 apko mise \u2705 apm asdf \u2705 apollo-ios mise \u2705 apollo-ios-cli mise \u2705 apollo-router mise \u2705 apollo-rover mise \u2705 aqua mise \u2705 arduino mise \u2705 arduino-cli mise \u2705 argc mise \u2705 argo mise \u2705 argo-rollouts mise \u2705 argocd asdf \u2705 asciidoctorj mise \u2705 asdf-plugin-manager asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) aspire mise \u2705 assh mise \u2705 ast-grep mise \u2705 astro mise \u2705 atlas mise \u2705 atlas-community mise \u2705 atmos asdf \u2705 atuin mise \u2705 aube mise \u2705 auto-doc mise \u2705 aws mise \u2705 aws-amplify mise \u2705 aws-cdk mise \u2705 aws-cli mise \u2705 aws-copilot mise \u2705 aws-iam-authenticator mise \u2705 aws-nuke mise \u2705 aws-sam mise \u2705 aws-sam-cli mise \u2705 aws-sso mise \u2705 aws-vault mise \u2705 awscli asdf \u2705 awscli-local mise \u2705 awsebcli mise \u2705 awsls mise \u2705 awsrm mise \u2705 awsweeper mise \u2705 azd mise \u2705 azure mise \u2705 azure-cli asdf \u2705 azure-functions-core-tools mise \u2705 azure-kubelogin mise \u2705 babashka mise \u2705 balena mise \u2705 balena-cli mise \u2705 basecamp mise \u2705 bashbot mise \u2705 bashly mise \u2705 bat mise \u2705 bat-extras mise \u2705 bats mise \u2705 bazel mise \u2705 bazel-watcher mise \u2705 bazelisk mise \u2705 benthos mise \u2705 betterleaks mise \u2705 bfs mise \u2705 bibtex-tidy mise \u2705 binnacle mise \u2705 biome mise \u2705 bitwarden mise \u2705 bitwarden-secrets-manager mise \u2705 black mise \u2705 blaze mise \u2705 blender mise \u2705 bob mise \u2705 boilerplate mise \u2705 bombardier mise \u2705 borg mise \u2705 bosh mise \u2705 bottom mise \u2705 boundary mise \u2705 bpkg mise \u2705 broot mise \u2705 btop mise \u2705 buck2 mise \u2705 buf mise \u2705 buildifier mise \u2705 buildpack mise \u2705 buildpacks mise \u2705 bun mise \u2705 bun asdf \u2705 bundler mise \u2705 cabal mise \u2705 caddy mise \u2705 calendarsync mise \u2705 calicoctl mise \u2705 carapace mise \u2705 cargo-binstall mise \u2705 cargo-deny mise \u2705 cargo-dist mise \u2705 cargo-insta mise \u2705 cargo-make asdf \u2705 cargo-msrv mise \u2705 cargo-release mise \u2705 carthage mise \u2705 ccache mise \u2705 cdk mise \u2705 certstrap mise \u2705 cf mise \u2705 cfn-lint mise \u2705 cfssl mise \u2705 cfssljson mise \u2705 chamber mise \u2705 changie mise \u2705 cheat mise \u2705 checkmake mise \u2705 checkov asdf \u2705 checkstyle mise \u2705 chezmoi mise \u2705 chezscheme mise \u2705 chicken mise \ud83e\udd14 Possibly unsupported due to backend(s): [\"vfox\"] chisel mise \u2705 choose mise \u2705 chromedriver mise \u2705 cidr-merger mise \u2705 cidrchk mise \u2705 cilium-cli mise \u2705 cilium-hubble mise \u2705 circleci mise \u2705 circleci-cli mise \u2705 clang mise \u2705 clang-format mise \u2705 claude mise \u2705 claude-code mise \u2705 claude-powerline mise \u2705 claude-squad mise \u2705 cliamp mise \u2705 clickhouse mise \u2705 clipboard mise \u2705 clj-kondo mise \u2705 cljstyle mise \u2705 cloc mise \u2705 clojure asdf \u2705 cloud-sql-proxy mise \u2705 cloudflare-cf mise \u2705 cloudflared mise \u2705 clusterawsadm mise \u2705 clusterctl asdf \u2705 cmake mise \u2705 cmctl mise \u2705 cmdx mise \u2705 cockroach mise \u2705 cocoapods mise \u2705 cocogitto mise \u2705 code mise \u2705 code-review-graph mise \u2705 codebuff mise \u2705 codefresh mise \u2705 codegraph mise \u2705 codeql mise \u2705 coder mise \u2705 codex mise \u2705 codon mise \u2705 colima mise \u2705 committed mise \u2705 communique mise \u2705 conan mise \u2705 conform mise \u2705 conftest asdf \u2705 consul mise \u2705 container mise \u2705 container-structure-test asdf \u2705 container-use mise \u2705 cookiecutter asdf \u2705 copier mise \u2705 copilot mise \u2705 copilot-cli mise \u2705 coredns mise \u2705 coreutils mise \u2705 cosign asdf \u2705 coursier mise \u2705 cowsay mise \u2705 cpz mise \u2705 crane mise \u2705 crictl mise \u2705 croc mise \u2705 crossplane mise \u2705 crossplane-cli mise \u2705 crush mise \u2705 crystal asdf \u2705 cspell mise \u2705 ctlptl mise \u2705 ctop mise \u2705 cue mise \u2705 curlie mise \u2705 cursor-agent mise \u274c cursor-cli mise \u274c cyclonedx mise \u2705 d2 mise \u2705 dagger mise \u2705 dagu mise \u2705 danger-js mise \u2705 danger-swift mise \u2705 dapr mise \u2705 dart asdf \u2705 dasel mise \u2705 databricks-cli mise \u2705 daytona mise \u2705 dbmate mise \u2705 dbt-fusion mise \u2705 deck mise \u2705 dekit mise \u2705 delta mise \u2705 deno mise \u2705 deno asdf \u2705 dependency-check mise \u2705 depot mise \u2705 desk mise \u2705 detekt asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) devcontainer-cli mise \u2705 devspace mise \u2705 dhall mise \u2705 diffoci mise \u2705 difftastic mise \u2705 direnv asdf \u2705 dive mise \u2705 docker-cli mise \u2705 docker-compose mise \u2705 docker-slim mise \u2705 dockle mise \u2705 doctl mise \u2705 docuum mise \u2705 doggo mise \u2705 doppler mise \u2705 dotenv-linter mise \u2705 dotenvx mise \u2705 dotnet mise \u2705 dotnet-core asdf \u2705 dotslash mise \u2705 dprint asdf \u2705 driftctl mise \u2705 drone mise \u2705 dt mise \u2705 dua mise \u2705 duckdb mise \u2705 duf mise \u2705 dust mise \u2705 dvc mise \u2705 dyff mise \u2705 dynatrace-monaco mise \u2705 e1s mise \u2705 earthly mise \u2705 ecs-cli mise \u2705 ecspresso asdf \u2705 edit mise \u2705 editorconfig-checker asdf \u2705 ejson mise \u2705 eksctl mise \u2705 elasticsearch mise \u2705 elixir mise \u2705 elixir asdf \u2705 elixir-ls mise \u2705 elm asdf \u2705 emsdk mise \u2705 engram mise \u2705 entire mise \u2705 entireio-cli mise \u2705 envsubst mise \u2705 erlang mise \u2705 erlang asdf \u2705 esc mise \u2705 etcd mise \u2705 evans mise \u2705 exiftool mise \u2705 expert mise \u2705 eza mise \u2705 fastfetch mise \u2705 fd mise \u2705 ffmpeg mise \u2705 figma-export mise \u2705 fillin mise \u2705 firebase mise \u2705 fission mise \u2705 flamingo mise \u2705 flatc mise \u2705 flutter asdf \u2705 fluttergen mise \u2705 flux-operator mise \u2705 flux-operator-mcp mise \u2705 flux2 asdf \u2705 fly mise \u2705 flyctl mise \u2705 flyway mise \u2705 fnox mise \u2705 foundry mise \u2705 func-e mise \u2705 furyctl mise \u2705 fx mise \u2705 fzf mise \u2705 gallery-dl mise \u2705 gam mise \u2705 gator mise \u2705 gauche asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) gcc-arm-none-eabi mise \u2705 gcloud mise \u2705 gdal mise \u2705 gdu mise \u2705 gemini mise \u2705 gemini-cli mise \u2705 gentle-ai mise \u2705 getenvoy mise \u2705 ggshield mise \u2705 gh mise \u2705 ghalint mise \u2705 ghc mise \u2705 ghcup mise \u2705 ghorg mise \u2705 ghq mise \u2705 ghtkn mise \u2705 ghui mise \u2705 ginkgo asdf \u2705 git-chglog mise \u2705 git-cliff mise \u2705 git-filter-repo mise \u2705 git-lfs mise \u2705 git-town mise \u2705 gitconfig mise \u2705 github-cli asdf \u2705 github-markdown-toc mise \u2705 gitleaks asdf \u2705 gitsign mise \u2705 gitu mise \u2705 gitui mise \u2705 gitversion mise \u2705 glab mise \u2705 gleam asdf \u2705 glooctl mise \u2705 glow mise \u2705 go mise \u2705 go-containerregistry mise \u2705 go-getter mise \u2705 go-jira mise \u2705 go-jsonnet mise \u2705 go-junit-report mise \u2705 go-swagger mise \u2705 goconvey mise \u2705 gocryptfs mise \u2705 godot mise \u2705 gofumpt mise \u2705 gohugo asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) gojq mise \u2705 gokey mise \u2705 golang asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) golangci-lint asdf \u2705 golangci-lint-langserver mise \u2705 golines mise \u2705 gomigrate mise \u2705 gomplate asdf \u2705 google-java-format mise \u2705 goose-agent mise \u2705 gopass mise \u2705 goreleaser mise \u2705 goss mise \u2705 gotestsum asdf \u2705 gping mise \u2705 graalvm mise \u2705 gradle mise \u2705 grafana-kubernetes-plugin mise \u2705 granted mise \u2705 graphite mise \u2705 grex mise \u2705 grok mise \u2705 gron mise \u2705 groovy mise \u2705 grpc-health-probe mise \u2705 grpcurl mise \u2705 grype mise \u2705 gsudo mise \u2705 gum mise \u2705 gup mise \u2705 gwvault mise \u2705 hadolint asdf \u2705 harper-cli mise \u2705 harper-ls mise \u2705 has mise \u2705 haskell asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) hasura-cli mise \u2705 hatch mise \u2705 haxe mise \u2705 hcl2json mise \u2705 hcloud mise \u2705 helix mise \u2705 helm asdf \u2705 helm-cr mise \u2705 helm-ct mise \u2705 helm-diff mise \u2705 helm-docs asdf \u2705 helm-ls mise \u2705 helmfile asdf \u2705 helmsman mise \u2705 helmwave mise \u2705 herdr mise \u2705 heroku mise \u2705 heroku-cli mise \u2705 hexyl mise \u2705 hey-cli mise \u2705 himalaya mise \u2705 hishtory mise \u2705 hivemind mise \u2705 hk mise \u2705 hledger mise \u2705 hledger-flow mise \u2705 hlint mise \u2705 hostctl mise \u2705 htmlq mise \u2705 httpie-go mise \u2705 hub mise \u2705 hugo asdf \u2705 hugo-extended mise \u2705 hugo-extended-withdeploy mise \u2705 hunk mise \u2705 hunkdiff mise \u2705 hurl mise \u2705 hwatch mise \u2705 hygen mise \u2705 hyperfine mise \u2705 iam-policy-json-to-terraform mise \u2705 iamlive mise \u2705 ibmcloud mise \u2705 idris asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) imagemagick mise \u2705 imessage-exporter mise \u2705 imgpkg mise \u2705 infisical mise \u2705 infracost mise \u2705 istioctl asdf \u2705 jactionlint mise \u2705 janet mise \u2705 jaq mise \u2705 java mise \u2705 java asdf \u2705 jb mise \u2705 jbang mise \u2705 jc mise \u2705 jd mise \u2705 jfrog-cli mise \u2705 jib mise \u2705 jiq mise \u2705 jj mise \u2705 jjui mise \u2705 jless mise \u2705 jmespath mise \u2705 jnv mise \u2705 jouet mise \u2705 jq mise \u2705 jqp mise \u2705 jreleaser mise \u2705 json5 mise \u2705 jsonnet-bundler mise \u2705 jsonschema mise \u2705 jujutsu mise \u2705 jujutsu-ui mise \u2705 jules mise \u2705 julia asdf \u2705 just asdf \u2705 jwt mise \u2705 jwtui mise \u2705 jx mise \u2705 k0sctl mise \u2705 k2tf mise \u2705 k3d mise \u2705 k3kcli mise \u2705 k3s asdf \u2705 k3sup mise \u2705 k6 mise \u2705 k9s mise \u2705 kafka mise \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) kafkactl mise \u2705 kapp mise \u2705 kbld mise \u2705 kcl mise \u2705 kconf mise \u2705 killport mise \u2705 kind asdf \u2705 kingfisher mise \u2705 kiota mise \u2705 kn mise \u2705 ko mise \u2705 koka mise \u2705 kompose mise \u2705 kopia mise \u2705 kops mise \u2705 kotlin asdf \u2705 kpt mise \u2705 krew mise \u2705 kscript mise \u2705 ksops mise \u2705 ktlint asdf \u2705 kube-capacity mise \u2705 kube-controller-tools mise \u2705 kube-linter mise \u2705 kube-score mise \u2705 kubebuilder asdf \u2705 kubecm mise \u2705 kubecolor mise \u2705 kubeconform mise \u2705 kubectl asdf \u2705 kubectl-bindrole mise \u2705 kubectl-convert mise \u2705 kubectl-kots mise \u2705 kubectl-kuttl mise \u2705 kubectl-rolesum mise \u2705 kubectx mise \u2705 kubelogin mise \u2705 kubens mise \u2705 kubent mise \u2705 kubeone mise \u2705 kubergrunt mise \u2705 kubeseal mise \u2705 kubesec mise \u2705 kubeshark mise \u2705 kubespy mise \u2705 kubeswitch mise \u2705 kubetail asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) kubeval mise \u2705 kubevela mise \u2705 kubie mise \u2705 kustomize asdf \u2705 kuttl mise \u2705 kwokctl mise \u2705 kyverno mise \u2705 lazydocker mise \u2705 lazygit mise \u2705 lazyjournal mise \u2705 lazyssh mise \u2705 ldc mise \u2705 lefthook mise \u2705 leiningen mise \u2705 libsql-server mise \u2705 license-plist mise \u2705 lima mise \u2705 linkerd mise \u2705 liquibase mise \u2705 lisette mise \u2705 litestream mise \u2705 llama.cpp mise \u2705 llmfit mise \u2705 lnav mise \u2705 localstack mise \u2705 localstack asdf \u2705 loki-logcli mise \u2705 longbridge-terminal mise \u2705 lore mise \u2705 ls-lint mise \u2705 lsd mise \u2705 lstk mise \u2705 lua asdf \u2705 lua-language-server mise \u2705 luajit mise \u2705 luau mise \u2705 lychee mise \u2705 maestro asdf \u2705 mage mise \u2705 magika mise \u2705 mago mise \u2705 mailpit mise \u2705 make mise \u2705 mani mise \u2705 mark mise \u2705 markdownlint-cli2 asdf \u2705 marksman mise \u2705 marp-cli mise \u2705 martin mise \u2705 mas mise \u2705 mask mise \u2705 maturin mise \u2705 maven asdf \u2705 mbx mise \u2705 mc mise \u2705 mdbook mise \u2705 mdbook-linkcheck mise \u2705 melange mise \u2705 mermaid-ascii mise \u2705 meson mise \u2705 micro mise \u2705 micromamba mise \u2705 micronaut mise \u2705 microsandbox mise \u2705 miller mise \u2705 mimirtool asdf \u2705 minify mise \u2705 minikube asdf \u2705 minio mise \u2705 miniserve mise \u2705 minishift mise \u2705 minisign mise \u2705 mint mise \u2705 mirrord mise \u2705 mitmproxy mise \u2705 mkcert mise \u2705 mockery asdf \u2705 mockolo mise \u2705 mold mise \u2705 mole mise \u2705 mongodb mise \u2705 mongosh mise \u2705 mosh mise \u2705 mprocs mise \u2705 mpv mise \u2705 mr-boxington mise \u2705 mssqldef mise \u2705 muse mise \u274c mutagen mise \u2705 mvnd mise \u2705 mysql mise \u2705 mysql-client mise \u2705 mysqldef mise \u2705 nancy mise \u2705 native-sdk mise \u2705 nats-server mise \u2705 navi mise \u2705 neko mise \u2705 nelm mise \u2705 neo4j mise \u274c neonctl mise \u2705 neovim mise \u2705 nerdctl mise \u2705 newrelic mise \u2705 newrelic-cli mise \u2705 nfpm mise \u2705 ni mise \u2705 nim asdf \u2705 ninja mise \u2705 node mise \u2705 nodejs asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) nomad mise \u2705 nomad-pack mise \u2705 nono mise \u2705 notation mise \u2705 nova mise \u2705 npm mise \u2705 nsc mise \u2705 nu mise \u2705 nub mise \u2705 nubr mise \u2705 numbat mise \u2705 nushell mise \u2705 oapi-codegen mise \u2705 oauth2c mise \u2705 oc mise \u2705 ocaml asdf \u26a0\ufe0f No longer supported as of mise 2026.10.25 linux-x64 (2026-10-31) oci asdf \u2705 octosql mise \u2705 odin mise \u2705 odo mise \u2705 oh-my-pi mise \u2705 oh-my-posh mise \u2705 oha mise \u2705 okta-aws mise \u2705 okta-aws-cli mise \u2705 okteto mise \u2705 ollama mise \u2705 ols mise \u2705 om mise \u2705 omnictl mise \u2705 onefetch mise \u2705 onyx mise \u2705 op mise \u2705 opa asdf \u2705 opam mise \u2705 openbao mise \u2705 opencode mise \u2705 openfaas-cli mise \u2705 openfga mise \u2705 opengrep mise \u2705 opensearch-cli mise \u2705 openshift-install mise \u274c opentofu mise \u2705 opentofu asdf \u2705 operator-sdk mise \u2705 oras mise \u2705 ori mise \u2705 ormolu mise \u2705 orval mise \u2705 osv-scanner mise \u2705 overmind mise \u2705 oxfmt mise \u2705 oxipng mise \u2705 oxker mise \u2705 oxlint mise \u2705 pack mise \u2705 packer mise \u2705 packer asdf \u2705 packslip mise \u2705 pandoc mise \u2705 pastel mise \u2705 patat mise \u2705 pdm mise \u2705 peco mise \u2705 periphery mise \u2705 perl asdf \u2705 pgroll mise \u2705 php asdf \u2705 pi mise \u2705 pinact mise \u2705 pinniped mise \u2705 pint mise \u2705 pipectl mise \u2705 pipenv mise \u2705 pipx mise \u2705 pitchfork mise \u2705 pivnet mise \u2705 pixi mise \u2705 pkgx mise \u2705 pkl mise \u2705 playwright mise \u2705 please mise \u2705 pluto mise \u2705 pnpm mise \u2705 pnpm asdf \u2705 pocketbase mise \u2705 podlet mise \u2705 podman mise \u2705 podman-tui mise \u2705 poetry asdf \u2705 polaris mise \u2705 popeye mise \u2705 poppler mise \u2705 porter mise \u2705 portless mise \u2705 postgres mise \u2705 powerline-go mise \u2705 powerpipe mise \u2705 powershell mise \u2705 powershell-core mise \u2705 pre-commit asdf \u2705 prek mise \u2705 prettier mise \u2705 process-compose mise \u2705 promtool mise \u2705 protobuf mise \u2705 protoc mise \u2705 protoc asdf \u2705 protoc-gen-connect-go mise \u2705 protoc-gen-go mise \u2705 protoc-gen-go-grpc mise \u2705 protoc-gen-js mise \u2705 protoc-gen-validate mise \u2705 protolint mise \u2705 psqldef mise \u2705 pulumi asdf \u2705 purescript mise \u2705 purty mise \u2705 python mise \u2705 python asdf \u2705 qdns mise \u2705 qsv mise \u2705 quarkus mise \u2705 quicktype mise \u2705 qwen mise \u2705 qwen-code mise \u2705 racket mise \u2705 railway mise \u2705 rancher mise \u2705 rbac-lookup mise \u2705 rclone mise \u2705 rea mise \u2705 rebar asdf \u2705 reckoner mise \u2705 redis mise \u2705 redpanda-connect mise \u2705 reg mise \u2705 regal mise \u2705 regctl mise \u2705 regsync mise \u2705 release-plz mise \u2705 restate mise \u2705 restate-server mise \u2705 restatectl mise \u2705 restic mise \u2705 restish mise \u2705 resvg mise \u2705 reviewdog mise \u2705 revive mise \u2705 rg mise \u2705 richgo mise \u2705 ripgrep mise \u2705 ripgrep-all mise \u2705 ripsecrets mise \u2705 rmz mise \u2705 rpk mise \u2705 rtk mise \u2705 ruby mise \u2705 ruby asdf \u2705 ruff mise \u2705 rumdl mise \u2705 rush mise \u2705 rust mise \u2705 rust asdf \u2705 rust-analyzer mise \u2705 rustfs mise \u2705 rustic mise \u2705 rye mise \u2705 s5cmd mise \u2705 saml2aws mise \u2705 sampler mise \u2705 sbt asdf \u2705 scala asdf \u2705 scala-cli mise \u2705 scalafmt mise \u2705 scaleway mise \u2705 scaleway-cli mise \u2705 scalingo-cli mise \u2705 scarb mise \u2705 sccache mise \u2705 schemacrawler mise \u2705 scie-pants mise \u2705 scooter mise \u2705 scorecard mise \u2705 sd mise \u2705 semgrep mise \u2705 semver mise \u2705 sentinel mise \u2705 sentry mise \u2705 sentry-cli mise \u2705 serverless mise \u2705 setup-envtest mise \u2705 sheldon mise \u2705 shell2http mise \u2705 shellcheck mise \u2705 shellcheck asdf \u2705 shellharden mise \u2705 shellspec mise \u2705 sherif mise \u2705 shfmt asdf \u2705 signadot mise \u2705 sing-box mise \u2705 skaffold asdf \u2705 skate mise \u2705 skeema mise \u2705 skim mise \u2705 sloth mise \u2705 slsa-verifier mise \u2705 smithy mise \u2705 snyk mise \u2705 sofka mise \u2705 soft-serve mise \u2705 solidity mise \u2705 sonar-scanner-cli mise \u2705 sonarqube-cli mise \u2705 sonobuoy mise \u2705 sops mise \u2705 sops asdf \u2705 sopstool mise \u2705 sourcery mise \u2705 spacectl mise \u2705 spago mise \u2705 spark mise \u2705 specstory mise \u2705 spectral mise \u2705 spicedb mise \u2705 spin mise \u2705 spin-framework mise \u2705 spotify-downloader mise \u2705 spotify-player mise \u2705 spring-boot mise \u2705 spruce mise \u2705 sqlc mise \u2705 sqlcl mise \u2705 sqlite mise \u2705 sqlite3def mise \u2705 sshi mise \u2705 sshuttle mise \u2705 sst mise \u2705 stack mise \u2705 starknet-foundry mise \u2705 starknet-foundry-sncast mise \u2705 starship mise \u2705 staticcheck mise \u2705 steampipe asdf \u2705 step mise \u2705 stern mise \u2705 stripe mise \u2705 stripe-cli mise \u2705 stylua mise \u2705 sui mise \u2705 supabase mise \u2705 superfile mise \u2705 superhtml mise \u2705 svgo mise \u2705 svu mise \u2705 swag mise \u2705 swift mise \u2705 swift-package-list mise \u2705 swiftformat mise \u2705 swiftgen mise \u2705 swiftlint mise \u2705 syft mise \u2705 syncthing mise \u2705 systemctl-tui mise \u2705 tailpipe mise \u2705 tak mise \u2705 talhelper asdf \u2705 talos mise \u2705 talosctl asdf \u2705 tanka mise \u2705 tanzu mise \u2705 taplo mise \u2705 tart mise \u2705 task mise \u2705 tauri-cli mise \u2705 tbls mise \u2705 tctl mise \u2705 tealdeer mise \u2705 tekton mise \u2705 tekton-cli mise \u2705 teleport-community mise \u2705 teleport-ent mise \u2705 telepresence mise \u2705 television mise \u2705 teller mise \u2705 temporal mise \u2705 terraform asdf \u2705 terraform-docs asdf \u2705 terraform-ls mise \u2705 terraform-lsp mise \u2705 terraform-validator mise \u2705 terraformer asdf \u2705 terragrunt mise \u2705 terragrunt asdf \u2705 terramate asdf \u2705 terrascan mise \u2705 tf-summarize mise \u2705 tfc-agent mise \u2705 tfctl mise \u2705 tfenv mise \u2705 tflint asdf \u2705 tfmigrate mise \u2705 tfnotify mise \u2705 tfsec asdf \u2705 tfstate-lookup mise \u2705 tfswitch mise \u2705 tfupdate mise \u2705 ticker mise \u2705 tigerbeetle mise \u2705 tilt mise \u2705 timoni mise \u2705 tiny mise \u2705 tinygo mise \u2705 tinymist mise \u2705 tinytex mise \u2705 tirith mise \u2705 tlrc mise \u2705 tmux mise \u2705 tokei mise \u2705 tombi mise \u2705 tomcat mise \u2705 tonnage mise \u2705 topgrade mise \u2705 traefik mise \u2705 transifex mise \u2705 trdsql mise \u2705 tree-sitter mise \u2705 tridentctl mise \u2705 trivy asdf \u2705 trufflehog mise \u2705 trunk mise \u2705 trzsz-go mise \u2705 trzsz-ssh mise \u2705 tssh mise \u2705 tsuru mise \u2705 ttyd mise \u2705 tuios mise \u2705 tuist asdf \u2705 turbo mise \u2705 turso mise \u2705 tusd mise \u2705 twg mise \u274c ty mise \u2705 typos asdf \u2705 typst mise \u2705 typstyle mise \u2705 ubi mise \u2705 umoci mise \u2705 unison mise \u2705 upctl mise \u2705 updatecli mise \u2705 upt mise \u2705 upx mise \u2705 usage mise \u2705 usql mise \u2705 uv asdf \u2705 v mise \u2705 vacuum mise \u2705 vale mise \u2705 vals mise \u2705 vault asdf \u2705 vcluster mise \u2705 vector mise \u2705 velad mise \u2705 velero mise \u2705 vendir mise \u2705 venom mise \u2705 vercel mise \u2705 vespa-cli mise \u2705 vfox mise \u2705 vhs mise \u2705 victoria-metrics mise \u2705 viddy mise \u2705 vim mise \u2705 viteplus mise \u2705 vivid mise \u2705 vlang mise \u2705 vp mise \u2705 vscode-cli mise \u2705 vultr mise \u2705 vultr-cli mise \u2705 wacli mise \u2705 wait-for-gh-rate-limit mise \u2705 wash mise \u2705 wasm-tools mise \u2705 wasmer mise \u2705 wasmtime mise \u2705 watchexec mise \u2705 waypoint mise \u2705 weave-gitops mise \u2705 websocat mise \u2705 werf mise \u2705 witr mise \u2705 workerd mise \u2705 workmux mise \u2705 worktrunk mise \u2705 wrangler mise \u2705 wtfutil mise \u2705 xc mise \u2705 xcbeautify mise \u2705 xchtmlreport mise \u2705 xcodegen mise \u2705 xcodes mise \u2705 xcresultparser mise \u2705 xcsift mise \u2705 xh mise \u2705 xxh mise \u2705 yamlfmt asdf \u2705 yamllint asdf \u2705 yamlscript mise \u2705 yara-x mise \u2705 yarn mise \u2705 yazi mise \u2705 yj mise \u2705 yor mise \u2705 youtube-dl mise \u2705 yq asdf \u2705 yt-dlp mise \u2705 yt-dlp-nightly mise \u2705 ytt mise \u2705 zarf mise \u2705 zellij mise \u2705 zephyr mise \u2705 zig mise \u2705 zig asdf \u2705 zigmod mise \u2705 zizmor mise \u2705 zk mise \u2705 zls mise \u2705 zmx mise \u2705 zola mise \u2705 zoxide mise \u2705 zprint mise \u2705"},{"location":"modules/manager/mix/","title":"Automated Dependency Updates for Mix","text":"

Categories: elixir

Renovate supports updating Mix dependencies.

"},{"location":"modules/manager/mix/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)mix\\.exs$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/mix/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, hex.

"},{"location":"modules/manager/mix/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description prod A production dependency dev A development-only dependency (restricted via only:)"},{"location":"modules/manager/mix/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)mix\\\\.exs$/\"\n  ]\n}\n
"},{"location":"modules/manager/mix/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/mix/#additional-information","title":"Additional Information","text":"

The mix manager uses Renovate's implementation of Elixir SemVer to evaluate update ranges.

The mix package manager itself is used to keep the lock file up-to-date.

The following depTypes are currently supported by the mix manager :

"},{"location":"modules/manager/mix/#lockfilemaintenance","title":"lockFileMaintenance","text":"

We recommend you use lockFileMaintenance for the mix manager.

lockFileMaintenance=true periodically refreshes your mix.lock files, ensuring all indirect dependencies are updated to their latest allowed versions.

This option will be skipped in umbrella projects, as they share a single mix.lock file for all applications mix.exs files.

"},{"location":"modules/manager/mix/#default-rangestrategyauto-behavior","title":"Default rangeStrategy=auto behavior","text":"

Renovate's default rangeStrategy is \"auto\". Here's how \"auto\" works with the mix manager:

Version type New version Old range New range after update What Renovate does Complex range 1.7.2 < 1.7.0 or ~> 1.7.1 < 1.7.0 or ~> 1.7.2 Widen range to include the new version. Simple range 0.39.0 <= 0.38.0 <= 0.39.0 If update outside current range: widens range to include the new version. Exact version constraint 0.13.0 == 0.12.0 == 0.13.0 Replace old version with new version."},{"location":"modules/manager/mix/#recommended-rangestrategy-for-apps-and-libraries","title":"Recommended rangeStrategy for apps and libraries","text":"

For applications, we recommend using rangeStrategy=pin. This pins your dependencies to exact versions, which is generally considered best practice for apps.

For libraries, use rangeStrategy=widen with version ranges in your mix.exs. This allows for greater compatibility with other projects that may use your library as a dependency.

"},{"location":"modules/manager/nix/","title":"Automated Dependency Updates for Nix","text":"

Categories: no-category

Renovate supports updating Nix dependencies.

"},{"location":"modules/manager/nix/#enabling","title":"Enabling","text":"

Nix functionality is currently in beta testing, so you must opt-in to test it. To enable it, add a configuration like this to either your self-hosted config or your renovate.json:

{\n  \"nix\": {\n    \"enabled\": true\n  }\n}\n

If you find any bugs, please create a new discussion first. If you find that it works well, then let us know too.

"},{"location":"modules/manager/nix/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)flake\\.nix$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/nix/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-refs.

"},{"location":"modules/manager/nix/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/nix/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)flake\\\\.nix$/\"\n  ],\n  \"commitMessageTopic\": \"nix\",\n  \"commitMessageExtra\": \"to {{newValue}}\",\n  \"enabled\": false\n}\n
"},{"location":"modules/manager/nix/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/nix/#additional-information","title":"Additional Information","text":"

The nix manager supports:

For specifying packageRules it is important to know how depName and packageName are defined for nix updates:

"},{"location":"modules/manager/nodenv/","title":"Automated Dependency Updates for nodenv","text":"

Categories: js, node

Renovate supports updating nodenv dependencies.

"},{"location":"modules/manager/nodenv/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.node-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/nodenv/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: node-version.

"},{"location":"modules/manager/nodenv/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/nodenv/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.node-version$/\"\n  ],\n  \"versioning\": \"node\"\n}\n
"},{"location":"modules/manager/nodenv/#additional-information","title":"Additional Information","text":"

Simply keeps the .node-version file updated.

"},{"location":"modules/manager/npm/","title":"Automated Dependency Updates for npm","text":"

Categories: js

Renovate supports updating npm dependencies.

"},{"location":"modules/manager/npm/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)package\\.json$/\n/(^|/)pnpm-workspace\\.yaml$/\n/(^|/)\\.yarnrc\\.yml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/npm/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-tags, node-version, npm.

"},{"location":"modules/manager/npm/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType prettyDepType Description dependencies dependency Listed under dependencies devDependencies devDependency Listed under devDependencies optionalDependencies optionalDependency Listed under optionalDependencies peerDependencies peerDependency Listed under peerDependencies engines engine Listed under engines volta volta Listed under volta resolutions resolutions Listed under resolutions (Yarn) packageManager packageManager Listed under packageManager overrides overrides Listed under overrides pnpm pnpm Listed under the top-level pnpm field pnpm.overrides overrides Listed under pnpm.overrides devEngines.runtime devEngines.runtime Listed under devEngines.runtime devEngines.packageManager devEngines.packageManager Listed under devEngines.packageManager pnpm-workspace.overrides overrides Listed under overrides in a pnpm workspace YAML file

Additionally, catalog dependencies produce dynamic depType values: pnpm.catalog.<name> for pnpm catalogs and yarn.catalog.<name> for yarn catalogs.

"},{"location":"modules/manager/npm/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)package\\\\.json$/\",\n    \"/(^|/)pnpm-workspace\\\\.yaml$/\",\n    \"/(^|/)\\\\.yarnrc\\\\.yml$/\"\n  ],\n  \"digest\": {\n    \"prBodyDefinitions\": {\n      \"Change\": \"{{#if displayFrom}}`{{{displayFrom}}}` \u2192 {{else}}{{#if currentValue}}`{{{currentValue}}}` \u2192 {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}\"\n    }\n  },\n  \"prBodyDefinitions\": {\n    \"Change\": \"[{{#if displayFrom}}`{{{displayFrom}}}` \u2192 {{else}}{{#if currentValue}}`{{{currentValue}}}` \u2192 {{/if}}{{/if}}{{#if displayTo}}`{{{displayTo}}}`{{else}}`{{{newValue}}}`{{/if}}]({{#if depName}}https://renovatebot.com/diffs/npm/{{replace '/' '%2f' depName}}/{{{currentVersion}}}/{{{newVersion}}}{{/if}})\"\n  }\n}\n
"},{"location":"modules/manager/npm/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Delegated to the underlying package manager CLI - npm, pnpm, or Yarn - depending on which lock file is present.

"},{"location":"modules/manager/npm/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/npm/#npm-problems-and-workarounds","title":"npm problems and workarounds","text":""},{"location":"modules/manager/npm/#invalid-lock-file-npm-ci-fails","title":"Invalid lock file (npm ci fails)","text":"

Unfortunately, npm itself sometimes generates invalid lock files which fail npm ci. Try adding \"postUpdateOptions\": [\"npmInstallTwice\"] to tell Renovate run any npm install command (which is used to update lock files) twice. This is less efficient than running npm once, but has been known to fix most problems of this type. Renovate already runs npm install twice during lock file maintenance, because regenerating a lock file from scratch is known to need a second pass.

If this npm bug remains unfixed, and it becomes too frequent for Renovate users, then we may need to modify Renovate to do this by default. Please post feedback to the Renovate repository \"Discussions\" if you're needing to use this feature frequently or widely.

"},{"location":"modules/manager/npm/#yarn","title":"Yarn","text":""},{"location":"modules/manager/npm/#version-selection-installation","title":"Version Selection / Installation","text":"

If Renovate detects a packageManager setting for Yarn in package.json then it will use Corepack to install Yarn.

"},{"location":"modules/manager/npm/#http-proxy-support","title":"HTTP Proxy Support","text":"

Yarn itself does not natively recognize/support the HTTP_PROXY and HTTPS_PROXY environment variables.

You can configure RENOVATE_X_YARN_PROXY=true as an environment variable to enable configuring of Yarn proxy (e.g. if you cannot configure these proxy settings yourself in ~/.yarnrc.yml).

If set, and Renovate detects Yarn 2+, and one or both of those variables are present, then Renovate will run commands like yarn config set --home httpProxy http://proxy prior to executing yarn install. This will result in the ~/.yarnrc.yml file being created or modified with these settings, and the settings are not removed afterwards.

Configuration/conversion of NO_PROXY to Yarn config is not supported.

"},{"location":"modules/manager/nuget/","title":"Automated Dependency Updates for NuGet","text":"

Categories: dotnet

Renovate supports updating NuGet dependencies.

"},{"location":"modules/manager/nuget/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/\\.(?:cs|fs|vb|sql)proj$/\n/\\.(?:props|targets)$/\n/(^|/)dotnet-tools\\.json$/\n/(^|/)global\\.json$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/nuget/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, dotnet-version, nuget.

"},{"location":"modules/manager/nuget/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description docker Container base image from ContainerBaseImage nuget NuGet package reference from PackageReference, PackageVersion, or similar elements msbuild-sdk MSBuild SDK reference from Sdk elements, Import elements, or Project Sdk attribute dotnet-sdk .NET SDK version from global.json"},{"location":"modules/manager/nuget/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.(?:cs|fs|vb|sql)proj$/\",\n    \"/\\\\.(?:props|targets)$/\",\n    \"/(^|/)dotnet-tools\\\\.json$/\",\n    \"/(^|/)global\\\\.json$/\"\n  ],\n  \"rangeStrategy\": \"bump\",\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\n        \"msbuild-sdk\"\n      ],\n      \"rangeStrategy\": \"bump\"\n    }\n  ]\n}\n
"},{"location":"modules/manager/nuget/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/nuget/#additional-information","title":"Additional Information","text":"

Use packageRules to control the behavior of the NuGet package manager.

The NuGet package manager supports these SDK-style files and formats:

MSBuild SDK dependencies are also extracted from:

.NET Core projects are supported by default.

For Renovate to work with .NET Framework projects, you need to update these files so they match the new SDK-style format:

You can also extract from the single code file projects (since .NET 10). But, you need to add those files manually to the managerFilePatterns as they are not supported by default.

"},{"location":"modules/manager/nuget/#disabling-updates-for-pinned-versions","title":"Disabling updates for pinned versions","text":"

In NuGet, when you use versions like Version=\"1.2.3\" then it means \"1.2.3 or greater\" (an open-ended minimum, with no upper bound). When you use versions like Version=\"[1.2.3]\" then it means \"exactly 1.2.3\".

If you would like Renovate to disable updating of exact versions (warning: you might end up years out of date and not realize it) then here is an example configuration to achieve that:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Skip pinned versions\",\n      \"matchManagers\": [\"nuget\"],\n      \"matchCurrentValue\": \"/^\\\\[[^,]+\\\\]$/\",\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/nuget/#getting-updates-for-non-pinned-bare-versions","title":"Getting updates for non-pinned (bare) versions","text":"

Per NuGet's versioning rules, a bare version such as Version=\"1.2.3\" is an open-ended minimum (1.2.3 or greater) \u2014 so it is NuGet, not Renovate, that treats this as a range rather than a single version. The default rangeStrategy of auto resolves to replace for NuGet, and replace cannot produce an update for an open-ended minimum: every newer release already satisfies \"1.2.3 or greater\", so there is nothing to replace. The result is that Renovate detects no updates for these dependencies and closes any existing update PRs.

To keep receiving updates for bare versions, set rangeStrategy to bump. With bump, Renovate raises the minimum to the newest release (for example 1.2.3 to 1.5.0):

{\n  \"packageRules\": [\n    {\n      \"description\": \"Bump bare NuGet versions to the latest release\",\n      \"matchManagers\": [\"nuget\"],\n      \"rangeStrategy\": \"bump\"\n    }\n  ]\n}\n

Note

This is a change in behavior. Earlier versions of Renovate anchored the \"current version\" directly to the value in your project file, so bare versions received updates under any rangeStrategy. Since Renovate 43.208.2, Renovate no longer treats a range (including a bare NuGet version) as the current version, so the rangeStrategy now decides the outcome: use bump to restore the previous update behavior.

"},{"location":"modules/manager/nuget/#workload-restore","title":"Workload restore","text":"

Sometimes you need to run dotnet workload restore to ensure that all required workloads are installed before restoring the project. You can enable this behavior by adding dotnetWorkloadRestore to the postUpdateOptions in your Renovate configuration.

{\n  \"postUpdateOptions\": [\"dotnetWorkloadRestore\"]\n}\n
"},{"location":"modules/manager/nvm/","title":"Automated Dependency Updates for nvm","text":"

Categories: js, node

Renovate supports updating nvm dependencies.

"},{"location":"modules/manager/nvm/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.nvmrc$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/nvm/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: node-version.

"},{"location":"modules/manager/nvm/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/nvm/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.nvmrc$/\"\n  ],\n  \"versioning\": \"node\",\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/nvm/#additional-information","title":"Additional Information","text":"

Simply keeps the .nvmrc file updated.

"},{"location":"modules/manager/ocb/","title":"Automated Dependency Updates for OpenTelemetry Collector Builder (ocb)","text":"

Categories: golang

Renovate supports updating OpenTelemetry Collector Builder (ocb) dependencies.

"},{"location":"modules/manager/ocb/#file-matching","title":"File Matching","text":"

Because file names for ocb cannot be easily determined automatically, Renovate will not attempt to match any ocb files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/ocb/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: go.

"},{"location":"modules/manager/ocb/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description collector The OpenTelemetry Collector version itself connectors Connector component module exports Exporter component module extensions Extension component module processors Processor component module providers Provider component module receivers Receiver component module"},{"location":"modules/manager/ocb/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/ocb/#additional-information","title":"Additional Information","text":"

Renovate uses this manager to update dependencies defined in the build definitions for the OpenTelemetry Collector Builder (ocb).

By default, the ocb manager has no managerFilePatterns patterns. This means you must set a managerFilePatterns pattern for the ocb manager, for Renovate to update your ocb files. Here's a configuration example:

If your builder file is named foo-builder.yml or builder.yaml or builder-config.yaml
{\n  \"ocb\": {\n    \"managerFilePatterns\": [\"/builder(-config)?.ya?ml$/\"]\n  }\n}\n

Supported dependencies and their respective depTypes are:

Name depType base collector collector connectors connectors exporters exports extensions extensions processors processors providers providers receivers receivers"},{"location":"modules/manager/osgi/","title":"Automated Dependency Updates for OSGi","text":"

Categories: java

Renovate supports updating OSGi dependencies.

"},{"location":"modules/manager/osgi/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)src/main/features/.+\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/osgi/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/osgi/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/osgi/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)src/main/features/.+\\\\.json$/\"\n  ]\n}\n
"},{"location":"modules/manager/osgi/#additional-information","title":"Additional Information","text":"

The osgi manager extracts dependencies from feature model definition files, typically located under src/main/features. It uses the maven datasource to find dependency updates.

Artifact list extensions are not supported. For the definition of artifact list extensions, read section 159.7.3 of the OSGi R8 spec.

References:

"},{"location":"modules/manager/paket/","title":"Automated Dependency Updates for Paket","text":"

Categories: dotnet

Renovate supports updating Paket dependencies.

"},{"location":"modules/manager/paket/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)paket\\.dependencies$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/paket/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: nuget.

"},{"location":"modules/manager/paket/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/paket/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)paket\\\\.dependencies$/\"\n  ],\n  \"versioning\": \"paket\"\n}\n
"},{"location":"modules/manager/paket/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/paket/#additional-information","title":"Additional Information","text":"

Manage dependencies for Paket

Extracts dependencies from files:

The source entries of each group are used as registry URLs for the dependencies of that group.

Restrictions:

"},{"location":"modules/manager/pep621/","title":"Automated Dependency Updates for PEP 621","text":"

Categories: python

Renovate supports updating PEP 621 dependencies.

"},{"location":"modules/manager/pep621/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)pyproject\\.toml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pep621/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: pypi.

"},{"location":"modules/manager/pep621/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description requires-python The requires-python constraint from [project] project.dependencies Listed under [project.dependencies] project.optional-dependencies Listed under [project.optional-dependencies] dependency-groups Listed under [dependency-groups] (PEP 735) build-system.requires Listed under [build-system.requires] tool.pdm.dev-dependencies Listed under [tool.pdm.dev-dependencies] tool.uv.dev-dependencies Listed under [tool.uv.dev-dependencies] tool.uv.sources Listed under [tool.uv.sources]

Hatch environments produce dynamic depType values in the form tool.hatch.envs.<env-name>.

"},{"location":"modules/manager/pep621/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)pyproject\\\\.toml$/\"\n  ]\n}\n
"},{"location":"modules/manager/pep621/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Delegated to the underlying package manager CLI - pdm or uv - depending on which lockfile format the project uses.

"},{"location":"modules/manager/pep621/#additional-information","title":"Additional Information","text":"

This manager supports updating dependencies inside pyproject.toml files.

In addition to standard dependencies, these toolsets are also supported:

"},{"location":"modules/manager/pep621/#trust-model-for-pixi-lock-file-updates","title":"Trust model for pixi lock file updates","text":"

Running pixi lock can execute arbitrary code from conda package hooks, so Renovate treats pixi.lock refreshes as an unsafe execution. See pixi's security documentation for details.

Self-hosted administrators must explicitly allow this path by including pixi in the global allowedUnsafeExecutions setting. When pixi is not allowed, dependencies in pyproject.toml are still updated, but pixi.lock is left unchanged.

"},{"location":"modules/manager/pep621/#private-modules-authentication","title":"Private Modules Authentication","text":"

Before running the pdm or uv commands to update the pdm.lock or uv.lock respectively, Renovate exports git insteadOf directives in environment variables.

Renovate uses this logic before it updates any \"artifacts\":

The token from the hostRules entry matching hostType=github and matchHost=api.github.com is added as the default authentication for github.com. For those running against github.com, this token will be the default platform token.

Next, all hostRules with both a token or username/password and matchHost will be fetched, except for any github.com one from above.

Rules from this list are converted to environment variable directives if they match any of these characteristics:

"},{"location":"modules/manager/pep723/","title":"Automated Dependency Updates for PEP 723","text":"

Categories: python

Renovate supports updating PEP 723 dependencies.

"},{"location":"modules/manager/pep723/#file-matching","title":"File Matching","text":"

Because file names for pep723 cannot be easily determined automatically, Renovate will not attempt to match any pep723 files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pep723/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: pypi.

"},{"location":"modules/manager/pep723/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description project.dependencies A dependency from the inline [script.dependencies] metadata (parsed as PEP 508)"},{"location":"modules/manager/pep723/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/pep723/#additional-information","title":"Additional Information","text":"

This manager supports updating dependencies inside Python files that use inline script metadata, also known as PEP 723.

"},{"location":"modules/manager/pip-compile/","title":"Automated Dependency Updates for pip-compile","text":"

Categories: python

Renovate supports updating pip-compile dependencies.

"},{"location":"modules/manager/pip-compile/#file-matching","title":"File Matching","text":"

Because file names for pip-compile cannot be easily determined automatically, Renovate will not attempt to match any pip-compile files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pip-compile/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, pypi.

"},{"location":"modules/manager/pip-compile/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description indirect Indirect/transitive dependency locked in the compiled requirements file, but not directly specified in source"},{"location":"modules/manager/pip-compile/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [],\n  \"lockFileMaintenance\": {\n    \"enabled\": true,\n    \"branchTopic\": \"pip-compile-refresh\",\n    \"commitMessageAction\": \"Refresh pip-compile outputs\"\n  }\n}\n
"},{"location":"modules/manager/pip-compile/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/pip-compile/#additional-information","title":"Additional Information","text":"

The pip-compile manager does not support all use cases for pip-compile, so if you find any areas lacking and without an existing Issue then please \"Suggest an Idea\" in the Discussions forum with your use case.

The uv pip compile command is also supported through this manager in the same fashion as pip-compile.

The current implementation has some limitations. Read the full document before you start using the pip-compile manager.

"},{"location":"modules/manager/pip-compile/#non-configured-managerfilepatterns","title":"Non-configured managerFilePatterns","text":"

The pip-compile manager has an empty array for default managerFilePatterns, meaning it won't match any files ever by default. You can \"activate\" the manager by specifying a managerFilePatterns pattern such as:

{\n  \"pip-compile\": {\n    \"managerFilePatterns\": [\"/(^|/)requirements\\\\.txt$/\"]\n  }\n}\n

pip-compile reads the output files to extract the arguments passed to the original command, as such the managerFilePatterns must be configured for *.txt files and not *.in.

"},{"location":"modules/manager/pip-compile/#assumption-of-header-with-a-command","title":"Assumption of header with a command","text":"

As Renovate matches a pip-compile output file it will extract original command that was used to create it from header in this file. Because of that pip-compile manager poses restrictions on how this file is generated:

In turn pip-compile manager will find all source files and parse them as package files using their respective managers.

The following files are currently supported:

Source filename Manager pyproject.toml pep621 setup.py pip_setup *.in pip_requirements

Example header:

#\n# This file is autogenerated by pip-compile with Python 3.11\n# by the following command:\n#\n#    pip-compile --no-emit-index-url --output-file=requirements.txt requirements.in\n#\n
"},{"location":"modules/manager/pip-compile/#conflicts-with-other-managers","title":"Conflicts with other managers","text":"

Because pip-compile will update source files with their associated manager you should disable them to avoid running these managers twice.

{\n  \"pip_requirements\": {\n    \"enabled\": false\n  },\n  \"pip_setup\": {\n    \"enabled\": false\n  }\n}\n
"},{"location":"modules/manager/pip-compile/#configuration-of-python-version","title":"Configuration of Python version","text":"

By default Renovate extracts Python version from the header for pip-compile, and from the --python-version option for uv. To get Renovate to use another version of Python, add a constraints` rule to the Renovate config:

{\n  \"constraints\": {\n    \"python\": \"==3.7\"\n  }\n}\n
"},{"location":"modules/manager/pip-compile/#pip-compile-arguments","title":"pip-compile arguments","text":"

Renovate reads the requirements.txt file and extracts these pip-compile arguments:

All other allowed pip-compile arguments will be passed over without modification.

"},{"location":"modules/manager/pip-compile/#transitive-indirect-dependencies","title":"Transitive / indirect dependencies","text":"

This manager detects dependencies that only appear in lock files. They are disabled by default but can be forced to enable by vulnerability alerts. They will be upgraded with --upgrade-package option.

"},{"location":"modules/manager/pip_requirements/","title":"Automated Dependency Updates for pip Requirements","text":"

Categories: python

Renovate supports updating pip Requirements dependencies.

"},{"location":"modules/manager/pip_requirements/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)[\\w-]*requirements([-._]\\w+)?\\.(txt|pip)$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pip_requirements/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, pypi.

"},{"location":"modules/manager/pip_requirements/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/pip_requirements/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)[\\\\w-]*requirements([-._]\\\\w+)?\\\\.(txt|pip)$/\"\n  ]\n}\n
"},{"location":"modules/manager/pip_requirements/#additional-information","title":"Additional Information","text":"

Supports requirements.txt and requirements.pip files. The default file pattern is fairly flexible, to try to catch similarly named ones too (eg requirements-*.txt requirements.*.txt requirements-*.pip and requirements.*.pip) but may be extended/changed.

"},{"location":"modules/manager/pip_setup/","title":"Automated Dependency Updates for pip setup.py","text":"

Categories: python

Renovate supports updating pip setup.py dependencies.

"},{"location":"modules/manager/pip_setup/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)setup\\.py$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pip_setup/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: pypi.

"},{"location":"modules/manager/pip_setup/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/pip_setup/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)setup\\\\.py$/\"\n  ]\n}\n
"},{"location":"modules/manager/pip_setup/#additional-information","title":"Additional Information","text":"

Renovate uses a JavaScript-based parser to process the pip_setup files.

"},{"location":"modules/manager/pipenv/","title":"Automated Dependency Updates for Pipenv","text":"

Categories: python

Renovate supports updating Pipenv dependencies.

"},{"location":"modules/manager/pipenv/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Pipfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pipenv/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: pypi.

"},{"location":"modules/manager/pipenv/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description packages Listed under [packages] dev-packages Listed under [dev-packages]

Dependencies from other package category groups in the Pipfile use the group name as the depType.

"},{"location":"modules/manager/pipenv/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Pipfile$/\"\n  ]\n}\n
"},{"location":"modules/manager/pipenv/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/pipenv/#additional-information","title":"Additional Information","text":"

Pipenv.lock updating is supported.

"},{"location":"modules/manager/pixi/","title":"Automated Dependency Updates for Pixi","text":"

Categories: python

Renovate supports updating Pixi dependencies.

"},{"location":"modules/manager/pixi/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/(^|/)pyproject\\.toml$/\n/(^|/)pixi\\.toml$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pixi/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: conda, pypi.

"},{"location":"modules/manager/pixi/#dependency-types","title":"Dependency types","text":"

Feature dependencies produce dynamic depType values in the form feature-<name>, where <name> is the feature name defined in the pixi configuration. Top-level dependencies (under [dependencies] or [pypi-dependencies]) do not have a depType set.

"},{"location":"modules/manager/pixi/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)pyproject\\\\.toml$/\",\n    \"/(^|/)pixi\\\\.toml$/\"\n  ]\n}\n
"},{"location":"modules/manager/pixi/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/pixi/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/pixi/#pixi-package-manager","title":"Pixi package manager","text":"

Currently support channels from anaconda and prefix.dev, other channels are not supported yet.

Whenever the pixi config in pyproject.toml or pixi.toml file is updated, pixi.lock file will be checked for updates as well.

When using pyproject.toml, standard PEP 621 dependencies (e.g. [project.dependencies] or [dependency-groups]) are handled by the pep621 manager, which also updates pixi.lock when those dependencies change.

"},{"location":"modules/manager/pixi/#trust-model-for-pixi-lock-file-updates","title":"Trust model for pixi lock file updates","text":"

Running pixi lock can execute arbitrary code from conda package hooks, so Renovate treats pixi.lock refreshes as an unsafe execution. See pixi's security documentation for details.

Self-hosted administrators must explicitly allow this path by including pixi in the global allowedUnsafeExecutions setting. When pixi is not allowed, the package file is still updated, but pixi.lock is left unchanged.

Renovatebot will pick pixi version in following order:

  1. renovatebot setting constraints.pixi
  2. requires-pixi in pixi.toml

The minimal support version of pixi is 0.40.0 (pixi lock has only been introduced with that version). Therefore when you are setting constraints.pixi in your renovatebot config or requires-pixi in pixi.toml, please be careful to pick a supported pixi version.

"},{"location":"modules/manager/poetry/","title":"Automated Dependency Updates for Poetry","text":"

Categories: python

Renovate supports updating Poetry dependencies.

"},{"location":"modules/manager/poetry/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)pyproject\\.toml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/poetry/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-refs, git-tags, github-releases, github-tags, gitlab-tags, pypi.

"},{"location":"modules/manager/poetry/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description dependencies Listed under [tool.poetry.dependencies] dev-dependencies Listed under [tool.poetry.dev-dependencies] extras An optional dependency marked with optional = true build-system.requires Listed under [build-system.requires] project.dependencies Listed under [project.dependencies] (PEP 621 style) project.optional-dependencies Listed under [project.optional-dependencies] (PEP 621 style) dependency-groups Listed under [dependency-groups] (PEP 735)

Dependency group names from [tool.poetry.group.<name>.dependencies] are also used as depType values.

"},{"location":"modules/manager/poetry/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)pyproject\\\\.toml$/\"\n  ]\n}\n
"},{"location":"modules/manager/poetry/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/poetry/#additional-information","title":"Additional Information","text":"

Poetry 0.x, 1.x and 2.x versions are supported.

Whenever the pyproject.toml file is updated, the Poetry lock file will be checked for updates as well.

Warning

Updating locked versions of Poetry dependencies is at times unreliable. We recommended that you pin dependency versions in your pyproject.toml instead.

Renovate cannot accurately update locked versions of Poetry dependency ranges due to limitations in Poetry. For example, if the pyproject.toml has a constraint like coverage = \"^7.2\", and the version in poetry.lock is 7.4.1, and we know that 7.4.3 is available, then Renovate can only run poetry update --lock --no-interaction coverage and hope the result is 7.4.3. Poetry does not support updating to a specific/exact version with the update command, and the above update command may not even update at all sometimes. For this reason it's much better to pin dependency versions in pyproject.toml, such as coverage = \"7.4.1\" because it then gives Renovate more control and the ability to accurate upgrade dependencies in increments like 7.4.1 to 7.4.3.

"},{"location":"modules/manager/pre-commit/","title":"Automated Dependency Updates for pre-commit","text":"

Categories: no-category

Renovate supports updating pre-commit dependencies.

"},{"location":"modules/manager/pre-commit/#enabling","title":"Enabling","text":"

pre-commit functionality is currently in beta testing, so you must opt-in to test it. To enable it, add a configuration like this to either your self-hosted config or your renovate.json:

{\n  \"pre-commit\": {\n    \"enabled\": true\n  }\n}\n

If you find any bugs, please create a new discussion first. If you find that it works well, then let us know too.

"},{"location":"modules/manager/pre-commit/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.pre-commit-config\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pre-commit/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: forgejo-tags, github-tags, gitlab-tags.

"},{"location":"modules/manager/pre-commit/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description repository Pre-commit hook repository reference pre-commit-node Node.js additional dependency for a pre-commit hook pre-commit-python Python additional dependency for a pre-commit hook pre-commit-golang Go additional dependency for a pre-commit hook"},{"location":"modules/manager/pre-commit/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"pre-commit hook {{depName}}\",\n  \"enabled\": false,\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.pre-commit-config\\\\.ya?ml$/\"\n  ],\n  \"prBodyNotes\": [\n    \"Note: The `pre-commit` manager in Renovate is not supported by the `pre-commit` maintainers or community. Please do not report any problems there, instead [create a Discussion in the Renovate repository](https://github.com/renovatebot/renovate/discussions/new) if you have any questions.\"\n  ]\n}\n
"},{"location":"modules/manager/pre-commit/#additional-information","title":"Additional Information","text":"

Important note: The pre-commit manager is disabled by default and must be opted into through config. Renovate's approach to version updating is not fully aligned with pre-commit autoupdate and this has caused frustration for pre-commit's creator/maintainer. Attempts to work with the pre-commit project to fix these gaps have been rejected, so we have chosen to disable the manager by default indefinitely. Please do not contact the pre-commit project/maintainer about any Renovate-related topic. To view a list of open issues related to the pre-commit manager in Renovate, see the filtered list using the manager:pre-commit label.

When enabled, Renovate supports updating of Git dependencies within pre-commit configuration .pre-commit-config.yaml files or other YAML files that use the same format (via managerFilePatterns configuration). Updates are performed if the files follow the conventional format used in typical pre-commit files:

repos:\n  - repo: https://github.com/pre-commit/pre-commit-hooks\n    rev: v1.0.0\n    hooks:\n      - id: some-hook-id\n

To enable the pre-commit manager, add the following config:

{\n  \"pre-commit\": {\n    \"enabled\": true\n  }\n}\n

Alternatively, add :enablePreCommit to your extends array.

"},{"location":"modules/manager/pre-commit/#frozen-revisions","title":"Frozen Revisions","text":"

Renovate cannot change a rev from the pinned tag format (e.g. rev: vX.Y.Z) to the pinned SHA format (e.g. rev: 0123456789abcdef0123456789abcdef01234567 # frozen: vX.Y.Z) written by pre-commit autoupdate --freeze. If you freeze the revs yourself, Renovate keeps the frozen format when it updates a frozen rev. If you try to freeze with pinDigests: true, Renovate proposes the pin, but the update will fail with update-failure since there is no template to write a digest into a plain rev.

"},{"location":"modules/manager/pre-commit/#additional-dependencies","title":"Additional Dependencies","text":"

Renovate has partial support for additional_dependencies, currently Go, Node.js and Python only.

You will need to explicitly add the language to your hooks with additional_dependencies to let Renovate know what kind of dependencies they are.

Examples for the supported languages are listed below.

"},{"location":"modules/manager/pre-commit/#go","title":"Go","text":"
- repo: https://github.com/rhysd/actionlint\n  rev: v1.7.7\n  hooks:\n    - id: actionlint\n      language: golang\n      additional_dependencies:\n        - 'github.com/wasilibs/go-shellcheck/cmd/shellcheck@v0.10.0'\n
"},{"location":"modules/manager/pre-commit/#nodejs","title":"Node.js","text":"
- repo: https://github.com/pre-commit/mirrors-prettier\n  rev: v3.1.0\n  hooks:\n    - id: prettier\n      language: node\n      additional_dependencies:\n        - '@trivago/prettier-plugin-sort-imports@^5.2.2'\n        - prettier@^3.6.2\n
"},{"location":"modules/manager/pre-commit/#python","title":"Python","text":"
- repo: https://github.com/psf/black\n  rev: 19.3b0\n  hooks:\n    - id: black\n      language: python\n      additional_dependencies:\n        - 'requests==1.1.1'\n
"},{"location":"modules/manager/proto/","title":"Automated Dependency Updates for proto","text":"

Categories: no-category

Renovate supports updating proto dependencies.

"},{"location":"modules/manager/proto/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: **/.prototools.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/proto/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases, github-tags, node-version, npm, ruby-version, rust-version.

"},{"location":"modules/manager/proto/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/proto/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/.prototools\"\n  ]\n}\n
"},{"location":"modules/manager/proto/#additional-information","title":"Additional Information","text":"

Renovate can update tool versions in proto .prototools configuration files.

"},{"location":"modules/manager/proto/#how-it-works","title":"How it works","text":"

Proto uses .prototools files (TOML format) to pin tool versions at the directory level. Tool versions are declared as top-level key-value pairs:

node = \"22.14.0\"\nbun = \"1.2.2\"\ngo = \"~1.22\"\nproto = \"0.56.0\"\n

Renovate extracts these version pins and updates them using the appropriate datasource for each tool.

Non-version sections ([settings], [plugins], [tools], [env], [shell], [backends]) are ignored.

"},{"location":"modules/manager/proto/#supported-tools","title":"Supported tools","text":"

Renovate's proto manager supports the following built-in proto tools:

Tool Datasource Package bun github-releases oven-sh/bun deno github-releases denoland/deno go github-tags golang/go moon github-releases moonrepo/moon node node-version node npm npm npm pnpm npm pnpm yarn npm @yarnpkg/cli python github-tags python/cpython ruby ruby-version ruby-version rust rust-version rust proto github-releases moonrepo/proto gh github-releases cli/cli poetry github-releases python-poetry/poetry uv github-releases astral-sh/uv"},{"location":"modules/manager/proto/#limitations","title":"Limitations","text":""},{"location":"modules/manager/pub/","title":"Automated Dependency Updates for pub","text":"

Categories: dart

Renovate supports updating pub dependencies.

"},{"location":"modules/manager/pub/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)pubspec\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pub/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: dart, dart-version, flutter-version.

"},{"location":"modules/manager/pub/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description dependencies Listed under dependencies dev_dependencies Listed under dev_dependencies"},{"location":"modules/manager/pub/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)pubspec\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/pub/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/pub/#additional-information","title":"Additional Information","text":"

This manager is used to keep pubspec files up-to-date.

"},{"location":"modules/manager/puppet/","title":"Automated Dependency Updates for Puppet","text":"

Categories: iac, ruby

Renovate supports updating Puppet dependencies.

"},{"location":"modules/manager/puppet/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Puppetfile$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/puppet/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, puppet-forge.

"},{"location":"modules/manager/puppet/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/puppet/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Puppetfile$/\"\n  ]\n}\n
"},{"location":"modules/manager/puppet/#additional-information","title":"Additional Information","text":"

Renovate can update Puppetfiles.

"},{"location":"modules/manager/puppet/#how-it-works","title":"How it works","text":"

Renovate:

  1. Searches each repository for any Puppetfile files
  2. Extracts dependencies from the relevant sections of the Puppetfile
  3. Resolves the dependency on the default forge: https://forgeapi.puppetlabs.com, or on a user-defined forge
  4. Creates a PR that updates the Puppetfile

Finally, if the source repository has a \"changelog\" file or uses GitHub releases, then Renovate puts the changelogs for each version in its PR.

"},{"location":"modules/manager/puppet/#supported-puppetfile-formats","title":"Supported Puppetfile formats","text":"

The puppet manager extracts the dependencies from one Puppetfile. You can define a forge in your puppetfile in these ways:

For example:

No forge
mod 'puppetlabs/apt', '8.3.0'\nmod 'puppetlabs/apache', '7.0.0'\n
One forge
forge \"https://forgeapi.puppetlabs.com\"\n\nmod 'puppetlabs/apt', '8.3.0'\nmod 'puppetlabs/apache', '7.0.0'\nmod 'puppetlabs/concat', '7.1.1'\n
Multiple forges
forge \"https://forgeapi.puppetlabs.com\"\n\nmod 'puppetlabs/apt', '8.3.0'\nmod 'puppetlabs/apache', '7.0.0'\nmod 'puppetlabs/concat', '7.1.1'\n\n# Private forge\nforge \"https://forgeapi.example.com\"\n\nmod 'example/infra', '3.3.0'\n
GitHub-based forge, tag based
mod 'example/standalone_jar',\n    :git => 'git@gitlab.example.de:puppet/example-standalone_jar',\n    :tag => '0.9.0'\n
Git-based forge, tag based
mod 'stdlib',\n    :git => 'git@gitlab.com:example/project_stdlib.git',\n    :tag => '5.0.0'\n
Git-based forge, branch based
mod 'example/samba',\n    :git    => 'https://github.com/example/puppet-samba',\n    :branch => 'stable_version'\n
Git-based forge, ref based
mod 'example/samba',\n    :git => 'https://github.com/example/puppet-samba',\n    :ref => 'stable_version'\n
"},{"location":"modules/manager/pyenv/","title":"Automated Dependency Updates for pyenv","text":"

Categories: python

Renovate supports updating pyenv dependencies.

"},{"location":"modules/manager/pyenv/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.python-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/pyenv/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/pyenv/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/pyenv/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.python-version$/\"\n  ],\n  \"versioning\": \"docker\",\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/pyenv/#additional-information","title":"Additional Information","text":"

Simply keeps the .python-version file updated.

"},{"location":"modules/manager/quadlet/","title":"Automated Dependency Updates for Quadlet","text":"

Categories: docker

Renovate supports updating Quadlet dependencies.

"},{"location":"modules/manager/quadlet/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/.+\\.container$/\n/.+\\.image$/\n/.+\\.volume$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/quadlet/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/quadlet/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description image Container image referenced in a Quadlet unit file"},{"location":"modules/manager/quadlet/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/.+\\\\.container$/\",\n    \"/.+\\\\.image$/\",\n    \"/.+\\\\.volume$/\"\n  ]\n}\n
"},{"location":"modules/manager/quadlet/#additional-information","title":"Additional Information","text":"

Renovate supports updating of Podman Quadlet .container, .image, or .volume files or other files that use the same systemd format (via managerFilePatterns configuration). Updates are performed if there is an Image option in Container, Image, or Volume units:

[Container]\nImage=docker.io/library/alpine:3.22\n

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/regex/","title":"Custom Manager Support using Regex","text":"

Categories: custom

With customManagers using regex you can configure Renovate so it finds dependencies that are not detected by its other built-in package managers.

Renovate supports the ECMAScript (JavaScript) flavor of regex.

Renovate uses the uhop/node-re2 package that provides bindings for google/re2. Read about uhop/node-re2's limitations in their readme. The regex manager is unique in Renovate because:

We have additional Handlebars helpers to help you perform common transformations on the regex manager's template fields. Also read the documentation for the customManagers config option.

If you have limited managers to run within enabledManagers config option, you need to add \"custom.regex\" to the list.

"},{"location":"modules/manager/regex/#required-fields","title":"Required Fields","text":"

The first two required fields are managerFilePatterns and matchStrings:

"},{"location":"modules/manager/regex/#information-that-renovate-needs-about-the-dependency","title":"Information that Renovate needs about the dependency","text":"

Before Renovate can look up a dependency and decide about updates, it must have this info about each dependency:

Info type Required Notes Docs Name of the dependency Yes datasource Yes Example datasources: npm, Docker, GitHub tags, and so on. Supported datasources Version scheme to use. Defaults to semver-coerced. Yes You may set another version scheme, like pep440. Supported versioning schemes"},{"location":"modules/manager/regex/#required-capture-groups","title":"Required capture groups","text":"

You must:

"},{"location":"modules/manager/regex/#optional-capture-groups","title":"Optional capture groups","text":"

You may use any of these items:

"},{"location":"modules/manager/regex/#regular-expression-capture-groups","title":"Regular Expression Capture Groups","text":"

To be effective with the regex manager, you should understand regular expressions and named capture groups. But enough examples may compensate for lack of experience.

Example Dockerfile
FROM node:12\nENV YARN_VERSION=1.19.1\nRUN curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version ${YARN_VERSION}\n

You would need to capture the currentValue with a named capture group, like this: ENV YARN_VERSION=(?<currentValue>.*?)\\\\n.

To update a version string multiple times in a line: use multiple matchStrings, one for each occurrence.

Full Renovate .json5 config
{\n  customManagers: [\n    {\n      customType: 'regex',\n      managerFilePatterns: ['file-you-want-to-match'],\n      matchStrings: [\n        // for the version on the left part, ignoring the right\n        '# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\\\s\\\\S+?:(?<currentValue>\\\\S+)\\\\s+\\\\S+:.+',\n        // for the version on the right part, ignoring the left\n        '# renovate: datasource=(?<datasource>.*?) depName=(?<depName>.*?)( versioning=(?<versioning>.*?))?\\\\s\\\\S+?:\\\\S+\\\\s+\\\\S+:(?<currentValue>\\\\S+)',\n      ],\n      versioningTemplate: '{{#if versioning}}{{{versioning}}}{{else}}semver{{/if}}',\n    },\n  ],\n}\n
Example of how the file-you-want-to-match could look like
# renovate: datasource=github-tags depName=org/repo versioning=loose\nsomething:4.7.2    something-else:4.7.2\n
"},{"location":"modules/manager/regex/#online-regex-testing-tool-tips","title":"Online regex testing tool tips","text":"

If you're looking for an online regex testing tool that supports capture groups, try regex101.com. You must select the ECMAScript (JavaScript) flavor of regex. Backslashes ('\\') of the resulting regex have to still be escaped e.g. \\n\\s \u2192 \\\\n\\\\s. You can use the Code Generator in the sidebar and copy the regex in the generated \"Alternative syntax\" comment into JSON.

"},{"location":"modules/manager/regex/#renovates-regex-differs-from-the-online-tools","title":"Renovate's regex differs from the online tools","text":"

The regex manager uses RE2 which does not support backreferences and lookahead assertions.

The regex manager matches are done per-file, not per-line! This means the ^ and $ regex assertions only match the beginning and end of the entire file. If you need to match line boundaries you can use (?:^|\\r\\n|\\r|\\n|$).

"},{"location":"modules/manager/regex/#configuration-templates","title":"Configuration templates","text":"

In many cases, named capture groups alone aren't enough and you'll need to give Renovate more information so it can look up a dependency. Continuing the above example with Yarn, here is the full Renovate config:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/^Dockerfile$/\"],\n      \"matchStrings\": [\"ENV YARN_VERSION=(?<currentValue>.*?)\\\\n\"],\n      \"depNameTemplate\": \"yarn\",\n      \"datasourceTemplate\": \"npm\"\n    }\n  ]\n}\n
"},{"location":"modules/manager/regex/#advanced-capture","title":"Advanced Capture","text":"

Say your Dockerfile has many ENV variables that you want to keep up-to-date. But you don't want to write a regex custom manager rule for each variable. Instead you enhance your Dockerfile like this:

# renovate: datasource=github-tags depName=node packageName=nodejs/node versioning=node\nENV NODE_VERSION=20.10.0\n# renovate: datasource=github-releases depName=composer packageName=composer/composer\nENV COMPOSER_VERSION=1.9.3\n# renovate: datasource=docker packageName=docker versioning=docker\nENV DOCKER_VERSION=19.03.1\n# renovate: datasource=npm packageName=yarn\nENV YARN_VERSION=1.19.1\n

This Dockerfile is meant as an example, your Dockerfile may be a lot bigger.

You could configure Renovate to update the Dockerfile like this:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"description\": \"Update _VERSION variables in Dockerfiles\",\n      \"managerFilePatterns\": [\n        \"/(^|/|\\\\.)Dockerfile$/\",\n        \"/(^|/)Dockerfile\\\\.[^/]*$/\"\n      ],\n      \"matchStrings\": [\n        \"# renovate: datasource=(?<datasource>[a-z-]+?)(?: depName=(?<depName>.+?))? packageName=(?<packageName>.+?)(?: versioning=(?<versioning>[a-z-]+?))?\\\\s(?:ENV|ARG) .+?_VERSION=(?<currentValue>.+?)\\\\s\"\n      ]\n    }\n  ]\n}\n

We could drop the versioningTemplate because Renovate defaults to semver-coerced versioning. But we included the versioningTemplate config option to show you why we call these fields templates: because they are compiled using Handlebars and so can be composed from values you collect in named capture groups.

You should use triple brace {{{ }}} templates like {{{versioning}}} to be safe. This is because Handlebars escapes special characters with double braces (by default).

By adding renovate: datasource= and depName= comments to the Dockerfile you only need one customManager instead of four. The Dockerfile is documented better as well.

The syntax in the example is arbitrary, and you can set your own syntax. If you do, update your matchStrings regex!

For example the appVersion property in a Chart.yaml of a Helm chart is always referenced to an Docker image. In such scenarios, some values can be hard-coded. For example:

apiVersion: v2\nname: amazon-eks-pod-identity-webhook\ndescription: A Kubernetes webhook for pods that need AWS IAM access\nversion: 1.0.3\ntype: application\n# renovate: image=amazon/amazon-eks-pod-identity-webhook\nappVersion: 'v0.4.0'\n

Using the customManagers below, Renovate looks for available Docker tags of the image amazon/amazon-eks-pod-identity-webhook.

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"datasourceTemplate\": \"docker\",\n      \"managerFilePatterns\": [\"/(^|/)Chart\\\\.yaml$/\"],\n      \"matchStrings\": [\n        \"#\\\\s?renovate: image=(?<depName>.*?)\\\\s?appVersion:\\\\s?\\\\'?(?<currentValue>[\\\\w+\\\\.\\\\-]*)'\"\n      ]\n    }\n  ]\n}\n
"},{"location":"modules/manager/regex/#using-custommanager-to-update-the-dependency-name-in-addition-to-version","title":"Using customManager to update the dependency name in addition to version","text":""},{"location":"modules/manager/regex/#updating-gitlab-ci-include-dep-names","title":"Updating gitlab-ci include dep names","text":"

You can use the regex manager to update the depName and the version. This can be handy when the location of files referenced in gitlab-ci includes: fields has changed.

You may need to set a second matchString for the new name to ensure the regex manager can detect the new value. For example:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/.*y[a]?ml$/\"],\n      \"matchStringsStrategy\": \"combination\",\n      \"matchStrings\": [\n        \"['\\\"]?(?<depName>/pipeline-fragments/fragment-version-check)['\\\"]?\\\\s*ref:\\\\s['\\\"]?(?<currentValue>[\\\\d-]*)['\\\"]?\",\n        \"['\\\"]?(?<depName>pipeline-solutions/gitlab/fragments/fragment-version-check)['\\\"]?\\\\s*ref:\\\\s['\\\"]?(?<currentValue>[\\\\d-]*)['\\\"]?\"\n      ],\n      \"depNameTemplate\": \"pipeline-solutions/gitlab/fragments/fragment-version-check\",\n      \"autoReplaceStringTemplate\": \"'{{{depName}}}'\\n    ref: {{{newValue}}}\",\n      \"datasourceTemplate\": \"gitlab-tags\",\n      \"versioningTemplate\": \"gitlab-tags\"\n    }\n  ]\n}\n

The config above will migrate:

- project: 'pipeline-fragments/docker-lint'\n  ref: 2-4-0\n  file: 'ci-include-docker-lint-base.yml'\n

To this:

- project: 'pipeline-solutions/gitlab/fragments/docker-lint'\n  ref: 2-4-1\n  file: 'ci-include-docker-lint-base.yml'\n
"},{"location":"modules/manager/regex/#handling-scenarios-where-dependency-name-must-be-extracted-from-the-file-path","title":"Handling scenarios where dependency name must be extracted from the file path","text":"

Some repositories structure dependencies so that the dependency name is embedded in the file path itself. Two common patterns are:

packages/\n  <package-name>/\n\n# or\n\npackages/\n  <package-name-1>/\n    version.txt\n  <package-name-2>/\n    version.txt\n

In these situations, the regex manager may need to derive the dependency name from either the filename or the directory containing that file.

Renovate exposes two template fields that help with this:

  1. packageFile: Filename of the matched file
  2. packageFileDir: Directory path where the file exists (relative to repo root)

For example, if you package file exists at home/packages/package.json, then:

packageFile will be package.json packageFileDir will be home/packages

These values can be referenced inside depNameTemplate or packageNameTemplate

If your dependency folder looks like:

packages/my-lib/version.txt\n

You can configure the regex manager like:

{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"packages/.*/version\\\\.txt$\"],\n      \"matchStrings\": [\"(?<currentValue>.+)\"],\n      \"depNameTemplate\": \"{{lookup (split packageFileDir '/') 1 }}\",\n      \"datasourceTemplate\": \"github-tags\"\n    }\n  ]\n}\n
"},{"location":"modules/manager/renovate-config/","title":"Automated Dependency Updates for Renovate Config","text":"

Categories: no-category

Renovate supports updating Renovate Config dependencies.

"},{"location":"modules/manager/renovate-config/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

renovate.json\nrenovate.jsonc\nrenovate.json5\n.github/renovate.json\n.github/renovate.jsonc\n.github/renovate.json5\n.gitlab/renovate.json\n.gitlab/renovate.jsonc\n.gitlab/renovate.json5\n.renovaterc\n.renovaterc.json\n.renovaterc.jsonc\n.renovaterc.json5\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/renovate-config/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: dart-version, dotnet-version, gitea-tags, github-releases, github-tags, gitlab-tags, gradle-version, java-version, npm, nuget, pypi, rubygems, rust-version.

"},{"location":"modules/manager/renovate-config/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/renovate-config/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"renovate.json\",\n    \"renovate.jsonc\",\n    \"renovate.json5\",\n    \".github/renovate.json\",\n    \".github/renovate.jsonc\",\n    \".github/renovate.json5\",\n    \".gitlab/renovate.json\",\n    \".gitlab/renovate.jsonc\",\n    \".gitlab/renovate.json5\",\n    \".renovaterc\",\n    \".renovaterc.json\",\n    \".renovaterc.jsonc\",\n    \".renovaterc.json5\"\n  ]\n}\n
"},{"location":"modules/manager/renovate-config/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/renovate-config/#config-presets","title":"Config presets","text":"

Renovate supports updating Shareable Config Presets for Renovate configuration.

The preset versions are only updated if the version is already pinned. For example, github>user/renovate-config#1.2.3 will be updated to github>user/renovate-config#1.2.4 if the 1.2.4 version is available, but github>user/renovate-config will not be pinned.

{\n  \"extends\": [\n    \"github>user/renovate-config#1.2.3\",\n    \"github>user/renovate-config:group\"\n  ]\n}\n
"},{"location":"modules/manager/renovate-config/#unsupported-config","title":"Unsupported Config","text":""},{"location":"modules/manager/renovate-config/#tool-constraints","title":"Tool constraints","text":"

Renovate will extract + suggest updates for package manager/tool versions in the constraints configuration.

Constraints set on tools that Containerbase supports will result in Renovate updates.

Other constraints will not be updated by Renovate.

"},{"location":"modules/manager/ruby-version/","title":"Automated Dependency Updates for .ruby-version","text":"

Categories: ruby

Renovate supports updating .ruby-version dependencies.

"},{"location":"modules/manager/ruby-version/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.ruby-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/ruby-version/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: ruby-version.

"},{"location":"modules/manager/ruby-version/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/ruby-version/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.ruby-version$/\"\n  ],\n  \"versioning\": \"ruby\"\n}\n
"},{"location":"modules/manager/ruby-version/#additional-information","title":"Additional Information","text":"

This will maintain .ruby-version files. Available versions will be determined from the official Ruby downloads page.

"},{"location":"modules/manager/runtime-version/","title":"Automated Dependency Updates for runtime.txt","text":"

Categories: python

Renovate supports updating runtime.txt dependencies.

"},{"location":"modules/manager/runtime-version/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)runtime.txt$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/runtime-version/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/runtime-version/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/runtime-version/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)runtime.txt$/\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/runtime-version/#additional-information","title":"Additional Information","text":"

Keep runtime.txt files updated.

Currently supports Python runtime updates, commonly used by platforms such as

"},{"location":"modules/manager/rust-toolchain/","title":"Automated Dependency Updates for Rust Toolchain","text":"

Categories: rust

Renovate supports updating Rust Toolchain dependencies.

"},{"location":"modules/manager/rust-toolchain/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)rust-toolchain(\\.toml)?$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/rust-toolchain/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: rust-version.

"},{"location":"modules/manager/rust-toolchain/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description toolchain Rust toolchain version"},{"location":"modules/manager/rust-toolchain/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"Rust\",\n  \"managerFilePatterns\": [\n    \"/(^|/)rust-toolchain(\\\\.toml)?$/\"\n  ]\n}\n
"},{"location":"modules/manager/rust-toolchain/#additional-information","title":"Additional Information","text":"

This manager can be used to update the Rust toolchain version in rust-toolchain.toml and rust-toolchain files.

It supports both the TOML format and the legacy plain-text format as specified in the Rust toolchain documentation.

"},{"location":"modules/manager/rust-toolchain/#version-pinning","title":"Version pinning","text":"

If you'd like to pin your toolchain to a particular version, the following configuration can be applied:

{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"rust-toolchain\"],\n      \"matchDepTypes\": [\"toolchain\"],\n      \"rangeStrategy\": \"pin\"\n    }\n  ]\n}\n
"},{"location":"modules/manager/rust-toolchain/#supported-renovations","title":"Supported renovations","text":"

With rangeStrategy: pin:

Note: The version numbers shown above are just examples for illustration purposes.

"},{"location":"modules/manager/sbt/","title":"Automated Dependency Updates for sbt","text":"

Categories: java

Renovate supports updating sbt dependencies.

"},{"location":"modules/manager/sbt/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

/\\.sbt$/\n/project/[^/]*\\.scala$/\n/project/build\\.properties$/\n/(^|/)repositories$/\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/sbt/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases, maven, sbt-package, sbt-plugin.

"},{"location":"modules/manager/sbt/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description plugin An sbt plugin added via addSbtPlugin or addCompilerPlugin

Other depType values are extracted dynamically from the classifier or configuration string in the build file (e.g. % \"test\", % Provided, classifier \"sources\").

"},{"location":"modules/manager/sbt/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.sbt$/\",\n    \"/project/[^/]*\\\\.scala$/\",\n    \"/project/build\\\\.properties$/\",\n    \"/(^|/)repositories$/\"\n  ],\n  \"versioning\": \"ivy\"\n}\n
"},{"location":"modules/manager/sbt/#additional-information","title":"Additional Information","text":"

Extracts Maven artifact dependencies for SBT.

"},{"location":"modules/manager/scalafmt/","title":"Automated Dependency Updates for Scalafmt","text":"

Categories: java

Renovate supports updating Scalafmt dependencies.

"},{"location":"modules/manager/scalafmt/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.scalafmt.conf$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/scalafmt/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/scalafmt/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/scalafmt/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.scalafmt.conf$/\"\n  ]\n}\n
"},{"location":"modules/manager/scalafmt/#additional-information","title":"Additional Information","text":"

Extracts scalafmt version from .scalafmt.conf file.

New versions of Scalafmt are looked up on Github Releases.

"},{"location":"modules/manager/setup-cfg/","title":"Automated Dependency Updates for Setuptools (setup.cfg)","text":"

Categories: python

Renovate supports updating Setuptools (setup.cfg) dependencies.

"},{"location":"modules/manager/setup-cfg/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)setup\\.cfg$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/setup-cfg/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: pypi.

"},{"location":"modules/manager/setup-cfg/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description install Listed under install_requires in the [options] section setup Listed under setup_requires in the [options] section test Listed under tests_require in the [options] section extra Listed under the [options.extras_require] section"},{"location":"modules/manager/setup-cfg/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)setup\\\\.cfg$/\"\n  ],\n  \"versioning\": \"pep440\"\n}\n
"},{"location":"modules/manager/setup-cfg/#additional-information","title":"Additional Information","text":"

Updates dependencies for Python setup.cfg files.

"},{"location":"modules/manager/smithy/","title":"Automated Dependency Updates for Smithy","text":"

Categories: java

Renovate supports updating Smithy dependencies.

"},{"location":"modules/manager/smithy/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)smithy-build\\.json$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/smithy/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: maven.

"},{"location":"modules/manager/smithy/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/smithy/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)smithy-build\\\\.json$/\"\n  ]\n}\n
"},{"location":"modules/manager/smithy/#additional-information","title":"Additional Information","text":"

Renovate updates the Maven dependencies declared in the maven.dependencies section of Smithy smithy-build.json files. For example:

Smithy build file
{\n  \"version\": \"1.0\",\n  \"maven\": {\n    \"dependencies\": [\"software.amazon.smithy:smithy-aws-traits:1.37.0\"],\n    \"repositories\": [{ \"url\": \"https://repo.example.com/maven\" }]\n  }\n}\n

Repositories from maven.repositories are used as the registries for version lookups. When the file defines no repositories, Renovate defaults to Maven Central, which matches Smithy's own resolution behavior.

Dependency coordinates or repository URLs that contain ${ENV_VAR} placeholders are skipped. If all your repositories use placeholders, configure registryUrls in your Renovate config instead.

Maven version ranges like [1.0, 2.0) are supported via Maven versioning.

"},{"location":"modules/manager/sveltos/","title":"Automated Dependency Updates for Sveltos","text":"

Categories: kubernetes, cd

Renovate supports updating Sveltos dependencies.

"},{"location":"modules/manager/sveltos/#file-matching","title":"File Matching","text":"

Because file names for sveltos cannot be easily determined automatically, Renovate will not attempt to match any sveltos files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/sveltos/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, helm.

"},{"location":"modules/manager/sveltos/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description ClusterProfile A Sveltos ClusterProfile resource Profile A Sveltos Profile resource EventTrigger A Sveltos EventTrigger resource ClusterPromotion A Sveltos ClusterPromotion resource"},{"location":"modules/manager/sveltos/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/sveltos/#additional-information","title":"Additional Information","text":"

Renovate uses the Sveltos manager to update the dependencies in Helm-Charts for Sveltos resources.

Learn about Sveltos Helm-Charts by reading the Sveltos documentation.

"},{"location":"modules/manager/sveltos/#you-must-set-a-managerfilepatterns-pattern","title":"You must set a managerFilePatterns pattern","text":"

The sveltos manager has no default managerFilePatterns pattern. This is because there is are no common filename or directory name conventions for Sveltos YAML files. You must set your own managerFilePatterns rules, so Renovate knows which *.yaml files are Sveltos definitions.

"},{"location":"modules/manager/sveltos/#managerfilepatterns-pattern-examples","title":"managerFilePatterns pattern examples","text":"If most .yaml files in your repository are for Sveltos
{\n  \"sveltos\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\"]\n  }\n}\n
Sveltos YAML files are in a sveltos/ directory
{\n  \"sveltos\": {\n    \"managerFilePatterns\": [\"/sveltos/.+\\\\.yaml$/\"]\n  }\n}\n
One Sveltos file in a directory
{\n  \"sveltos\": {\n    \"managerFilePatterns\": [\"/^config/sveltos\\\\.yaml$/\"]\n  }\n}\n
"},{"location":"modules/manager/sveltos/#disabling-parts-of-the-sveltos-manager","title":"Disabling parts of the sveltos manager","text":"

You can use depTypes for fine-grained control, for example to disable parts of the Sveltos manager.

Disable ClusterPromotion resources
{\n  \"packageRules\": [\n    {\n      \"matchManagers\": [\"sveltos\"],\n      \"matchDepTypes\": [\"ClusterPromotion\"],\n      \"enabled\": false\n    }\n  ]\n}\n
"},{"location":"modules/manager/swift/","title":"Automated Dependency Updates for Swift Package Manager","text":"

Categories: swift

Renovate supports updating Swift Package Manager dependencies.

"},{"location":"modules/manager/swift/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)Package\\.swift/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/swift/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, gitlab-tags.

"},{"location":"modules/manager/swift/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/swift/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)Package\\\\.swift/\"\n  ],\n  \"versioning\": \"swift\",\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/swift/#additional-information","title":"Additional Information","text":"

Anything other than .exact(<...>) or exact:<...> will be treated as range with respect to Swift specific. Because of this, some PR descriptions will look like from: <...> => <...>.

Examples:

package(name: \"<...>\", .exact(\"1.2.3\"))   // => 1.2.3\npackage(name: \"<...>\", exact: \"1.2.3\")    // => 1.2.3\npackage(name: \"<...>\", from: \"1.2.3\")     // => from: \"2.0.0\"\npackage(name: \"<...>\", \"1.2.3\"...)        // => \"2.0.0\"...\npackage(name: \"<...>\", \"1.2.3\"...\"1.3.0\") // => \"1.2.3\"...\"2.0.0\"\npackage(name: \"<...>\", \"1.2.3\"..<\"1.3.0\") // => \"1.2.3\"..<\"2.0.0\"\npackage(name: \"<...>\", ...\"1.2.3\")        // => ...\"2.0.0\"\npackage(name: \"<...>\", ..<\"1.2.3\")        // => ..<\"2.0.0\"\n
"},{"location":"modules/manager/tekton/","title":"Automated Dependency Updates for Tekton","text":"

Categories: ci, cd

Renovate supports updating Tekton dependencies.

"},{"location":"modules/manager/tekton/#file-matching","title":"File Matching","text":"

Because file names for tekton cannot be easily determined automatically, Renovate will not attempt to match any tekton files by default. For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/tekton/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, git-tags.

"},{"location":"modules/manager/tekton/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description tekton-annotation Tekton resource referenced via an annotation (e.g. GitHub release or git tag URL) tekton-bundle Tekton Bundle OCI image reference tekton-step-image Container image used in a Tekton step, sidecar, or step template"},{"location":"modules/manager/tekton/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": []\n}\n
"},{"location":"modules/manager/tekton/#additional-information","title":"Additional Information","text":"

Tekton is an Open Source cloud-native Continuous Integration and Continuous Delivery/Deployment solution.

Tekton uses Tasks to capture specific commands to be executed, and Pipelines to combine different Tasks, to achieve a goal, like building a container image. Tasks and Pipelines are defined as Kubernetes custom resources.

The Tekton documentation is a great resource to learn more about the overall concepts and how to start using it.

"},{"location":"modules/manager/tekton/#distributing-tasks-and-pipeline-definitions","title":"Distributing Tasks and Pipeline definitions","text":"

There are different ways to distribute Task and Pipeline definitions. They can be created directly as a Kubernetes resource with standard tools like kubectl. Tasks and Pipeline definitions can also live outside the Kubernetes cluster and get fetched by Tekton when needed, this approach relies on Tekton resource references rather than the resource definition. The tekton manager focuses on providing updates to Tekton resource references.

Right now, Renovate's Tekton manager supports references that are Bundles and PipelinesAsCode with remote HTTP URL resolver. Read the Tekton Pipeline remote resolution docs for the different kinds of Tekton references and their corresponding resolvers.

"},{"location":"modules/manager/tekton/#using-a-pipelinesascode-remote-url-reference","title":"Using a PipelinesAsCode remote URL reference","text":"

By specifying the annotation with a remote task or a remote pipeline based on the recommended way using git based versioning. How this can be used can be seen in the example below.

How an annotation could look like in an pipeline-run.yaml
apiVersion: tekton.dev/v1\nkind: PipelineRun\nmetadata:\n  name: main\n  annotations:\n    pipelinesascode.tekton.dev/task: 'https://github.com/foo/bar/raw/v0.0.1/task/my-task/my-task.yaml'\n    pipelinesascode.tekton.dev/pipeline: 'https://github.com/foo/bar/raw/v0.0.1/pipeline/my-pipeline/my-pipeline.yaml'\n

Supported URLs:

  1. https://github.com/foo/bar/raw/v0.0.1/tasks/task/task.yaml<
  2. https://raw.githubusercontent.com/foo/bar/v0.0.1/tasks/task/task.yaml
  3. https://github.com/foo/bar/releases/download/v0.0.1/create-git-tag-task.yaml
"},{"location":"modules/manager/tekton/#using-a-tekton-bundle-reference","title":"Using a Tekton Bundle reference","text":"

There are three ways to use a Tekton Bundle reference:

  1. Via the Tekton Bundles Resolver
  2. Via the tektoncd/resolution project
  3. Via the taskRun.spec.taskRef.bundle and the pipelineRun.spec.pipelineRef.bundle attributes

Renovate's Tekton manager supports all the methods listed above.

"},{"location":"modules/manager/tekton/#configuring-images-in-tekton-tasks","title":"Configuring images in Tekton Tasks","text":"

You can configure the container images that Tekton uses when it runs tasks. You may use these attributes to configure images in a:

  1. Task step
  2. Task stepTemplate
  3. Task sidecar

You can define Tekton Tasks within these Tekton resources:

  1. Task
  2. TaskRun
  3. Pipeline
  4. PipelineRun
  5. StepAction

Renovate's Tekton manager supports all the image attributes for the Tekton resources mentioned above.

"},{"location":"modules/manager/tekton/#set-your-own-managerfilepatterns-pattern","title":"Set your own managerFilePatterns pattern","text":"

The tekton manager does not have a default managerFilePatterns pattern. This means it won't match any files until you set a managerFilePatterns pattern. This is to avoid problems with unrelated YAML files since there is no well-established file name pattern for Tekton resources. As an example, the following config matches all the YAML files in a repository:

{\n  \"tekton\": {\n    \"managerFilePatterns\": [\"/\\\\.yaml$/\", \"/\\\\.yml$/\"]\n  }\n}\n

See our versioning documentation for details on the existing versioning rules and possible alterations.

"},{"location":"modules/manager/terraform/","title":"Automated Dependency Updates for Terraform","text":"

Categories: iac, terraform

Renovate supports updating Terraform dependencies.

"},{"location":"modules/manager/terraform/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching any of the following regular expressions:

**/*.tf\n**/*.tofu\n

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/terraform/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, docker, git-tags, github-releases, github-tags, helm, terraform-module, terraform-provider.

"},{"location":"modules/manager/terraform/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description module A Terraform module source reference provider A Terraform provider declared in a provider block required_provider A Terraform provider declared in a required_providers block required_version The Terraform version constraint in a required_version field helm_release A Helm chart deployed via a helm_release resource tfe_workspace A Terraform version pinned in a tfe_workspace resource docker_image A Docker image in a docker_image resource docker_container A Docker image in a docker_container resource docker_service A Docker image in a docker_service resource docker_registry_image A Docker image in a docker_registry_image data source kubernetes_pod A container image in a kubernetes_pod resource kubernetes_pod_v1 A container image in a kubernetes_pod_v1 resource kubernetes_cron_job A container image in a kubernetes_cron_job resource kubernetes_cron_job_v1 A container image in a kubernetes_cron_job_v1 resource kubernetes_daemonset A container image in a kubernetes_daemonset resource kubernetes_daemon_set_v1 A container image in a kubernetes_daemon_set_v1 resource kubernetes_deployment A container image in a kubernetes_deployment resource kubernetes_deployment_v1 A container image in a kubernetes_deployment_v1 resource kubernetes_job A container image in a kubernetes_job resource kubernetes_job_v1 A container image in a kubernetes_job_v1 resource kubernetes_replication_controller A container image in a kubernetes_replication_controller resource kubernetes_replication_controller_v1 A container image in a kubernetes_replication_controller_v1 resource kubernetes_stateful_set A container image in a kubernetes_stateful_set resource kubernetes_stateful_set_v1 A container image in a kubernetes_stateful_set_v1 resource"},{"location":"modules/manager/terraform/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"Terraform {{depName}}\",\n  \"managerFilePatterns\": [\n    \"**/*.tf\",\n    \"**/*.tofu\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/terraform/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Renovate performs lock file maintenance itself, without calling the underlying package manager.

"},{"location":"modules/manager/terraform/#additional-information","title":"Additional Information","text":""},{"location":"modules/manager/terraform/#terraform-vs-opentofu","title":"Terraform vs OpenTofu","text":"

Renovate can not know if you want to use the Terraform or OpenTofu registry. By default, Renovate uses the Terraform registry (registry.terraform.io) for providers and modules without a registry definition.

You can override this default with your own packageRules, for example:

Prefer releases from OpenTofu
{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"terraform-provider\", \"terraform-module\"],\n      \"registryUrls\": [\"https://registry.opentofu.org\"]\n    }\n  ]\n}\n
"},{"location":"modules/manager/terraform/#supported-dependencies","title":"Supported dependencies","text":"

Renovate supports updating the Terraform dependencies listed below. Check the tables to see where some dependencies can be hosted.

"},{"location":"modules/manager/terraform/#modules","title":"Modules","text":"Name Public hosting Private hosting GitTags yes yes GithubTags yes yes TerraformRegistry yes yes"},{"location":"modules/manager/terraform/#providers","title":"Providers","text":"

Providers are deprecated in Terraform 0.13.0.

Name Public hosting Private hosting TerraformRegistry yes yes"},{"location":"modules/manager/terraform/#required_providers-block","title":"required_providers block","text":"

Needs Terraform >= 0.13.0.

Name Public hosting Private hosting TerraformRegistry yes yes"},{"location":"modules/manager/terraform/#required_version","title":"required_version","text":"

Renovate can update the required_version attribute of the Terraform block.

"},{"location":"modules/manager/terraform/#helm_release","title":"helm_release","text":"

Renovate can update the version attribute of helm_release resources. This applies to both helm chart repositories and charts published in OCI registries.

Name Public hosting Private hosting chart repository yes yes"},{"location":"modules/manager/terraform/#docker","title":"Docker","text":"

Renovate can update image references of the Docker provider resources (docker\\_\\*).

Name Public hosting Private hosting Docker registry yes yes"},{"location":"modules/manager/terraform/#kubernetes","title":"Kubernetes","text":"

Renovate can update image references of Kubernetes provider resources (kubernetes\\_\\*).

Name Public hosting Private hosting Docker registry yes yes"},{"location":"modules/manager/terraform/#tfe_workspaces","title":"tfe_workspaces","text":"

Renovate can update tfe_workspaces. Renovate searches for the terraform_version argument.

"},{"location":"modules/manager/terraform/#range-constraints","title":"Range constraints","text":"

Renovate understands these Terraform range constraints:

Terraform range Notes >= 1.2.0 version 1.2.0 or newer <= 1.2.0 version 1.2.0 or older ~> 1.2.0 any non-beta version >= 1.2.0 and < 1.3.0, e.g. 1.2.X ~> 1.2 any non-beta version >= 1.2.0 and < 2.0.0, e.g. 1.X.Y >= 1.0.0, <= 2.0.0 any version between 1.0.0 and 2.0.0 inclusive"},{"location":"modules/manager/terraform/#disabling-parts-of-the-manager","title":"Disabling parts of the manager","text":"

You can use these depTypes for fine-grained control, for example to disable parts of the Terraform manager.

Resource depType Notes Terraform provider provider required Terraform provider required_provider required Terraform version required_version This handles the required_version in terraform blocks TFE workspace tfe_workspace This handles the terraform_version argument in tfe_workspace resources Terraform module module Helm release helm_release Docker container docker_container Docker image docker_image Docker service docker_service Kubernetes CronJob kubernetes_cron_job Kubernetes CronJob v1 kubernetes_cron_job_v1 Kubernetes DaemonSet kubernetes_daemon_set Kubernetes DaemonSet v1 kubernetes_daemon_set_v1 Kubernetes Deployment kubernetes_deployment Kubernetes Deployment v1 kubernetes_deployment_v1 Kubernetes Job kubernetes_job Kubernetes Job v1 kubernetes_job_v1 Kubernetes Pod kubernetes_pod Kubernetes Pod v1 kubernetes_pod_v1 Kubernetes Replication Controller kubernetes_replication_controller Kubernetes Replication Controller v1 kubernetes_replication_controller_v1 Kubernetes StatefulSet kubernetes_stateful_set Kubernetes StatefulSet v1 kubernetes_stateful_set_v1 Data Source depType Notes Docker registry image docker_registry_image

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/terraform-version/","title":"Automated Dependency Updates for .terraform-version","text":"

Categories: terraform

Renovate supports updating .terraform-version dependencies.

"},{"location":"modules/manager/terraform-version/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.terraform-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/terraform-version/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/terraform-version/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/terraform-version/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.terraform-version$/\"\n  ],\n  \"versioning\": \"hashicorp\",\n  \"extractVersion\": \"^v(?<version>.*)$\"\n}\n
"},{"location":"modules/manager/terraform-version/#additional-information","title":"Additional Information","text":"

This will maintain .terraform-version files. Available versions will be determined from the official Terraform downloads page.

"},{"location":"modules/manager/terragrunt/","title":"Automated Dependency Updates for Terragrunt","text":"

Categories: iac, terraform

Renovate supports updating Terragrunt dependencies.

"},{"location":"modules/manager/terragrunt/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)terragrunt\\.hcl$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/terragrunt/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: bitbucket-tags, git-tags, gitea-tags, github-tags, gitlab-tags, terraform-module.

"},{"location":"modules/manager/terragrunt/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description github Terragrunt module sourced from a GitHub repository gitTags Terragrunt module sourced from a generic Git repository terragrunt Terragrunt module sourced from a Terraform Module registry"},{"location":"modules/manager/terragrunt/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"Terragrunt dependency {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)terragrunt\\\\.hcl$/\"\n  ]\n}\n
"},{"location":"modules/manager/terragrunt/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is not implemented separately for Terragrunt. It reuses the Terraform manager's lock file logic in-process, so Renovate computes the updated .terraform.lock.hcl hashes directly instead of calling the terragrunt or terraform CLI.

"},{"location":"modules/manager/terragrunt/#additional-information","title":"Additional Information","text":"

Currently by default, Terragrunt support is limited to Terraform registry sources and GitHub sources that include SemVer refs, e.g. like github.com/hashicorp/example?ref=v1.0.0.

You can create a custom versioning config to support non-SemVer references. For example, if you want to reference a tag like module-v1.2.5, a block like this would work:

{\n  \"terragrunt\": {\n    \"versioning\": \"regex:^((?<compatibility>.*)-v|v*)(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)$\"\n  }\n}\n

Pinned Terragrunt dependencies like the following will get a PR whenever there is a newer version available:

terraform {\n  source = \"github.com/hashicorp/example?ref=v1.0.0\"\n}\n
"},{"location":"modules/manager/terragrunt/#terraform-lockfiles","title":"Terraform lockfiles","text":"

The Terragrunt manager supports lock file maintenance for .terraform.lock.hcl artifacts. These artifacts will be updated if and only if the update type is lockFileMaintenance.

"},{"location":"modules/manager/terragrunt-version/","title":"Automated Dependency Updates for .terragrunt-version","text":"

Categories: terraform

Renovate supports updating .terragrunt-version dependencies.

"},{"location":"modules/manager/terragrunt-version/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.terragrunt-version$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/terragrunt-version/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/terragrunt-version/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/terragrunt-version/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.terragrunt-version$/\"\n  ],\n  \"versioning\": \"hashicorp\",\n  \"extractVersion\": \"^v(?<version>.+)$\"\n}\n
"},{"location":"modules/manager/terragrunt-version/#additional-information","title":"Additional Information","text":"

This will maintain .terragrunt-version files. Available versions will be determined from gruntwork-io/terragrunt GitHub releases.

"},{"location":"modules/manager/tflint-plugin/","title":"Automated Dependency Updates for TFLint Plugins","text":"

Categories: terraform

Renovate supports updating TFLint Plugins dependencies.

"},{"location":"modules/manager/tflint-plugin/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.tflint\\.hcl$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/tflint-plugin/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: github-releases.

"},{"location":"modules/manager/tflint-plugin/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description plugin TFLint plugin sourced from GitHub Releases"},{"location":"modules/manager/tflint-plugin/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"TFLint plugin {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/\\\\.tflint\\\\.hcl$/\"\n  ],\n  \"extractVersion\": \"^v(?<version>.*)$\"\n}\n
"},{"location":"modules/manager/tflint-plugin/#additional-information","title":"Additional Information","text":"

Renovate maintains your TFLint configuration file, and updates the plugins in the file.

Supports plugins hosted in public repositories on github.com. This is because TFLint only supports public repositories.

"},{"location":"modules/manager/travis/","title":"Automated Dependency Updates for Travis CI","text":"

Categories: ci

Renovate supports updating Travis CI dependencies.

"},{"location":"modules/manager/travis/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /^\\.travis\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/travis/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: node-version.

"},{"location":"modules/manager/travis/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/travis/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/^\\\\.travis\\\\.ya?ml$/\"\n  ],\n  \"major\": {\n    \"enabled\": false\n  },\n  \"versioning\": \"node\"\n}\n
"},{"location":"modules/manager/travis/#additional-information","title":"Additional Information","text":"

This manager is intended to keep Travis config files (.travis.yml) up-to-date, this file controls the CI build environment. Currently Renovate can only update the node_js section of this file.

Renovate \"understands\" Travis's Build Matrix concept as well, so it will try to update all found Node.js versions to the latest LTS, e.g.

node_js:\n-  - 8.10.0\n-  - 10.10.0\n+  - 16.13.0\n+  - 16.13.0\n

Due to this, major updates for Travis are disabled by default. If you enable major updates and use a version matrix, then you will likely need to manually fix any major update PRs raised by Renovate. Here's how to enable major updates in your Renovate config:

{\n  \"travis\": {\n    \"major\": {\n      \"enabled\": true\n    }\n  }\n}\n
"},{"location":"modules/manager/typst/","title":"Automated Dependency Updates for Typst package","text":"

Categories: no-category

Renovate supports updating Typst package dependencies.

"},{"location":"modules/manager/typst/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /\\.typ$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/typst/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: typst.

"},{"location":"modules/manager/typst/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/typst/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/\\\\.typ$/\"\n  ]\n}\n
"},{"location":"modules/manager/typst/#additional-information","title":"Additional Information","text":"

Manages versions of Typst package imports in .typ files for update.

The Typst datasource fetches package information from the official public Typst index. Only the preview namespace is supported. Local and other unsupported namespaces are skipped. Custom registries are not supported.

"},{"location":"modules/manager/unity3d/","title":"Automated Dependency Updates for Unity3d","text":"

Categories: dotnet

Renovate supports updating Unity3d dependencies.

"},{"location":"modules/manager/unity3d/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: **/ProjectSettings/ProjectVersion.txt.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/unity3d/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: unity3d.

"},{"location":"modules/manager/unity3d/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/unity3d/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/ProjectSettings/ProjectVersion.txt\"\n  ]\n}\n
"},{"location":"modules/manager/unity3d/#additional-information","title":"Additional Information","text":"

Manages version numbers in the ProjectVersion.txt file located within the ProjectSettings folder of a Unity project.

Example path: /home/user/testUnityProject/ProjectSettings/ProjectVersion.txt.

ProjectVersion.txt always have two version references in YAML syntax; one with revision and another one without it. Both are updated together.

m_EditorVersion: 2020.3.15f2\nm_EditorVersionWithRevision: 2020.3.15f2 (6cf78cb77498)\n
"},{"location":"modules/manager/velaci/","title":"Automated Dependency Updates for Vela","text":"

Categories: ci

Renovate supports updating Vela dependencies.

"},{"location":"modules/manager/velaci/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)\\.vela\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/velaci/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/velaci/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/velaci/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/(^|/)\\\\.vela\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/velaci/#additional-information","title":"Additional Information","text":"

Extracts Docker-type dependencies from VelaCI config files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/vendir/","title":"Automated Dependency Updates for vendir","text":"

Categories: helm, kubernetes

Renovate supports updating vendir dependencies.

"},{"location":"modules/manager/vendir/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /(^|/)vendir\\.yml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/vendir/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker, helm.

"},{"location":"modules/manager/vendir/#dependency-types","title":"Dependency types","text":"

This manager extracts the following depType values:

depType Description HelmChart Helm chart dependency in vendir configuration GitSource Git reference-based source GithubRelease GitHub release-based source HttpSource HTTP-based source"},{"location":"modules/manager/vendir/#default-config","title":"Default config","text":"
{\n  \"commitMessageTopic\": \"vendir {{depName}}\",\n  \"managerFilePatterns\": [\n    \"/(^|/)vendir\\\\.yml$/\"\n  ]\n}\n
"},{"location":"modules/manager/vendir/#lock-file-maintenance","title":"Lock File Maintenance","text":"

This manager supports lockFileMaintenance for the following file(s):

Lock file maintenance is delegated to the underlying package manager, which Renovate runs as an external command.

"},{"location":"modules/manager/vendir/#additional-information","title":"Additional Information","text":"

Renovate can update Helm Chart references and Git references in vendir.yml files, with the vendir tool.

For Renovate to work you must:

"},{"location":"modules/manager/vendir/#helm-charts","title":"Helm Charts","text":"

Renovate supports HTTPS and OCI Helm chart repositories.

Example helm chart vendir.yml
apiVersion: vendir.k14s.io/v1alpha1\nkind: Config\n\n# one or more directories to manage with vendir\ndirectories:\n  - # path is relative to the `vendir` CLI working directory\n    path: config/_ytt_lib\n    contents:\n      path: github.com/cloudfoundry/cf-k8s-networking\n      helmChart:\n        # chart name (required)\n        name: stable/redis\n        # use specific chart version (string; optional)\n        version: '1.2.1'\n        # specifies Helm repository to fetch from (optional)\n        repository:\n          # repository url; supports experimental OCI Helm fetch via\n          # oci:// scheme (required)\n          url: https://...\n        # specify Helm binary version to use;\n        # '3' means binary 'helm3' needs to be on the path (optional)\n        helmVersion: '3'\n
"},{"location":"modules/manager/vendir/#registry-aliases","title":"Registry Aliases","text":""},{"location":"modules/manager/vendir/#oci","title":"OCI","text":"

Aliases for OCI registries are supported via Renovate's dockerfile or docker managers.

"},{"location":"modules/manager/vendir/#git","title":"Git","text":"

Renovate can update explicit refs in Git references in vendir.yml files.

Example git vendir.yml
apiVersion: vendir.k14s.io/v1alpha1\nkind: Config\n\n# one or more directories to manage with vendir\ndirectories:\n  - path: config/_ytt_lib\n    contents:\n      path: github.com/cloudfoundry/cf-k8s-networking\n      git:\n        # HTTP or SSH URLs are supported (required)\n        url: https://github.com/cloudfoundry/cf-k8s-networking\n        # branch, tag, commit; origin is the name of the remote (required)\n        # optional if refSelection is specified (available in v0.11.0+)\n        ref: origin/master\n        # depth of commits to fetch; 0 (default) means everything (optional; v0.29.0+)\n        depth: 1\n        ...\n
"},{"location":"modules/manager/vendir/#githubrelease","title":"GithubRelease","text":"

Renovate can update explicit tags in GitHub releases in vendir.yml files.

Example GitHub vendir.yml
directories:\n  - path: config/_ytt_lib\n    contents:\n      path: github.com/cloudfoundry/cf-k8s-networking\n      githubRelease:\n        # slug for repository (org/repo) (required)\n        slug: k14s/kapp-controller\n        # use release tag (optional)\n        # optional if tagSelection is specified (available in v0.22.0+)\n        tag: v0.1.0\n
"},{"location":"modules/manager/vendir/#http","title":"HTTP","text":"

Note

Updates to dependencies tracked through the HTTP source can only be updated using lockFileMaintenance.

Renovate can extract HTTP dependency sources, but will not update them without lockFileMaintenance.

Example vendir.yml for syncing a remote file
apiVersion: vendir.k14s.io/v1alpha1\nkind: Config\ndirectories:\n  - path: internal\n    contents:\n      - path: renovate-ce\n        http:\n          url: https://raw.githubusercontent.com/mend/renovate-ce-ee/refs/main/docs/openapi-community.yaml\n
"},{"location":"modules/manager/woodpecker/","title":"Automated Dependency Updates for Woodpecker","text":"

Categories: ci

Renovate supports updating Woodpecker dependencies.

"},{"location":"modules/manager/woodpecker/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: /^\\.woodpecker(?:/[^/]+)?\\.ya?ml$/.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/woodpecker/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: docker.

"},{"location":"modules/manager/woodpecker/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/woodpecker/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"/^\\\\.woodpecker(?:/[^/]+)?\\\\.ya?ml$/\"\n  ]\n}\n
"},{"location":"modules/manager/woodpecker/#additional-information","title":"Additional Information","text":"

Extracts all Docker images from Woodpecker Pipeline YAML files.

If you need to change the versioning format, read the versioning documentation to learn more.

"},{"location":"modules/manager/xcodegen/","title":"Automated Dependency Updates for XcodeGen","text":"

Categories: swift

Renovate supports updating XcodeGen dependencies.

"},{"location":"modules/manager/xcodegen/#file-matching","title":"File Matching","text":"

By default, Renovate will check any files matching the following regular expression: **/project.yml.

For details on how to extend a manager's managerFilePatterns value, please follow this link.

"},{"location":"modules/manager/xcodegen/#supported-datasources","title":"Supported datasources","text":"

This manager supports extracting the following datasources: git-tags, github-tags, gitlab-tags.

"},{"location":"modules/manager/xcodegen/#dependency-types","title":"Dependency types","text":"

This manager has no documented depType values.

"},{"location":"modules/manager/xcodegen/#default-config","title":"Default config","text":"
{\n  \"managerFilePatterns\": [\n    \"**/project.yml\"\n  ],\n  \"pinDigests\": false\n}\n
"},{"location":"modules/manager/xcodegen/#additional-information","title":"Additional Information","text":"

Extracts Swift package dependencies from XcodeGen project.yml files.

The default project.yml file name is used for file matching, but users can extend the managerFilePatterns config option to match custom file names.

Supported version specifiers:

The following version specifiers are detected but not supported for updates:

Local packages (specified with path) are ignored.

Both url and github shorthand are supported for specifying the package source.

"},{"location":"modules/platform/","title":"Renovate Platforms","text":"

Renovate aims to be platform-neutral, while also taking advantage of good platform-specific features.

"},{"location":"modules/platform/#supported-platforms","title":"Supported platforms","text":"

Supported values for platform are:

Additionally, the following platform values are experimental:

"},{"location":"modules/platform/azure/","title":"Azure DevOps and Azure DevOps Server","text":""},{"location":"modules/platform/azure/#authentication","title":"Authentication","text":""},{"location":"modules/platform/azure/#personal-access-token-pat","title":"Personal Access Token (PAT)","text":"

First, create a Personal Access Token for the Renovate account. Let Renovate use your PAT by doing one of the following:

Permissions for your PAT should be at minimum:

Scope Permission Description Code Read & Write Required Work Items Read & write Needed for link to work item and dependecy dashboards

Remember to set platform=azure somewhere in your Renovate config file.

"},{"location":"modules/platform/azure/#microsoft-entra-id-bearer-token-oauth","title":"Microsoft Entra ID Bearer Token (OAuth)","text":"

Renovate also supports authenticating to Azure DevOps Services using Microsoft Entra ID (formerly Azure AD) Bearer tokens. This works with service principals, managed identities, and user-delegated tokens.

Renovate automatically detects whether a token is a JWT (Bearer token) or a PAT based on its format. No additional configuration is needed. Just set the token field to your Entra ID access token:

// config.js\nmodule.exports = {\n  platform: 'azure',\n  endpoint: 'https://dev.azure.com/your-organization',\n  token: '<your-entra-access-token>',\n};\n

Or via environment variables:

export RENOVATE_PLATFORM=azure\nexport RENOVATE_ENDPOINT=https://dev.azure.com/your-organization\nexport RENOVATE_TOKEN=<your-entra-access-token>\n

Renovate inspects the token structure to decide the authentication method:

"},{"location":"modules/platform/azure/#obtaining-a-bearer-token","title":"Obtaining a Bearer token","text":"

For service principals:

az login --service-principal -u <client-id> -p <client-secret> --tenant <tenant-id>\naz account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query accessToken -o tsv\n

For managed identities (Azure-hosted Renovate):

az login --identity\naz account get-access-token --resource 499b84ac-1321-427f-aa17-267ca6975798 --query accessToken -o tsv\n
"},{"location":"modules/platform/azure/#requirements-for-service-principals-managed-identities","title":"Requirements for service principals / managed identities","text":"
  1. The identity must be added to the Azure DevOps organization (Organization Settings \u2192 Users).
  2. The identity must have at least a Basic license.
  3. Grant permissions: Code (Read & Write) at the project level.
"},{"location":"modules/platform/azure/#limitations","title":"Limitations","text":""},{"location":"modules/platform/azure/#running-renovate-in-azure-pipelines","title":"Running Renovate in Azure Pipelines","text":""},{"location":"modules/platform/azure/#setting-up-a-new-pipeline","title":"Setting up a new pipeline","text":"

Create a brand new pipeline within Azure DevOps, and select your source:

Then select your repository.

Within Configure your pipeline select: Starter pipeline

Replace all content in the starter pipeline with:

schedules:\n  - cron: '0 3 * * *'\n    displayName: 'Every day at 3am (UTC)'\n    branches:\n      include: [main]\n    always: true\n\ntrigger: none\n\npool:\n  vmImage: ubuntu-latest\n\nsteps:\n  - task: npmAuthenticate@0\n    inputs:\n      workingFile: .npmrc\n\n  - bash: |\n      add-apt-repository ppa:git-core/ppa\n      apt update && apt install git -y\n    displayName: 'Install latest version of Git'\n\n  - bash: |\n      git config --global user.email 'bot@renovateapp.com'\n      git config --global user.name 'Renovate'\n      npx --userconfig .npmrc renovate\n    env:\n      RENOVATE_PLATFORM: azure\n      RENOVATE_ENDPOINT: $(System.CollectionUri)\n      RENOVATE_CONFIG_FILE: $(Build.SourcesDirectory)/renovate_bot_config.json\n      RENOVATE_TOKEN: $(System.AccessToken)\n      LOG_LEVEL: debug\n
"},{"location":"modules/platform/azure/#create-a-npmrc-file","title":"Create a .npmrc file","text":"

Create a .npmrc file in your repository:

registry=https://pkgs.dev.azure.com/YOUR-ORG/_packaging/YOUR-FEED/npm/registry/\nalways-auth=true\n

For the registry key, replace YOUR-ORG with your Azure DevOps organization and YOUR-FEED with your Azure Artifacts feed.

"},{"location":"modules/platform/azure/#create-a-configjs-file","title":"Create a config.js file","text":"

Create a config.js file in your repository:

module.exports = {\n  hostRules: [\n    {\n      hostType: 'npm',\n      matchHost: 'pkgs.dev.azure.com',\n      username: 'apikey',\n      password: process.env.RENOVATE_TOKEN,\n    },\n  ],\n  repositories: ['YOUR-PROJECT/YOUR-REPO'],\n};\n

For the repositories key, replace YOUR-PROJECT/YOUR-REPO with your Azure DevOps project and repository.

"},{"location":"modules/platform/azure/#using-azure-devops-internal-api-for-pipeline-tasks-versions","title":"Using Azure DevOps internal API for pipeline tasks versions","text":"

Info

Renovate now uses the set of APIs that Azure provides to query the azure-pipelines tasks versions directly from the instance. Read pull request 32966 and discussion 24820 for more background information on this change.

To let Renovate use the Azure DevOps internal API, you must set these variables in your config:

Example config file in JSON format
{\n  \"platform\": \"azure\",\n  \"endpoint\": \"https://dev.azure.com/ORG_NAME\",\n  \"azure-pipelines\": {\n    \"enabled\": true\n  },\n  \"repositories\": [\"PROJECT_NAME/REPO_NAME\"],\n  \"prHourlyLimit\": 0,\n  \"baseBranchPatterns\": [\"main\"],\n  \"hostRules\": [\n    {\n      \"matchHost\": \"https://dev.azure.com/\",\n      \"hostType\": \"azure-pipelines-tasks\"\n    }\n  ],\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"azure-pipelines-tasks\"],\n      \"extractVersion\": \"^(?<version>\\\\d+)\"\n    }\n  ]\n}\n
"},{"location":"modules/platform/azure/#yarn-users","title":"Yarn users","text":"

To do a successful yarn install you need to match the URL of the registry fully. Use the matchHost config option to specify the full path to the registry.

module.exports = {\n  platform: 'azure',\n  hostRules: [\n    {\n      matchHost:\n        'https://myorg.pkgs.visualstudio.com/_packaging/myorg/npm/registry/',\n      token: process.env.RENOVATE_TOKEN,\n      hostType: 'npm',\n    },\n    {\n      matchHost: 'github.com',\n      token: process.env.RENOVATE_GITHUB_COM_TOKEN,\n    },\n  ],\n  repositories: ['YOUR-PROJECT/YOUR-REPO'],\n};\n

Put this in your repository's .npmrc file:

registry=https://myorg.pkgs.visualstudio.com/_packaging/myorg/npm/registry/\nalways-auth=true\n
"},{"location":"modules/platform/azure/#add-renovatejson-file","title":"Add renovate.json file","text":"

Additionally, you can create a renovate.json file (which holds the Renovate configuration) in the root of the repository you want to update. Read more about the Renovate configuration options

"},{"location":"modules/platform/azure/#using-a-single-pipeline-to-update-multiple-repositories","title":"Using a single pipeline to update multiple repositories","text":"

If you want to use a single Renovate pipeline to update multiple repositories you must take the following steps.

Add the names of the repositories to config.js. Make sure that the \"Project Collection Build Service (YOUR-PROJECT)\" user has the following permissions on the repositories:

The user must have the following permission at Project-level:

"},{"location":"modules/platform/azure/#linking-a-work-item-to-the-pull-requests","title":"Linking a work item to the Pull Requests","text":"

If you want Renovate to automatically link an existing work item to the Pull Requests, you can set the azureWorkItemId configuration. Make sure the user has the following permissions on the work item's area path:

If the user does not have these permissions, Renovate still creates a PR but it won't have a link to the work item.

"},{"location":"modules/platform/azure/#dependency-dashboard-work-item-state","title":"Dependency Dashboard work item state","text":"

On Azure DevOps, Renovate stores the Dependency Dashboard (and any other issues) as a work item of type Issue. Renovate resolves the correct open and closed state names from the process for the project automatically, so it works across the different processes (for example To Do/Done on Basic, New/Active/Closed on Agile, and custom inherited processes).

When creating the work item, Renovate does not set a state, so Azure DevOps applies the default initial state of the work item type. If the states cannot be read (for example on older Azure DevOps Server versions), Renovate falls back to the New and Closed state names.

The work item description is rendered as Markdown only on Azure DevOps Services (cloud), which is the only product that supports the work item Markdown format field. On Azure DevOps Server (on-premises) Renovate omits that field, so the description is stored as plain text.

"},{"location":"modules/platform/azure/#adding-tags-to-pull-requests","title":"Adding tags to Pull Requests","text":"

Tags can be added to Pull Requests using the labels or addLabels configurations. If the tag does not exist in the DevOps project, it will be created automatically during creation of the Pull Request as long as the user has the permissions at Project-level:

Otherwise, when a tag does not exist and the user does not have permission to create it, Renovate will output an error during creation of the Pull Request.

"},{"location":"modules/platform/bitbucket/","title":"Bitbucket Cloud","text":"

Most of the information on this page is meant for users who want to self-host Renovate on Bitbucket Cloud.

"},{"location":"modules/platform/bitbucket/#easiest-way-to-run-renovate","title":"Easiest way to run Renovate","text":"

For most users, the easiest way to get started is to install the Mend app for Bitbucket and use the free Renovate plan. When you use the app, Mend will:

If you self-host Renovate you must do the things listed above yourself. Self-hosting is meant for users with advanced use cases, or who want to be in full control of Renovate and the environment it runs in. We recommend most users install the Mend app.

Read the Security and Permissions page to learn about the Security and Permissions needed for the Mend app.

After you installed the hosted app, please read the reading list to learn how to use and configure Renovate.

"},{"location":"modules/platform/bitbucket/#authentication","title":"Authentication","text":"

First, create an API token for the Renovate account. Give the API token the following permission scopes:

Permission Scope read:repository:bitbucket Repository: Read write:repository:bitbucket Repository: Write read:pullrequest:bitbucket Pull requests: Read write:pullrequest:bitbucket Pull requests: Write read:user:bitbucket User: Read read:workspace:bitbucket Workspace: Read

Renovate also needs to validate the workspace membership status of pull-request reviewers, for that, create a new user group in the workspace with the Create repositories permission and add the Renovate user to it.

Let Renovate use your API token by doing one of the following:

Remember to:

"},{"location":"modules/platform/bitbucket/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":""},{"location":"modules/platform/bitbucket-server/","title":"Bitbucket Data Center and Server","text":""},{"location":"modules/platform/bitbucket-server/#authentication","title":"Authentication","text":"

First, create a HTTP access token for the Renovate account. Let Renovate use your HTTP access token by doing one of the following:

If you use project or repository based HTTP access tokens, it can only be used as token.

Remember to set platform=bitbucket-server somewhere in your Renovate config file.

If you're not using @renovate-bot as username then set your custom username for the Renovate account.

If you use MySQL or MariaDB you must set unicodeEmoji to false in the global self-hosted config (RENOVATE_CONFIG_FILE) to prevent issues with emojis.

"},{"location":"modules/platform/bitbucket-server/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":""},{"location":"modules/platform/bitbucket-server/#features-awaiting-implementation","title":"Features awaiting implementation","text":""},{"location":"modules/platform/bitbucket-server/#testing","title":"Testing","text":"

If you want a test Bitbucket server locally rather than with your production server, Atlassian's Bitbucket Server Docker image is really convenient.

In line with their instructions, the following commands bring up a new server:

docker volume create --name bitbucketVolume\ndocker run -v bitbucketVolume:/var/atlassian/application-data/bitbucket --name=\"bitbucket\" -d -p 7990:7990 -p 7999:7999 atlassian/bitbucket-server:8.9.6\n

Once it's running and initialized, the quickest way to testing with Renovate is:

  1. Create the admin user as prompted
  2. Create a new project and a repository for that project
  3. Make sure the repository has a package file in it for Renovate to find, e.g. .nvmrc or package.json
  4. Create a dedicated Renovate user @renovate-bot and grant it write access to the project
  5. Note down the password for @renovate-bot and use it in the Renovate CLI

At this point you should have a project ready for Renovate, and the @renovate-bot account ready to run on it. You can then run like this:

npx renovate --platform=bitbucket-server --endpoint=http://localhost:7990 --git-fs=http --username=renovate-bot --password=abc123456789! --log-level=debug --autodiscover=true\n

Alternatively using env:

export RENOVATE_PLATFORM=bitbucket-server\nexport RENOVATE_ENDPOINT=http://localhost:7990\nexport RENOVATE_GIT_FS=http\nexport RENOVATE_USERNAME=renovate-bot\nexport RENOVATE_PASSWORD=abc123456789!\nexport LOG_LEVEL=debug\nnpx renovate --autodiscover=true\n

You should then get a \"Configure Renovate\" onboarding PR in any projects that @renovate-bot has been invited to.

"},{"location":"modules/platform/bitbucket-server/#supported-versions","title":"Supported versions","text":"

We support all Bitbucket Server versions which are not EOL. See Atlassian Support End of Life Policy for up-to-date versions.

"},{"location":"modules/platform/codecommit/","title":"AWS CodeCommit","text":"

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

No new features for the Codecommit platform

In July 2024, Amazon deprecated the CodeCommit platform. In November 2025, Amazon re-instated support for CodeCommit. Since July 2024, CodeCommit is in a \"feature freeze\", and Amazon re-instating support for CodeCommit as of November 2025 does not currently change that. The Renovate maintainers have decided that we will not add any new features unless a company is willing to contribute feature(s) for CodeCommit and maintain them. For more details see Discussion 39741.

"},{"location":"modules/platform/codecommit/#authentication","title":"Authentication","text":""},{"location":"modules/platform/codecommit/#iam-role","title":"IAM Role","text":""},{"location":"modules/platform/codecommit/#machine-pre-requisites","title":"Machine pre-requisites","text":"
  1. Install the aws-cli program on the machine.
  2. Set up the environment with the git-credentials-helper:
  3. Set the environment variable AWS_REGION.
"},{"location":"modules/platform/codecommit/#codebuild-configuration","title":"Codebuild Configuration","text":"Add git-credential helper to your buildspec.yml file
env: git-credential-helper:yes\n
"},{"location":"modules/platform/codecommit/#iam-user","title":"IAM User","text":"

First, you must get an AWS IAM Access Key id and a Secret access key id. After that, let Renovate use the AWS CodeCommit authentication keys, by picking one of these methods:

"},{"location":"modules/platform/codecommit/#method-1-create-a-renovate-config-file-configjs","title":"Method 1: Create a Renovate config file (config.js)","text":"
username: AWS IAM access key id\npassword: AWS Secret access key\nendpoint: the URL endpoint e.g https://git-codecommit.us-east-1.amazonaws.com/\ntoken: AWS session token, if you have one\n
"},{"location":"modules/platform/codecommit/#method-2-set-the-environment-with-all-required-aws-environment-variables","title":"Method 2: Set the environment with all required AWS environment variables","text":"
AWS_ACCESS_KEY_ID: AWS IAM access key id\nAWS_SECRET_ACCESS_KEY: AWS Secret access key\nAWS_REGION: the AWS region e.g us-east-1\nAWS_SESSION_TOKEN: AWS session token, if you have one\n
"},{"location":"modules/platform/codecommit/#method-3-set-aws-credentials-with-cli-parameters","title":"Method 3: Set AWS credentials with CLI parameters","text":"
--username: AWS IAM access key id\n--password: AWS Secret access key\n--endpoint: the URL endpoint for example https://git-codecommit.us-east-1.amazonaws.com/\n--token: AWS session token, if you have one\n
"},{"location":"modules/platform/codecommit/#permissions","title":"Permissions","text":"

Create a new AWS policy for Renovate with these permissions, then attach it to the user/role.

Change the Resource value to the resources you want to use:

Example policy JSON file
{\n  \"Version\": \"2012-10-17\",\n  \"Statement\": [\n    {\n      \"Sid\": \"RenovatePolicy\",\n      \"Effect\": \"Allow\",\n      \"Action\": [\n        \"codecommit:DeleteCommentContent\",\n        \"codecommit:UpdatePullRequestDescription\",\n        \"codecommit:GitPull\",\n        \"codecommit:ListPullRequests\",\n        \"codecommit:GetCommentsForPullRequest\",\n        \"codecommit:ListRepositories\",\n        \"codecommit:UpdatePullRequestTitle\",\n        \"codecommit:GetFile\",\n        \"codecommit:UpdateComment\",\n        \"codecommit:GetRepository\",\n        \"codecommit:CreatePullRequest\",\n        \"codecommit:CreatePullRequestApprovalRule\",\n        \"codecommit:GitPush\",\n        \"codecommit:UpdatePullRequestStatus\",\n        \"codecommit:GetPullRequest\"\n      ],\n      \"Resource\": \"*\"\n    }\n  ]\n}\n
"},{"location":"modules/platform/codecommit/#running-renovate","title":"Running Renovate","text":"

Once you have followed method 1, 2 or 3, and have set up the permissions, you're ready to configure Renovate:

You're ready to run Renovate now, and it will process your repositories.

"},{"location":"modules/platform/codecommit/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":"

These Renovate features are not supported on Codecommit:

"},{"location":"modules/platform/codecommit/#recommendations","title":"Recommendations","text":"

Limit the number of open Renovate PRs by setting a prConcurrentLimit.

If you close a PR but don\u2019t want Renovate to recreate the PR later, then use package rules with the \"enabled\": false key. This workaround is needed due to platform limitations.

"},{"location":"modules/platform/codecommit/#example-configuration","title":"Example configuration","text":"Example config.js file
module.exports = {\n  endpoint: 'https://git-codecommit.us-east-1.amazonaws.com/',\n  platform: 'codecommit',\n  repositories: ['abc/def', 'abc/ghi'],\n  username: 'ACCESS_KEY_ID_GOES_HERE',\n  password: 'SECRET_ACCESS_KEY_GOES_HERE',\n  token: 'AWS_SESSION_TOKEN_GOES_HERE',\n  gitAuthor: 'your_email@domain',\n  packageRules: [\n    {\n      matchPackageNames: ['package_name', 'package_name2'],\n      enabled: false,\n    },\n  ],\n};\n
"},{"location":"modules/platform/codecommit/#codebuild-examples","title":"CodeBuild examples","text":"

Create a repository with a buildspec.yml file in it. This repository will be your BuildProject job repository to run Renovate on your repositories.

"},{"location":"modules/platform/codecommit/#renovate-docker-buildspecyml","title":"Renovate Docker buildspec.yml","text":"Example buildspec.yml file
version: 0.2\nenv:\n  shell: bash\n  git-credential-helper: yes\n  variables:\n    RENOVATE_PLATFORM: 'codecommit'\n    RENOVATE_REPOSITORIES: '[\"repoName1\", \"repoName2\"]'\n    RENOVATE_CONFIG: '{\"extends\":[\"config:recommended\"]}'\n    LOG_LEVEL: 'debug'\n    AWS_REGION: 'us-east-1'\nphases:\n  build:\n    on-failure: CONTINUE\n    commands:\n      - docker run --rm -e AWS_REGION -e RENOVATE_CONFIG -e RENOVATE_PLATFORM -e RENOVATE_REPOSITORIES -e LOG_LEVEL renovate/renovate\n
"},{"location":"modules/platform/codecommit/#renovate-cli-buildspecyml","title":"Renovate CLI buildspec.yml","text":"Example buildspec.yml file
version: 0.2\nenv:\n  shell: bash\n  git-credential-helper: yes\n  variables:\n    RENOVATE_PLATFORM: 'codecommit'\n    RENOVATE_REPOSITORIES: '[\"repoName1\", \"repoName2\"]'\n    RENOVATE_CONFIG: '{\"extends\":[\"config:recommended\"]}'\n    LOG_LEVEL: 'debug'\n    AWS_REGION: 'us-east-1'\nphases:\n  build:\n    on-failure: CONTINUE\n    commands:\n      - npm install -g renovate\n      - renovate\n
"},{"location":"modules/platform/codecommit/#notes","title":"Notes","text":"

To keep BuildProject processing times reasonable, we recommend that you install Renovate on the BuildProject Renovate job repository. This also avoids running the npm install command.

You can add the config.js global config to the repository.

You can add the BuildProject repository to the RENOVATE_REPOSITORIES variable and get updates on new Renovate versions.

"},{"location":"modules/platform/forgejo/","title":"Forgejo","text":"

Renovate supports Forgejo.

"},{"location":"modules/platform/forgejo/#authentication","title":"Authentication","text":"

First, create a Personal Access Token (PAT) for the Renovate account. The Renovate account should have full name and email address configured. Then let Renovate use your PAT by doing one of the following:

You must set platform=forgejo in your Renovate config file.

The PAT should have these permissions:

Scope Permission Valid for Forgejo versions Notes repo Read and Write all user Read all issue Read and Write >= 1.20.0 organization Read >= 1.20.0 Required to read org labels and teams email Read <= 1.19.3 misc Read Only for 1.20.0 and 1.20.1

If you use Forgejo packages, add the read:packages scope.

"},{"location":"modules/platform/forgejo/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":""},{"location":"modules/platform/forgejo/#features-awaiting-implementation","title":"Features awaiting implementation","text":""},{"location":"modules/platform/forgejo/#repo-autodiscover","title":"Repo autodiscover","text":"

Renovate can discover repositories on Forgejo using the autodiscover feature. Repositories are ignored when one of the following conditions is met:

You can change the default server-side sort method and order for autodiscover API. Set those via autodiscoverRepoSort and autodiscoverRepoOrder. Read the Forgejo swagger docs for more details.

"},{"location":"modules/platform/forgejo/#merge-style","title":"Merge style","text":"

Renovate uses the repository's default merge style if allowed; if the default merge style is not an allowed merge style, renovate falls back to an allowed merge style as per an order chosen to minimize commits. If no merge style is allowed, the repository is blocked.

"},{"location":"modules/platform/gerrit/","title":"Gerrit","text":"

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

"},{"location":"modules/platform/gerrit/#supported-gerrit-versions","title":"Supported Gerrit versions","text":"

Renovate supports all Gerrit 3.x versions.

Support for Gerrit is currently experimental, meaning that it might still have some undiscovered bugs or design limitations, and that we might need to change functionality in a non-backwards compatible manner in a non-major release.

Renovate stores its metadata in the commit message footer.

"},{"location":"modules/platform/gerrit/#authentication","title":"Authentication","text":"First, create a HTTP access token for the Renovate account.

Let Renovate use your HTTP access token by doing one of the following:

The Gerrit user account must be allowed to assign the Code-Review label with \"+2\" to their own changes for \"automerge\" to work.

You must set platform=gerrit in your Renovate config file.

"},{"location":"modules/platform/gerrit/#renovate-prbranch-model-with-gerrit-and-needed-permissions","title":"Renovate PR/Branch-Model with Gerrit and needed permissions","text":"

If you use the \"Code-Review\" label and want to get automerge working then you must set autoApprove=true in your Renovate config. Renovate will now add the Code-Review label with the value \"+2\" to each of its \"pull requests\" (Gerrit-Change).

Note

The Renovate user account must have permission to give +2 for the Code-Review label.

The Renovate option automergeType: \"branch\" makes no sense for Gerrit, because there are no branches used to create pull requests. It works similar to the default option \"pr\".

"},{"location":"modules/platform/gerrit/#optional-features","title":"Optional features","text":"

You can use the statusCheckNames configuration to map any of the available branch checks (like minimumReleaseAge, mergeConfidence, and so on) to a Gerrit label.

For example, if you want to use the Merge Confidence feature and map the result of the Merge Confidence check to your Gerrit label \"Renovate-Merge-Confidence\" you can configure:

{\n  \"statusCheckNames\": {\n    \"mergeConfidence\": \"Renovate-Merge-Confidence\"\n  }\n}\n

Also, labels in renovate.json will be mapped to hashtags in Gerrit. Example:

{\n  \"packageRules\": [\n    {\n      \"matchDepTypes\": [\"devDependencies\"],\n      \"labels\": [\"renovate:devDependencies\"]\n    }\n  ]\n}\n
"},{"location":"modules/platform/gerrit/#server-version-dependent-features","title":"Server version dependent features","text":"

We use the Gerrit Get Version REST API to fetch the server version. You can use the experimental feature flag RENOVATE_X_PLATFORM_VERSION to set a specific server version. By setting the server version yourself, you save an API call that fetches the server version.

"},{"location":"modules/platform/gerrit/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":""},{"location":"modules/platform/gitea/","title":"Gitea","text":"

Renovate supports Gitea.

Note

Use forgejo as the platform if you are using Forgejo. Forgejo support will be removed from gitea platform in a future release.

"},{"location":"modules/platform/gitea/#authentication","title":"Authentication","text":"

First, create a Personal Access Token (PAT) for the Renovate account. The Renovate account should have full name and email address configured. Then let Renovate use your PAT by doing one of the following:

You must set platform=gitea in your Renovate config file.

The PAT should have these permissions:

Scope Permission Valid for Gitea versions Notes repo Read and Write all user Read all issue Read and Write >= 1.20.0 organization Read >= 1.20.0 Required to read org labels and teams email Read <= 1.19.3 misc Read Only for 1.20.0 and 1.20.1

If you use Gitea packages, add the read:packages scope.

"},{"location":"modules/platform/gitea/#unsupported-platform-featuresconcepts","title":"Unsupported platform features/concepts","text":""},{"location":"modules/platform/gitea/#features-awaiting-implementation","title":"Features awaiting implementation","text":""},{"location":"modules/platform/gitea/#repo-autodiscover","title":"Repo autodiscover","text":"

Renovate can discover repositories on Gitea using the autodiscover feature. Repositories are ignored when one of the following conditions is met:

You can change the default server-side sort method and order for autodiscover API. Set those via autodiscoverRepoSort and autodiscoverRepoOrder. Read the Gitea swagger docs for more details.

"},{"location":"modules/platform/gitea/#merge-style","title":"Merge style","text":"

Renovate uses the repository's default merge style if allowed; if the default merge style is not an allowed merge style, renovate falls back to an allowed merge style as per an order chosen to minimize commits. If no merge style is allowed, the repository is blocked.

"},{"location":"modules/platform/github/","title":"GitHub and GitHub Enterprise Server","text":"

Most of the information on this page is meant for users who want to self-host Renovate on GitHub or GitHub Enterprise Server.

"},{"location":"modules/platform/github/#easiest-way-to-run-renovate","title":"Easiest way to run Renovate","text":"

For users on GitHub Cloud (github.com), the easiest way to get started is to install the Mend Renovate app from the GitHub marketplace. When you use the app, Mend will:

If you self-host Renovate you must do the things listed above yourself. Self-hosting is meant for users with advanced use cases, or who want to be in full control of Renovate and the environment it runs in. We recommend most users install the Mend Renovate app.

Read the Security and Permissions page to learn about the Security and Permissions needed for the Mend Renovate app.

After you installed the hosted app, please read the reading list to learn how to use and configure Renovate.

"},{"location":"modules/platform/github/#authentication","title":"Authentication","text":"

First, create a fine-grained or a classic PAT. The PAT must have the repo scope. If you want Renovate to also update your GitHub Action files, you must grant the workflow scope.

Read the GitHub Docs, about Personal Access Tokens to learn more about PATs.

Let Renovate use your PAT by doing one of the following:

Remember to set platform=github somewhere in your Renovate config file.

If you use GitHub Enterprise Server then endpoint must point to https://github-enterprise.example.com/api/v3/. You can choose where you want to set endpoint:

Labels and forking mode

If you're self-hosting Renovate on GitHub.com with GitHub Actions in forking mode, and want Renovate to apply labels then you must give the PAT triage level rights on issues. The triage level allows the PAT to apply/dismiss existing labels.

"},{"location":"modules/platform/github/#running-using-a-fine-grained-token","title":"Running using a fine-grained token","text":""},{"location":"modules/platform/github/#permissions","title":"Permissions","text":"

A fine-grained token must have these permissions:

Permission Access Level Members Read-only Organization Commit statuses Read and write Repository or Organization Contents Read and write Repository or Organization Dependabot alerts Read-only Repository or Organization Issues Read and write Repository or Organization Pull requests Read and write Repository or Organization Workflows Read and write Repository or Organization

Use a dedicated role account

Consider creating a GitHub App to use instead of using your own GitHub user account.

"},{"location":"modules/platform/github/#running-as-a-github-app","title":"Running as a GitHub App","text":"

Instead of a dedicated account with a Personal Access Token you can run renovate as a self-hosted GitHub App.

When creating the GitHub App give it the following permissions:

Repository permissions

Permission Access Administration read Checks read + write Commit statuses read + write Contents read + write Dependabot alerts read Issues read + write Merge queues read + write Metadata read Pull requests read + write Workflows read + write

The Merge queues permission is needed to enqueue pull requests when the repository uses a merge queue.

Organization permissions

Permission Access Members read

Other values like Homepage URL, User authorization callback URL and webhooks can be disabled or filled with dummy values.

Inside your config.js you need to set the following values, assuming the name of your app is self-hosted-renovate:

token:\"ghs_123exampletoken\"

You must use a GitHub App Installation token.

Previously, the token had to be prefixed with x-access-token:. We recommend you replace any prefixed tokens with normal tokens. We will drop support for prefixed tokens in the future.

Any tokens that do not start with ghs_ (for example tokens from GitHub Enterprise Server versions before version 3.2) must be prefixed with x-access-token:.

Note

The installation tokens expire after 1 hour and need to be regenerated regularly. Alternatively as environment variable RENOVATE_TOKEN, or via CLI --token=.

Third-party tools to regenerate installation tokens

If you're self-hosting Renovate within a GitHub Actions workflow, then you can use the actions/create-github-app-token action. If you use Node.js/CLI, then you can use the github-app-installation-token package. If you use Docker, then you can use the mshekow/github-app-installation-token image.

repositories: [\"orgname/repo-1\",\"orgname/repo-2\"]

List of repositories to run on. Alternatively as comma-separated environment variable RENOVATE_REPOSITORIES. The GitHub App installation token is scoped at most to a single organization and running on multiple organizations requires multiple invocations of renovate with different token and repositories parameters.

username:\"self-hosted-renovate[bot]\" (optional, autodetected if not supplied)

The slug name of your app with [bot] appended

gitAuthor:\"Self-hosted Renovate <123456+self-hosted-renovate[bot]@users.noreply.github.enterprise.com>\" (optional, autodetected if not supplied)

The GitHub App associated email to match commits to Renovate. It needs to have the user id and the username followed by the users.noreply.-domain of either github.com or the GitHub Enterprise Server. A way to get the user id of a GitHub app is to query the user API at api.github.com/users/self-hosted-renovate[bot] (github.com) or github.enterprise.com/api/v3/users/self-hosted-renovate[bot] (GitHub Enterprise Server).

"},{"location":"modules/platform/github/#package-registry-credentials","title":"Package Registry Credentials","text":"

When Renovate runs against repositories on github.com, and the environment variable RENOVATE_X_GITHUB_HOST_RULES is set, then Renovate automatically provisions hostRules for these GitHub Packages registries using the platform token:

Warning

We reverted the Package Registry Credentials feature to experimental mode, because users reported it's not working correctly with app tokens.

"},{"location":"modules/platform/gitlab/","title":"GitLab","text":""},{"location":"modules/platform/gitlab/#easiest-way-to-run-renovate","title":"Easiest way to run Renovate","text":"

For users on GitLab.com, the easiest way to get started is to install the Mend-hosted Renovate app by following these instructions when logging into the Mend Developer Platform. When you use the app, Mend will:

If you self-host Renovate you must do the things listed above yourself. Self-hosting is meant for users with advanced use cases, or who want to be in full control of the bot and the environment it runs in. We recommend most users install the Mend-hosted app.

Read the GitLab security page to learn about the security model for both the Mend-hosted app and self-hosted deployments.

After you installed the hosted app, please read the reading list to learn how to use and configure Renovate.

"},{"location":"modules/platform/gitlab/#authentication","title":"Authentication","text":"

You can authenticate Renovate to GitLab, with one of these methods:

"},{"location":"modules/platform/gitlab/#three-ways-to-authenticate-choose-one","title":"Three ways to authenticate, choose one","text":"

To start, create either:

"},{"location":"modules/platform/gitlab/#renovate-account-or-token-must-have-at-least-developer-role","title":"Renovate account or token must have at least developer role","text":"

The Renovate account, or token, must have at least the Developer role. The developer role allows Renovate to create issues and merge requests.

"},{"location":"modules/platform/gitlab/#if-you-want-renovate-to-automerge-give-appropriate-permissions","title":"If you want Renovate to automerge, give appropriate permissions","text":"

If you are using automerge, the Renovate account, or token, must have the appropriate \"Allowed to merge\" permission on the protected branch of your projects.

"},{"location":"modules/platform/gitlab/#if-only-maintainers-are-allowed-to-merge-give-maintainer-role","title":"If only maintainers are allowed to merge, give Maintainer role","text":"

If merging is restricted to Maintainers, the Renovate account or token must have the Maintainer role.

"},{"location":"modules/platform/gitlab/#setting-up-project-access-tokens-or-group-access-tokens","title":"Setting up Project Access Tokens or Group Access Tokens","text":"

If you are using a project access token, or a group access token, GitLab creates an internal bot user for you. This bot user is the one that will be used to create merge requests and issues.

Use the name and email of this bot user to configure Renovate when verifing users using push rules. For group access tokens, an expiration date is required, unlike project access tokens where it is optional.

To keep using the same GitLab-generated bot account you must rotate/refresh the Group Access Token before the token's expiry date.

We refer to personal access tokens, project access tokens and group access tokens as access tokens in the instructions that follow.

"},{"location":"modules/platform/gitlab/#permissions-for-access-tokens-on-real-runs","title":"Permissions for access tokens on real runs","text":"

For real runs, give the access token these scopes:

"},{"location":"modules/platform/gitlab/#permissions-for-access-tokens-on-dry-runs","title":"Permissions for access tokens on dry runs","text":"

For dry runs, give the access token these scopes:

"},{"location":"modules/platform/gitlab/#letting-renovate-use-your-access-token","title":"Letting Renovate use your access token","text":"

Let Renovate use your access token by doing one of the following:

"},{"location":"modules/platform/gitlab/#set-platformgitlab-in-your-renovate-config-file","title":"Set platform=gitlab in your Renovate config file","text":"

Remember to set platform=gitlab somewhere in your Renovate config file.

"},{"location":"modules/platform/gitlab/#setting-up-renovate-for-a-private-gitlab-container-registry","title":"Setting up Renovate for a Private Gitlab container registry","text":"

If you use a private GitLab container registry, you must:

You may also use a dedicated Deploy Token instead of using RENOVATE_TOKEN as the password in the above host rule example.

"},{"location":"modules/platform/gitlab/#get-colored-output","title":"Get colored output","text":"

You may want to set FORCE_COLOR: 3 to the job, in order to get colored output. GitLab Runner runs the container\u2019s shell in non-interactive mode, so the shell\u2019s TERM environment variable is set to dumb.

"},{"location":"modules/platform/gitlab/#features-awaiting-implementation","title":"Features awaiting implementation","text":""},{"location":"modules/platform/gitlab/#server-version-dependent-features","title":"Server version dependent features","text":"

We use the GitLab version API to fetch the server version. You can use the experimental feature flag RENOVATE_X_PLATFORM_VERSION to set a specific server version. By setting the server version yourself, you save a API call that fetches the server version.

"},{"location":"modules/platform/gitlab/#multiple-merge-request-assignees","title":"Multiple merge request assignees","text":"

Multiple assignees are only available on GitLab Premium and Ultimate tiers. Because of a safeguard in GitLab's API if multiple assignees are set, but not available to the project, only the first assignee will be applied.

"},{"location":"modules/platform/gitlab/#verifying-users-using-push-rules","title":"Verifying users using push rules","text":"

When verifying users using push rules, you must use the name and email of the bot user for gitAuthor.

"},{"location":"modules/platform/gitlab/#repo-autodiscover","title":"Repo autodiscover","text":"

Renovate can discover repositories on GitLab using the autodiscover feature.

You can change the default server-side sort method and order for autodiscover API. Set those via autodiscoverRepoSort and autodiscoverRepoOrder. Read the GitLab Projects API docs for more details.

"},{"location":"modules/platform/local/","title":"Local","text":"

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

With the \"local\" platform you can perform dry runs of Renovate against the local file system. This can be handy when testing a new Renovate configuration for example.

"},{"location":"modules/platform/local/#usage","title":"Usage","text":"

Run the renovate --platform=local command in the directory you want Renovate to run in. In this mode, Renovate defaults to dryRun=lookup. You can override this by passing --dry-run=extract to stop after the extract phase. Other dryRun values (such as full) are not supported on the local platform and fall back to lookup.

Avoid giving \"repositories\" arguments, as this command can only run in a single directory, and it can only run in the current working directory.

You may run the command above on \"plain\" directories, or \"Git directories\". You don't need to provide any config, as the command will run with or without \"repo config\".

The command doesn't do any \"compare\" - or before and after analysis - if you want to test a new config then you must manually compare.

"},{"location":"modules/platform/local/#limitations","title":"Limitations","text":""},{"location":"modules/platform/scm-manager/","title":"SCM-Manager","text":"

This feature is flagged as experimental

Experimental features might be changed or even removed at any time.

Renovate supports the SCM-Manager platform. This platform is considered experimental.

"},{"location":"modules/platform/scm-manager/#authentication","title":"Authentication","text":"
  1. Create an API Key for your technical Renovate user in SCM-Manager
  2. The technical user must have a valid name and email address
  3. Put the API key in the RENOVATE_TOKEN environment variable, so that Renovate can use it
"},{"location":"modules/platform/scm-manager/#set-correct-platform","title":"Set correct platform","text":"

You must set the platform config option to scm-manager in your admin config file.

"},{"location":"modules/platform/scm-manager/#set-permissions","title":"Set permissions","text":"

The technical user must have the permissions to:

  1. read the repository
  2. pull/checkout the repository
  3. push/commit the repository
  4. create pull requests for the repository

Those permissions can be granted on a repository level within the permission settings of each repository.

"},{"location":"modules/platform/scm-manager/#install-review-plugin","title":"Install Review Plugin","text":"

To let Renovate access the Pull Request API, you must install the Review Plugin with at least version 3.11.0. Find the list of available plugins by going to Administration \u2192 Plugins \u2192 Available.

"},{"location":"modules/platform/scm-manager/#supported-versions-of-scm-manager","title":"Supported versions of SCM-Manager","text":"

Renovate supports SCM-Manager major version 3.x. The minimum version for the 3.x range is 3.10.0.

"},{"location":"modules/platform/scm-manager/#automerge","title":"Automerge","text":"

Currently, the Renovate automerge feature is not supported by the SCM-Manager platform. Every pull request requires merging them manually for now.

"},{"location":"modules/versioning/","title":"Versioning","text":"

Versioning is one of Renovate's core \"module\" types. The other modules are Platform, Manager and Datasource. Renovate uses the version module to answer questions such as:

How Renovate uses its core modules during a run:

  1. Renovate's Manager module extracts the dependencies
  2. Renovate's Datasource finds the versions of the dependencies
  3. Renovate's Versioning scheme sorts and filters the results

The \"versioning\" chosen can be different per package manager, because different package managers use different versioning schemes. For example, npm uses 1.0.0-beta.1 while pip uses 1.0.0b1.

"},{"location":"modules/versioning/#why-you-might-need-to-manually-configure-versioning","title":"Why you might need to manually configure versioning","text":"

Renovate interprets versions correctly out-of-the-box most of the time. But Renovate can't automatically detect all versioning schemes. So sometimes you need to tell Renovate what versioning scheme it should use.

For some ecosystems, automatic version selection works nearly every time (e.g. for npm-compliant managers, use npm versioning). For other ecosystems such as Docker or GitHub tags, there is no consistent convention for versions, so the default choice may not always work. For example some Docker images may use SemVer, some PEP440, some Calendar Versioning, etc.

If the automatic version selection does not work for a dependency update: set the versioning for that dependency in the Renovate config file.

"},{"location":"modules/versioning/#general-concepts-behind-overriding-versioning","title":"General concepts behind overriding versioning","text":""},{"location":"modules/versioning/#examples-of-versioning-overrides","title":"Examples of versioning overrides","text":""},{"location":"modules/versioning/#overriding-docker-versioning-to-use-a-versioning-specific-for-a-package","title":"Overriding Docker versioning to use a versioning specific for a package","text":"

The configuration below overrides Renovate's default docker versioning for the python Docker image and instead uses the pep440 versioning scheme to evaluate versions.

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"python\"],\n      \"versioning\": \"pep440\"\n    }\n  ]\n}\n
"},{"location":"modules/versioning/#using-a-custom-regex-versioning-scheme","title":"Using a custom regex versioning scheme","text":"
{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"foo/bar\"],\n      \"versioning\": \"regex:^(?<compatibility>.*)-v?(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)?$\"\n    }\n  ]\n}\n
"},{"location":"modules/versioning/#breaking-changes","title":"Breaking Changes","text":"

In most ecosystems, especially SemVer, major upgrades are treated as breaking changes. But other updates may have breaking changes too, for example:

It can be tempting to propose ideas like \"let's treat minor updates of Python as major updates\" but that is swapping one problem for a worse problem. The definitions of major and minor should not be redefined and broken in order to shoehorn in the related concept of \"breaking change\". Instead, Renovate has the concept of isBreaking, which can be decided independently of updateType.

Here's an example of grouping all non-breaking updates together:

{\n  \"packageRules\": [\n    {\n      \"description\": \"Group non-breaking updates\",\n      \"matchUpdateTypes\": [\"minor\", \"patch\", \"digest\"],\n      \"matchJsonata\": [\"isBreaking != true\"],\n      \"groupName\": \"Non-breaking updates\"\n    }\n  ]\n}\n
"},{"location":"modules/versioning/#supported-versioning","title":"Supported Versioning","text":"

Supported values for versioning are:

"},{"location":"modules/versioning/apk/","title":"Alpine Package Keeper (APK) Versioning","text":""},{"location":"modules/versioning/apk/#identifier","title":"Identifier","text":"

apk

"},{"location":"modules/versioning/apk/#references","title":"References","text":""},{"location":"modules/versioning/apk/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, pin, replace

"},{"location":"modules/versioning/apk/#description","title":"Description","text":"

Alpine Package Keeper (APK) versioning is used for packages served from APK repositories, such as the official Alpine Linux repositories or the Wolfi APK package repository

This implementation follows the Alpine Linux Package versions for version formatting.

Versions are similar to other Linux distributions, e.g. 3.2.1-r0

"},{"location":"modules/versioning/apk/#version-format-examples","title":"Version Format Examples","text":""},{"location":"modules/versioning/apk/#pre-release-handling","title":"Pre-release Handling","text":""},{"location":"modules/versioning/apk/#version-constraints","title":"Version constraints","text":"

Constraints follow apk-world(5), which builds the operator from its characters, so the characters may be given in any order and may repeat. This means ~, =~ and ~= all mean the same thing.

Operator Meaning (none) exact version = exact version < less than <= less than or equal > greater than >= greater than or equal ~ prefix match >~ greater than or prefix match <~ less than or prefix match

A prefix match compares token by token rather than by string, so ~1.6 matches 1.6, 1.6.0_pre1, 1.6.0, 1.6.5 and 1.6.9_p1, but not 1.60. Because a revision is a token of its own, ~8.12.1 matches every 8.12.1-rN, which is how Wolfi and Chainguard images commonly pin their packages.

Renovate keeps the precision a prefix constraint was written with, so ~8.12.1 becomes ~8.13.0 rather than ~8.13.0-r0, and ~8.12 becomes ~8.13.

With rangeStrategy=bump, Renovate raises a lower bound which includes its boundary to the new version, so >=8.12.1 becomes >=8.13.0-r0 and >~8.12 becomes >~8.13.0-r0. A bare > is left alone, as >8.13.0-r0 would exclude the very version it was bumped to, and < and <= are upper bounds so there is nothing to raise.

Otherwise Renovate does not propose a replacement for the <, <=, >, >=, >~ and <~ operators, as there is no single obvious new bound for them. The >< operator constrains a package to an identity hash rather than to a version, so it is not a version constraint Renovate can resolve.

"},{"location":"modules/versioning/aws-eks-addon/","title":"aws-eks-addon Versioning","text":""},{"location":"modules/versioning/aws-eks-addon/#identifier","title":"Identifier","text":"

aws-eks-addon

"},{"location":"modules/versioning/aws-eks-addon/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/aws-eks-addon/#description","title":"Description","text":"

AWS versioning syntax is used for EKS Addon updates.

It is based off Semantic Versioning 2.0 but with a subset of addon build metadata syntax.

At the moment every ESK Addon that matches the regex ^v?\\d+\\.\\d+\\.\\d+-eksbuild\\.\\d+$ is considered a valid \"release\".

Key Points about EKS Addon Versioning

  1. Versioning Scheme: Add-ons typically follow a semantic versioning scheme (e.g., Major.Minor.Patch). This helps in understanding the significance of changes between versions:

  2. Default Versions: When creating a new EKS cluster, AWS often selects a default version for each addon based on the cluster's Kubernetes version and other factors. This default version is usually the most stable and recommended for the specific cluster configuration

  3. Build metadata. Example eksbuild.1. The eksbuild.1 part signifies a specific build or release within the 1.19.0 version, likely managed by the EKS build system. It helps differentiate this particular release from others that might have been built independently. The build metadata provides additional context about the specific release, which can be useful for tracking and troubleshooting.

"},{"location":"modules/versioning/aws-machine-image/","title":"aws-machine-image Versioning","text":""},{"location":"modules/versioning/aws-machine-image/#identifier","title":"Identifier","text":"

aws-machine-image

"},{"location":"modules/versioning/aws-machine-image/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/aws-machine-image/#description","title":"Description","text":"

Renovate's AWS Machine Image versioning is a kind of hack to support Amazon Machine Images (AMI) updates.

At the moment every AMI that matches the regex ^ami-[a-z0-9]{17}$ is considered a valid \"release\".

"},{"location":"modules/versioning/azure-rest-api/","title":"azure-rest-api Versioning","text":""},{"location":"modules/versioning/azure-rest-api/#identifier","title":"Identifier","text":"

azure-rest-api

"},{"location":"modules/versioning/azure-rest-api/#references","title":"References","text":""},{"location":"modules/versioning/azure-rest-api/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/azure-rest-api/#description","title":"Description","text":"

The Azure REST APIs use a YYYY-MM-DD version with an optional -preview suffix: https://github.com/microsoft/api-guidelines/blob/vNext/azure/Guidelines.md#api-versioning

Internally at Microsoft they are using other additional suffixes: https://github.com/Azure/bicep/blob/a1d217e3bb3d049fc5c6c21b466c3a29585a6c69/src/Bicep.Core/Analyzers/Linter/ApiVersions/ApiVersionHelper.cs#L15

"},{"location":"modules/versioning/bazel-module/","title":"Bazel Module Versioning","text":""},{"location":"modules/versioning/bazel-module/#identifier","title":"Identifier","text":"

bazel-module

"},{"location":"modules/versioning/bazel-module/#references","title":"References","text":""},{"location":"modules/versioning/bazel-module/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/cargo/","title":"Cargo Versioning","text":""},{"location":"modules/versioning/cargo/#identifier","title":"Identifier","text":"

cargo

"},{"location":"modules/versioning/cargo/#references","title":"References","text":""},{"location":"modules/versioning/cargo/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, replace, pin

"},{"location":"modules/versioning/cargo/#description","title":"Description","text":"

Cargo versioning uses Semantic Versioning 2.0.

Cargo supports ranges in a similar manner to npm, but not identical. The important differences are:

Use of commas

Multiple version requirements can also be separated with a comma, e.g. >= 1.2, < 1.5. We interpret this to mean AND.

No exact versions unless using equals =

In Cargo, 1.2.3 doesn't mean \"exactly 1.2.3\", it actually means >=1.2.3 <2.0.0. So this is like the equivalent of ^1.2.3 in npm.

"},{"location":"modules/versioning/composer/","title":"Composer Versioning","text":""},{"location":"modules/versioning/composer/#identifier","title":"Identifier","text":"

composer

"},{"location":"modules/versioning/composer/#references","title":"References","text":""},{"location":"modules/versioning/composer/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, update-lockfile

"},{"location":"modules/versioning/composer/#description","title":"Description","text":"

Composer uses Semver-like versioning, but some package authors may use versions that are not completely valid, e.g. 1.2 instead of 1.2.0.

Composer supports ranges in a similar manner to npm, but not identical. The main difference is with tilde ranges.

Tilde ranges with \"short\" versions are different to npm. e.g.

~4 is equivalent to ^4 in npm ~4.1 is equivalent to ^4.1 in npm ~0.4 is equivalent to >=0.4 <1 in npm

Composer supports patches in the version numbers, which are considered stable. E.g., 1.2.3-p1 is recognized by npm as unstable, Renovate implements additional logic to support correct sorting and stability checks on composer patch versions syntax.

"},{"location":"modules/versioning/conan/","title":"conan Versioning","text":""},{"location":"modules/versioning/conan/#identifier","title":"Identifier","text":"

conan

"},{"location":"modules/versioning/conan/#references","title":"References","text":""},{"location":"modules/versioning/conan/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: auto, bump, widen, replace

"},{"location":"modules/versioning/conan/#description","title":"Description","text":"

Conan versioning supports Semantic Versioning 2.0 but some packages don't follow this specification.

Conan implements python-node-semver.

Read the Conan docs about version ranges for more information.

syntax description 5.45 Equivalent to 5.45 16.00 Equivalent to 16.00 2.8.3 Equivalent to 2.8.3 [>1.1 <2.1] Keep version within range [2.8] Equivalent to =2.8 [~=3.0] Compatible, according to SemVer [>1.1 \\|\\| 0.8] Conditions can be OR'ed [1.2.7 \\|\\| >=1.2.9 <2.0.0] This range would match the versions 1.2.7, 1.2.9, and 1.4.6, but not the versions 1.2.8 or 2.0.0 [>1.1 <2.1, include_prerelease=True] Would e.g. accept 2.0.0-pre.1 as match [~1.2.3, loose=False] Would only accept correct Semantic Versioning strings. E.g. version 1.2.3.4 would not be accepted [~1.2.3, loose=False, include_prerelease=True] Both options can be used for the same version range"},{"location":"modules/versioning/conda/","title":"conda Versioning","text":""},{"location":"modules/versioning/conda/#identifier","title":"Identifier","text":"

conda

"},{"location":"modules/versioning/conda/#references","title":"References","text":""},{"location":"modules/versioning/conda/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, pin

"},{"location":"modules/versioning/conda/#description","title":"Description","text":"

Conda versioning uses pep440-extended version syntax.

More details: conda version spec

"},{"location":"modules/versioning/deb/","title":"Deb version Versioning","text":""},{"location":"modules/versioning/deb/#identifier","title":"Identifier","text":"

deb

"},{"location":"modules/versioning/deb/#references","title":"References","text":""},{"location":"modules/versioning/deb/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/deb/#description","title":"Description","text":"

Deb versioning compares versions like package managers on Debian-based Linux distributions compare packages (dpkg, apt). Deb versioning supports complicated version numbers, including alphabetical characters almost everywhere. Similar to our \"loose\" versioning, deb versioning is a \"best effort\" attempt to convert deb versions to SemVer fields like major, minor, patch.

"},{"location":"modules/versioning/debian/","title":"Debian Versioning","text":""},{"location":"modules/versioning/debian/#identifier","title":"Identifier","text":"

debian

"},{"location":"modules/versioning/debian/#references","title":"References","text":""},{"location":"modules/versioning/debian/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: replace

"},{"location":"modules/versioning/debian/#description","title":"Description","text":"

Debian versioning is used for Debian container images that are referenced by their major release version or a codename.

Versions to which this scheme applies are e.g. 11 and bullseye. Container image tags such as 11-slim, 11.4 or 11.4-slim, bullseye-20220822 or bullseye-backports are not compliant with the current implementation.

"},{"location":"modules/versioning/deno/","title":"deno Versioning","text":""},{"location":"modules/versioning/deno/#identifier","title":"Identifier","text":"

deno

"},{"location":"modules/versioning/deno/#references","title":"References","text":""},{"location":"modules/versioning/deno/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, pin, replace

"},{"location":"modules/versioning/deno/#description","title":"Description","text":"

deno versioning is a well known implementation of Semantic Versioning 2.0.

"},{"location":"modules/versioning/devbox/","title":"devbox Versioning","text":""},{"location":"modules/versioning/devbox/#identifier","title":"Identifier","text":"

devbox

"},{"location":"modules/versioning/devbox/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/devbox/#description","title":"Description","text":"

Devbox's Nixhub uses fairly strict versioning, characters such as ~, ^ and >= are not allowed. The semver values must not include \"*\" or \"x\". \"1.2.3\" \"1.2\" and \"1\" are the only valid formats.

"},{"location":"modules/versioning/docker/","title":"Docker Versioning","text":""},{"location":"modules/versioning/docker/#identifier","title":"Identifier","text":"

docker

"},{"location":"modules/versioning/docker/#references","title":"References","text":""},{"location":"modules/versioning/docker/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/docker/#description","title":"Description","text":"

Docker images don't really have versions, instead they have \"tags\". Tags are often used by Docker image authors as a form of versioning.

Renovate tries to follow the most common conventions that are used to tag Docker images. In particular, Renovate treats the text after the first hyphen as a type of platform/compatibility indicator.

For example, many images have releases with the -alpine suffix. The official node Docker image has tags like 12.15.0-alpine which is not compatible with 12.15.0 or 12.15.0-stretch. Users on -alpine don't want updates to 12.16.0 or 12.16.0-stretch. Those users only want upgrades to 12.16.0-alpine and not 12.16.0 or 12.16.0-stretch.

Similarly, a user on 12.14 expects to be upgraded to 12.15 and not 12.15.0.

What type of versioning is used?

Docker image authors can use whatever tag they want, it's a \"wild west\". Docker tags don't always follow SemVer. This means that Renovate tries to accept and sort SemVer-like versions, but this won't always work.

You may need to help Renovate and create your own rules for some Docker images. For example:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"badly-versioned-docker-image\"],\n      \"versioning\": \"loose\"\n    }\n  ]\n}\n

Are ranges supported?

No. You may think a tag like 12.15 also means 12.15.x, but it's a tag of its own. The 12.15 tag may or may not point to any of the available 12.15.x tags, including 12.15.0.

Are commit hashes supported?

No, Renovate ignores Docker image tags that look like a Git commit hash.

"},{"location":"modules/versioning/elm/","title":"Elm Versioning","text":""},{"location":"modules/versioning/elm/#identifier","title":"Identifier","text":"

elm

"},{"location":"modules/versioning/elm/#references","title":"References","text":""},{"location":"modules/versioning/elm/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/elm/#description","title":"Description","text":"

Elm enforces strict Semantic Versioning at the compiler level, automatically detecting API changes and requiring appropriate version bumps.

Ranges

Elm packages use range constraints in the format 1.0.0 <= v < 2.0.0, where the lower bound is inclusive and the upper bound is exclusive.

Exact versions

Elm applications use exact versions like 1.0.0 in their elm.json files.

Both exact versions and ranges are fully supported.

"},{"location":"modules/versioning/exact/","title":"Exact Versioning","text":""},{"location":"modules/versioning/exact/#identifier","title":"Identifier","text":"

exact

"},{"location":"modules/versioning/exact/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/exact/#description","title":"Description","text":"

Exact versioning treats any non-empty string as a valid version. It only guarantees strict string equality \u2014 a version matches only itself and is never considered greater than another.

This is useful for dependencies like GitHub Actions where each tag represents a specific feature, and only the digest should be updated while keeping the tag unchanged.

"},{"location":"modules/versioning/git/","title":"git Versioning","text":""},{"location":"modules/versioning/git/#identifier","title":"Identifier","text":"

git

"},{"location":"modules/versioning/git/#references","title":"References","text":""},{"location":"modules/versioning/git/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/git/#description","title":"Description","text":"

Renovate's Git versioning is a kind of hack to support Git submodule updating.

"},{"location":"modules/versioning/github-actions/","title":"GitHub Actions Versioning","text":""},{"location":"modules/versioning/github-actions/#identifier","title":"Identifier","text":"

github-actions

"},{"location":"modules/versioning/github-actions/#references","title":"References","text":""},{"location":"modules/versioning/github-actions/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: pin, replace

"},{"location":"modules/versioning/github-actions/#description","title":"Description","text":"

Versioning specific to GitHub Actions' usage of Semantic Versioning, for mutable and immutable tags.

The \"shortest\" tag will be used where possible - if you are previously using v7, and there is an upgrade to v7.5.3, v7 will be used.

"},{"location":"modules/versioning/github-actions/#immutable-tags","title":"Immutable Tags","text":"

When using Immutable Releases for GitHub Tags, it is required to use explicit SemVer major.minor.patch versions.

If you have previously used an unpinned version, such as @v7, Renovate will migrate you on the next update, such as:

-       uses: astral-sh/setup-uv@v7\n+       uses: astral-sh/setup-uv@v10.3.2\n
"},{"location":"modules/versioning/glasskube/","title":"glasskube Versioning","text":""},{"location":"modules/versioning/glasskube/#identifier","title":"Identifier","text":"

glasskube

"},{"location":"modules/versioning/glasskube/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/go-mod-directive/","title":"Go Modules Directive Versioning","text":""},{"location":"modules/versioning/go-mod-directive/#identifier","title":"Identifier","text":"

go-mod-directive

"},{"location":"modules/versioning/go-mod-directive/#references","title":"References","text":""},{"location":"modules/versioning/go-mod-directive/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, replace

"},{"location":"modules/versioning/go-mod-directive/#description","title":"Description","text":"

This versioning is used exclusively for the go directive in go.mod files.

It ensures that a value like 1.16 is treated like ^1.16 and not ~1.16.

By default this will mean that the go directive in go.mod files won't get upgraded to any new Go version, such as 1.19. If you wish to upgrade this value every time there's a new minor Go release, configure rangeStrategy to be \"bump\" like so:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"golang-version\"],\n      \"rangeStrategy\": \"bump\"\n    }\n  ]\n}\n
"},{"location":"modules/versioning/gomod/","title":"Go Modules Versioning","text":""},{"location":"modules/versioning/gomod/#identifier","title":"Identifier","text":"

gomod

"},{"location":"modules/versioning/gomod/#references","title":"References","text":""},{"location":"modules/versioning/gomod/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/gomod/#description","title":"Description","text":"

Versioning for Go modules.

It behaves like the semver versioning for now, and is not yet the default for the go datasource or the gomod manager. Go-specific behaviour, such as for pseudo-versions like v0.0.0-20191109021931-daa7c04131f5, will be added over time.

"},{"location":"modules/versioning/gradle/","title":"Gradle Versioning","text":""},{"location":"modules/versioning/gradle/#identifier","title":"Identifier","text":"

gradle

"},{"location":"modules/versioning/gradle/#references","title":"References","text":""},{"location":"modules/versioning/gradle/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump

"},{"location":"modules/versioning/hashicorp/","title":"Hashicorp Versioning","text":""},{"location":"modules/versioning/hashicorp/#identifier","title":"Identifier","text":"

hashicorp

"},{"location":"modules/versioning/hashicorp/#references","title":"References","text":""},{"location":"modules/versioning/hashicorp/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/hashicorp/#description","title":"Description","text":"

Hashicorp versioning syntax is used for Terraform.

It is based off Semantic Versioning 2.0 but with a subset of npm's range syntax.

"},{"location":"modules/versioning/helm/","title":"helm Versioning","text":""},{"location":"modules/versioning/helm/#identifier","title":"Identifier","text":"

helm

"},{"location":"modules/versioning/helm/#references","title":"References","text":""},{"location":"modules/versioning/helm/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, widen

"},{"location":"modules/versioning/hermit/","title":"Hermit Versioning","text":""},{"location":"modules/versioning/hermit/#identifier","title":"Identifier","text":"

hermit

"},{"location":"modules/versioning/hermit/#references","title":"References","text":""},{"location":"modules/versioning/hermit/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/hermit/#description","title":"Description","text":"

Hermit versioning is a mix of version and channel.

Version

Hermit's package version comes from the package's original Git tag. The version is an extension to SemVer, with an extra build number to accommodate package versions from OpenJDK, which has a value 15.0.1_9.

Channel

Channel could be Hermit-generated or user-defined. Channel is considered unstable version and normally won't upgrade. If you would like to get out of Channel, you could replace the Channel with a given version number and let Renovate manage it.

"},{"location":"modules/versioning/hex/","title":"Hex Versioning","text":""},{"location":"modules/versioning/hex/#identifier","title":"Identifier","text":"

hex

"},{"location":"modules/versioning/hex/#references","title":"References","text":""},{"location":"modules/versioning/hex/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, update-lockfile, pin

"},{"location":"modules/versioning/hex/#description","title":"Description","text":"

Hex versioning syntax is used for Elixir, Erlang and Gleam hex dependencies. It is based on Semantic Versioning 2.0 and supports a subset of npm's range syntax.

"},{"location":"modules/versioning/ivy/","title":"Ivy Versioning","text":""},{"location":"modules/versioning/ivy/#identifier","title":"Identifier","text":"

ivy

"},{"location":"modules/versioning/ivy/#references","title":"References","text":""},{"location":"modules/versioning/ivy/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/julia/","title":"Julia Versioning","text":""},{"location":"modules/versioning/julia/#identifier","title":"Identifier","text":"

julia

"},{"location":"modules/versioning/julia/#references","title":"References","text":""},{"location":"modules/versioning/julia/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, pin, replace, widen

"},{"location":"modules/versioning/julia/#description","title":"Description","text":"

Julia's Pkg uses Semantic Versioning 2.0 with a few syntactic differences from npm:

Caret is the default specifier

Bare versions in Project.toml's [compat] section are interpreted as caret ranges. Example = \"1.2.3\" is the same as Example = \"^1.2.3\", i.e. [1.2.3, 2.0.0).

Comma is union, not intersection

Multiple specifiers separated by commas form a union: Example = \"1.2, 2\" resolves to [1.2.0, 3.0.0). (Contrast with Cargo, where comma is intersection.)

\u2265 is a synonym for >=

Example = \"\u2265 1.2.3\" is equivalent to Example = \">= 1.2.3\".

Hyphen ranges

1.2.3 - 4.5.6 resolves to [1.2.3, 4.5.6]. Trailing components in the second endpoint are wildcards (1.2.3 - 4.5 resolves to [1.2.3, 4.6.0)); trailing components in the first endpoint are zeros (1.2 - 4.5.6 resolves to [1.2.0, 4.5.6]).

Tilde and caret semantics, including the leading-zero behavior, match npm's.

Updating [compat] entries

Under every strategy, an exact pin such as \"=6.1.0\" stays exact (\"=6.1.1\"), and a hyphen range is left unchanged. New values are written as major.minor.patch: Pkg rejects prerelease tags and build numbers in [compat], so a JLL release 1.6.10+0 is written as 1.6.10.

See the Julia Pkg compatibility docs for the full specification.

"},{"location":"modules/versioning/kubernetes-api/","title":"Kubernetes API Versioning","text":""},{"location":"modules/versioning/kubernetes-api/#identifier","title":"Identifier","text":"

kubernetes-api

"},{"location":"modules/versioning/kubernetes-api/#references","title":"References","text":""},{"location":"modules/versioning/kubernetes-api/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/lambda-node/","title":"Lambda Node.js Runtime Versioning","text":""},{"location":"modules/versioning/lambda-node/#identifier","title":"Identifier","text":"

lambda-node

"},{"location":"modules/versioning/lambda-node/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/lambda-node/#description","title":"Description","text":"

Renovate's Lambda Node.js versioning is a wrapper around the existing Node.js Versioning module with the only difference being that it lists versions not currently supported by AWS as being unstable. This is intended to be a drop-in replacement for dependencies that follow the node versioning schedule if you need to keep them in line with Lambda Runtime releases.

Its primary purpose is to add Node Runtime support awareness, e.g.:

You can not use lambda-node versioning to replace docker versioning if you are using node tags with suffixes like -alpine. This is because npm versioning treats these suffixes as implying pre-releases/instability.

"},{"location":"modules/versioning/loose/","title":"Loose Versioning","text":""},{"location":"modules/versioning/loose/#identifier","title":"Identifier","text":"

loose

"},{"location":"modules/versioning/loose/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/loose/#description","title":"Description","text":"

Renovate's \"loose\" versioning was created for cases where no strict versioning is in place. It works like SemVer if SemVer-compliant versions are supplied, but otherwise is \"best effort\". Essentially \"loose\" versioning does its best to sort versions and ignores \"unsortable\" versions.

"},{"location":"modules/versioning/maven/","title":"Maven Versioning","text":""},{"location":"modules/versioning/maven/#identifier","title":"Identifier","text":"

maven

"},{"location":"modules/versioning/maven/#references","title":"References","text":""},{"location":"modules/versioning/maven/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, pin, replace

"},{"location":"modules/versioning/maven/#description","title":"Description","text":"

Maven versioning is similar to SemVer but also very different in places. It's specified by Maven itself.

Ranges are supported using Maven's special syntax.

For development purposes, download maven-artifact JAR and run:

$ java -jar maven-artifact-*.jar 3.2.4-alpha-1 3.2.4-SNAPSHOT 3.2.4.0\nDisplay parameters as parsed by Maven (in canonical form) and comparison result:\n1. 3.2.4-alpha-1 == 3.2.4.alpha.1\n   3.2.4-alpha-1 < 3.2.4-SNAPSHOT\n2. 3.2.4-SNAPSHOT == 3.2.4.snapshot\n   3.2.4-SNAPSHOT < 3.2.4.0\n3. 3.2.4.0 == 3.2.4\n
"},{"location":"modules/versioning/nixpkgs/","title":"Nixpkgs Versioning","text":""},{"location":"modules/versioning/nixpkgs/#identifier","title":"Identifier","text":"

nixpkgs

"},{"location":"modules/versioning/nixpkgs/#references","title":"References","text":""},{"location":"modules/versioning/nixpkgs/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/nixpkgs/#description","title":"Description","text":"

Nixpkgs versioning is designed to be used with the nix manager.

NixOS releases follow the YY.MM pattern. There are also some prefixes and suffixes allowed. Using 22.05 as an example the allowed combination of prefixes and suffixes are:

Additionally, there are some floating versions:

"},{"location":"modules/versioning/node/","title":"Node.js Versioning","text":""},{"location":"modules/versioning/node/#identifier","title":"Identifier","text":"

node

"},{"location":"modules/versioning/node/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/node/#description","title":"Description","text":"

Renovate's Node.js versioning is a wrapper around npm versioning. But Renovate removes any v prefixes from semantic versions when replacing.

Its primary purpose is to add Node.js LTS awareness:

Up to Node.js 26 the release lines followed an odd/even scheme, where odd-numbered majors never reached LTS. From Node.js 27 onwards the schedule changed: every major eventually becomes LTS, so stability is derived from the release schedule rather than the major number being odd or even.

You can not use node versioning to replace docker versioning if you are using node tags with suffixes like -alpine. This is because npm versioning treats these suffixes as implying pre-releases/instability.

"},{"location":"modules/versioning/npm/","title":"npm Versioning","text":""},{"location":"modules/versioning/npm/#identifier","title":"Identifier","text":"

npm

"},{"location":"modules/versioning/npm/#references","title":"References","text":""},{"location":"modules/versioning/npm/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/npm/#description","title":"Description","text":"

npm versioning is the most well known/widely-used implementation of Semantic Versioning 2.0.

It's important to understand that \"npm\" versioning scheme is not the same as \"semver\" versioning. SemVer's spec does not define ranges at all - so all range/constraint syntax in npm is npm-specific and not part of the spec.

"},{"location":"modules/versioning/nuget/","title":"NuGet Versioning","text":""},{"location":"modules/versioning/nuget/#identifier","title":"Identifier","text":"

nuget

"},{"location":"modules/versioning/nuget/#references","title":"References","text":""},{"location":"modules/versioning/nuget/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, pin

"},{"location":"modules/versioning/nuget/#description","title":"Description","text":"

NuGet versioning matches as closely as possible to the version comparison that NuGet itself uses.

"},{"location":"modules/versioning/paket/","title":"Paket Versioning","text":""},{"location":"modules/versioning/paket/#identifier","title":"Identifier","text":"

paket

"},{"location":"modules/versioning/paket/#references","title":"References","text":""},{"location":"modules/versioning/paket/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, update-lockfile, pin

"},{"location":"modules/versioning/paket/#description","title":"Description","text":"

Paket versioning implements the version constraint syntax of the paket.dependencies file.

Paket versions are NuGet versions, so version parsing and comparison match the nuget versioning module. But the range syntax differs from NuGet ranges and the two conflict where they overlap: a plain version like 1.2.3 is an exact pin in Paket, while NuGet range syntax treats it as \"at least 1.2.3\". This is why Paket needs its own versioning module.

The following constraints are supported:

Constraint Meaning 1.2.3 or = 1.2.3 exactly version 1.2.3 == 1.2.3 exactly version 1.2.3, overriding conflicts >= 1.2.3 at least version 1.2.3 > 1.2.3 greater than version 1.2.3 <= 1.2.3 at most version 1.2.3 < 1.2.3 less than version 1.2.3 ~> 1.2.3 pessimistic constraint, >= 1.2.3 and < 1.3 >= 1.2.3 < 1.5 combined bounds ~> 1.2 >= 1.2.3 pessimistic constraint with a floor

Prerelease channels may follow the constraint, like >= 1.2.3 alpha or ~> 1.2 prerelease. Stable versions always match, while prerelease versions only match when their channel is listed, or when the prerelease keyword allows all of them. A constraint written with a prerelease version, like ~> 1.2.3-alpha001, allows its own channel implicitly. Following Paket, the literal prerelease suffix sorts below any other prerelease of the same version, so 1.2.3-prerelease acts as a floor under all prereleases of 1.2.3.

The resolver strategy prefixes ! and @, like !~> 1.2, do not change which versions match and are preserved when Renovate updates a range.

When Renovate replaces a range, it keeps the shape of the constraint:

The bump strategy raises the floor to the exact new version where the syntax allows it, for example ~> 1.2 becomes ~> 1.2 >= 1.2.5. The widen strategy keeps the lower bound and only extends the upper bound, decomposing ~> 1.2 into >= 1.2 < 3 when needed.

"},{"location":"modules/versioning/pep440/","title":"PEP440 Versioning","text":""},{"location":"modules/versioning/pep440/#identifier","title":"Identifier","text":"

pep440

"},{"location":"modules/versioning/pep440/#references","title":"References","text":""},{"location":"modules/versioning/pep440/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, pin

"},{"location":"modules/versioning/pep440/#description","title":"Description","text":"

PEP 440 is defined as part of the Python project, and its versioning is independent of others such as SemVer.

Ranges are supported using the syntax defined as part of the PEP440 spec.

"},{"location":"modules/versioning/perl/","title":"Perl Versioning","text":""},{"location":"modules/versioning/perl/#identifier","title":"Identifier","text":"

perl

"},{"location":"modules/versioning/perl/#references","title":"References","text":""},{"location":"modules/versioning/perl/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/perl/#description","title":"Description","text":"

Perl versioning is based on Perl's version module.

This could be used in combination with the regex manager and the cpan datasource.

"},{"location":"modules/versioning/poetry/","title":"Poetry Versioning","text":""},{"location":"modules/versioning/poetry/#identifier","title":"Identifier","text":"

poetry

"},{"location":"modules/versioning/poetry/#references","title":"References","text":""},{"location":"modules/versioning/poetry/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/poetry/#description","title":"Description","text":"

Poetry versioning is a little like a mix of PEP440 and SemVer.

Currently Renovate's implementation is based off npm versioning. This works by parsing versions using the same patterns and similar normalization rules as Poetry, passing them to the npm versioning implementation, and then reversing the normalizations. This allows Renovate to meaningfully compare the SemVer-style versions allowed in pyproject.toml to the PEP440 representations used on PyPI. These are equivalent for major.minor.patch releases, but different for pre-, post-, and dev releases.

"},{"location":"modules/versioning/pvp/","title":"Package Versioning Policy (Haskell) Versioning","text":""},{"location":"modules/versioning/pvp/#identifier","title":"Identifier","text":"

pvp

"},{"location":"modules/versioning/pvp/#references","title":"References","text":""},{"location":"modules/versioning/pvp/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: widen

"},{"location":"modules/versioning/pvp/#description","title":"Description","text":"

Package Versioning Policy is used with Haskell. It's like semver, except that the first two parts are of the major version. That is, in A.B.C:

The remaining parts are all considered of the patch version, and they will be concatenated to form a number, i.e. IEEE 754 double. This means that both 0.0.0.0.1 and 0.0.0.0.10 have patch version 0.1.

The range syntax comes from Cabal, specifically the build-depends section.

This module is considered experimental since it only supports ranges of forms:

"},{"location":"modules/versioning/python/","title":"Python Versioning","text":""},{"location":"modules/versioning/python/#identifier","title":"Identifier","text":"

python

"},{"location":"modules/versioning/python/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/python/#description","title":"Description","text":"

Python versioning is a little like a mix of PEP440 and Poetry SemVer.

"},{"location":"modules/versioning/redhat/","title":"Red Hat Versioning","text":""},{"location":"modules/versioning/redhat/#identifier","title":"Identifier","text":"

redhat

"},{"location":"modules/versioning/redhat/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/redhat/#description","title":"Description","text":"

Red Hat versioning is used with container images that are maintained by Red Hat.

Red Hat version definitions follow this pattern:

Examples of valid Red Hat versions:

Ranges are not supported by this versioning.

"},{"location":"modules/versioning/regex/","title":"Regular Expression Versioning","text":""},{"location":"modules/versioning/regex/#identifier","title":"Identifier","text":"

regex

"},{"location":"modules/versioning/regex/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/regex/#description","title":"Description","text":"

Regular Expression Versioning is designed to be a flexible fallback versioning approach if Renovate's other versioning schemes don't do the job.

The regex scheme makes use of Regular Expression capture groups.

The valid capture groups for regex versioning are:

The compatibility concept was originally introduced for Docker versioning but sometimes package authors may use/misuse suffixes to mean compatibility in other versioning schemes.

Important: all capture groups must contain only purely numeric values. Even if there is a string prefix which is identical in all available versions, it must not be part of the capture group. For example a build capture group containing r4 cannot be evaluated as number; Renovate cannot compare the build in this case. The capture group must be 4 instead.

Here is an example of using regex versioning to correct behavior of the guava Maven package, which misuses suffixes as compatibility indicators:

{\n  \"packageRules\": [\n    {\n      \"matchPackageNames\": [\"com.google.guava:guava\"],\n      \"versioning\": \"regex:^(?<major>\\\\d+)(\\\\.(?<minor>\\\\d+))?(\\\\.(?<patch>\\\\d+))?(-(?<compatibility>.*))?$\"\n    }\n  ]\n}\n

Here is another example, this time for handling python Docker images, which use both pre-release indicators as well as version suffixes for compatibility:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"python\"],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)(?<prerelease>[^.-]+)?(-(?<compatibility>.*))?$\"\n    }\n  ]\n}\n

Here is another example, this time for handling Bitnami Docker images, which use build and revision indicators as well as version suffixes for compatibility:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"bitnami/**\", \"docker.io/bitnami/**\"],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)(?:-(?<compatibility>.+)(?<build>\\\\d+)-r(?<revision>\\\\d+))?$\"\n    }\n  ]\n}\n

Here is another example, this time for handling ghcr.io/linuxserver/tautulli Docker images, which use major and build indicators with string prefixes:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"ghcr.io/linuxserver/tautulli\"],\n      \"versioning\": \"regex:^v(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)-ls(?<build>.+)$\"\n    }\n  ]\n}\n

Here is another example, this time for handling ghcr.io/linuxserver/openssh-server Docker images, which use patch, build and revision indicators with string prefixes:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"ghcr.io/linuxserver/openssh-server\"],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)_p(?<patch>\\\\d+)-r(?<build>\\\\d)-ls(?<revision>.+)$\"\n    }\n  ]\n}\n

The regex scheme also accepts a comparator range wherever a version is matched against a constraint, such as allowedVersions and matchCurrentVersion, evaluated with the scheme's own version comparison: the major, minor, and patch capture groups are compared in that order of precedence, regardless of where they appear in the pattern. For example, calendar versioning YYYY.DD.MM (day before month) sorts correctly by capturing the month as minor and the day as patch, so comparison follows year, then month, then day. The supported operators are <, <=, >, >=, = and ==, and several comparators separated by whitespace or a comma are combined with logical AND. Because the comparison uses the scheme's own ordering rather than npm semver, a numeric suffix captured as build is ordered correctly, where semver would treat it as a prerelease and reject the range.

For example, to hold a GitLab EE image at or below a required upgrade stop, capture the -ee suffix as a numeric build group and cap it with allowedVersions:

{\n  \"packageRules\": [\n    {\n      \"matchDatasources\": [\"docker\"],\n      \"matchPackageNames\": [\"gitlab/gitlab-ee\"],\n      \"versioning\": \"regex:^(?<major>\\\\d+)\\\\.(?<minor>\\\\d+)\\\\.(?<patch>\\\\d+)-ee\\\\.(?<build>\\\\d+)$\",\n      \"allowedVersions\": \"<=19.1.2-ee.0\"\n    }\n  ]\n}\n
"},{"location":"modules/versioning/rez/","title":"rez Versioning","text":""},{"location":"modules/versioning/rez/#identifier","title":"Identifier","text":"

rez

"},{"location":"modules/versioning/rez/#references","title":"References","text":""},{"location":"modules/versioning/rez/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/rez/#description","title":"Description","text":"

rez versioning was developed to support the rez Package Manager. It's based on Semantic Versioning but includes its own concept of ranges.

Use of dots

A range is expressed with dots 1.2..2 means >=1.2.x <2.0.0.

No exact versions unless using two equals ==

In rez, 1.2.3 doesn't mean \"exactly 1.2.3\", it actually means >= 1.2.3 <1.2.4. If you want to use an exact version use two equal characters, like this: ==1.2.3.

Use of pipes

rez uses pipes as an OR operator, 2.7..3|4 means >=2.7 <3 OR 4.x.x.

This has not been implemented yet. The current iteration of rez versioning does not support pipes yet.

"},{"location":"modules/versioning/rpm/","title":"RPM version Versioning","text":""},{"location":"modules/versioning/rpm/#identifier","title":"Identifier","text":"

rpm

"},{"location":"modules/versioning/rpm/#references","title":"References","text":""},{"location":"modules/versioning/rpm/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/ruby/","title":"Ruby Versioning","text":""},{"location":"modules/versioning/ruby/#identifier","title":"Identifier","text":"

ruby

"},{"location":"modules/versioning/ruby/#references","title":"References","text":""},{"location":"modules/versioning/ruby/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace, pin

"},{"location":"modules/versioning/ruby/#description","title":"Description","text":"

The RubyGems team urges gem developers to follow the Semantic Versioning standard for their gem\u2019s versions, but it is not enforced.

Range syntax is similar to npm's but not identical. The main difference is the use of \"pessimistic\" greater than or equals: ~>

"},{"location":"modules/versioning/rust-release-channel/","title":"Rust Release Channel Versioning","text":""},{"location":"modules/versioning/rust-release-channel/#identifier","title":"Identifier","text":"

rust-release-channel

"},{"location":"modules/versioning/rust-release-channel/#references","title":"References","text":""},{"location":"modules/versioning/rust-release-channel/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: pin, replace

"},{"location":"modules/versioning/rust-release-channel/#description","title":"Description","text":"

This versioning scheme handles Rust release channel identifiers as used by rustup and other Rust-related tools.

"},{"location":"modules/versioning/rust-release-channel/#supported-formats","title":"Supported Formats","text":""},{"location":"modules/versioning/rust-release-channel/#channel-names-ranges","title":"Channel Names (Ranges)","text":""},{"location":"modules/versioning/rust-release-channel/#versioned-releases","title":"Versioned Releases","text":""},{"location":"modules/versioning/rust-release-channel/#dated-nightlies","title":"Dated Nightlies","text":""},{"location":"modules/versioning/rust-release-channel/#compatibility-groups","title":"Compatibility Groups","text":"

This affects which updates Renovate will offer.

"},{"location":"modules/versioning/rust-release-channel/#stability","title":"Stability","text":"

Only final releases without prerelease suffixes are considered \"stable\":

"},{"location":"modules/versioning/rust-release-channel/#range-strategies","title":"Range Strategies","text":""},{"location":"modules/versioning/rust-release-channel/#pin","title":"pin","text":"

Always pins to the exact new version:

"},{"location":"modules/versioning/rust-release-channel/#replace","title":"replace","text":"

Maintains the format style of the current value:

"},{"location":"modules/versioning/rust-release-channel/#majorminorpatch-extraction","title":"Major/Minor/Patch Extraction","text":"

For versioned releases:

For nightlies:

"},{"location":"modules/versioning/rust-release-channel/#resources","title":"Resources","text":""},{"location":"modules/versioning/same-major/","title":"Same Major Versioning Versioning","text":""},{"location":"modules/versioning/same-major/#identifier","title":"Identifier","text":"

same-major

"},{"location":"modules/versioning/same-major/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/same-major/#description","title":"Description","text":"

The 'Same Major' versioning is designed to handle the case where a version needs to treated as a \"greater than or equal to\" constraint. Specifically, the case where the version say, X.Y.Z signifies a range of compatibility from greater than or equal to X.Y.Z to less than X+1.

This process uses Semver-Coerced versioning beneath the surface, single versions (e.g., X.Y.Z) are converted to a range like X+1 and then passed to the corresponding semver-coerced method.

This method is handy when managing dependencies like dotnet-sdk's rollForward settings. Let's say a project uses dotnet-sdk version 3.1.0. It needs to be compatible with any version in the 3.x.x range but not with versions in the next major version, like 4.x.x.

For example:

{\n  \"sdk\": {\n    \"version\": \"6.0.300\",\n    \"rollForward\": \"major\"\n  }\n}\n

The roll-forward policy to use when selecting an SDK version, either as a fallback when a specific SDK version is missing or as a directive to use a higher version. In this case with major it means that select the latest version with the same major. ie. >= 6.0.300 < 7.0.0

For such cases, the users would not want Renovate to create an update PR for any version within the range >= 6.0.300 < 7.0.0 as it would not change the behaviour on their end, since it is handled by the manager already.

Note: You should create a discussion before using this versioning as this is an experimental support and might have some edge cases unhandled.

"},{"location":"modules/versioning/semver/","title":"Semantic Versioning","text":""},{"location":"modules/versioning/semver/#identifier","title":"Identifier","text":"

semver

"},{"location":"modules/versioning/semver/#references","title":"References","text":""},{"location":"modules/versioning/semver/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/semver/#description","title":"Description","text":"

Renovate's semver versioning strictly implements the Semantic Versioning 2.0 specification. Because the SemVer 2.0 specification does not allow ranges, Renovate's semver versioning also does not support ranges.

Only use the semver versioning when you mean to follow the full SemVer 2.0 specifications strictly. If you need a more forgiving variant use semver-coerced.

"},{"location":"modules/versioning/semver-coerced/","title":"Coerced Semantic Versioning Versioning","text":""},{"location":"modules/versioning/semver-coerced/#identifier","title":"Identifier","text":"

semver-coerced

"},{"location":"modules/versioning/semver-coerced/#references","title":"References","text":""},{"location":"modules/versioning/semver-coerced/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/semver-coerced/#description","title":"Description","text":"

Renovate's Coerced Semantic Versioning is a forgiving variant of Semantic Versioning 2.0 with coercion enabled for versions.

This versioning provides a very forgiving translation of inputs in non-strict-SemVer format into strict SemVer. For example, \"v1\" is coerced into \"1.0.0\", \"2.1\" => \"2.1.0\", \"~3.1\" => \"3.1.0\", \"1.1-foo\" => \"1.1.0\". Look at the Coercion section of this page for more info on input coercion.

Since this versioning is very forgiving, it doesn't actually provide the coercion for version ranges. The range functions only accept strict SemVer as input and equivalent to those provided by the Renovate's semver versioning.

"},{"location":"modules/versioning/semver-partial/","title":"Partial Semantic Versioning Versioning","text":""},{"location":"modules/versioning/semver-partial/#identifier","title":"Identifier","text":"

semver-partial

"},{"location":"modules/versioning/semver-partial/#references","title":"References","text":""},{"location":"modules/versioning/semver-partial/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: pin, replace

"},{"location":"modules/versioning/semver-partial/#description","title":"Description","text":"

Renovate's Partial Semantic Versioning supports partial version numbers that resolve to the latest matching full version, following Semantic Versioning 2.0 conventions.

This versioning is used by GitLab CI/CD Components to allow specifying incomplete version numbers that automatically resolve to the latest version matching that pattern. This enables you to receive updates within a specific version range without specifying the full version.

Version Resolution:

Example:

Given available versions: 1.0.0, 1.1.0, 1.1.1, 1.2.0, 2.0.0, 2.0.1, 2.1.0:

Pre-release Handling:

Pre-release versions (e.g., 1.0.1-rc, 2.0.0-beta) are not selected by partial versions. You must specify the full version to match a pre-release.

"},{"location":"modules/versioning/swift/","title":"Swift Versioning","text":""},{"location":"modules/versioning/swift/#identifier","title":"Identifier","text":"

swift

"},{"location":"modules/versioning/swift/#references","title":"References","text":""},{"location":"modules/versioning/swift/#rangesconstraints","title":"Ranges/Constraints","text":"

\u2705 Ranges are supported.

Valid rangeStrategy values are: bump, widen, replace

"},{"location":"modules/versioning/swift/#description","title":"Description","text":"

Swift versioning was developed to support the Swift Package Manager. It's based on Semantic versioning but includes its own concept of ranges.

"},{"location":"modules/versioning/ubuntu/","title":"Ubuntu Versioning","text":""},{"location":"modules/versioning/ubuntu/#identifier","title":"Identifier","text":"

ubuntu

"},{"location":"modules/versioning/ubuntu/#references","title":"References","text":""},{"location":"modules/versioning/ubuntu/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/ubuntu/#description","title":"Description","text":"

Ubuntu versioning is used for Ubuntu container images that are referenced by their release version or a codename.

Versions to which this scheme applies are e.g. 24.04, noble and noble-20240423.

"},{"location":"modules/versioning/unity3d/","title":"Unity3D Versioning","text":""},{"location":"modules/versioning/unity3d/#identifier","title":"Identifier","text":"

unity3d

"},{"location":"modules/versioning/unity3d/#references","title":"References","text":""},{"location":"modules/versioning/unity3d/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/unity3d/#description","title":"Description","text":"

Unity versioning follow semantic versioning, followed by a letter, number and an optional hash:

Examples:

"},{"location":"modules/versioning/unity3d-packages/","title":"Unity3D Packages Versioning","text":""},{"location":"modules/versioning/unity3d-packages/#identifier","title":"Identifier","text":"

unity3d-packages

"},{"location":"modules/versioning/unity3d-packages/#references","title":"References","text":""},{"location":"modules/versioning/unity3d-packages/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/unity3d-packages/#description","title":"Description","text":"

Unity versioning follow semantic versioning, followed optionally by -exp.# or -pre.#: https://docs.unity3d.com/Manual/upm-lifecycle.html

Examples:

"},{"location":"modules/versioning/vcpkg/","title":"vcpkg Versioning","text":""},{"location":"modules/versioning/vcpkg/#identifier","title":"Identifier","text":"

vcpkg

"},{"location":"modules/versioning/vcpkg/#references","title":"References","text":""},{"location":"modules/versioning/vcpkg/#rangesconstraints","title":"Ranges/Constraints","text":"

\u274c No range support.

"},{"location":"modules/versioning/vcpkg/#description","title":"Description","text":"

Renovate vcpkg versioning targets the per-port version schemes used by the vcpkg package manager.

A vcpkg port declares one of four version fields, each with its own comparison rules:

Renovate detects which scheme applies by inspecting the input, then delegates to the matching underlying versioning module (semver, loose, or a direct date comparison). vcpkg itself takes the scheme from the field a version is published under, not from its text, so the two can disagree. A port that publishes dotted text under version-string, like 2.3.1, is treated as a version here and ordered against the port's other dotted versions, which vcpkg would refuse to compare.

A vcpkg port can also carry a port-version integer for changes that affect packaging without changing the upstream source. The canonical text form combines the base version and port-version with a # separator, like 1.2.3#1, and the port-version is omitted when zero. Renovate treats the port-version as a tie-breaker after the base versions compare equal, so 1.2.3#1 is greater than 1.2.3#0, while 1.2.4 is still greater than 1.2.3#1 because the base version wins.

vcpkg has no range expression syntax. Manifest dependencies carry a single version>= lower bound, and overrides carry an exact pin. In both cases the value is a bare version, with no operator, so Renovate compares values for equality like other versioning modules without ranges.

"},{"location":"user-stories/maintaining-aur-packages-with-renovate/","title":"Maintaining AUR packages with Renovate","text":""},{"location":"user-stories/maintaining-aur-packages-with-renovate/#maintaining-aur-packages-with-renovate","title":"Maintaining AUR packages with Renovate","text":"

This article was written by Jamie Magee and originally published on Jamie Magee's blog.

Note

Jamie Magee helps to maintain Renovate. They obviously like Renovate, and want you to use it.

One big advantage that Arch Linux has over other distributions, apart from being able to say \u201cBTW I use Arch.\u201d, is the Arch User Repository (AUR). It\u2019s a community-driven repository with over 80,000 packages. If you\u2019re looking for a package, chances are you'll find it in the AUR.

Keeping all those packages up to date, takes a lot of manual effort by a lot of volunteers. People have created and used tools, like urlwatch and aurpublish, to let them know when upstream releases are cut and automate some parts of the process. I know I do. But I wanted to automate the entire process. I think Renovate can help here.

"},{"location":"user-stories/maintaining-aur-packages-with-renovate/#updating-versions-with-renovate","title":"Updating versions with Renovate","text":"

Renovate is an automated dependency update tool. You might have seen it opening pull requests on GitHub and making updates for npm or other package managers, but it\u2019s a lot more powerful than just that.

Renovate has a couple of concepts that I need to explain first: datasources and managers. Datasources define where to look for new versions of a dependency. Renovate comes with over 50 different datasources, but the one that is important for AUR packages is the git-tags datasource. Managers are the Renovate concept for package managers. There isn\u2019t an AUR or PKGBUILD manager, but there is a regex manager that I can use.

I can create a renovate.json configuration with the following custom manager configuration:

renovate.json
{\n  \"customManagers\": [\n    {\n      \"customType\": \"regex\",\n      \"managerFilePatterns\": [\"/(^|/)PKGBUILD$/\"],\n      \"matchStrings\": [\n        \"pkgver=(?<currentValue>.*) # renovate: datasource=(?<datasource>.*) depName=(?<depName>.*)\"\n      ],\n      \"extractVersionTemplate\": \"^v?(?<version>.*)$\"\n    }\n  ]\n}\n

Breaking that down:

And here\u2019s an extract from the PKGBUILD for the bicep-bin AUR package that I maintain:

pkgver=0.15.31 # renovate: datasource=github-tags depName=Azure/bicep\n

Here I\u2019m configuring Renovate to use the github-tags datasource and to look in the Azure/bicep GitHub repository for new versions. That means it\u2019ll look in the list of tags for the Azure/bicep repository for any new versions. If Renovate finds any new versions, it\u2019ll automatically update the PKGBUILD and open a pull request with the updated version.

So I\u2019ve automated the PKGBUILD update, but that\u2019s only half of the work. The checksums and .SRCINFO must be updated before pushing to the AUR. Unfortunately, Renovate can\u2019t do that (yet, see Renovate issue #16923), but GitHub Actions can!

"},{"location":"user-stories/maintaining-aur-packages-with-renovate/#updating-checksums-and-srcinfo-with-github-actions","title":"Updating checksums and .SRCINFO with GitHub Actions","text":"

Updating the checksums with updpkgsums is easy, and generating an updated .SRCINFO with makepkg --printsrcinfo > .SRCINFO is straightforward too. But doing that for a whole repository of AUR packages is going to be a little trickier. So let me build up the GitHub actions workflow step-by-step.

First, I only want to run this workflow on pull requests targeting the main branch.

on:\n  pull_request:\n    types:\n      - opened\n      - synchronize\n    branches:\n      - main\n

Next, I\u2019m going to need to check out the entire history of the repository, so I can compare the files changed in the latest commit with the Git history.

jobs:\n  updpkgsums:\n    runs-on: ubuntu-latest\n    steps:\n      - name: Checkout\n        uses: actions/checkout@3df4ab11eba7bda6032a0b82a6bb43b11571feac # v4.0.0\n        with:\n          fetch-depth: 0\n          ref: ${{ github.ref }}\n

Getting the package that changed in a pull request requires a little bit of shell magic.

- name: Find updated package\n  run: |\n    #!/usr/bin/env bash\n    set -euxo pipefail\n\n    echo \"pkgbuild=$(git diff --name-only origin/main origin/${GITHUB_HEAD_REF} \"*PKGBUILD\" | head -1 | xargs dirname)\" >> $GITHUB_ENV\n

Now I\u2019ve found the package that changed in the Renovate pull request, I can update the files.

This step in the workflow uses a private GitHub Action that I have in my aur-packages repository. I\u2019m not going to break it down here, but at its core it runs updpkgsums and makepkg --printsrcinfo > .SRCINFO with a little extra configuration required to run Arch Linux on GitHub Actions runners. You can check out the full code on GitHub.

- name: Validate package\n  if: ${{ env.pkgbuild != '' }}\n  uses: ./.github/actions/aur\n  with:\n    action: 'updpkgsums'\n    pkgname: ${{ env.pkgbuild }}\n

Finally, once the PKGBUILD and .SRCINFO are updated I need to commit that change back to the pull request.

- name: Commit\n  if: ${{ env.pkgbuild != '' }}\n  uses: stefanzweifel/git-auto-commit-action@3ea6ae190baf489ba007f7c92608f33ce20ef04a # v4.16.0\n  with:\n    file_pattern: '*/PKGBUILD */.SRCINFO'\n

Check out this pull request for bicep-bin where Renovate opened a pull request, and my GitHub Actions workflow updated the b2sums in the PKGBUILD and updated the .SRCINFO.

But why stop there? Let\u2019s talk about publishing.

"},{"location":"user-stories/maintaining-aur-packages-with-renovate/#publishing-to-the-aur","title":"Publishing to the AUR","text":"

Each AUR package is its own Git repository. So to update a package in the AUR, I only need to push a new commit with the updated PKGBUILD and .SRCINFO. Thankfully, KSXGitHub created the github-actions-deploy-aur GitHub Action to streamline the whole process.

If I create a new GitHub Actions workflow to publish to the AUR, I can reuse the first two steps from my previous workflow to check out the repository and find the updated package. Then all I need to do is to use the github-actions-deploy-aur GitHub Action:

- name: Publish package\n  uses: KSXGitHub/github-actions-deploy-aur@065b6056b25bdd43830d5a3f01899d0ff7169819 # v2.6.0\n  if: ${{ env.pkgbuild != '' }}\n  with:\n    pkgname: ${{ env.pkgbuild }}\n    pkgbuild: ${{ env.pkgbuild }}/PKGBUILD\n    commit_username: ${{ secrets.AUR_USERNAME }}\n    commit_email: ${{ secrets.AUR_EMAIL }}\n    ssh_private_key: ${{ secrets.AUR_SSH_PRIVATE_KEY }}\n
"},{"location":"user-stories/maintaining-aur-packages-with-renovate/#all-together-now","title":"All together now","text":"

If you own any AUR packages and want to automate some of the maintenance burden, check out my AUR packages template GitHub repository. It contains all of the steps I showed in this blog post. And if you want to see how it works in practice, check out my AUR packages GitHub repository.

"},{"location":"user-stories/swissquote/","title":"Swissquote","text":""},{"location":"user-stories/swissquote/#how-swissquote-is-keeping-software-dependencies-up-to-date-with-renovate","title":"How Swissquote is keeping software dependencies up-to-date with Renovate","text":"

This article was originally published on Medium by St\u00e9phane Goetz, Principal Software Engineer at Swissquote Bank.

Swissquote has more than 1000 distinct applications running in production. They come in many different flavors including services, daemons, and web apps, and their age can be counted from days to more than a decade. While there are many topics of interest when talking about software maintenance, today\u2019s topic is software dependencies. We\u2019ll see in this article why it\u2019s important to keep them up-to-date and why it\u2019s not as simple as one may think.

Software dependencies have been a heavily discussed topic in the past months. One aspect that\u2019s discussed a lot is security issues like the recent Log4Shell, Supply chain attacks, an expiring SSL Certificate. But there are also other aspects like bugs caused by your dependencies.

Depending on third-party software is a sword of Damocles; you never know when a new issue will force you to drop everything to upgrade your software.

XKCD comic 2347 is always relevant when talking about dependencies.

Each software dependency is a risk. For example: SQL Injections, is the ORM you are using properly escaping the content you are passing to it? Will your current driver be able to connect to your database if it gets upgraded? Every dependency, while solving an issue for you, will also bring new risks to your software. How can you mitigate those risks?

If the title of the article is of any help, the idea would be to keep your dependencies up-to-date to fix bugs, security issues, and more.

"},{"location":"user-stories/swissquote/#i-dont-feel-like-upgrading-what-if","title":"I don\u2019t feel like upgrading, what if?","text":"

But what if the upgrades do the complete opposite? What if the new version introduces a new security issue?

For example, a new version of a dependency could be victim of a supply chain attack. If you never update your dependencies, you won\u2019t get the infected version. Sounds fair, right?

It\u2019s a valid argument, but your application doesn\u2019t exist in a vacuum; many external factors could force you to upgrade at some point, and when it happens it\u2019s usually at the wrong time.

Let\u2019s go through some examples.

"},{"location":"user-stories/swissquote/#an-external-factor-has-changed-forcing-you-to-change-your-app","title":"An external factor has changed, forcing you to change your app","text":"

Let\u2019s say the machine your apps runs on is obsolete and you need to move to another machine. This could be as simple as \u201cinstall app on machine; done\u201d but usually ends up with:

  1. The newer OS version prevents you from installing an outdated runtime
  2. You need to find a compatible runtime for your new hardware
  3. Your app\u2019s dependencies aren\u2019t compatible with your new runtime, you need to update them as well

Instead of a single change, you now have a combination of changes, each can go wrong in a different way.

"},{"location":"user-stories/swissquote/#a-new-vulnerability-is-found-on-a-library-you-depend-on","title":"A new vulnerability is found on a library you depend on","text":"

As we\u2019ve covered at the beginning of the article this can happen and can be an all-hands-on-deck kind of situation. Imagine a legacy application; continuous integration is constantly failing \u2014 or worse it may not even exist. How long do you think it will take to deploy that single library update?

"},{"location":"user-stories/swissquote/#the-team-already-has-too-many-dependencies-in-too-many-different-versions","title":"The team already has too many dependencies in too many different versions","text":"

That\u2019s unfortunate, but it will happen if your team or company exists for long enough. Upgrading libraries is not only about bumping versions, sometimes it\u2019s also about replacing a library by another library.

"},{"location":"user-stories/swissquote/#how-do-you-see-your-dependencies","title":"How do you see your dependencies?","text":"

Look at your software as if it was a train. You are the locomotive and each wagon is a dependency, how long would your train be? Locomotives can pull dozens, even hundreds of wagons, but they eventually reach a limit. The situation is the same for your brain, each dependency adds to your cognitive load, at some point it\u2019s just too much. You are using three different libraries for caching? There is a chance you need to know how each library works, and your present and future teammates might have to know that too.

Which of these two would you prefer to start with:

Am I exaggerating with my examples? Maybe a little, but I have seen cases very close to those.

Let me ask you some questions about your projects:

As time goes forward, projects come and go, you will most likely have decade-old, and recent ones. Some might be using the latest version of Java with the latest Spring, some with slightly outdated libraries and others might be using Stripes and libraries that have had no release in 7 years.

Every company that\u2019s been around for sometime has that old project still running. People talk about it laughingly but become livid when a request comes to change anything in it.

There is a fix to make on that project, the last person working on it left three years ago."},{"location":"user-stories/swissquote/#dependencies-at-swissquote","title":"Dependencies at Swissquote","text":"

I\u2019ve identified three main approaches people use to upgrade their dependencies at Swissquote:

  1. Critical fixes only; update dependencies that have a CVE attached
  2. Opportunistic; also known as the boy scout rule, leave the project with more up-to-date dependencies than you found it
  3. Update your dependencies regularly; manually or with a tool
"},{"location":"user-stories/swissquote/#critical-fixes-only","title":"Critical fixes only","text":"

Every once in a while, a library gets an update that fixes a vulnerability. Our security team is on the lookout for critical vulnerabilities and will quickly warn all impacted teams if an update needs to be done.

We also configured GitHub\u2019s Dependabot Alerts that will inform teams that a vulnerability has been discovered and which version they should upgrade to to be safe (more on this later).

This approach, while it mostly works, can be very risky. If the project hasn\u2019t been touched for quite a while, the number of dependencies to update can be high depending on the vulnerability and the time to update will increase significantly.

"},{"location":"user-stories/swissquote/#opportunistic","title":"Opportunistic","text":"

This rule is simple, when you receive a task on a project, the first step is to upgrade its dependencies. Once that is done, you can go ahead with the implementation of your task.

This approach is similar to fixing a bit of tech debt with every business project you take on, it helps to stay ahead in case a vulnerability comes up and keep a baseline for all your projects.

"},{"location":"user-stories/swissquote/#update-your-dependencies-regularly","title":"Update your dependencies regularly","text":"

This one sounds easy, every few weeks you check what\u2019s outdated, bump the versions and run your CI. If it succeeds, you push the change. Maybe there is even a way to automate that?

"},{"location":"user-stories/swissquote/#lets-give-renovate-a-try","title":"Let's give Renovate a try","text":"

One day in November 2019, I discovered that Renovate provides a Docker image that you can run on-premise with your own package registries. The app creates Pull Requests automatically to inform you of dependencies updates and the CI can then build it automatically so you know if it\u2019s safe to merge or not.

On our first try, we enabled 30 repositories, a cron task was running every hour to create Pull Requests.

We received 700 Pull Requests in the first month, it was a never ending Pull Request whack-a-mole: every time we merged one, another replaced it.

Me and my team merging Pull Requests.

The awesome thing with Renovate is that it\u2019s very configurable, and this configuration can be shared. Very early on we created a shared configuration for our team with some custom policies, here are a few things we decided to do:

This helped a lot to reduce the noise in PRs, the second month we got 400 Pull Requests, and on the third month only 200.

"},{"location":"user-stories/swissquote/#what-we-learned-from-automating-dependencies-updates","title":"What we learned from automating dependencies updates","text":""},{"location":"user-stories/swissquote/#a-word-on-renovate","title":"A word on Renovate","text":"

The next section could look like an ad or a sponsored post; it\u2019s not. We\u2019re just big fans of the product.

The ease of getting started with Renovate\u2019s Docker image is what got us onboard easily. But what confirmed our choice is the insane crazy amount of features and configuration options.

Some features and options we enjoy:

There is an on-premise option, but you can also use the Mend Renovate App. On our side, we\u2019re not using the on-premise but rather a custom scheduler using the open source Docker image.

"},{"location":"user-stories/swissquote/#some-stats-after-four-years-with-renovate","title":"Some stats after four years with Renovate","text":"

The figures here have been updated in November 2023

We started using Renovate in 2019, using the (now deprecated) renovate/pro Docker image. We installed it as a GitHub app and some early adopters started to use it.

Pretty quickly, we ran into the biggest limitation; this Docker image runs all repositories one after another. A single loop was taking hours and made it very difficult to check the logs as they weren\u2019t separated per repository.

This is why we created our own scheduler; each hour, all repositories would be queued to run, and GitHub app events would schedule a single repository. We started to collect metrics and store the logs separately for each repository.

Here is the dashboard for our current scheduler:

A dashboard we made at Swissquote to keep our Renovate runs in check, November 2023.

We don\u2019t force any team to use Renovate, each team can decide to opt-in and do it for each project separately.

Some statistics:

"},{"location":"user-stories/swissquote/#how-does-the-scheduler-work","title":"How does the scheduler work?","text":"

The scheduler is a Node.js application that handles an in-memory queue and starts Docker containers to run Renovate on. Our custom scheduler application regularly sends data points to our InfluxDB database, which we then display in Grafana.

Here is how it works:

A diagram explaining how our scheduler interacts with Renovate.

All the information on the dashboard you saw above is created from three measurements:

  1. Queue: Every 5 minutes, we send the status of the queue size and the number of jobs currently running
  2. Webhook: When receiving a webhook request from GitHub, we send a data point on the duration of treatment for that item
  3. Runs: After each run, we send a data point on the run duration, success, and number of PRs created/updated/merged/closed

The queue is filled by webhooks or by re-queueing all repositories at regular intervals. For each repository, we start a Renovate Docker image and pipe its logs to a file. This allows us to run ten workers in parallel. We could technically run more workers but decided not to hammer our GitHub instance.

You can find more details in this discussion on the Renovate repository, from November 2023.

"},{"location":"user-stories/swissquote/#the-future-of-renovate-at-swissquote","title":"The future of Renovate at Swissquote","text":"

Not all teams are using Renovate at this stage, as some teams prefer to manually update their dependencies. We would like to enable Renovate for critical dependencies in all repositories and hope to make it useful and easy so other teams will adopt it for more dependencies.

"},{"location":"user-stories/swissquote/#how-should-i-get-started-with-renovate","title":"How should I get started with Renovate?","text":"

If this article convinced you, how should you get started?

  1. First, if you know your software is very outdated; don\u2019t enable Renovate right away, you will be swamped with Pull Requests, we\u2019ve been there and it\u2019s not a happy memory. First take the time to manually upgrade all that you can. npm outdated, mvn versions:display-dependency-updates or your package manager\u2019s equivalent of that command can help you get started, test your application and commit that
  2. You can now enable Renovate and will receive a Pull Request to add a configuration file, read this first PR carefully as it will explain what kind of PRs you are going to receive and when
  3. Make sure to pick a schedule, otherwise you will receive PRs at any time of the day. Our team schedules all third party dependencies on the weekend, automatically merging when the tests pass and we investigate the failing ones on Monday morning
  4. Group Pull Requests, if every PR has to go through CI, it can become quite heavy, once most PRs succeed, you can start grouping minor and patch updates so that you get a single PR per repository. Investigating issues becomes a bit trickier because of that. To give you some numbers out of 90 repositories enabled with Renovate, we have on average 4 PRs to investigate per week. Everything else is automatically merged
  5. Enable auto merging after some time, make sure your tests are solid and that you won\u2019t upgrade something that wasn\u2019t tested and will break once in production
"},{"location":"user-stories/swissquote/#is-all-this-effort-worth-it","title":"Is all this effort worth it?","text":"

The short answer is yes!

It took us almost a year, way longer than we thought, to catch up with the latest version of everything in our technical stack. But once we were confident enough in our tests to enable automatic merging of Pull Requests we were satisfied with the work we did to update our software stack. We knew we would be ready when an unplanned change arrives.

When that day came, in December 2021 with Log4Shell, it was a matter of hours to release the freshly merged Pull Requests, deploy the few applications we had, and notify the teams depending on our libraries. We were so quick to do it, in fact, that we had to do that three times with the chain of vulnerabilities that was found in Log4j that week.

Keep in mind that keeping your dependencies up-to-date is not just about the tooling, it\u2019s also about having a process:

We know the answers for our situation, we\u2019ll let you decide what the answers are for you.

"}]}