frust 0.5.2

• User-visible text matches the released framework (#15): generated projects' settings.gradle.kts and .gitignore, the frust-auth-session "Gradle module is not linked" error and the plugin READMEs no longer name a nonexistent frust plugin add command (it is the TUI's Add Plugin), and plugin Android modules are shown wired through frustLocalDir("frust.plugin.<module>.dir") from the gitignored android/local.properties, with iOS packages through the project's ios/<Package> symlinks.
• First release published from CI through crates.io Trusted Publishing; the release workflow waits out the update rate limit (#16).

All 47 crates are published at 0.5.2. Install or upgrade with cargo install frust-cli; a project depends on frust = { package = "frust-ui", version = "0.5.2" }.

frust 0.5.1

frust create scaffolds projects that depend on the crates.io release (frust = { package = "frust-ui", version = "0.5.1" } and the plugin crates at the same version) instead of a framework checkout; --frust-path <checkout> is the contributor mode. The Android and iOS embeddings and every plugin's native module are located through cargo and wired into untracked files (android/local.properties, ios/<Package> symlinks) by frust create, refreshed by frust run/frust build, and shown by frust doctor. All 47 packages are published at 0.5.1; frust-cli and frust-tui 0.5.0 are yanked.

Install: cargo install frust-cli, then frust create my_app && cd my_app && frust run. Docs: https://frust.dev/docs/get-started/install

frust 0.5.0

First crates.io release: 47 packages (the frust-ui facade — imported as frust, see lloydmeta/frunk#258 — the engine, shells, plugins, tooling and clean-signals-frust).

Use 0.5.1. The frust-cli and frust-tui 0.5.0 binaries scaffold a path dependency into a framework checkout instead of the registry, and they no longer compile from source against the 0.5.1 siblings; both are yanked. Every other 0.5.0 crate is identical in content to its 0.5.1 version.