-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
question: plan or thought on upgrading to latest semantic-release version #103
Comments
Migration to semrel v19 is a reasonable change, no doubts. I see several options:
Anyway, I think we should configure v2 branch to release only for patches and vulns fixes to support our users who still need old nodejs versions for some reasons. |
I would go with 2. and release a |
Hello @antongolub! Do you see one of these options happening sometime soon? There are currently bunch of vulnerabilities in the dependencies. Tried something in this pull #122 request but not quite sure how to deal with the error in the CI job. |
There's an issue with one test, which seems related to npm changes: everything is fine in Node16 / npm 8.5.0 and fails in Node 18.8.0 / npm 8.18.0. I'm afraid I have not enough time to figure out what exaclty went wrong, so I just disabled the test case. |
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Awesome, thanks! 👏 |
@antongolub, tests are fixed in #124 😉 @janpe, thanks for helping releasing this feature! 🎉 |
Currently this package is using :
"semantic-release": "^17.4.7"
whereas the latest is19.0.2
.I've had an issue with
semantic-release
(#2407) that might be fixed one day (hopefully ^^).And if so, I was wondering what's the current plan or thought for MSR to upgrade to the latest SR version ?
Thanks!
The text was updated successfully, but these errors were encountered: