| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
|
Please also document the process mentioned in #47975 (comment)! |
Sorry, something went wrong.
|
|
||
| and substitute this guard version with the release version `x`. | ||
|
|
||
| #### Step 4. Update test version guards |
There was a problem hiding this comment.
| #### Step 4. Update test version guards | |
| #### Step 3. Update test version guards |
The next step is step 4.
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, updated!
Sorry, something went wrong.
There was a problem hiding this comment.
Doc looks great! Just a few comments.
Sorry, something went wrong.
|
@gabrielschulhof thanks for the suggestions! I've added a section to update the change history and backport the release to LTS lines. Please take a look again. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
PR-URL: nodejs#47972 Fixes: nodejs#47664 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
| Back | FazBrowse Home | New Git URL |
With the change in #45715 landed, there are several code sites that need to be updated with the release Node-API version when a new Node-API version is being released.
This PR adds a document to the guides of a checklist necessary for creating a Node-API release PR.
Fixes: #47664