Skip to content

Conversation

@mtrezza
Copy link
Member

@mtrezza mtrezza commented Nov 18, 2023

No description provided.

parseplatformorg and others added 22 commits September 26, 2023 03:02
# [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))
…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.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))
* release:
  chore(release): 4.3.0 [skip ci]
  release
## [4.3.1-beta.1](parse-community/Parse-SDK-JS@4.3.0...4.3.1-beta.1) (2023-11-16)

### 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))
* Docs fail with `Cannot find module 'taffydb'` ([parse-community#2036](parse-community#2036)) ([dc91d0f](parse-community@dc91d0f))
* Error in web context when `window.indexedDB` API is available but protected ([parse-community#2039](parse-community#2039)) ([360981f](parse-community@360981f))
* Security upgrade browserify-sign from 4.2.1 to 4.2.2 ([parse-community#2043](parse-community#2043)) ([fd50b9d](parse-community@fd50b9d))
* Security upgrade crypto-js from 4.1.1 to 4.2.0 ([parse-community#2042](parse-community#2042)) ([681fbdf](parse-community@681fbdf))
@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title build: release build: Release Nov 18, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please link an issue that describes the reason for this pull request, otherwise your pull request will be closed. Make sure to write it as Closes: #123 in the PR description, so I can recognize it.

@codecov
Copy link

codecov bot commented Nov 18, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (ac556fc) 100.00% compared to head (d2c7b28) 100.00%.
Report is 2 commits behind head on release.

Additional details and impacted files
@@            Coverage Diff            @@
##           release     #2052   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           61        61           
  Lines         6168      6178   +10     
  Branches      1498      1496    -2     
=========================================
+ Hits          6168      6178   +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mtrezza mtrezza merged commit 9449cc3 into parse-community:release Nov 18, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.1

@parseplatformorg parseplatformorg added the state:released Released as stable version label Nov 18, 2023
@mtrezza mtrezza deleted the build-release branch November 18, 2023 14:16
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 4.3.1-alpha.1

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Nov 18, 2023
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-alpha.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:released Released as stable version state:released-alpha Released as alpha version

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants