OverviewFilesCommitsIssuesDocsReleasesPeers

favela-android commits / d5e434e

0.0.2: a version the installer can tell apart
versionCode has been 1 for every APK built this week — nine releases, one version number. Android uses versionCode to decide what an upgrade IS, so every install has been indistinguishable from the last, and nothing on the device could say which build was running. `pgh deploy log` knows; the phone does not. Also the first bump since the foreground service and the notification that reports what is being served, both of which shipped under 0.0.1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
d5e434ef9e4bd7f449647a197f31a58522c7dc5a
by plankatron <fleeky@gmail.com> · 2026-08-18T15:15:10.000Z

Changed files (2) +3 -3

android/app/build.gradle +2 -2
……@@ -97,8 +97,8 @@ android {
9797 applicationId "to.favela.android"
9898 minSdk rootProject.ext.minSdkVersion
9999 targetSdk rootProject.ext.targetSdkVersion
100 versionCode 1
101 versionName "0.0.1"
100 versionCode 2
101 versionName "0.0.2"
102102
103103 ndk {
104104 // ⛔ ARM64 ONLY. An APK is a self-contained sideloadable ZIP with no notion of "the arch I
package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "favela-android",
3 "version": "0.0.1",
3 "version": "0.0.2",
44 "description": "favela-android — a React Native client over a bare-kit worklet running a FULL favela node (hyper-proto-peer + appview + hyperswarm) on the phone. favela-web is reference for the logic, NOT the rendering: this is a different rendering surface. See spec/architecture.md.",
55 "private": true,
66 "type": "module",