Can the node version upgrade be part of v3?

[kishaningithub]

Context

• We have failing pipelines due to 2.8.2 minor version which upgrades the node runtime from 16 to 20. Since we are running this in a self hosted runner running amzon linux 2 which out of the box comes with an ancient GLIBC version and is not supported from node js versions >= 18

Error

/home/runner-7748545357-818749055714-0/action-runner/externals/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /home/runner-7748545357-818749055714-0/action-runner/externals/node20/bin/node)
/home/runner-7748545357-818749055714-0/action-runner/externals/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /home/runner-7748545357-818749055714-0/action-runner/externals/node20/bin/node)

Our pipeline

  - name: Post Comment to GitHub PR
    uses: mshick/add-pr-comment@v2
    with:
      message-path: "long-message.txt"

Proposal

• The node runtime version bump should result in a major version bump (v2 to v3). All the other github actions also follow this practive. Examples below where the major version was bumped because of an upgrade to the node runtime from 16 to 20
  • https://github.com/actions/checkout/releases/tag/v4.0.0
  • https://github.com/actions/setup-go/releases/tag/v5.0.0
  • https://github.com/actions/setup-python/releases/tag/v5.0.0

[kishaningithub]

It would be great if this request can be treated with high priority