Pick node versions from node-build

[zbynek]

Tell us more.

Currently .tool-versions updates are proposed when the new Node version is published to nodejs.org (I believe https://nodejs.org/download/release/index.json is used ), but for it to actually work with asdf it needs to be added to https://github.com/nodenv/node-build/tree/main/share/node-build which happens later, resulting in broken build on the first CI run. It might be useful to check node-build support instead.

[rarkins]

It's a good idea for us to follow this, but what's the best way to get the "listing"? Depending on a "curl" of https://github.com/nodenv/node-build/tree/main/share/node-build is risky because it relies on GitHub not changing their HTML formatting.

Here is an example with curl and jq which we could port into a new datasource, or someone could probably convert into a custom JSON datasource right away: curl -s "https://api.github.com/repos/nodenv/node-build/git/trees/main?recursive=1" | jq -r '[.tree[] | select(.path | startswith("share/node-build/")) | .path | sub("share/node-build/"; "")]'. Note: no release timestamps unless we used a different API or approach and could get git last modified date somehow (which would be usually accurate, but not always).

[rarkins]

@zbynek FYI you could even potentially do this via config, e.g. packageRules with overrideDatasource, overridePackageName, and then a custom datasource to match. However I think it's a good idea to support this datasource natively one day

[zbynek]

Another alternative without HTML parsing:

curl -L  -H "Accept: application/vnd.github+json"   -H "X-GitHub-Api-Version: 2022-11-28"   https://api.github.com/repos/nodenv/node-build/contents/share/node-build | jq '.[].name'

One problem with using the GH folder listing is that it also contains versions that are not numeric, e.g. "20.x-dev".

[rarkins]

Renovate's versioning can be used to filter those out. e.g. if you use semver versioning, it will ignore any results which aren't numerical x.y.z

[rarkins]

@zbynek can you put this into a demo repo? i.e. a repo with .tool-versions or whatever it is.

I think we can add this as a built-in custom datasource to begin with.

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team