Skip to content
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

[Snyk] Upgrade parse from 4.1.0 to 4.3.1 #4

Open
wants to merge 1 commit into
base: alpha
Choose a base branch
from

Conversation

kiarza2543
Copy link
Owner

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.


  • The recommended version is 23 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2023-11-18.
Release notes
Package name: parse
  • 4.3.1 - 2023-11-18

    4.3.1 (2023-11-18)

    Bug Fixes

    • Connection failure in Parse.Object.saveEventually and Parse.Object.destroyEventually not handled on custom Parse.Error.CONNECTION_FAILURE message (#2032) (4da3ebc)
    • Docs fail with Cannot find module 'taffydb' (#2036) (dc91d0f)
    • Error in web context when window.indexedDB API is available but protected (#2039) (360981f)
    • 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

    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 (#2032) (4da3ebc)
    • Docs fail with Cannot find module 'taffydb' (#2036) (dc91d0f)
    • Error in web context when window.indexedDB API is available but protected (#2039) (360981f)
    • 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

    4.3.1-alpha.1 (2023-11-18)

    Bug Fixes

    • Connection failure in Parse.Object.saveEventually and Parse.Object.destroyEventually not handled on custom Parse.Error.CONNECTION_FAILURE message (#2032) (4da3ebc)
    • Docs fail with Cannot find module 'taffydb' (#2036) (dc91d0f)
    • Error in web context when window.indexedDB API is available but protected (#2039) (360981f)
    • 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

    4.3.0 (2023-11-16)

    Bug Fixes

    • ParseUser.linkWith doesn't remove anonymous auth data (#2007) (7e2585c)
    • Hard-coding of react-native path does not work for workspace builds (#1930) (8222f3c)

    Features

    • Add Bytes type to Parse.Schema (#2001) (343d0d7)
    • Add Cloud Code context accessibility to ParseUser.logIn (#2010) (2446007)
    • Add support for custom EventEmitter (#1999) (ca568a6)
    • Add support for excluding keys in ParseQuery.findAll (#2000) (012ba4c)
    • Add support to invoke a Cloud Function with a custom installationId via Parse.Cloud.run (#1939) (eb70b93)
    • Allow overriding Parse.Error message with custom message via new Core Manager option PARSE_ERRORS (#2014) (be0c8a6)
    • Login with username, password and additional authentication data via ParseUser.logInWithAdditionalAuth (#1955) (2bad411)
  • 4.3.0-beta.1 - 2023-09-16
  • 4.3.0-alpha.6 - 2023-10-28

    4.3.0-alpha.6 (2023-10-28)

    Bug Fixes

    • Security upgrade browserify-sign from 4.2.1 to 4.2.2 (#2043) (fd50b9d)
  • 4.3.0-alpha.5 - 2023-10-26

    4.3.0-alpha.5 (2023-10-26)

    Bug Fixes

    • Security upgrade crypto-js from 4.1.1 to 4.2.0 (#2042) (681fbdf)
  • 4.3.0-alpha.4 - 2023-10-07

    4.3.0-alpha.4 (2023-10-07)

    Bug Fixes

    • Error in web context when window.indexedDB API is available but protected (#2039) (360981f)
  • 4.3.0-alpha.3 - 2023-10-04

    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 (#2032) (4da3ebc)
  • 4.3.0-alpha.2 - 2023-10-03

    4.3.0-alpha.2 (2023-10-03)

    Bug Fixes

    • Docs fail with Cannot find module 'taffydb' (#2036) (dc91d0f)
  • 4.3.0-alpha.1 - 2023-09-26

    4.3.0-alpha.1 (2023-09-26)

    Bug Fixes

    • ParseUser.linkWith doesn't remove anonymous auth data (#2007) (7e2585c)
    • Hard-coding of react-native path does not work for workspace builds (#1930) (8222f3c)

    Features

    • Add Bytes type to Parse.Schema (#2001) (343d0d7)
    • Add Cloud Code context accessibility to ParseUser.logIn (#2010) (2446007)
    • Add support for custom EventEmitter (#1999) (ca568a6)
    • Add support for excluding keys in ParseQuery.findAll (#2000) (012ba4c)
    • Add support to invoke a Cloud Function with a custom installationId via Parse.Cloud.run (#1939) (eb70b93)
    • Allow overriding Parse.Error message with custom message via new Core Manager option PARSE_ERRORS (#2014) (be0c8a6)
    • Login with username, password and additional authentication data via ParseUser.logInWithAdditionalAuth (#1955) (2bad411)
  • 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 notes
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants