Upgrade to NodeJS 22 runtimes

[joebowbeer]

The GitHub workflows in this repo are specifying NodeJS runtime 19.x, which is an unmaintained version.

NodeJS 19.x was a non-LTS (odd) release that was only active for 6 months in 2022/23.

The recommended runtime today is NodeJS 22 (aka Jod), which is the Active LTS version:

• NodeJS 18 reached EOL on 5/2025
• NodeJS 19 reached EOL on 6/2023
• NodeJS 20 is currently in Maintenance mode
• NodeJS 22 is the Active LTS release until 11/2025

https://nodejs.org/en/about/previous-releases

sdk-typescript/package.json

Line 55 in abeea26

"node": ">= 18.13"

sdk-typescript/.github/workflows/publish.yml

Line 16 in abeea26

node-version: "19.x"

sdk-typescript/.github/workflows/test.yml

Line 16 in abeea26

node-version: [19.x]

[joebowbeer]

NodeJS 18.x is now unmaintained.

Neither NodeJS 18.x nor NodeJS 19.x will receive additional security updates such as the following:

https://nodejs.org/en/blog/vulnerability/may-2025-security-releases

[slinkydeveloper]

We now use node 20 as base, i think this can be closed. reopen if you need it

[joebowbeer]

Node 20 hasn't been active LTS for a year and will reach EOL in 7 months (4/30/2026).

If it reaches EOL, then it's not suitable for deployment - because vulnerabilities are no longer patched.

@slinkydeveloper If it takes 5 months to update the base, then the next ticket should be created in 2 months?

Or create the next ticket now? Node 24 will be active LTS next month (10/2025)

[slinkydeveloper]

I think we should bump to minimum 22 when 20 reaches EOL

[joebowbeer]

@slinkydeveloper writes

I think we should bump to minimum 22 when 20 reaches EOL

As I wrote, that will be several months too late for security conscious users.

That's why Node recommends planning to upgrade as soon as the release reaches maintenance phase, which for Node 20 was one year ago.