Update github workloads

[camillobruni]

• Use latest action versions
• Bump node version to current stable v22
• Use caches for node modules to slightly speed up setup
• Mild formatting was applied

[netlify]

✅ Deploy Preview for webkit-speedometer ready!

Name	Link
🔨 Latest commit	a8686c5
🔍 Latest deploy log	https://app.netlify.com/sites/webkit-speedometer/deploys/67a2326a79fad3000894db8f
😎 Deploy Preview	https://deploy-preview-478--webkit-speedometer.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rniwa]

Looks okay to me.

[camillobruni]

Simplified the test.yml file based on the feedback.
Looks like the netlify deployment is now unhappy with the upped node version requirement. @julienw is this easy to fix or should I just lower the requirements again?

[julienw]

Simplified the test.yml file based on the feedback. Looks like the netlify deployment is now unhappy with the upped node version requirement. @julienw is this easy to fix or should I just lower the requirements again?

just changed it :)

Another way would be to use a .node-version or .nvmrc file in the repository (this would also override any setting in the configuration UI BTW). I think node-version-file can also use that one BTW.
It's a bit too bad that netlify can't use the version specified in package.json :(

[julienw]

Thanks, looks good to me!

[julienw]

do we want to ensure that we stay on v22 by adding < 23 as well? I'm a bit afraid that this will switch to v24 automatically and we'll get build errors. We can always change that later if this happens of course.

[julienw]

I believe you need to run npm i to update package-lock.json as well.

[camillobruni]

ah yeah... of course.
Let me add a CI check for that as well in a separate PR.

[julienw]

I think npm ci does it for dependencies, it's disappointing it doesn't work for everything that can update it!

[julienw]

much better!