If you mean a custom nodes package.json then yes, there should be a node-red section (but it is not mandatory, just recommended & good authorship & scored against)
If you mean the node-red-node-test-helpers package should have a node-red section, then I am not certain it does since it is typically included as a dev dependency alongside the min supported node-red version in your custom node (see the readme)
OK, but it would seem sensible to have a minimum node-red version listed somewhere? Unless there really isn't a minimum, in which case, it might be sensible to say so in the docs?
There are explicit Node-RED version numbers in the Getting Started doc: 1.1.0 and 1.3.5 in two sections as of today.
This leaves an impression that one of those versions should be the go-to version for beginners, although they might be random situational examples (?).
For this reason, our internal NR had been locked onto a recommended version by that page for a long time.
When I was following the test-helper node's tutorial, I forgot to link node-red executable, which brought me up all the way to 3.0.2. So I was a bit confused and was wondering if NR 3.x was required.
I just wanted to confirm that we can stay with a version older than 3.x, say 2.0.5, and introduce the test-helper node to our codebase at the same time.
The main breakage was dropping support for node 12 and earlier. That meant that users had to also update nodejs. And then recompile any nodes that had binary bindings etc. any other breakage would be noted in the release notes.