Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 9, 2024

🤖 I have created a release beep boop

0.19.1 (2024-12-09)

Bug Fixes


This PR was generated with Release Please. See documentation.

@addaleax
Copy link
Member

@cclauss Not sure how the required status here are supposed to be kicked off, but fwiw, I started runs manually (node-gyp integration, Node.js integration) and they're all green

@cclauss
Copy link
Contributor

cclauss commented Dec 10, 2024

@legendecas How do we make this release happen?

@legendecas
Copy link
Member

the token of release-please used in this repo is github auto generated and will not trigger CI. Repo owners can merge this bypassing the requirement.

I'll fix up the token with https://github.com/nodejs/admin/blob/main/request-an-access-token.md

@legendecas legendecas merged commit a61df70 into main Dec 10, 2024
32 checks passed
@legendecas legendecas deleted the release-please--branches--main--components--gyp-next branch December 10, 2024 16:48
@github-actions
Copy link
Contributor Author

🤖 Release is at https://github.com/nodejs/gyp-next/releases/tag/v0.19.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.

4 participants