fix: bump conventional commits parser to version 3.2.3 #293
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
travi
approved these changes
Nov 24, 2021
as i mentioned in the other thread, i'm in favor of raising the minimum end of the range in cases like this, but updating a project's lockfile to use the newer version, still in-range, would also solve the mentioned CVE. is there part of the bigger picture that i am overlooking that is preventing updates that makes you suggest that this is a need? |
|
🎉 This PR is included in version 10.0.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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 fixes CVE-2021-23425.
@travi Unfortunately, I did not see that this project also uses this package. This means the upstream semantic-release needs to be updated one more time.