From de9aaf289ec3df08643a9fbf60fa34acb9bf9cf5 Mon Sep 17 00:00:00 2001 From: coreybutler Date: Sat, 11 Sep 2021 17:38:12 -0500 Subject: [PATCH] Update notes for v1.1.8 --- v1.1.8.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/v1.1.8.md b/v1.1.8.md index e0cd225..f503e06 100644 --- a/v1.1.8.md +++ b/v1.1.8.md @@ -1,12 +1,12 @@ # NVM for Windows v1.1.8 Notes -Truth be told, I did not want to release this version right now. I am actively working on the successor project [rt](https://github.com/coreybutler/nvm-windows/discussions/565). I hoped NVM for Windows 1.1.8 would be the last version before releasing rt. However, there have been notable changes in the Node ecosystem, which warrant a new version now. +Truth be told, I did not want to release this version right now. I am working on the successor project [rt](https://github.com/coreybutler/nvm-windows/discussions/565), which was supposed to be the last version before the rt release. However, notable changes in the Node ecosystem warrant a new version now. **Node Corepack** -In September 2021, Node.js v16.9.0 introduced [corepack](https://nodejs.org/api/corepack.html). This experimental new feature essentially allows developers to use transparently use npm, pnpm, or yarn. To support this feature, NVM4W must download and process a different distribution file than it has used previously. +In September 2021, Node.js v16.9.0 introduced [corepack](https://nodejs.org/api/corepack.html). This experimental new feature allows transparent use of npm, pnpm, or yarn. To support this feature, NVM4W must download and process a different distribution file than it has used previously. -_NVM for Windows 1.1.8 is being released to support corepack._ +As a result, NVM for Windows 1.1.8 is being released to support corepack. ## How to Upgrade @@ -22,17 +22,17 @@ nvm-update.exe can also be run from the command line using the `/S` flag to supp ## What's New -Several long-requested features/fixes have been merged since v1.1.7. I did not get to test all of them as extensively as I wanted to. That said, I believe they are stable. These features include: +Several long-requested features/fixes have been merged since v1.1.7. I did not get to test all of them as extensively as I wanted to, but I believe they are stable. These features include: 1. corepack support (see above) 2. Support for spaces in filepaths [#355](https://github.com/coreybutler/nvm-windows/pull/355). -3. `nvm install latest` installs the latest patch version of Node (instead of latest minor). -4. `nvm install lts` installs the latest LTS patch version (new). +3. `nvm install latest` - installs the latest patch version of Node (instead of latest minor). +4. `nvm install lts` - installs the latest LTS patch version (new). 5. `nvm use latest`, `nvm use lts`, and `nvm use newest` (new) now supported. 6. Elevated permissions applied only when necessary [#511](https://github.com/coreybutler/nvm-windows/pull/511). 7. `nvm current` (new) displays the active version. -Several additional minor updates have been applied as well. +Numerous edge case fixes have been applied as well. ## What didn't make it in? @@ -50,10 +50,10 @@ Non-code-signed applications can _usually_ be installed, but they will throw a w **Why?** -I paid for the last code signing certificates out of pocket, but they've expired. Sponsorships, to date, haven't even come close to covering the cost of a new code signing certificate (let alone the last one). I plan to purchase a new code signing certificate for my commercial software endeavors. At that time, I will release a code-signed version of NVM4W. That will most likely be after the holidays (early next year). +I paid for the last code signing certificates out of pocket, but they've expired. Sponsorships, to date, haven't even come close to covering the cost of a new code signing certificate (let alone the last one). **Who will this affect?** This won't affect most users, but enterprise users and those distributing NVM4W in corporate environments may run into problems. -**If your organization is impacted by this and cannot wait, I will accept sponsorship money to expedite the delivery of a code-signed version.** The required certificate is about $1000. Please direct message me on Twitter [@goldglovecb](https://twitter.com/goldglovecb) if you'd like to help with this. +**If your organization is impacted by this, I will accept sponsorship money to expedite the delivery of a code-signed version.** The required EV certificate is about $1000. Please direct message me on Twitter [@goldglovecb](https://twitter.com/goldglovecb) if you'd like to help cover this cost.