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

refactor: Upgrade parse from 4.0.1 to 4.1.0 #8604

Merged
merged 1 commit into from
Jun 3, 2023

Conversation

parseplatformorg
Copy link
Contributor

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade parse from 4.0.1 to 4.1.0.

ℹ️ 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 6 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-05-01.
Release notes
Package name: parse
  • 4.1.0 - 2023-05-01

    4.1.0 (2023-05-01)

    Bug Fixes

    • LiveQuerySubscription.unsubscribe resolves promise before unsubscribing completes (#1727) (1c96205)
    • Node engine version upper range is <19 despite Node 19 support (#1732) (febe187)
    • Saving a new Parse.Object with an unsaved Parse.File fails (#1662) (16535a4)

    Features

    • LiveQueryClient.close returns promise when WebSocket closes (#1735) (979d660)
    • Upgrade Node Package Manager lock file package-lock.json to version 2 (#1729) (e993786)
  • 4.1.0-beta.1 - 2023-03-01

    4.1.0-beta.1 (2023-03-01)

    Bug Fixes

    • LiveQuerySubscription.unsubscribe resolves promise before unsubscribing completes (#1727) (1c96205)
    • Node engine version upper range is <19 despite Node 19 support (#1732) (febe187)
    • Saving a new Parse.Object with an unsaved Parse.File fails (#1662) (16535a4)

    Features

    • LiveQueryClient.close returns promise when WebSocket closes (#1735) (979d660)
    • Upgrade Node Package Manager lock file package-lock.json to version 2 (#1729) (e993786)
  • 4.1.0-alpha.4 - 2023-04-28

    4.1.0-alpha.4 (2023-04-28)

    Features

  • 4.1.0-alpha.3 - 2023-04-02

    4.1.0-alpha.3 (2023-04-02)

    Features

    • Add ParseQuery.watch to trigger LiveQuery only on update of specific fields (#1839) (7479343)
  • 4.1.0-alpha.2 - 2023-03-01

    4.1.0-alpha.2 (2023-03-01)

    Bug Fixes

    • Parse.File.cancel starts new attempt to save file (#1781) (b755e42)
  • 4.1.0-alpha.1 - 2023-03-01

    4.1.0-alpha.1 (2023-03-01)

    Bug Fixes

    • LiveQuerySubscription.unsubscribe resolves promise before unsubscribing completes (#1727) (1c96205)
    • Node engine version upper range is <19 despite Node 19 support (#1732) (febe187)
    • Saving a new Parse.Object with an unsaved Parse.File fails (#1662) (16535a4)

    Features

    • LiveQueryClient.close returns promise when WebSocket closes (#1735) (979d660)
    • Upgrade Node Package Manager lock file package-lock.json to version 2 (#1729) (e993786)
  • 4.0.1 - 2023-01-31
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

@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 [Snyk] Upgrade parse from 4.0.1 to 4.1.0 refactor: Upgrade parse from 4.0.1 to 4.1.0 Jun 2, 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 Jun 2, 2023

Codecov Report

Patch coverage has no change and project coverage change: +0.02 🎉

Comparison is base (3ec453d) 94.32% compared to head (b99907e) 94.35%.

❗ Current head b99907e differs from pull request most recent head f38e55b. Consider uploading reports for the commit f38e55b to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha    #8604      +/-   ##
==========================================
+ Coverage   94.32%   94.35%   +0.02%     
==========================================
  Files         183      183              
  Lines       14576    14576              
==========================================
+ Hits        13749    13753       +4     
+ Misses        827      823       -4     

see 3 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@mtrezza mtrezza merged commit 8c9a56e into alpha Jun 3, 2023
@mtrezza mtrezza deleted the snyk-upgrade-7dc0cb747599b38f3061ffb7c4d9a5a0 branch June 3, 2023 12:16
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 6.1.0-alpha.17

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Jun 7, 2023
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 6.3.0-beta.1

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Jun 10, 2023
@parseplatformorg
Copy link
Contributor Author

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

@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 6.3.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Sep 16, 2023
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 state:released-beta Released as beta version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants