Open Manuscript Studio 0.3.0-beta.12
Release preparation: 30 October 2026. This release packages the merged native dependency security updates and macOS installer fixes after beta.11 into a new application version.
What changes for users
- TLS dependencies: updates
rustls-webpkito0.103.16for RUSTSEC-2026-0382 / CVE-2026-111943, addressing acceptance of distrusted emSign intermediate certificates. The lockfile also updates the wasm32-onlywebpki-root-certsbranch to1.0.10for RUSTSEC-2026-0383; that branch is not activated in the desktop or Android targets. - Native async runtime: updates Tokio to
1.53.3for the AsyncFd I/O-safety issue RUSTSEC-2026-0386. Release-security tests reject reintroduction of the affected dependency versions. - Native plugins: includes
tauri-plugin-opener2.7.2andtauri-plugin-persisted-scope2.4.2. The opener update fixes a Linux/BSD runtime panic when revealing a file in its directory. - macOS installers: separates application compilation from DMG packaging. Transient
hdiutilresource-busy failures retry only packaging, at most three times with 10- and 20-second waits; other failures still stop the job. - Portable format: the OMI manuscript format remains
OMI-SPEC-320@0.3.0.
These Rust dependency updates concern the native application dependency graph and its target-specific branches. They do not establish a vulnerability in the Node.js API server. The upstream glib advisory is not resolved by this release.
Application versions
| Platform or contract | Version |
|---|---|
| Shared Studio / web / native app version | 0.3.0-beta.12 |
| Windows MSI product version | 0.3.0.12 |
| iOS / iPadOS short version | 0.3.0 |
| iOS / iPadOS build | 24 |
| Android checked-in versionCode floor | 1211 |
| Portable OMI format | OMI-SPEC-320@0.3.0 |
Updating and deployment
After the release PR is merged, native build workflows create new packages from the merged commit and publish the new release only after all required builds pass. Existing releases and their assets remain immutable. The Studio downloads page follows the current published release.
Google Play requires a new Android Release run from the merged main branch. The workflow derives a new versionCode for that run; rerunning an already uploaded run does not create a new Play update. iOS public distribution still requires Apple signing, provisioning and device/TestFlight validation.
No database migration is added by beta.12. Updating from beta.11 requires rebuilding and distributing the native applications; a web-only deployment does not update an installed Android or desktop application.