Do we need a node@15? We typically only keep versioned formulae if they're either a) still maintained, or b) needed by other formulae.

My understanding of the node version scheme is that node@15 will no longer be maintained, and I'm not sure other formulae will need this.

Node 15 will be maintained until June 1st, see https://nodejs.org/en/about/releases/

But that is of course a very short period of time. I would totally understand if the Homebrew projects decides against adding a dedicated node@15 formula.

Do you think users will find it useful? If there's a genuine use for it that you can't get for some reason with node@14 and node@16, then I won't be opposed to it. (I don't speak for other maintainers here though.)

If we do add it, though, we should probably already add the deprecate! line for when it's no longer supported. Oops, missed that you already did this.

It looks like some formulae failed the tests at #75595, so it may well be that they do need node@15.

Do you think users will find it useful? If there's a genuine use for it that you can't get for some reason with node@14 and node@16, then I won't be opposed to it. (I don't speak for other maintainers here though.)

If you look at the test failure of the node 16 bump, you can see at least one formula that is apparently not yet ready for node 16. Keeping Node 15 for a little while might smoothen the transition.

If we do add it, though, we should probably already add the deprecate! line for when it's no longer supported.

I've added this already.

Honestly, I'd rather just make jhipster depend on node@14.

Node 15 will only last another month while if we introduce this formula we would have to go through the full deprecation -> disabled -> removal process which takes much, much longer.

All right, let's close this PR then. 😃