build: add support for latest node versions

[maschad]

Closes #2221

This also upgrades pnpm

[arboleya]

@maschad You must add the new node version to the CI matrix.

@danielbate Right?

fuels-ts/.github/workflows/test.yaml

Lines 20 to 26 in 93f1407

	matrix:
	env:
	[
	{ name: node, version: 18.18.2 },
	{ name: node, version: 20 },
	{ name: browser },
	]

Another question is: should we still support v18?

[maschad]

@maschad You must add the new node version to the CI matrix.

@danielbate Right?

That looks about right, good catch!

Another question is: should we still support v18?

I would say so given it's still maintained according to the current release working group

[danielbate]

There's a few places (here, here etc.) where we default to v20, lets get those updated too?

[petertonysmith94]

There's a few places (here, here etc.) where we default to v20, lets get those updated too?

I'd suggest updating to v20.14.0 as it's the LTS version of Node.

[maschad]

There's a few places (here, here etc.) where we default to v20, lets get those updated too?

Thanks for pointing that out, I've done that in e54dda8 (#2539) , unfortunately there isn't a clear formulaic way to ensure I've updated it everywhere, but I've looked where I thought may be relevant 😅

[maschad]

One workflow seems to be stuck.

I believe the only way to unfreeze it is to do what we discussed since it's still a required workflow. I would do that after this is merged though to prevent interference with other open PRs.

[maschad]

@nedsalk do you have any ideas why this might be failing to fetch coverage here

Seems to be happening on quite a few PRs, raised an issue #2612

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
79.38%(+0%)	71.29%(+0%)	76.44%(+0%)	79.45%(+0%)

Changed Files:

Coverage values did not change👌.