Bump to v0.6.1

frontend/package.json

@@ -1,6 +1,6 @@
 {
   "name": "frontend",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "",
   "main": "index.js",
   "scripts": {

mobile/android/app/build.gradle

@@ -152,7 +152,7 @@ android {
         minSdkVersion rootProject.ext.minSdkVersion
         targetSdkVersion rootProject.ext.targetSdkVersion
         versionCode 1
-        versionName "0.6.0-alpha"
+        versionName "0.6.1-alpha"
         buildConfigField "boolean", "IS_NEW_ARCHITECTURE_ENABLED", isNewArchitectureEnabled().toString()
 
         if (isNewArchitectureEnabled()) {

mobile/package.json

@@ -1,6 +1,6 @@
 {
   "name": "robosats",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "private": true,
   "scripts": {
     "android": "react-native run-android",

release_notes.md

@@ -1,41 +1,45 @@
-RoboSats v0.6.0 is now out! :rocket:
+RoboSats v0.6.1 is now out! :rocket:
 
 # Changes
-## New Features
-### Decentralization
-RoboSats v0.6.0 introduces a major upgrade, introducing the RoboSats Federation, a decentralized system of independent coordinators to host orders, enhancing the platform's robustness and user experience. This version is a significant step towards decentralization, allowing users to interact with any coordinator seamlessly.
+## What's new
+### Android app comes back stronger than ever!
+After we skipped several Android app releases in order to focus on the decentralization, now the Android app comes back with all the strength. The Android app is now THE BEST WAY to use RoboSats. The It's a full RoboSats self-hosted client, it connects to all RoboSats coordinators and can generate robot identities fully locally. All of the networking is torified by default and now torification is more stable than it ever was. With this release, we aim to publish on F-Droid.
 
-It's crucial to choose trustworthy coordinators due to the potential risks of malicious activity. The federated client is available for testing at specific URLs, with a stable release planned. Key features include multiple coordinators competing for users, decentralized instances for increased robustness, and a focus on coordinators profiles and trust.
+## Other
+This release contains many small client and coordinator bug fixes. Most importantly, this release has a large bump on critical coordinator dependencies (Django v5). Introduces some new coordinator panel utilities and adds a new Coordinator setting to Geo block F2F orders in some countries.
 
-Learn more in https://learn.robosats.com/robosats/update/pre-release-robosats-decentralized/
+## Special thanks
+Special thanks to @KoalaSat who has driven all the work to improve the torification of the Android app, the embedding of the robot avatar generator libraries and got the app cleaned up and ready for publishing on F-Droid.
 
-### New avatar generator
-Your Robot identity is now generated in your client app, when previously, the robot identity was created by the coordinator. This allows now for super-fast Robot avatar and nickname generation that works even if your connection to the coordinators is down. The new robot avatars, are in fact, more diverse and better looking, however, the same token will now yield a different avatar when compared to v0.5.4 (but the robot identity remains the same, also keeping the same nickname).
+# Android
 
-## Bug Fixes and Performance Improvements
-The whole app architecture is new. There might be new bugs, solved bugs, worse performance and better performance: who knows!! :D
+**[Click to download universal RoboSats APK for Android](https://github.com/RoboSats/robosats/releases/download/v0.6.1-alpha/robosats-v0.6.1.alpha-universal.apk)**
+Smaller bundles for each CPU architecture available in the attachments.
 
-## Special thanks
-Special thanks to @KoalaSat who has driven some of the largest development pushes needed to get The Federation Layer fully working.
+### Verify the app using GPG:
 
-# Android
+1. [Download the ascii armored signature](https://github.com/Reckless-Satoshi/robosats/releases/download/v0.6.1-alpha/robosats-v0.6.1.alpha-universal.apk.asc)
+
+2. Run this command on a directory that contains the apk file and and the ascii armored signature.
+`gpg --verify robosats-v0.6.1.alpha-universal.apk.asc`
 
-The Android app is currently not supported on this early phase of the Federated app.
+3. Verify the signer is actually Reckless-Satoshi (fingerprints match): [B4AB5F19113D4125DDF217739C4585B561315571](https://keys.openpgp.org/vks/v1/by-fingerprint/B4AB5F19113D4125DDF217739C4585B561315571)
 
+Alternatively you can also verify with the release with the SHA256 checksum.
 
 # Docker Images
 
-[Coordinator Backend Image v0.6.0-alpha (Docker Hub)](https://hub.docker.com/r/recksato/robosats/tags?page=1&name=v0.6.0-alpha)
+[Coordinator Backend Image v0.6.1-alpha (Docker Hub)](https://hub.docker.com/r/recksato/robosats/tags?page=1&name=v0.6.1-alpha)
 
 
 ```bash
-docker pull recksato/robosats:v0.6.0-alpha
+docker pull recksato/robosats:v0.6.1-alpha
 ```
 
-[Client App Image v0.6.0-alpha (Docker Hub)](https://hub.docker.com/r/recksato/robosats-client/tags?page=1&name=v0.6.0-alpha)
+[Client App Image v0.6.1-alpha (Docker Hub)](https://hub.docker.com/r/recksato/robosats-client/tags?page=1&name=v0.6.1-alpha)
 
 ```bash
-docker pull recksato/robosats-client:v0.6.0-alpha
+docker pull recksato/robosats-client:v0.6.1-alpha
 ```
 
 See [nodeapp/docker-compose.yml](https://github.com/Reckless-Satoshi/robosats/blob/2cd9d748706a8dcc0f03006b483acc6000e0572a/nodeapp/docker-compose.yml) for an example docker-compose usage of the `robosats-client` image.

version.json

@@ -1,5 +1,5 @@
 {
   "major": 0,
   "minor": 6,
-  "patch": 0
+  "patch": 1
 }