Bot releases are hidden (Show)
ubuntu-latest
by @sitiom in https://github.com/coreybutler/nvm-windows/pull/1016
Full Changelog: https://github.com/coreybutler/nvm-windows/compare/1.1.11...1.1.12
Published by coreybutler over 1 year ago
This is a maintenance release. A new experimental debug
command has been added for troubleshooting.
Full Changelog: https://github.com/coreybutler/nvm-windows/compare/1.1.10...1.1.11
Published by coreybutler almost 2 years ago
This is primarily a bug fix release.
Many users have requested UAC prompts be reinstated. NVM4W attempts to run commands without elevation. If this succeeds (i.e. developer mode is enabled and active), the process continues without prompts. If a command fails, an attempt to run it with elevated privileges will trigger the UAC prompt.
nvm use
to be called with the part of the semver by @vladonemo in https://github.com/coreybutler/nvm-windows/pull/709
A few PR's were manually added, since merging them proved to be difficult after other changes. So, I'd like to give a special thanks to the following folks whose PR's were manually included (but not recognized in the changelog):
Full Changelog: https://github.com/coreybutler/nvm-windows/compare/1.1.9...1.1.10
Published by coreybutler almost 3 years ago
NOTICE: If you downloaded this version before Dec 15, 2021 and are affected by issue #706, please re-download. This fix was not present in the initial binary and has since been corrected.
Full Changelog: https://github.com/coreybutler/nvm-windows/compare/1.1.8...1.1.9
Added nvm-setup.exe after initial release to support winget efforts.
Published by coreybutler about 3 years ago
Truth be told, I did not want to release this version right now. I am working on the successor project rt, 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. 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.
As a result, NVM for Windows 1.1.8 is being released to support corepack.
All files can be found on the release page.
If you do not have NVM for Windows installed
Use the instructions in the README.
If you already have an older version of NVM for Windows installed
Download nvm-update.zip and extract it. You will find a file called nvm-update.exe. Double click to run it. This will prompt for the version you wish to upgrade to (pre-populated w/ 1.1.8).
nvm-update.exe can also be run from the command line using the /S
flag to suppress the prompt. To do this, run nvm-update.exe 1.1.8 /S
.
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:
nvm install latest
- installs the latest patch version of Node (instead of latest minor).nvm install lts
- installs the latest LTS patch version (new). (@tats-u)nvm use latest
, nvm use lts
(@tats-u), and nvm use newest
(new) (@EEJesse) now supported.nvm current
(new) displays the active version. (@riazXrazor)Numerous edge case fixes have been applied as well.
A number of documentation updates have also been merged.
Version 1.1.8 is not code signed. Code-signed applications are trusted by Windows and will install easily. Users are prompted with a screen like this one:
Non-code-signed applications can usually be installed, but they will throw a warning like this:
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).
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, 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 if you'd like to help cover this cost.
Published by coreybutler about 6 years ago
Merged several outstanding PR's:
Several documentation PR's were included in the repo as well.
The build process has been updated to provide:
Published by coreybutler over 7 years ago
Leverages Go's native filepath management, which should fix issues with spaces and special characters in path names.
Published by coreybutler over 7 years ago
A hotfix to support the newer node version categorization logic.
Published by coreybutler over 7 years ago
Merged #269 to fix #268 (issue retrieving latest version of Node)
Published by coreybutler over 7 years ago
This is a patch update, fixing some mirroring issues, courtesy of PR #251. A nice new benefit is rollback support when a download fails.
Published by coreybutler over 7 years ago
This version fixes an issue with the nvm ls available
feature, which was not showing current versions properly.
It is now possible to add an --insecure
flag to installations if you need to bypass the SSL validation check performed against the remote server. This is an insecure process where mitm attacks can occur, so it is not enabled by default. This should only be used with trusted download sources.
Published by coreybutler over 8 years ago
nodejs.org/dist/index.json
.nvm ls available
to display a pretty table, up to 20 results. Displays Current, LTS, Stable, and Unstable versions.Published by coreybutler about 9 years ago
Merged support for Node v4.x.
Published by coreybutler almost 10 years ago
A hotfix release to resolve issue #15.
Published by coreybutler about 10 years ago
Feature Updates:
nvm use 32|64
"quick switching" from 32-bit to 64-bit or vice versa.nvm list available
provide a list of the versions available for download.Fixes:
Misc:
Published by coreybutler about 10 years ago
This is a bug fix & tooling release.
nvm use 32
or nvm use 64
properly overrides the default architecture.Published by coreybutler about 10 years ago
The installer has been upgraded with a few new features. If node.js is already installed, you'll be provided an option to let nvm control it. As a result, you no longer have to uninstall node.js before installing NVM for Windows.
There are now two downloads.
nvm-setup.zip
contains the installer and the full application.
nvm-noinstall.zip
contains the nvm.exe
and required files for a manual installation. See the wiki for additional instructions.
Published by coreybutler about 10 years ago
A patch for the installer to better support integration with existing node.js installations.
Published by coreybutler about 10 years ago
A minor patch to fix issue #1.
Published by coreybutler about 10 years ago
The initial release supports installation of multiple versions of node.js. This coincides with the release of the node/npm distribution list.
Download and extract the zip (it only contains one file, nvm-setup.exe
). Run the installer and start using nvm for Windows.