fix: bump @semantic-release/commit-analyzer to 9.0.2 #2258
Merged
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 23, 2021
|
keep in mind that these issues have been resolvable all along by updating lockfiles since this only changes the lower end of the defined semver ranges. i'm supportive of updating in order to more strongly encourage updating within the earlier ranges, but these should not have been blocking problems |
|
🎉 This PR is included in version 18.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
morey-tech
pushed a commit
to ratehub/semantic-release
that referenced
this pull request
Sep 12, 2022
adityahex27
pushed a commit
to hextrust/semantic-release
that referenced
this pull request
Oct 31, 2022
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 which was just fixed in the downstream project semantic-release/commit-analyzer#289.
@travi could you please review this PR as well?