-
-
Notifications
You must be signed in to change notification settings - Fork 598
build: Release beta #1658
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
build: Release beta #1658
Conversation
BREAKING CHANGE: This release removes support for Node versions <14
# [4.0.0-alpha.1](parse-community/Parse-SDK-JS@3.5.1-alpha.2...4.0.0-alpha.1) (2022-11-10) ### Bug Fixes * Remove support for Node <14 ([parse-community#1603](parse-community#1603)) ([bc04b4b](parse-community@bc04b4b)) ### BREAKING CHANGES * This release removes support for Node versions <14 ([bc04b4b](bc04b4b))
…error in Cloud Code Triggers `beforeConnect` or `beforeSubscribe` (parse-community#1490) BREAKING CHANGE: Calling `Parse.Query.subscribe()` will now return a rejected promise if an error is thrown in Cloud Code Triggers `beforeConnect` or `beforeSubscribe`; in previous releases a resolved promise was returned, even if subscribing failed and it was necessary to create an `error.on` listener to handle these errors (parse-community#1490)
# [4.0.0-alpha.2](parse-community/Parse-SDK-JS@4.0.0-alpha.1...4.0.0-alpha.2) (2022-11-15) ### Bug Fixes * `Parse.Query.subscribe()` does not return a rejected promise on error in Cloud Code Triggers `beforeConnect` or `beforeSubscribe` ([parse-community#1490](parse-community#1490)) ([96d7174](parse-community@96d7174)) ### BREAKING CHANGES * Calling `Parse.Query.subscribe()` will now return a rejected promise if an error is thrown in Cloud Code Triggers `beforeConnect` or `beforeSubscribe`; in previous releases a resolved promise was returned, even if subscribing failed and it was necessary to create an `error.on` listener to handle these errors (parse-community#1490) ([96d7174](96d7174))
# [4.0.0-alpha.3](parse-community/Parse-SDK-JS@4.0.0-alpha.2...4.0.0-alpha.3) (2022-11-18) ### Performance Improvements * Avoid CORS preflight request by removing upload listener when not used ([parse-community#1610](parse-community#1610)) ([6125419](parse-community@6125419))
# [4.0.0-alpha.5](parse-community/Parse-SDK-JS@4.0.0-alpha.4...4.0.0-alpha.5) (2023-01-06) ### Features * Add node 19 support ([8ed0fab](parse-community@8ed0fab)) * Add Node 19 support ([parse-community#1643](parse-community#1643)) ([dfb5196](parse-community@dfb5196))
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request!
|
Codecov ReportBase: 99.93% // Head: 99.89% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## beta #1658 +/- ##
==========================================
- Coverage 99.93% 99.89% -0.04%
==========================================
Files 61 61
Lines 5966 5973 +7
Branches 1366 1367 +1
==========================================
+ Hits 5962 5967 +5
- Misses 4 6 +2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@dblythy did we forget anything here in the node 16 CI? the node 16 tests are consistently failing with connection errors. could you take a look? |
I will investigate |
Interestingly, the Node 16 tests for the latest commit on the alpha branch seemed to pass except for one flaky test. So it's strange this is failing in this PR where the only difference is commit 5b31b9f. It may be something that occurs due to the merge. |
Ran the Node 16 tests again and they passed except for 1 flaky test. There may be some other issue with the CI. Going ahead and merging. |
🎉 This change has been released in version 4.0.0-beta.1 |
🎉 This change has been released in version 4.0.0 |
🎉 This change has been released in version 4.0.0-alpha.6 |
No description provided.