Prepare for release

CHANGELOG.md

@@ -7,11 +7,11 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 <!-- markdownlint-disable MD024 -->
 
-## [Unreleased] (date goes here)
+## [6.6.0] (2020-07-04)
 
 ### Added
 
-- node support aliases (limited support)
+- labels for node support aliases, such as `lts_latest`
 
 ### Fixed
 

README.md

@@ -11,7 +11,7 @@ Node.js version management: no subshells, no profile setup, no convoluted API, j
 
 (Note: `n` is not supported natively on Windows.)
 
-- [`n` – Interactively Manage Your Node.js Versions](#n-%e2%80%93-interactively-manage-your-nodejs-versions)
+- [`n` – Interactively Manage Your Node.js Versions](#n--interactively-manage-your-nodejs-versions)
     - [Installation](#installation)
         - [Third Party Installers](#third-party-installers)
     - [Installing Node Versions](#installing-node-versions)
@@ -113,11 +113,11 @@ There is support for the named release streams:
 
 - `argon`, `boron`, `carbon`: codenames for LTS release streams
 
-These node support aliases may be used, although for now simply resolve to the latest matching version:
+These node support aliases may be used, although simply simply resolve to the latest matching version:
 
 - `active`, `lts_active`, `lts_latest`, `lts`, `current`, `supported`
 
-The last form is for specifying [other releases](https://nodejs.org/download) available using the name of the remote download folder optionally followed by the complete or incomplete version.
+The last version form is for specifying [other releases](https://nodejs.org/download) available using the name of the remote download folder optionally followed by the complete or incomplete version.
 
 - `chakracore-release/latest`
 - `nightly`

bin/n

@@ -40,7 +40,7 @@ function echo_red() {
 # Setup and state
 #
 
-VERSION="6.5.2-0"
+VERSION="6.6.0"
 
 N_PREFIX="${N_PREFIX-/usr/local}"
 N_PREFIX=${N_PREFIX%/}