SDK catalog / Mobile Converter

Mobile Converter

alpha 0.3.0-alpha.4

Preview documentation for @wf/mobile-converter@0.3.0-alpha.4. Existing legacy downloads may use a different API; this page does not announce a new release.

Join the alpha Sign in with Google, then add your name. We review alpha access requests.

BrightOps mobile-converter changes

0.3.0-alpha.4

YAML app.nativePlugins packages reviewed local Capacitor plugins without editing the generated project. Archives require an exact SHA-256, remain inside the allowed workspace, and participate in prepare/verify ownership checks. Native compilation still requires allowBuilds. Existing configurations are unchanged.

Optional YAML app.version and app.buildNumber set one version for Android and iOS during sync. Both fields are required together. Verification refuses stale native version settings, and custom dynamic version expressions are preserved with an actionable error.

0.3.0-alpha.3 — @wf package scope

The package is now @wf/mobile-converter. Replace imports and dependencies on @workforce-sdk/mobile-converter; keep YAML, host credentials and application data. Existing archives remain unchanged. BrightOps remains the publisher.

0.3.0-alpha.3 — private preview

Recover a killed converter through an OS-released SQLite writer lease while preserving its legacy lock as evidence. Live and unidentified owners stay protected. Wire the native signing check. Node.js 22.19 or newer is required; existing app identities, saved data and YAML remain unchanged.

0.3.0-alpha.2 (private preview)

The shipped buyer example and integration documentation use the WF package name without requiring a legacy alias. Inspection uses the web build directory configured in YAML, matching preparation. Regression coverage executes the shipped example without the legacy package and inspects a non-default build directory. Native compilation and application backend integration remain separate from asset packaging.

0.3.0-alpha.1 (private preview)

Canonical ownership moves from Interview to WF. Applications consume this package through its public exports. Existing data and YAML formats are preserved. Registry publication and new platform verification are pending.