ci: pin node to under 20.5.1

[buffalojoec]

I spotted this in one of the PRs linked in nodejs/node#49497 .

It should solve our CI problem until the issue is resolved (?).

[steveluscher]

I'm going to presume we can preemptively allowlist >=20.6.1. Let's see if CI is OK with that.

[mergify]

Automerge label removed due to a CI failure

[buffalojoec]

I'm going to presume we can preemptively allowlist >=20.6.1. Let's see if CI is OK with that.

Didn't work on mine either, weird.

[steveluscher]

Didn't work on mine either, weird.

Well, it depends on what you mean by ‘work.’ The engines thing doesn't affect this, I don't think:

solana-web3.js/.github/workflows/pull-requests.yml

Lines 60 to 63 in 94b4d49

	matrix:
	node:
	- 'current'
	- 'lts/*'

That's the only thing that will fix CI. The engines thing is for people who install us, I think.

[steveluscher]

I wouldn't worry about it too much. Let's just let them ship nodejs/node#49528.

[2501babe]

perhaps temporarily remove the rule where a failure on node current aborts the run on node lts? assuming this is trivial anyway

[buffalojoec]

That's the only thing that will fix CI. The engines thing is for people who install us, I think.

This does sound more logical ha

[github-actions]

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.