Support Node 24 runtime

[levibuzolic]

Description

Update the action runtime, engine constraint, and CI workflow pins from Node 20 to Node 24 per GitHub's guidance on the deprecation of Node 20 on GitHub Actions runners: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

To align with other GitHub actions it'd probably make sense to release this under a new major version.

• I have read and understood the contributing guidelines

[paulo-ferraz-oliveira]

Is this breaking for the consumer? What's the consequence of just moving versions to the one that'll come after this PR is accepted?

[paulo-ferraz-oliveira]

new major version

Is it absolutely necessary and/or breaking? We don't wanna bump for the sake of it, but only if required.

If, at the same time this is being accepted, support is also dropped for older runners, I'm Ok to not bump major.

@starbelly, @wojtekmach, any ideas?

[levibuzolic]

Could see reasons both for and against. But really this should be all completely unnoticeable to downstream users, so just a regular version bump is probably fine. 👍

[paulo-ferraz-oliveira]

I'll wait on further feedback. If we deem it breaking we will want to respect versioning, but if it's not (or e.g. GitHub only supports 24+ is their own runners) then it should be fine to just bump minor.

[PJUllrich]

Small FYI: GitHub will force-run this action on Node 24 from June 2nd, 2026 onward (https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/). Ideally, a v2 running on Node 24 would be released before that date so that we can test it out before it becomes compulsory.

[paulo-ferraz-oliveira]

a v2 running on Node 24

We've stayed away from moving to v2 in the past for similar reasons (I'm not really sure how this would break, though). As soon as I have feedback from other maintainers we'll move this forward.

[wojtekmach]

I'm fine with either, I'd personally keep it as v1 as node 20 will be defunct in a few months anyway.

[paulo-ferraz-oliveira]

Ok, let's go v1 then. I agree with what you say, and if it's failing for newer releases developers can most likely pin it to whatever is the current version.

[paulo-ferraz-oliveira]

ℹ️ This has been released in v1.24.0.

v1.24 was moved to accompany this tag, as was v1.