build(release): move Android bundle publishing into GoReleaser

- build the Android universal bundle from GoReleaser hooks
- attach the bundle as a release asset
- remove the separate post-release upload step
- simplify Make targets around cross-platform builds
This commit is contained in:
wenjie
2026-04-13 11:52:35 +08:00
parent ea2107e8a9
commit d73a0e89b4
15 changed files with 18 additions and 102 deletions
+3 -10
View File
@@ -187,9 +187,6 @@ make build-launcher
# Build core binaries for all Makefile-managed platforms
make build-all
# Build release-only artifacts packaged separately from the main GoReleaser outputs
make build-release-artifacts
# Build for Raspberry Pi Zero 2 W
# 32-bit: make build-linux-arm
# 64-bit: make build-linux-arm64
@@ -199,10 +196,6 @@ make build-pi-zero
make install
```
`make build-all` builds the core `picoclaw` binaries for all Makefile-managed platforms.
`make build-release-artifacts` builds release-only artifacts that are packaged separately from the main GoReleaser outputs.
**Raspberry Pi Zero 2 W:** Use the binary that matches your OS: 32-bit Raspberry Pi OS -> `make build-linux-arm`; 64-bit -> `make build-linux-arm64`. Or run `make build-pi-zero` to build both.
## 🚀 Quick Start Guide
@@ -232,7 +225,7 @@ picoclaw-launcher
<img src="assets/launcher-webui.jpg" alt="WebUI Launcher" width="600">
</p>
**Getting started:**
**Getting started:**
Open the WebUI, then: **1)** Configure a Provider (add your LLM API key) -> **2)** Configure a Channel (e.g., Telegram) -> **3)** Start the Gateway -> **4)** Chat!
@@ -310,7 +303,7 @@ picoclaw-launcher-tui
<img src="assets/launcher-tui.jpg" alt="TUI Launcher" width="600">
</p>
**Getting started:**
**Getting started:**
Use the TUI menus to: **1)** Configure a Provider -> **2)** Configure a Channel -> **3)** Start the Gateway -> **4)** Chat!
@@ -385,7 +378,7 @@ This creates `~/.picoclaw/config.json` and the workspace directory.
```
> See `config/config.example.json` in the repo for a complete configuration template with all available options.
>
>
> Please note: config.example.json format is version 0, with sensitive codes in it, and will be auto migrated to version 1+, then, the config.json will only store insensitive data, the sensitive codes will be stored in .security.yml, if you need manually modify the codes, please see `docs/security_configuration.md` for more details.