Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: test on Node 22 explicitely #2831

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Conversation

bashmish
Copy link
Member

@bashmish bashmish commented Oct 23, 2024

What I did

  1. While Node 23 and 24 are being relesed, we start getting errors on them and we lost Node 22 testing which is probably most important at the moment, so I added it to the suite explicitely.

Node 18 is still required since it's in official maintenance until 2025-04-30
https://nodejs.org/en/about/previous-releases
https://github.com/nodejs/release#release-schedule

Copy link

changeset-bot bot commented Oct 23, 2024

⚠️ No Changeset found

Latest commit: 7392434

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@bashmish bashmish merged commit fe1bfd0 into master Oct 23, 2024
7 of 9 checks passed
@bashmish bashmish deleted the fix/test-on-node-22-explicitely branch October 23, 2024 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant