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

[Snyk] Upgrade semver from 6.1.2 to 6.3.0 #2

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade semver from 6.1.2 to 6.3.0.

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 3 versions ahead of your current version.
  • The recommended version was released 2 years ago, on 2019-07-23.
Release notes
Package name: semver from semver GitHub release notes
Commit messages
Package name: semver
  • 0eeceec 6.3.0
  • 2779d96 Expose the token enum on the exports
  • 9f5f615 changelog
  • ce6190e 6.2.0
  • 24af461 Add test coverage for bin file
  • 388ec1c Add `rtl` option to coerce from right to left
  • d062593 coerce(number) will coerce to a string
  • 3dc88f3 6.1.3
  • c44e124 Handle X ranges properly in includePrelease mode
  • ba19e8f Add a -0 prerelease on >X and <X ranges

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

@CALISOULB CALISOULB had a problem deploying to releaseNewActionVersion April 22, 2022 06:42 Failure
@CALISOULB CALISOULB had a problem deploying to releaseNewActionVersion April 22, 2022 06:43 Failure
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants