refactor: upgrade semver from 7.3.4 to 7.3.5

[snyk-bot]

Snyk has created this PR to upgrade semver from 7.3.4 to 7.3.5.

ℹ️ 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 2021-03-23.

Release notes

Package name: semver

• 7.3.5 - 2021-03-23
  

  7.3.5

• 7.3.4 - 2020-12-01
  

  7.3.4

from semver GitHub release notes

Commit messages

Package name: semver

• e79ac3a 7.3.5
• 0ce87d6 Correctly handle prereleases/ANY ranges in subset
• 15ed208 fix(subset): check any as superset

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

[codecov]

Codecov Report

Merging #7343 (61325ce) into master (6a2c21d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7343   +/-   ##
=======================================
  Coverage   93.97%   93.97%           
=======================================
  Files         181      181           
  Lines       13354    13354           
=======================================
  Hits        12550    12550           
  Misses        804      804           

Impacted Files	Coverage Δ
src/batch.js	91.37% <0.00%> (-1.73%)	⬇️
src/Adapters/Files/GridFSBucketAdapter.js	79.50% <0.00%> (-0.82%)	⬇️
src/RestWrite.js	93.73% <0.00%> (-0.16%)	⬇️
src/Adapters/Storage/Mongo/MongoStorageAdapter.js	93.33% <0.00%> (+0.64%)	⬆️

---

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 6a2c21d...61325ce. Read the comment docs.

[mtrezza]

@davimacedo Do you remember why you closed this? I see that we are still on "semver": "7.3.4".

I'll reopen for now, so we don't forget about it.

[mtrezza]

⚠️ Important change for merging PRs from Parse Server 5.0 onwards!

We are planning to release the first beta version of Parse Server 5.0 in October 2021.

If a PR contains a breaking change and is not merged before the beta release of Parse Server 5.0, it cannot be merged until the end of 2022. Instead it has to follow the Deprecation Policy and phase-in breaking changes to be merged during the course of 2022.

One of the most voiced community feedbacks was the demand for predictability in breaking changes to make it easy to upgrade Parse Server. We have made a first step towards this by introducing the Deprecation Policy in February 2021 that assists to phase-in breaking changes, giving developers time to adapt. We will follow-up with the introduction of Release Automation and a branch model that will allow breaking changes only with a new major release, scheduled for the beginning of each calendar year.

We understand that some PRs are a long time in the making and we very much appreciate your contribution. We want to make it easy for PRs that contain a breaking change and were created before the introduction of the Deprecation Policy. These PRs can be merged with a breaking change without being phased-in before the beta release of Parse Server 5.0. We are making this exception because we appreciate that this is a time of transition that requires additional effort from contributors to adapt. We encourage everyone to prepare their PRs until the end of September and account for review time and possible adaptions.

If a PR contains a breaking change and should be merged before the beta release, please mention @parse-community/server-maintenance and we will coordinate with you to merge the PR.

Thanks for your contribution and support during this transition to Parse Server release automation!

[parse-github-assistant]

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

[parseplatformorg]

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

[parseplatformorg]

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

[parseplatformorg]

🎉 This change has been released in version 5.0.0