-
-
Notifications
You must be signed in to change notification settings - Fork 598
build: Release #1664
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
Merged
Merged
build: Release #1664
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.4](parse-community/Parse-SDK-JS@4.0.0-alpha.3...4.0.0-alpha.4) (2022-12-21) ### Features * Add Node 16 and 18 support ([parse-community#1598](parse-community#1598)) ([2c79a31](parse-community@2c79a31))
# [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))
# [4.0.0-beta.1](parse-community/Parse-SDK-JS@3.5.1...4.0.0-beta.1) (2023-01-23) ### 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)) * Remove support for Node <14 ([parse-community#1603](parse-community#1603)) ([bc04b4b](parse-community@bc04b4b)) ### Features * Add Node 16 and 18 support ([parse-community#1598](parse-community#1598)) ([2c79a31](parse-community@2c79a31)) * Add node 19 support ([8ed0fab](parse-community@8ed0fab)) * Add Node 19 support ([parse-community#1643](parse-community#1643)) ([dfb5196](parse-community@dfb5196)) ### Performance Improvements * Avoid CORS preflight request by removing upload listener when not used ([parse-community#1610](parse-community#1610)) ([6125419](parse-community@6125419)) ### 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)) * This release removes support for Node versions <14 ([bc04b4b](bc04b4b))
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request!
|
🎉 This change has been released in version 4.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.