-
-
Notifications
You must be signed in to change notification settings - Fork 129
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
feat: upgrade [email protected] #155
Conversation
1c997c9
to
b2fc056
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much also for this upgrade! The change looks good to me, but again, can you revert the change to the built file?
Potentially while you're at it, would you mind to leave a note about this in the contributors guide?
97f3daa
to
9179e5f
Compare
I've added a line, but I'm not sure if I understood your intention or made the right wording ^^ |
CONTRIBUTORS.md
Outdated
@@ -2,6 +2,8 @@ | |||
|
|||
Thank you very much for contributing to this project! | |||
|
|||
Just a heads up, this project uses node16. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I should have been more precise. I meant if you can add a note at the bottom that the built file should not be included in the PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed to add the intended text instead 😆
9179e5f
to
b3307ec
Compare
@xuatz The lockfile changed from your other PR, care to resolve that quickly? 🙂 |
* upgraded to node@16 * https://github.com/semantic-release/semantic-release/releases/tag/v19.0.0 BREAKING CHANGE: dropped support for node <=15
b3307ec
to
b13c44a
Compare
🎉 This PR is included in version 4.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
Details
Workflow still works (fails) if the PR title is horrible
Notes
You might not be interested in this PR, but since I'm updating it to fix the "vulnerabilities" to comply with company regulations, I decide to make a PR just in case you want the changes.
Checklist