Document problem with `lts/*` staleness from actions/setup-node ?

[karlhorky]

actions/setup-node installs stale versions of Node.js when aliases like lts/* are used:

• Security: lts/* installs old LTS versions up to 1 month+ after release actions/setup-node#1236

Since nubjs/setup-nub aims for drop-in compatibility with actions/setup-node, I'm wondering whether this means bug-for-bug compatibility. I guess probably not, since I see some behavior differences.

But if this staleness problem is indeed present in nubjs/setup-nub too, then maybe this should be documented clearly.

[karlhorky]

I see this from the "How nub's Node provisioning differs from setup-node" section in the readme:

node-version and node-version-file are warm-up hints, not pins. They pre-provision that Node into nub's cache so the first nub call is warm — but nub still runs the project's declared Node at runtime. If the input disagrees with the project's resolved pin, the action emits a warning and the project pin wins.

It appears to almost answer my question, but doesn't speak specifically to how aliases are resolved... 🤔