Closed programmer-of-doom closed 1 year ago
Running npm audit
on the current main branch gives me zero vulnerabilities. However, it does look like we've had releases broken in this repository for quite some time, with an error I can reproduce locally on Node v18.14.2.
I've created #249 to roll back semantic-release to the last successful version. @gr2m do you think this is a reasonable approach? My initial thought was the error might be due to the ESM-only nature of semantic-release v20, but perhaps that's not the case.
:tada: This issue has been resolved in version 2.1.8 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Hello - I am requesting an updated to some dependencies that got flagged for this repo so that we can take advantage of it where I work.
The following dependencies came up as having security vulnerabilities:
Would it be possible to have these upgraded by any chance?
Thank you for your time.