release v0.2.0

CHANGELOG.md

@@ -5,6 +5,8 @@ This project adheres to [Semantic Versioning](http:https://semver.org/).
 
 ## [Unreleased]
 
+## [v0.2.0]
+
 ### Added
 
 - Statically linked binary releases for Linux (x86 musl targets)
@@ -134,7 +136,8 @@ to *always* trigger a sysroot rebuild.
 
 - Initial release
 
-[Unreleased]: https://github.com/japaric/xargo/compare/v0.1.14...HEAD
+[Unreleased]: https://github.com/japaric/xargo/compare/v0.2.0...HEAD
+[v0.2.0]: https://github.com/japaric/xargo/compare/v0.1.14...v0.2.0
 [v0.1.14]: https://github.com/japaric/xargo/compare/v0.1.13...v0.1.14
 [v0.1.13]: https://github.com/japaric/xargo/compare/v0.1.12...v0.1.13
 [v0.1.12]: https://github.com/japaric/xargo/compare/v0.1.11...v0.1.12

README.md

@@ -30,7 +30,7 @@ The magic happens when you call `xargo` with the `--target` flag. In that case,
 care of building a sysroot with cross compiled crates and calling `cargo build` with the appropriate
 `RUSTFLAGS` variable. Example below:
 
-![Screenshot](http:https://i.imgur.com/pUIfnwu.jpg)
+![Screenshot](https:https://i.imgur.com/qAvB81X.png)
 
 `xargo` will cache the sysroot, so you can use it across different Cargo projects without having to
 build a sysroot for each project. `xargo` will also take care of rebuilding the sysroot when