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 semver from 7.3.8 to 7.5.0 #8593

Merged
merged 2 commits into from
Jun 1, 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.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 2 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-04-17.
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
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.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade semver from 7.3.8 to 7.5.0 refactor: Upgrade semver from 7.3.8 to 7.5.0 May 29, 2023
@codecov
Copy link

codecov bot commented May 31, 2023

Codecov Report

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

Comparison is base (bf2a224) 94.33% compared to head (a9b3f01) 94.35%.

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

Additional details and impacted files
@@            Coverage Diff             @@
##            alpha    #8593      +/-   ##
==========================================
+ Coverage   94.33%   94.35%   +0.02%     
==========================================
  Files         183      183              
  Lines       14576    14576              
==========================================
+ Hits        13750    13753       +3     
+ Misses        826      823       -3     

see 2 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 3ec453d into alpha Jun 1, 2023
@mtrezza mtrezza deleted the snyk-upgrade-5ac03fe6d24c29f887d6942796f81dd7 branch June 1, 2023 14:09
@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