build: Release #2050
Merged
build: Release #2050
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
# [4.3.0-alpha.1](parse-community/Parse-SDK-JS@4.2.0...4.3.0-alpha.1) (2023-09-26) ### Bug Fixes * `ParseUser.linkWith` doesn't remove anonymous auth data ([parse-community#2007](parse-community#2007)) ([7e2585c](parse-community@7e2585c)) * Hard-coding of `react-native` path does not work for workspace builds ([parse-community#1930](parse-community#1930)) ([8222f3c](parse-community@8222f3c)) ### Features * Add Bytes type to `Parse.Schema` ([parse-community#2001](parse-community#2001)) ([343d0d7](parse-community@343d0d7)) * Add Cloud Code context accessibility to `ParseUser.logIn` ([parse-community#2010](parse-community#2010)) ([2446007](parse-community@2446007)) * Add support for custom EventEmitter ([parse-community#1999](parse-community#1999)) ([ca568a6](parse-community@ca568a6)) * Add support for excluding keys in `ParseQuery.findAll` ([parse-community#2000](parse-community#2000)) ([012ba4c](parse-community@012ba4c)) * Add support to invoke a Cloud Function with a custom `installationId` via `Parse.Cloud.run` ([parse-community#1939](parse-community#1939)) ([eb70b93](parse-community@eb70b93)) * Allow overriding `Parse.Error` message with custom message via new Core Manager option `PARSE_ERRORS` ([parse-community#2014](parse-community#2014)) ([be0c8a6](parse-community@be0c8a6)) * Login with username, password and additional authentication data via `ParseUser.logInWithAdditionalAuth` ([parse-community#1955](parse-community#1955)) ([2bad411](parse-community@2bad411))
# [4.3.0-alpha.2](parse-community/Parse-SDK-JS@4.3.0-alpha.1...4.3.0-alpha.2) (2023-10-03) ### Bug Fixes * Docs fail with `Cannot find module 'taffydb'` ([parse-community#2036](parse-community#2036)) ([dc91d0f](parse-community@dc91d0f))
…bject.destroyEventually` not handled on custom `Parse.Error.CONNECTION_FAILURE` message (parse-community#2032)
# [4.3.0-alpha.3](parse-community/Parse-SDK-JS@4.3.0-alpha.2...4.3.0-alpha.3) (2023-10-04) ### Bug Fixes * Connection failure in `Parse.Object.saveEventually` and `Parse.Object.destroyEventually` not handled on custom `Parse.Error.CONNECTION_FAILURE` message ([parse-community#2032](parse-community#2032)) ([4da3ebc](parse-community@4da3ebc))
# [4.3.0-alpha.4](parse-community/Parse-SDK-JS@4.3.0-alpha.3...4.3.0-alpha.4) (2023-10-07) ### Bug Fixes * Error in web context when `window.indexedDB` API is available but protected ([parse-community#2039](parse-community#2039)) ([360981f](parse-community@360981f))
# [4.3.0-alpha.5](parse-community/Parse-SDK-JS@4.3.0-alpha.4...4.3.0-alpha.5) (2023-10-26) ### Bug Fixes * Security upgrade crypto-js from 4.1.1 to 4.2.0 ([parse-community#2042](parse-community#2042)) ([681fbdf](parse-community@681fbdf))
# [4.3.0-alpha.6](parse-community/Parse-SDK-JS@4.3.0-alpha.5...4.3.0-alpha.6) (2023-10-28) ### Bug Fixes * Security upgrade browserify-sign from 4.2.1 to 4.2.2 ([parse-community#2043](parse-community#2043)) ([fd50b9d](parse-community@fd50b9d))
|
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request!
|
* release: chore(release): 4.3.0 [skip ci] release
|
🎉 This change has been released in version 4.3.1-beta.1 |
|
🎉 This change has been released in version 4.3.1 |
|
🎉 This change has been released in version 4.3.1-alpha.1 |
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.