This repository has been archived by the owner on May 30, 2024. It is now read-only.
update semver
package and fix security issues in transitive deps
#151
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.
I encountered a random
yarn check
error in a project I'm working on, and drilled it down to thesemver
dependency in this package that was locked to v5.5.0 (most other transitive semver dependencies were^5.5.1
).This isn't really a problem with the package itself, but i figured I could help with dependency maintenance and upgrade it to the latest
semver
v6.0.0, which is officially a breaking change, but only for an API that is not being used here (semver CHANGELOG), so all tests pass.npm audit
also found a few important security vulnerabilities in transitive dependencies, so I rannpm audit fix
to updatepackage-lock.json
with those updates. Again, all tests pass and this is just a background maintenance update.