feat: automate creation of the first LTS release #514
Conversation
Add an option to `git node release` that marks the release being created as the transition from Current to LTS.
Codecov Report
@@ Coverage Diff @@
## master #514 +/- ##
==========================================
+ Coverage 82.29% 82.49% +0.19%
==========================================
Files 34 35 +1
Lines 1717 1742 +25
==========================================
+ Hits 1413 1437 +24
- Misses 304 305 +1
Continue to review full report at Codecov.
|
|
See https://gist.github.com/richardlau/17d87552525d4e05da1298163fdf7cb7 for a sample session (creating |
lib/prepare_release.js
Outdated
| return await cli.prompt( | ||
| 'Enter the LTS code name for this release line:', | ||
| { questionType: 'input', noSeparator: true, defaultAnswer: '' } | ||
| ); |
There was a problem hiding this comment.
Add a link to https://github.com/nodejs/Release/blob/master/CODENAMES.md ?
There was a problem hiding this comment.
Add a link to https://github.com/nodejs/Release/blob/master/CODENAMES.md ?
Done.
|
14.15.0 (created using this PR in its current state) has now gone out. |
Add an option to
git node releasethat marks the release beingcreated as the transition from Current to LTS.
cc @nodejs/releasers