Let Renovate reach the example plugins' manifests

README.md

@@ -713,8 +713,8 @@ included, since the plugin folder *is* the repo. A baked image needs no extra st
   contract, turning a sign-in redirect into a 500, so discovery refuses one there at boot.
 - **The host never upgrades or dedupes your dependencies.** Two plugins depending on the same package
   each get their own copy at their own version, so neither can break the other by upgrading — and
-  keeping yours current, and audited, is yours to own. Renovate here watches the host's manifests
+  keeping yours current, and audited, is yours to own. Renovate here watches every manifest in this
-  only.
+  repo, the example plugins included — a plugin in its own repo needs its own.
 - **Depend on packages that ship JavaScript.** Node refuses to strip types under `node_modules`, so a
   dependency whose entry is `.ts` fails at import with `ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING`.
 

renovate.json

@@ -1,6 +1,8 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
   "extends": ["config:recommended"],
+  "description": "ignorePaths overrides config:recommended's :ignoreModulesAndTests, which ignores **/examples/** — an example plugin's dependencies get update PRs like any other manifest here",
+  "ignorePaths": ["**/node_modules/**"],
   "automerge": true,
   "commitBody": "Release-Bump: {{{updateType}}}",
   "packageRules": [