OverviewFilesCommitsIssuesDocsReleasesPeers

favela-android commits / 8a9a591

0.1.4: carry favela-web 0.3.87 to the handset
No source change — the release name is <branch>-<shortsha>, so an unchanged HEAD is refused and favela-web work (vendored from the live checkout at pack time) cannot reach the phone. Carries: 0.3.86 a bsky account s posts render even when we hold their profile record. The lens gate required lensProfile, which is only fetched when we hold NO profile — so the common case (discovered via a backlink) showed a real name and avatar above "no posts from this author". 0.3.87 the lens is a setting in the UI. This matters most here: a handset has no apps.json, so remote reading could not be configured on it by any means. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
8a9a591bf7a3c3a9cf4c4f049cce20e99ead8de6
by plankatron <fleeky@gmail.com> · 2026-08-25T19:10:50.000Z

Changed files (1) +1 -1

package.json +1 -1
……@@ -1,6 +1,6 @@
11{
22 "name": "favela-android",
3 "version": "0.1.3",
3 "version": "0.1.4",
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",