Comment 14 for bug 1979639

> ...it has basically no impact on our own applications...

Just because you and I can't find a case that would break doesn't mean there isn't one. So there's risk. And I think the consequences, because of the nature of this package, could be quite large.

> I'm not particularly keen on doing this SRU just for the sake of 1/, and 2/ can be fixed in that package, but do we want to break things for 3/ ?

We'll have to break it at some point, right? Otherwise the configuration file format in /etc could never move on. A new release would be the appropriate time, as has happened in Jammy. So now seems a good a time as any, given that it's already happened, and it requires effort and risk to reverse it.

Upstream NodeJS should be able to release a fixed version themselves. In fact I believe it's the norm for external software sources to have to adjust themselves for new distribution releases anyway. Is there any reason this isn't acceptable to them?