fix: Bump version of semver to address vulnerability warnings #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
standard-versionfor the most popular fork,commit-and-tag-version, which additionally addresses some vulnerability warnings.Full disclosure, I maintain
commit-and-tag-version- it's a fork of the now-unmaintainedstandard-version, which has had some good traction. Aside: this repository now doesn't actually need either tool - it would be better to use release-please, which is a much more streamlined release process for repositories hosted in github.@tvdstaaij The semver issue is causing a few downstream vulnerability warnings - it would be awesome to get this in and released. Let me know if you'd like a version of this PR without introducing a tool that I maintain - I remember you were quite careful with security.
Hope you're well!