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 3.4.0 to 3.4.1 #7783

Merged
merged 1 commit into from
Jan 25, 2022

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade parse from 3.4.0 to 3.4.1.

merge advice
ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2022-01-01.
Release notes
Package name: parse
  • 3.4.1 - 2022-01-01

    3.4.1 (2022-01-01)

    Bug Fixes

  • 3.4.0 - 2021-11-01

    3.4.0 (2021-11-01)

    Bug Fixes

    • update parse server dependency branch; recreate package lock (#1424) (38455ef)
    • upgrade @ babel/runtime from 7.14.8 to 7.15.3 (#1404) (8cb321c)

    Features

    • add options to enable polling and set the polling interval; fixes excessive polling (#1419) (0f804b8)
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 3.4.0 to 3.4.1 refactor: upgrade parse from 3.4.0 to 3.4.1 Jan 24, 2022
@codecov
Copy link

codecov bot commented Jan 24, 2022

Codecov Report

Merging #7783 (2a3058c) into alpha (9082351) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##            alpha    #7783   +/-   ##
=======================================
  Coverage   93.95%   93.95%           
=======================================
  Files         183      183           
  Lines       13655    13655           
=======================================
  Hits        12830    12830           
  Misses        825      825           
Impacted Files Coverage Δ
src/ParseServerRESTController.js 96.96% <0.00%> (-1.52%) ⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js 93.14% <0.00%> (-0.22%) ⬇️
src/RestWrite.js 94.20% <0.00%> (+0.15%) ⬆️
src/batch.js 94.73% <0.00%> (+1.75%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 350b59a...2a3058c. Read the comment docs.

@mtrezza mtrezza merged commit 433e82f into alpha Jan 25, 2022
@mtrezza mtrezza deleted the snyk-upgrade-e73aed6ce59de7091be0411aaf3412e3 branch January 25, 2022 00:42
@parseplatformorg
Copy link
Contributor

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

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Jan 25, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.0.0-beta.10

@parseplatformorg parseplatformorg added the state:released-beta Released as beta version label Mar 15, 2022
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 5.1.0

@parseplatformorg parseplatformorg added the state:released Released as stable version label Mar 18, 2022
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