Tags

Tags give the ability to mark specific points in history as being important

  • v0.14.1

    d72941d9 · fix: raise the emulator memory cap to 12g and drop versions from the README · 
    v0.14.1

- `ANDROID_LAB_EMULATOR_MEMORY_LIMIT` overrides the emulator memory cap. `start` accepts a whole number followed by `m` or `g` and rejects anything else.

- The emulator container's memory cap is 12g instead of 8g. A 4 GiB guest with software rendering holds about 7.4 GiB, so long test runs hit the 8g cap and the kernel killed the emulator mid-run.

- A running lab keeps its old cap until `android-lab restart` recreates the emulator with this release.

- The README and the installer's usage comment write `<version>` and show how to pick a release from the tags, as the `android-lab` skill already does. A release now changes only `VERSION`.

  • v0.14.0

    e84447c7 · feat: publish the android-lab skill to ClawHub and fix the default viewer port · 
    v0.14.0

- `AGENTS.md` is tracked. It documents the lab workflow and the version references to update when `VERSION` changes.
- The `android-lab` skill is published to ClawHub on each release. It tells an agent how to pick a release from the tags, install the images, build with Gradle, run the emulator, install APKs, inspect the UI and forward ports from the app's own directory, with the exact `docker run` commands.

- `android-lab start` publishes the web viewer on 127.0.0.1:61326 by default. Before, Compose bound 61325 while the readiness check waited for 61326, so `start` failed unless `ANDROID_LAB_VNC_HOST_PORT` was set.

- On 0.13.0, set `ANDROID_LAB_VNC_HOST_PORT=61326` for lifecycle commands, or install 0.14.0.

  • v0.13.0

    913b4c30 · feat: install tagged releases with install.sh and publish GitHub releases · 
    v0.13.0

- `install.sh` builds the local images for one tagged release. It is meant for `curl | bash`, keeps images that already exist, checks the tag's `VERSION`, and needs only Bash, Git, Make and Docker on the host. `make test` covers it with stubbed Docker, Git and Make.
- Tag pushes create a GitHub Release after the checks pass.
- Portable Android Lab skills and setup references, with README instructions for installing them in another Android project.
- Codeberg and GitLab mirrors, scheduled mirror issue sync, and public archive jobs.

- The README documents generic port forwarding without launcher-specific protocols.
- Make sizes tool CPU limits and Gradle workers for the Docker host, capped at ten CPUs.
- Split Dikciz Launcher into a standalone repository. Android Lab now embeds generic Gradle, emulator and device commands in local versioned tooling images.
- Consumers build Android Lab images locally, then use their own Makefiles. Images are not published to a registry.
- Gradle projects may live at the consumer workspace root. Controllers use explicit host workspace paths and workspace-specific Compose names.

- Lab contract tests check the configured Gradle worker count instead of requiring ten workers on every runner.
- The pipeline's concurrency group no longer collides with the reusable code workflow's group.
- The development image pins `shfmt` 3.13.1-r3. Alpine removed the -r2 rebuild, which broke `make dev-image`.

- Build both images with `install.sh` or `make build` in Android Lab after SDK license acceptance, then run Dikciz operations from its separate checkout.
- Preserve `.android-lab/` when migrating. It contains the saved phone and stable signing identity.
- Changelog entries before 0.13.0 describe the combined lab and launcher repository.