Skip to content

v0.3.2

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 Sep 10:16
· 13 commits to main since this release
v0.3.2
ce727e8

v0.3.2 — reliable failure receipts

Status: published on 2026-09-08 at GitHub Release v0.3.2. Cargo metadata and the published binary are 0.3.2. The tag points to ce727e89711958fc09daa57ac17d90bf8743e8c3; the release workflow, checksums, clean-container install and provenance verification passed.

What is already on main

The release includes the changes listed below, supervised readers, observation after readiness/PID discovery, main-process continuity checks and launch-scoped crash detection. These behaviors have local regressions and hosted Linux/KVM evidence.

  • Failed runs after backend selection produce schema-v1 JSON, HTML, JUnit and Markdown receipts with a stable stage, classification and path-free summary.
  • Best-effort artifact capture preserves the primary run failure when an additional log source is unavailable.
  • HTML receipts escape ABI values correctly.
  • SHA-256 receipt encoding is compatible with sha2 0.11; the known digest-vector test passes.
  • Rust dependencies and workflow actions were updated. The Expo fixture uses Expo 57.0.20, React 19.2.3 and React Native 0.86.3; its workflow now checks SDK compatibility.

Publication and verification evidence

Hosted candidate evidence (September 8): c6c3df9 passed the API 35 action contract and fresh-runner tests. Its API 30 host workflow passed success, process exit, Java crash, missing launcher and performance checks. d1ad34c passed Linux archive/checksum/clean-container installation and locked packaged-source installation. The later exact-candidate nine-case validation below supersedes the initial four-case runtime coverage. These are commit-specific gates, not publication proof.

  • Resolve and verify the observation-window/reader-lifecycle risks in ROADMAP.md M1. The nine-case matrix at d9022f9 passed, including real ANR, injected reader/marker failures and cleanup precedence, alongside local observer regressions.
  • Run the failure matrix and normal fixture on Linux/KVM at the exact candidate revision. Exact-candidate host validation checked out archive source 2754c3e and passed the runtime/smoke suite, nine failure-matrix cases and performance gate. Matrix reports were downloaded and inspected.
  • Update Cargo.toml/Cargo.lock, changelog and action examples to the tested release. The published tag is v0.3.2 and the reusable examples pin the tag commit ce727e89711958fc09daa57ac17d90bf8743e8c3.
  • Build the x86_64 Linux archive and checksum, verify clean-container installation and attach provenance. Published workflow passed for tag v0.3.2; the downloaded release archive SHA-256 is 0617c7ace752cfdb924e68edf8df391c6e76da395a1dba78e97e7bdc77ca0656, and the fixture SHA-256 is 5006fcae4718a1998dbba7097283792807284c29a7eff79f1d3a7a072492cf60. gh attestation verify identifies source ce727e89711958fc09daa57ac17d90bf8743e8c3.
  • Record the complete real success/failure emulator demo and attach its raw evidence. Capture 34209082936 and green FFmpeg export 34210495967 are documented in docs/receipts/product-demo.md.
  • After publication, download and verify the tagged assets and execute the README quickstart on a clean supported host. Published-release verification 34215919027 passed on a GitHub Linux runner with an API 35 test_avd; the downloaded v0.3.2 fixture checksum is 5006fcae4718a1998dbba7097283792807284c29a7eff79f1d3a7a072492cf60, and the receipt reports package com.rustdroid.fixture.launch, activity com.rustdroid.fixture.launch.MainActivity, headless execution, and total duration 39905 ms.

Validation before publication

On September 8, main at ce727e8 passed local Rust tests, Clippy with warnings denied, formatting, shell checks, Cargo package verification, cargo-deny and the Expo install/audit/compatibility checks. Emulator-dependent tests run only on GitHub Linux/KVM runners, not on this Mac. These checks complement the published Linux release gates.

Limits to retain in the published notes

Linux/KVM is the supported runtime. macOS CLI compilation is not macOS emulator support. A successful smoke receipt does not validate business flows or a device matrix. Failures before receipt ownership retain their documented stderr/exit-code limits. Logs can contain application data.

The release is immutable; do not move the v0.3.2 tag or relabel its binary. The dedicated clean-runner quickstart receipt is now verified; future changes must publish a new tag rather than mutating this release.

Assets 7
Loading