-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
feat: Add Node 22 support #9187
Conversation
Thanks for opening this pull request!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #9187 +/- ##
=======================================
Coverage 94.16% 94.16%
=======================================
Files 186 186
Lines 14750 14750
=======================================
Hits 13889 13889
Misses 861 861 ☔ View full report in Codecov by Sentry. |
@dplewis the issue is that there are 4 tests failing. The punycode library that should be used instead of the deprecated Node.js feature describes how to implement it, but that doesn't seem to work. It still seems to be using the Node.js feature. |
From the failing tests I assume this these deprecation warnings come from certain dependencies which have a sub-dependency on Node.js internal punycode. With
I believe these errors come from 3rd party dependencies, so we cannot do much about it. A solution is to change the tests so they ignore deprecation warnings in the stderr output. This is just a deprecation warnings after all, not an error. The history of DEP0040 shows that while the deprecation happened in Node 7, only since Node 21 is it a runtime deprecation, so that's why it became visible now. |
Changed the tests so that deprecation gets ignored; once the feature gets removed from Node.js, the process should fail to launch a Parse Server instance and the tests will also fail. Also removed Parse Server's internal code reliance on Node.js punycode feature to make it ready for the feature removal. |
# [7.3.0-alpha.1](7.2.0...7.3.0-alpha.1) (2024-07-09) ### Features * Add Node 22 support ([#9187](#9187)) ([7778471](7778471))
🎉 This change has been released in version 7.3.0-alpha.1 |
# [7.3.0-beta.1](7.2.0...7.3.0-beta.1) (2024-10-03) ### Bug Fixes * Custom object ID allows to acquire role privileges ([GHSA-8xq9-g7ch-35hg](GHSA-8xq9-g7ch-35hg)) ([#9317](#9317)) ([13ee52f](13ee52f)) * Parse Server `databaseOptions` nested keys incorrectly identified as invalid ([#9213](#9213)) ([77206d8](77206d8)) * Parse Server installation fails due to post install script incorrectly parsing required min. Node version ([#9216](#9216)) ([0fa82a5](0fa82a5)) * Parse Server option `maxLogFiles` doesn't recognize day duration literals such as `1d` to mean 1 day ([#9215](#9215)) ([0319cee](0319cee)) * Security upgrade path-to-regexp from 6.2.1 to 6.3.0 ([#9314](#9314)) ([8b7fe69](8b7fe69)) ### Features * Add atomic operations for Cloud Config parameters ([#9219](#9219)) ([35cadf9](35cadf9)) * Add Cloud Code triggers `Parse.Cloud.beforeSave` and `Parse.Cloud.afterSave` for Parse Config ([#9232](#9232)) ([90a1e4a](90a1e4a)) * Add Node 22 support ([#9187](#9187)) ([7778471](7778471)) * Add support for asynchronous invocation of `FilesAdapter.getFileLocation` ([#9271](#9271)) ([1a2da40](1a2da40))
🎉 This change has been released in version 7.3.0-beta.1 |
# [7.3.0](7.2.0...7.3.0) (2024-10-03) ### Bug Fixes * Custom object ID allows to acquire role privileges ([GHSA-8xq9-g7ch-35hg](GHSA-8xq9-g7ch-35hg)) ([#9317](#9317)) ([13ee52f](13ee52f)) * Parse Server `databaseOptions` nested keys incorrectly identified as invalid ([#9213](#9213)) ([77206d8](77206d8)) * Parse Server installation fails due to post install script incorrectly parsing required min. Node version ([#9216](#9216)) ([0fa82a5](0fa82a5)) * Parse Server option `maxLogFiles` doesn't recognize day duration literals such as `1d` to mean 1 day ([#9215](#9215)) ([0319cee](0319cee)) * Security upgrade path-to-regexp from 6.2.1 to 6.3.0 ([#9314](#9314)) ([8b7fe69](8b7fe69)) ### Features * Add atomic operations for Cloud Config parameters ([#9219](#9219)) ([35cadf9](35cadf9)) * Add Cloud Code triggers `Parse.Cloud.beforeSave` and `Parse.Cloud.afterSave` for Parse Config ([#9232](#9232)) ([90a1e4a](90a1e4a)) * Add Node 22 support ([#9187](#9187)) ([7778471](7778471)) * Add support for asynchronous invocation of `FilesAdapter.getFileLocation` ([#9271](#9271)) ([1a2da40](1a2da40))
🎉 This change has been released in version 7.3.0 |
Pull Request
Approach
Just trying out CI; this also removes specific Node.js versions for testing; still to be discussed whether we want that.
Tasks