[Snyk] Upgrade parse from 4.1.0 to 4.3.1 #4
  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.
  
    
  
    
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade parse from 4.1.0 to 4.3.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: parse
- 
        4.3.1 - 2023-11-18
 - Connection failure in 
- Docs fail with 
- Error in web context when 
- Security upgrade browserify-sign from 4.2.1 to 4.2.2 (#2043) (fd50b9d)
- Security upgrade crypto-js from 4.1.1 to 4.2.0 (#2042) (681fbdf)
 
- 
        4.3.1-beta.1 - 2023-11-16
 - Connection failure in 
- Docs fail with 
- Error in web context when 
- Security upgrade browserify-sign from 4.2.1 to 4.2.2 (#2043) (fd50b9d)
- Security upgrade crypto-js from 4.1.1 to 4.2.0 (#2042) (681fbdf)
 
- 
        4.3.1-alpha.1 - 2023-11-18
 - Connection failure in 
- Docs fail with 
- Error in web context when 
- Security upgrade browserify-sign from 4.2.1 to 4.2.2 (#2043) (fd50b9d)
- Security upgrade crypto-js from 4.1.1 to 4.2.0 (#2042) (681fbdf)
 
- 
        4.3.0 - 2023-11-16
 
- Hard-coding of 
 - Add Bytes type to 
- Add Cloud Code context accessibility to 
- Add support for custom EventEmitter (#1999) (ca568a6)
- Add support for excluding keys in 
- Add support to invoke a Cloud Function with a custom 
- Allow overriding 
- Login with username, password and additional authentication data via 
 
- 
        4.3.0-beta.1 - 2023-09-16
      
- 
        4.3.0-alpha.6 - 2023-10-28
 - Security upgrade browserify-sign from 4.2.1 to 4.2.2 (#2043) (fd50b9d)
 
- 
        4.3.0-alpha.5 - 2023-10-26
 - Security upgrade crypto-js from 4.1.1 to 4.2.0 (#2042) (681fbdf)
 
- 
        4.3.0-alpha.4 - 2023-10-07
 - Error in web context when 
 
- 
        4.3.0-alpha.3 - 2023-10-04
 - Connection failure in 
 
- 
        4.3.0-alpha.2 - 2023-10-03
 - Docs fail with 
 
- 
        4.3.0-alpha.1 - 2023-09-26
 
- Hard-coding of 
 - Add Bytes type to 
- Add Cloud Code context accessibility to 
- Add support for custom EventEmitter (#1999) (ca568a6)
- Add support for excluding keys in 
- Add support to invoke a Cloud Function with a custom 
- Allow overriding 
- Login with username, password and additional authentication data via 
 
- 
        4.2.0 - 2023-09-15
      
- 
        4.2.0-beta.1 - 2023-05-01
      
- 
        4.2.0-alpha.10 - 2023-09-03
      
- 
        4.2.0-alpha.9 - 2023-09-01
      
- 
        4.2.0-alpha.8 - 2023-08-30
      
- 
        4.2.0-alpha.7 - 2023-08-29
      
- 
        4.2.0-alpha.6 - 2023-08-27
      
- 
        4.2.0-alpha.5 - 2023-08-27
      
- 
        4.2.0-alpha.4 - 2023-07-23
      
- 
        4.2.0-alpha.3 - 2023-06-11
      
- 
        4.2.0-alpha.2 - 2023-06-08
      
- 
        4.2.0-alpha.1 - 2023-05-01
      
- 
        4.1.0 - 2023-05-01
      
from parse GitHub release notes4.3.1 (2023-11-18)
Bug Fixes
Parse.Object.saveEventuallyandParse.Object.destroyEventuallynot handled on customParse.Error.CONNECTION_FAILUREmessage (#2032) (4da3ebc)Cannot find module 'taffydb'(#2036) (dc91d0f)window.indexedDBAPI is available but protected (#2039) (360981f)4.3.1-beta.1 (2023-11-16)
Bug Fixes
Parse.Object.saveEventuallyandParse.Object.destroyEventuallynot handled on customParse.Error.CONNECTION_FAILUREmessage (#2032) (4da3ebc)Cannot find module 'taffydb'(#2036) (dc91d0f)window.indexedDBAPI is available but protected (#2039) (360981f)4.3.1-alpha.1 (2023-11-18)
Bug Fixes
Parse.Object.saveEventuallyandParse.Object.destroyEventuallynot handled on customParse.Error.CONNECTION_FAILUREmessage (#2032) (4da3ebc)Cannot find module 'taffydb'(#2036) (dc91d0f)window.indexedDBAPI is available but protected (#2039) (360981f)4.3.0 (2023-11-16)
Bug Fixes
ParseUser.linkWithdoesn't remove anonymous auth data (#2007) (7e2585c)react-nativepath does not work for workspace builds (#1930) (8222f3c)Features
Parse.Schema(#2001) (343d0d7)ParseUser.logIn(#2010) (2446007)ParseQuery.findAll(#2000) (012ba4c)installationIdviaParse.Cloud.run(#1939) (eb70b93)Parse.Errormessage with custom message via new Core Manager optionPARSE_ERRORS(#2014) (be0c8a6)ParseUser.logInWithAdditionalAuth(#1955) (2bad411)4.3.0-alpha.6 (2023-10-28)
Bug Fixes
4.3.0-alpha.5 (2023-10-26)
Bug Fixes
4.3.0-alpha.4 (2023-10-07)
Bug Fixes
window.indexedDBAPI is available but protected (#2039) (360981f)4.3.0-alpha.3 (2023-10-04)
Bug Fixes
Parse.Object.saveEventuallyandParse.Object.destroyEventuallynot handled on customParse.Error.CONNECTION_FAILUREmessage (#2032) (4da3ebc)4.3.0-alpha.2 (2023-10-03)
Bug Fixes
Cannot find module 'taffydb'(#2036) (dc91d0f)4.3.0-alpha.1 (2023-09-26)
Bug Fixes
ParseUser.linkWithdoesn't remove anonymous auth data (#2007) (7e2585c)react-nativepath does not work for workspace builds (#1930) (8222f3c)Features
Parse.Schema(#2001) (343d0d7)ParseUser.logIn(#2010) (2446007)ParseQuery.findAll(#2000) (012ba4c)installationIdviaParse.Cloud.run(#1939) (eb70b93)Parse.Errormessage with custom message via new Core Manager optionPARSE_ERRORS(#2014) (be0c8a6)ParseUser.logInWithAdditionalAuth(#1955) (2bad411)Commit messages
Package name: parse
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs