Release cargo-apk 0.6.0 and ndk-build 0.2.0

cargo-apk/CHANGELOG.md

@@ -1,4 +1,4 @@
-# Unreleased
+# 0.6.0 (2021-04-20)
 
 - **Breaking:** uses `ndk-build`'s new (de)serialized `Manifest` struct to properly serialize a toml's `[package.metadata.android]` to an `AndroidManifest.xml`. The `[package.metadata.android]` now closely resembles the structure of [an android manifest file](https://developer.android.com/guide/topics/manifest/manifest-element). See [README](README.md) for an example of the new `[package.metadata.android]` structure and all manifest attributes that are currently supported.
 

cargo-apk/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "cargo-apk"
-version = "0.5.6"
+version = "0.6.0"
 authors = ["The Rust Windowing contributors"]
 edition = "2018"
 description = "Helps cargo build APKs"
@@ -16,7 +16,7 @@ cargo-subcommand = "0.5.0"
 dunce = "1.0.1"
 env_logger = "0.8.2"
 log = "0.4.14"
-ndk-build = { path = "../ndk-build", version = "0.1.4" }
+ndk-build = { path = "../ndk-build", version = "0.2.0" }
 serde = "1.0.123"
 thiserror = "1.0.23"
 toml = "0.5.8"

ndk-build/CHANGELOG.md

@@ -1,4 +1,4 @@
-# Unreleased
+# 0.2.0 (2021-04-20)
 
 - **Breaking:** refactored `Manifest` into a proper (de)serialization struct. `Manifest` now closely matches [`an android manifest file`](https://developer.android.com/guide/topics/manifest/manifest-element).
 - **Breaking:** removed `Config` in favor of using the new `Manifest` struct directly. Instead of using `Config::from_config` to create a `Manifest`, now you instantiate `Manifest` directly using, almost all, the same values.

ndk-build/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "ndk-build"
-version = "0.1.4"
+version = "0.2.0"
 authors = ["The Rust Windowing contributors"]
 edition = "2018"
 description = "Utilities for building Android binaries"