Use node 22 in CI

[bluwy]

Changes

Use node 22 instead of 18 since 22 is now the active LTS. Also added a new matrix to test ubuntu and node 22.

Theoretically it should be a little faster with node's recent perf improvements.

Testing

CI should pass

Docs

n/a

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4753318

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ematipico]

I don't think we should drop v18 yet (for macOS and Windows). We state that we still support it, so the CI should reflect that in case we break something.

[bluwy]

Wouldn't the same apply for node 20 and 22? Both have breaking changes which could not work in Astro, so they could be useful to be tested. But to not bloat our matrix we'd have to pick one between 18, 20, and 22, and picking v22 as the baseline as its the active LTS seems ok to me 🤔 Or do we want to test against the oldest supported LTS only?

[ematipico]

Now that I think about about, I believe we shouldn't support v18 anymore. Our semver says latest Maintenance LTS.

At the moment, there are two maintenance LTS, and the latest is v20. Did I get it right? If so, should we drop node v18?

[ematipico]

I think we can merge this PR, I don't have strong concerns that should block the PR