-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Create a Node-API release checklist #47664
Comments
With #45715 landed, the document must also mention that, as part of the release process, not only will new APIs in the headers have to be moved from |
PR-URL: #47972 Fixes: #47664 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gabriel Schulhof <[email protected]>
PR-URL: nodejs#47972 Fixes: nodejs#47664 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gabriel Schulhof <[email protected]>
PR-URL: #47972 Fixes: #47664 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gabriel Schulhof <[email protected]>
PR-URL: #47972 Fixes: #47664 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gabriel Schulhof <[email protected]>
PR-URL: nodejs#47972 Fixes: nodejs#47664 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Gabriel Schulhof <[email protected]>
What is the problem this feature will solve?
We need to make sure when we release a new version of Node-API we do not overlook any of the steps.
What is the feature you are proposing to solve the problem?
Let's add a document to the guides containing a list of steps necessary for creating a Node-API release PR.
What alternatives have you considered?
Looking at existing release commits to remember the steps. However, a new step will be added at https://github.com/nodejs/node/pull/45715/files#diff-2057dbe503dbb37a65a74cf86e056d50c27ba828070577e0f7f07e734365c9bcR658 which previous releases will not reflect.
The text was updated successfully, but these errors were encountered: