-
Notifications
You must be signed in to change notification settings - Fork 73
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
chore(main): release 0.15.1 #197
chore(main): release 0.15.1 #197
Conversation
5b9e8cd
to
e5d7e60
Compare
accb4cd
to
899f65c
Compare
899f65c
to
78dfb26
Compare
Agreed. This has happened to me several times. Perhaps we need a bot that fails PRs that have unacceptable titles. There is one on |
I just verified that there is one, but it references https://github.com/nodejs/core-validate-commit/ Also, I'm wondering how the release process works for gyp-next; do we need a second reviewer and/or a specific reviewer? |
78dfb26
to
d5710f6
Compare
🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.15.1 🌻 |
🤖 I have created a release beep boop
0.15.1 (2023-09-08)
Bug Fixes
This PR was generated with Release Please. See documentation.