Update to Node 24?

[Aloe-recite]

Hi, many containers are stuck on Node 22, I manually updated to 24 and all were working fine, but i see the "update" command overwrites with node 22 again (node 22 is also giving me signature warnings in APT?).
Is it feasible to maually update to 24 and keep it that way, or is a general update coming?
TIA

[tremor021]

Which ones are "stuck"?

[Aloe-recite]

As far as I remember: Outline, Karakeep, Cronicle, UptimeKuma, Homepage, Peanut.... all old installations. 24 gets overwritten if I run "update"

[tremor021]

Outline

Karakeep

Cronicle

UptimeKuma

HomePage

PeaNUT

LTS was 22

So, basically you want us to update these apps to Node.js 24 even though apps themselves are not supporting that yet?
Interesting... Surely nothing can go wrong there

[Aloe-recite]

I don't want anything mate - I don't feel entitled to anything and much less in the position or experience to tell you what to do or give suggestions. I was just asking a general question, sorry if I made a stupid one.
These apps all seemed to work fine in my (obviously limited) tests, and since I keep getting the annoying "Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details" in APT, I thought that maybe an upgrade was due / necessary / feasible / whatever. Just a bad guess.

[tremor021]

We want to avoid updating apps to Node.js versions that app themselves are not officially supporting. There are cases where we did that, after we thoroughly checked the app, but its not something we wanna do by default. If we update Node.js to latest blindly, then any problem with the app is up to us to solve, as we are using unsupported method of deployment...