Prep for 0.9.0 release

CHANGELOG.md

@@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.9.0] - 2020-12-07
+
 ### Added
 
 * Notify admins on Slack when new project is ready for review ([#155](https://github.com/iomega/paired-data-form/issues/155))
@@ -209,7 +211,11 @@ This version requires following migration steps.
 
 Initial release.
 
-[Unreleased]: https://github.com/iomega/paired-data-form/compare/v0.7.0...HEAD
+[Unreleased]: https://github.com/iomega/paired-data-form/compare/v0.9.0...HEAD
+[0.9.0]: https://github.com/iomega/paired-data-form/compare/v0.8.2...v0.9.0
+[0.8.2]: https://github.com/iomega/paired-data-form/compare/v0.8.1...v0.8.2
+[0.8.1]: https://github.com/iomega/paired-data-form/compare/v0.8.0...v0.8.1
+[0.8.0]: https://github.com/iomega/paired-data-form/compare/v0.7.0...v0.8.0
 [0.7.0]: https://github.com/iomega/paired-data-form/compare/v0.6.2...v0.7.0
 [0.6.2]: https://github.com/iomega/paired-data-form/compare/v0.6.1...v0.6.2
 [0.6.1]: https://github.com/iomega/paired-data-form/compare/v0.6.0...v0.6.1

README.md

@@ -63,7 +63,9 @@ This chapter is for developers of the platform.
 To make a new release of the platform do:
 
 1. Determine new version of release, using semantic versioning (x.y.z)
-2. Add version to CHANGELOG.md
+2. Add version to [CHANGELOG.md](CHANGELOG.md)
+    * Create a new `##` chapter for the new version
+    * Update version links at bottom of CHANGELOG
 3. Set new version of api web service by
 
     ```shell

api/package.json

@@ -1,6 +1,6 @@
 {
   "name": "podp-api",
-  "version": "0.8.2",
+  "version": "0.9.0",
   "description": "",
   "license": "Apache-2.0",
   "scripts": {

app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "paired-data-platform",
-  "version": "0.8.2",
+  "version": "0.9.0",
   "private": true,
   "dependencies": {
     "@root/encoding": "^1.0.1",