v3.0.0

CHANGELOG

@@ -8,6 +8,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [3.0.0] - 2020-04-13
+New endpoints to create/update aliases:
+    PUT /api/aliases/:alias_id
+    GET /api/aliases/:alias_id/contacts
+    POST /api/aliases/:alias_id/contacts
+    GET /api/v2/aliases
+(Optional) Spam detection by Spamassassin
+Handling for bounced emails
+Support Multiple recipients (in To and Cc headers)
+
 ## [2.1.0] - 2020-03-23
 Support PGP
 

README.md

@@ -61,7 +61,7 @@ docker run --name sl -it --rm \
     -e RESET_DB=true \
     -e CONFIG=/code/example.env \
     -p 7777:7777 \
-    simplelogin/app:2.1.0 python server.py
+    simplelogin/app:3.0.0 python server.py
 ```
 
 Then open http://localhost:7777, you should be able to login with `john@wick.com/password` account!
@@ -477,7 +477,7 @@ sudo docker run --rm \
     -v $(pwd)/dkim.pub.key:/dkim.pub.key \
     -v $(pwd)/simplelogin.env:/code/.env \
     --network="sl-network" \
-    simplelogin/app:2.1.0 flask db upgrade
+    simplelogin/app:3.0.0 flask db upgrade
 ```
 
 This command could take a while to download the `simplelogin/app` docker image.
@@ -494,7 +494,7 @@ sudo docker run -d \
     -p 7777:7777 \
     --restart always \
     --network="sl-network" \
-    simplelogin/app:2.1.0
+    simplelogin/app:3.0.0
 ```
 
 Next run the `email handler`
@@ -509,7 +509,7 @@ sudo docker run -d \
     -p 20381:20381 \
     --restart always \
     --network="sl-network" \
-    simplelogin/app:2.1.0 python email_handler.py
+    simplelogin/app:3.0.0 python email_handler.py
 ```
 
 ### Nginx

docs/upgrade.md

@@ -4,6 +4,13 @@ No emails or any data is lost in the upgrade process. The same process is by the
 
 Sometimes upgrading to a major version might require running a manual migration. This is for example the case when upgrading to 2.0.0. In this case please follow the corresponding migration first before running these scripts.
 
+The latest version 3.0.0 has unfortunately some breaking changes with regard to 2x versions. 
+Upgrading from 2x to 3.0.0 might require some manual database verifications. 
+If you are currently running a version prior to 2.1.0 and want to upgrade to 3.0.0, please: 
+
+- first upgrade to 2.1.0
+- then try to upgrade to 3.0.0. If any error happens, please get in touch with us.
+
 <details>
 <summary>Upgrade to 2.1.0 from 2.0.0</summary>
 <p>