Version 0.14 release

CHANGELOG.md

@@ -6,7 +6,7 @@ incremental in minor, bugfixes only are patches.
 See [0Ver](https://0ver.org/).
 
 
-## 0.14.0 WIP
+## 0.14.0
 
 ### Features
 

README.md

@@ -617,6 +617,7 @@ Or read these articles:
 - [Python exceptions considered an anti-pattern](https://sobolevn.me/2019/02/python-exceptions-considered-an-antipattern)
 - [Enforcing Single Responsibility Principle in Python](https://sobolevn.me/2019/03/enforcing-srp)
 - [Typed functional Dependency Injection in Python](https://sobolevn.me/2020/02/typed-functional-dependency-injection)
+- [How Async Should Have Been](https://sobolevn.me/2020/06/how-async-should-have-been)
 
 Do you have an article to submit? Feel free to open a pull request!
 

docs/pages/future.rst

@@ -257,6 +257,8 @@ Python happens to have its own meaning for this word.
 In our worldview, these two ``Future`` entities should never meet each other
 in a single codebase.
 
+It is also not related to `concurrent.Future <https://docs.python.org/3/library/concurrent.futures.html>`.
+
 How to create unit objects?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
@@ -293,6 +295,7 @@ You can always covert it with methods like
 Further reading
 ---------------
 
+- `How Async Should Have Been <https://sobolevn.me/2020/06/how-async-should-have-been>`_
 - `What Color is Your Function? <https://journal.stuffwithstuff.com/2015/02/01/what-color-is-your-function/>`_
 - `From Promises to Futures <https://dev.to/nadeesha/from-promises-to-futures-in-javascript-2m6g>`_
 

pyproject.toml

@@ -9,7 +9,7 @@ style = "https://raw.githubusercontent.com/wemake-services/wemake-python-stylegu
 
 [tool.poetry]
 name = "returns"
-version = "0.13.0"
+version = "0.14.0"
 description = "Make your functions return something meaningful, typed, and safe!"
 license = "BSD-3-Clause"