Setting up renovate bot with nodesource

[kevin-kortum-trustedshops]

Hi there,
i'd like to set up https://github.com/renovatebot/renovate for a NodeJS based setup which pull the package from the nodesource repository. However, due to the missing possibility to list files in the browser, i don't how a check would look like.

Here is what i got so far:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:recommended",
  ],
  "customManagers": [
    {
      "customType": "regex",
      "fileMatch": [
        "^Dockerfile"
      ],
      "matchStrings": [
        "#\\s*renovate:\\s*?(release=(?<release>.*?))?\\s*depName=(?<depName>.*?)?\\sENV .*?_VERSION=\"(?<currentValue>.*)\""
      ],
      "registryUrlTemplate": "https://deb.debian.org/debian?{{#if release }}release={{release}}{{else}}suite=stable{{/if}}&components=main,contrib,non-free&binaryArch=amd64",
      "datasourceTemplate": "deb"
    }
  ],
  "packageRules": [
    {
      "matchDatasources": [
        "deb"
      ],
      "matchPackageNames": [
        "nodejs"
      ],
      "registryUrls": [
        "https://deb.nodesource.com/node_{{major}}.x/pool/main/n/nodejs/{{depName}}_{{version}}-1nodesource1_{{binaryArch}}.deb"
      ]
    },
  ]
}

The parser above is just copy & paste from the documentation at https://docs.renovatebot.com/modules/datasource/deb/#set-url-when-using-a-debian-repository so i think i might need to update it to fit the uncommon url scheme of nodesource. But to be honest, i have no clue.

Has anyone made experiences with it if it even works?

[NaveenHiranya]

I haven't tested this exact setup with NodeSource, but I think the main issue is that the deb datasource expects a Debian repository structure with package metadata that Renovate can query. NodeSource's repository layout appears to be different from the standard Debian mirrors used in the documentation example.

[kevin-kortum-trustedshops]

Yeah, that is quite possible. I have a similar situation with the official nginx debian repository, which randomly works. For me it is either the manager or the source that is borked. But that would require deeper research. If the nodesource repo was broken, people should not be able to use it, right? Something there must be correct then.