[github-actions]

🤖 I have created a release beep boop

romm-api: 1.5.0

1.5.0 (2026-11-04)

Features

• api: add RomCache::get_complete for stale ROM list reads (745752e)

romm-cli: 1.3.2

1.3.2 (2026-11-04)

romm-tui: 1.5.0

1.5.0 (2026-11-04)

Features

• tui: load OpenAPI locally and refresh after first paint (d085a68)
• tui: paint cached ROM lists before network refresh (749d3c4)

---

This PR was generated with Release Please. See documentation.

[patricksmill]

Release preparation: compatibility matrix corrected in 1dfb2d6 for romm-api 1.5.0 / romm-cli 1.3.2 / romm-tui 1.5.0. Before correction, versions-only preflight failed on the TUI 1.4.2 versus 1.5.0 mismatch. After correction, full bash tools/release-check.sh passed: API 1.5.0 package dry-run verification and frontend release builds (frontend package dry-runs remain deferred until API 1.5.0 reaches crates.io). No real upload occurred. Built CLI smoke printed romm-cli 1.3.2; the built TUI launched its setup wizard in an isolated terminal and exited with Esc. The TUI does not parse --version; the runbook is corrected in #108, along with invoking the non-executable preflight script through bash. Existing Cargo.lock warning: async-executor 1.14.0 is yanked; dependencies were not changed. Merge typing-indicator PR #108 and let Release Please refresh this PR before shipping if that fix should be included. #108 passed 439 workspace tests, formatting, both Clippy variants and 19 render smoke scenarios. Release not merged or published.

[github-actions]

🤖 Created releases:

• romm-api-v1.5.0
• romm-cli-v1.3.2
• romm-tui-v1.5.0

🌻