Yosoi 0.3.0 release notes
Summary
Section titled “Summary”Yosoi 0.3.0 makes Python Contracts use normal Pydantic validation and gives Rust and Python a shared workflow for saving and inspecting browser evidence. The Concepts series follows one QScrape product from local HTML through browser work and offline inspection.
Highlights
Section titled “Highlights”Validated Python records
Section titled “Validated Python records”Product.extract(document) and ys.extract(document, Product) return validated Pydantic models. Field and model validators, custom types, defaults and constraints run automatically. Use extract_report to inspect accepted records, rejected candidates and retained diagnostics; ExtractionPolicy bounds the work and controls rejection handling.
Archive and inspect completed browser work
Section titled “Archive and inspect completed browser work”Python can save Documents, compiled Plans and AutomationRecords through the existing Rust Archive backend. Both languages can retain a Flow’s results, cleanup receipts and observations, then reopen them without launching another browser. Bounded View pages preserve observation identity and reject foreign or changed continuation sources.
Complete binary response bodies
Section titled “Complete binary response bodies”Request attempts expose their complete retained body bytes and content type independently of searchable Documents. Binary responses can remain useful even when no text Document can be projected. Truncated or unavailable bodies are not presented as complete.
Installation-aware CLI maintenance
Section titled “Installation-aware CLI maintenance”The CLI supports self update and uninstall for standalone, UV and Cargo installations, with installation-specific behavior. Documentation now presents the supported installation paths and a progressive worked Concepts series.
Known limitations
Section titled “Known limitations”The reviewed Linux browser launch window moves from Chrome 155/154 to regular Stable 156/155. Update to current Stable before using browser workflows; M154 is now outside the supported milestone window. The 30-day review and release-age limits remain enforced. This refresh changes launch eligibility, not the controller or generated protocol: Chromiumoxide 0.9.1 and the Chrome 153 CDP schema remain unchanged. It does not claim a new fully certified browser/controller/protocol tuple. See Google’s Chrome 156 announcement.
The headless and headful browser container recipes pin Debian Chromium 156.0.8078.47-1~deb13u1, replacing the retired M154 package. The image base remains pinned, and the browser still runs as an unprivileged user with sandboxing enabled.
The local Archive backend currently supports Unix filesystems. Windows returns an explicit unsupported-platform error. Saved evidence does not restore live browser authority or replay effects. Arbitrary Python/Pydantic objects are not portable Rust archive values. Public remote-CDP attachment and recursive Contract roots remain deferred.
Upgrading
Section titled “Upgrading”Update the Rust SDK dependency and Python yosoi package to 0.3.0. CLI users install or upgrade yosoi-cli, rather than the legacy Python CLI package.
Python Contract extraction now returns validated model instances. Code using the former Contract.extract(located) intermediate pipeline should use Contract.assemble(located); use Contract.extract(document) for the convenient validated path. Rust’s explicit Contract extraction and validation pipeline remains available.
Full changelog and contributors
Section titled “Full changelog and contributors”Thanks to everyone who contributed to this release.
What’s Changed
Section titled “What’s Changed”- feat(cli): add self update and uninstall for 0.3.0 by @AndrewPBerg in https://github.com/CascadingLabs/Yosoi/pull/161
Full Changelog: https://github.com/CascadingLabs/Yosoi/compare/v0.2.1...v0.3.0