Merge pull request #1005 from heroku/ccasey/changelog_v196

Update CHANGELOG.md before publishing v196

Author: colincasey

CHANGELOG.md

@@ -1,12 +1,13 @@
 # Node.js Buildpack Changelog
 
 ## main
+
+## v196 (2022-05-31)
 - Add metrics plugin for Node 17 and 18 ([#1002](https://github.com/heroku/heroku-buildpack-nodejs/pull/1002))
 - Add warning message for Node 18+ incompatibility with heroku-18 ([#1002](https://github.com/heroku/heroku-buildpack-nodejs/pull/1002))
 - Enable Yarn 2 `devDependency` pruning using a custom plugin for all customers ([#1001](https://github.com/heroku/heroku-buildpack-nodejs/pull/1001))
 - Test against Heroku-22 ([#1003](https://github.com/heroku/heroku-buildpack-nodejs/pull/1003))
 
-
 ## v195 (2022-04-13)
 - Enable Yarn 2 `devDependency` pruning using a custom plugin for 20% of customers ([#999](https://github.com/heroku/heroku-buildpack-nodejs/pull/999))
 - Set xtrace mode in buildpack when BUILDPACK_XTRACE environment variable is set ([#925](https://github.com/heroku/heroku-buildpack-nodejs/pull/925))

README.md

@@ -40,7 +40,7 @@ heroku buildpacks:set https://github.com/heroku/heroku-buildpack-nodejs#latest -
 Even though it's suggested to use the latest release, you may want to lock dependencies - including buildpacks - to a specific version.
 
 First, find the version you want from
-[the list of buildpack versions](https://github.com/heroku/heroku-buildpack-nodejs/releases).
+[the list of buildpack versions](https://github.com/heroku/heroku-buildpack-nodejs/tags).
 Then, specify that version with `buildpacks:set`:
 
 ```
@@ -150,4 +150,4 @@ this is the log file
 test log file
 ```
 
-The test output writes to `$STD_OUT`, so you can use `cat $STD_OUT` to read output.
+The test output writes to `$STD_OUT`, so you can use `cat $STD_OUT` to read output.