allwright

Changelog

What shipped, release by release.

allwright cuts a lot of small releases — most are packaging fixes or internal hardening nobody needs to read about. This page groups the ones that actually changed what you can build, newest first. For the full, unfiltered commit history, see the tags on GitHub.

Next up is v0.1.0, allwright's first minor version — coming soon. Read what's tangible today on the way there.

  1. v0.0.57 – v0.0.58Sep 1, 2026

    Android automation reaches parity with web

    • Android locators gained count, focus, press-key, read-text, and wait-for-selector — the same actions already available on web, now available on mobile too.
    • Full-page Android screenshots now stitch several scrolled captures into one seamless image instead of cropping at the visible screen.
    • The Vitest integration gained a config helper that starts the engine once for a whole test run and shuts it down when the suite finishes, instead of every test bootstrapping its own.
  2. v0.0.54 – v0.0.55Sep 1, 2026

    Screenshots, everywhere

    • Screenshot capture shipped for every client language, on both web pages and Android apps.
    • Added full-page capture and the option to save a screenshot straight to a file.
  3. v0.0.53Aug 29, 2026

    One shared automation model for web and mobile

    • Unified the underlying session model so web and Android automation describe "what to act on" the same way, instead of two separate mental models.
    • Added a consistent, matching getting-started example for every client language, for both the web and Android surfaces.
    • Started early groundwork toward iOS support.
  4. v0.0.45 – v0.0.52Aug 29, 2026

    Mobile automation debuts: Android

    • Android joined web as a real automation surface: connect to a device or emulator, install and launch an app, and drive it with the same locator model already used for the browser.
    • Android selector support expanded to match common testing patterns — by visible text, resource id, class name, or state (like whether an element is clickable).
    • Apps can now be installed straight from a URL, not just a local file.
    • Web automation got more reliable: actions now wait for an element to be visible and settled before clicking or filling it, cutting down on flaky failures.
  5. v0.0.35Aug 27, 2026

    Zero-install experience

    • Client libraries now download and manage the engine and the surface plugin automatically the first time they're used — no separate CLI install step required before writing a test.
  6. v0.0.33Aug 26, 2026

    Firefox support, and a Playwright-style API redesign

    • Every client — Rust, Go, Java, Python, and TypeScript — gained a proper Browser / Page / Locator object model.
    • Firefox joined Chromium as a fully supported browser.
  7. v0.0.27 – v0.0.30Aug 26, 2026

    Config-file driven setup

    • Introduced allwright.config.yaml for describing how to launch a browser — binary, timeouts, named profiles — without writing it in code.
    • Wired the config file into every client so it's picked up automatically.
  8. v0.0.31Aug 26, 2026

    Java client published

    • The Java client became a real, installable Maven Central package, with its own test suite.
  9. v0.0.24Aug 26, 2026

    Python client, and first-class Vitest support

    • The Python client was published to PyPI.
    • Launched a dedicated Vitest integration package for TypeScript/JavaScript teams, with retrying, Playwright-style assertions.
  10. v0.0.19Aug 25, 2026

    TypeScript client published to npm

    • The TypeScript client became a normal npm install.
  11. v0.0.16Aug 25, 2026

    Rust crates published to crates.io

    • The Rust engine and client became a normal cargo install.
  12. v0.0.14Aug 24, 2026

    First real browser actions ship

    • Launch a browser, open/navigate a page, click, fill, hover, focus, press a key, highlight, count, read text, and wait for an element to appear — allwright's first real automation commands.
    • These actions retry automatically until they succeed or time out, instead of failing on the first attempt.
  13. v0.0.11Aug 24, 2026

    Plugin architecture

    • Automation surfaces became installable plugins loaded on demand — starting with web — instead of one fixed, all-or-nothing engine.
    • This is the architectural foundation every later surface (Android, and eventually iOS, desktop, and API) builds on.
  14. v0.0.7Aug 24, 2026

    Initial public release

    • allwright launched with an installable CLI, a plugin system for automation surfaces, and client libraries for five languages at once: Rust, Go, Java, Python, and TypeScript.

See what's real today

The changelog is history. For the current, continuously updated picture of what each surface can and can't do yet, see Availability.

Full availability breakdownStar on GitHub