Files
Jamie Tanna a462e4ec3b refactor(docs): don't use an end for autogenerated docs (#43242)
* refactor(docs): don't use an `end` for autogenerated docs

As part of #42910, we wanted to avoid needing a "begin" and "end" to
each of our autogenerated docs replacements.

While looking into it, we're not actually using the "end" for anything,
so we can instead refactor this to be a single-line replacement.

To simplify the code and docs, we can remove this. At the point we need
this again, we can re-add the functionality.

Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io>

* fixup! Merge remote-tracking branch 'origin/HEAD' into chore/no-replaceStop

---------

Co-authored-by: Claude Sonnet 4.6 <jamie.tanna+claude-code@mend.io>
2026-05-13 15:49:00 +00:00

28 lines
652 B
Markdown

---
title: Datasources
---
# Datasources
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:
```json
{
"packageRules": [
{
"matchDatasources": ["npm"],
"matchPackageNames": ["lodash"],
"automerge": true
}
]
}
```
## Supported Datasources
<!-- Autogenerate in https://github.com/renovatebot/renovate -->