chore(engines): bump node max version to v24.x.x LTS

[sjoukedv]

What does it do?

Bump node engine constraint maximum

Why is it needed?

Node v24 is the latest LTS version

Related issue(s)/PR(s)

Fixes #112

[dosubot]

Related Documentation

Checked 7 published document(s) in 1 knowledge base(s). No updates required.

^{How did I do? Any feedback?}  

[sjoukedv]

@jhoward1994 / @nclsndr could you give this a quick review?

[nclsndr]

Thank you @sjoukedv for raising this PR!
I'll take care of reviewing it asap.

Side note: in general, please avoid mentioning strapi maintainers directly on GH for new issue or PR. We have automated tracking and triage of new PRs, direct mentions mainly adds noise to this management. Thank you for your understanding 🙏

[nclsndr]

The change by itself is legit.
Yet, we also need to add node 24 in .github/workflows so that we guarantee the CI also checks for that version.

@sjoukedv let me know if you'd like to do it, otherwise I'd replay those changes in another PR.

[sjoukedv]

Thank you @sjoukedv for raising this PR! I'll take care of reviewing it asap.

Side note: in general, please avoid mentioning strapi maintainers directly on GH for new issue or PR. We have automated tracking and triage of new PRs, direct mentions mainly adds noise to this management. Thank you for your understanding 🙏

Sure, I had no idea how active this repository is considering the client is relatively new (at least for me). This was the only package for my application that did not support node v24 making me downgrade to v22. It's getting very confusing and frustrating with all the cross @strapi/ package node engine constraint, but also their dependency version amongst each other. Would be great to have automation in place to automatically bump the node version everywhere or a package constraint.

The change by itself is legit. Yet, we also need to add node 24 in .github/workflows so that we guarantee the CI also checks for that version.

@sjoukedv let me know if you'd like to do it, otherwise I'd replay those changes in another PR.

Done! I left 20 in there. Let me know if you would like to have it removed @nclsndr .

[nclsndr]

Thank you for the update @sjoukedv 👌

It's getting very confusing and frustrating with all the cross @strapi/ package node engine constraint, but also their dependency version amongst each other. Would be great to have automation in place to automatically bump the node version everywhere or a package constraint.

I'd be glad to have your pov on how you would improve the situation. Please consider opening a discussion on strapi/strapi main repository.

[nclsndr]

I left 20 in there

Yes that's perfect, we'd remove Node 20 once EOL is reached: https://nodejs.org/en/about/previous-releases

[nclsndr]

LGTM

[nclsndr]

@sjoukedv package release has been done: v1.6.1