Skip to content
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

Merged
merged 1 commit into from
Oct 3, 2023

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 30, 2023

🤖 I have created a release beep boop

0.15.1 (2023-09-08)

Bug Fixes


This PR was generated with Release Please. See documentation.

@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from 5b9e8cd to e5d7e60 Compare June 20, 2023 12:49
@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch 2 times, most recently from accb4cd to 899f65c Compare July 17, 2023 18:13
@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from 899f65c to 78dfb26 Compare August 26, 2023 00:07
@rzhao271
Copy link
Contributor

rzhao271 commented Aug 26, 2023

Looks like the bot picked up the changes. The description didn't get updated because my PRs didn't format the titles properly, but I'm thinking the release notes can be updated manually after

CI changes

@cclauss
Copy link
Contributor

cclauss commented Aug 26, 2023

Agreed. This has happened to me several times. Perhaps we need a bot that fails PRs that have unacceptable titles. There is one on nodejs/node if memory serves.

@rzhao271
Copy link
Contributor

I just verified that there is one, but it references https://github.com/nodejs/core-validate-commit/
Instead, we might be able to use https://github.com/amannn/action-semantic-pull-request without further configuration, considering this is a much smaller repository

Also, I'm wondering how the release process works for gyp-next; do we need a second reviewer and/or a specific reviewer?

@github-actions github-actions bot force-pushed the release-please--branches--main--components--gyp-next branch from 78dfb26 to d5710f6 Compare September 8, 2023 16:07
@cclauss cclauss merged commit 98da389 into main Oct 3, 2023
@cclauss cclauss deleted the release-please--branches--main--components--gyp-next branch October 3, 2023 03:33
@github-actions
Copy link
Contributor Author

github-actions bot commented Oct 3, 2023

🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.15.1 🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants