Release v3.0

Changelog.md

@@ -0,0 +1,31 @@
+Mailvelope Key Server Changelog
+===============================
+
+v3.0.0
+-------
+__Mar 4, 2019__
+  * Add upload, update and removal for single user IDs
+  * Migrate to koa 2 with async/await instead of generators
+  * Use eslint instead of jscs/jshint
+  * Use winston instead of npmlog
+  * Use co-body directly instead of koa-body
+  * Send email message with PGP inline not PGP/MIME
+  * Use OpenPGP.js directly instead of nodemailer-openpgp plugin
+  * Use native ES6 string templates instead of nodemailer template engine
+  * Update OpenPGP.js to 4.4 and other dependencies
+
+v2.0.0
+-------
+__Aug 15, 2017__
+
+  * Add release npm script for travis deployment
+  * Use eslint instead of jscs/jshint
+  * Use ES6 destructuring
+  * Replace grunt with npm scripts
+  * Update dependencies
+
+v1.0.0
+-------
+__Jun 13, 2016__
+
+  * Initial release

README.md

@@ -31,18 +31,18 @@ Try out the server here: [https://keys.mailvelope.com](https://keys.mailvelope.c
 
 
 
-# Api
+# API
 
-The key server provides a modern RESTful api, but is also backwards compatible to the OpenPGP HTTP Keyserver Protocol (HKP). The following properties are enforced by the key server to enable reliable automatic key look in user agents:
+The key server provides a modern RESTful API, but is also backwards compatible to the OpenPGP HTTP Keyserver Protocol (HKP). The following properties are enforced by the key server to enable reliable automatic key look in user agents:
 
 * Only public keys with at least one verified email address are served
 * There can be only one public key per verified email address at a given time
 * A key ID specified in a query must be at least 16 hex characters (64-bit long key ID)
 * Key ID collisions are checked upon key upload to prevent collision attacks
 
-## HKP api
+## HKP API
 
-The HKP apis are not documented here. Please refer to the [HKP specification](https://tools.ietf.org/html/draft-shaw-openpgp-hkp-00) to learn more. The server generally implements the full specification, but has some constraints to improve the security for automatic key lookup:
+The HKP APIs are not documented here. Please refer to the [HKP specification](https://tools.ietf.org/html/draft-shaw-openpgp-hkp-00) to learn more. The server generally implements the full specification, but has some constraints to improve the security for automatic key lookup:
 
 #### Accepted `search` parameters
 * Email addresses
@@ -57,7 +57,7 @@ The HKP apis are not documented here. Please refer to the [HKP specification](ht
 #### Accepted `options` parameters
 * mr
 
-## REST api
+## REST API
 
 ### Lookup a key
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "mailvelope-keyserver",
-  "version": "2.0.0",
+  "version": "3.0.0",
   "license": "AGPL-3.0",
   "repository": {
     "type": "git",

src/static/index.html

@@ -64,7 +64,7 @@
             <li><a target="_blank" href="https://www.mailvelope.com/privacy-service">Privacy</a></li>
           </ul>
         </nav>
-        <p>&copy; 2016 Mailvelope GmbH</p>
+        <p>&copy; 2019 Mailvelope GmbH</p>
       </footer>
 
     </div> <!-- /container -->