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.

Sign up for GitHub

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

Jump to bottom

refactor: Upgrade semver from 7.3.8 to 7.5.1 #8606

Merged
merged 2 commits into from
Jun 4, 2023
Merged

refactor: Upgrade semver from 7.3.8 to 7.5.1 #8606

merged 2 commits into from
Jun 4, 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 semver from 7.3.8 to 7.5.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 3 versions ahead of your current version.
  • The recommended version was released 21 days ago, on 2023-05-12.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Arbitrary File Upload
SNYK-JS-PARSESERVER-5661794		 386/1000
Why? Recently disclosed, CVSS 6.3		 No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: semver from semver GitHub release notes
Commit messages
Package name: semver

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 semver from 7.3.8 to 7.5.1 refactor: Upgrade semver from 7.3.8 to 7.5.1 Jun 3, 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 3, 2023 •
edited
Loading

Codecov Report

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

Comparison is base (f5c6b3e) 94.10% compared to head (69a7459) 94.13%.

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

Additional details and impacted files 
@@                Coverage Diff                @@
##           release-5.x.x    #8606      +/-   ##
=================================================
+ Coverage          94.10%   94.13%   +0.02%     
=================================================
  Files                183      183              
  Lines              13798    13798              
=================================================
+ Hits               12985    12989       +4     
+ Misses               813      809       -4

see 5 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 a036071 into release-5.x.x Jun 4, 2023
28 checks passed
@mtrezza mtrezza deleted the snyk-upgrade-54e8fb90afd09e1fa09f024c53ce4796 branch June 4, 2023 16:05
@parseplatformorg
Copy link
Contributor Author

🎉 This change has been released in version 5.5.2

@parseplatformorg parseplatformorg added the state:released-5.x.x Released as LTS version label Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mtrezza mtrezza mtrezza approved these changes

Assignees
No one assigned
Labels
state:released-5.x.x Released as LTS version
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@parseplatformorg @mtrezza @snyk-bot