Prepare for release

Author: BenMorel

README.md

@@ -26,7 +26,7 @@ The current releases are numbered `0.x.y`. When a non-breaking change is introdu
 
 **When a breaking change is introduced, a new `0.x` version cycle is always started.**
 
-It is therefore safe to lock your project to a given release cycle, such as `0.3.*`.
+It is therefore safe to lock your project to a given release cycle, such as `0.5.*`.
 
 If you need to upgrade to a newer release cycle, check the [release history](https://github.com/brick/std/releases)
 for a list of changes introduced by each further `0.x.0` version.