chore: Update action to use node20

[gansheer]

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

[gansheer]

@squakez could you tell me if there is a ci failure not linked to #19 ? 🙏

[squakez]

Most probably it's linked with that issue.

[gansheer]

Most probably it's linked with that issue.

Can it be merged then ?

[karfau]

It looks like the release is tagged in the repository and that version is also listed in the GitHub Marketplace, but when using the action v2 it is still resulting in a warning about using node16.

Maybe it is related to the failed checks on the main branch?

Found the issue: the v2 tag is still pointing to f47f727, so using the full version should be a workaround.

[squakez]

Found the issue: the v2 tag is still pointing to f47f727, so using the full version should be a workaround.

You need to use v2.0.4 which is the version that had this fixed. We haven't updated v2 which is the same as v2.0.0.

[karfau]

May it's worth mentioning this in the readme, since it is very common to do that, and it is recommended in the github docs: https://docs.github.com/en/actions/creating-actions/releasing-and-maintaining-actions#example-developer-process

We recommend creating releases using semantically versioned tags – for example, v1.1.3 – and keeping major (v1) and minor (v1.1) tags current to the latest appropriate commit. For more information, see "About custom actions" and "About semantic versioning.

[squakez]

I'll do an update shortly then.

[squakez]

Should be done now. v2 is updated to v2.0.4 git commit.