Skip to content

v3.1.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 12 Oct 11:38
· 10 commits to main since this release
v3.1.1
cc533fb

PinkCollab v3.1.1: recover OMP after installation path changes

Fixes

  • Setup can recover a stale OMP path after switching installation channels. It validates the replacement and requires interactive confirmation or an explicit --omp option; a working saved launcher remains preferred.
  • Setup and doctor avoid probing the same failed launcher twice, including Windows filename case variants such as omp.exe and omp.EXE. Doctor reports recovery options without changing configuration or migrating the database.
  • Recovery documentation now focuses on commands and necessary precautions.

Upgrade

  • Update with npm install -g pinkcollab@3.1.1, then run pinkcollab setup with your existing transport settings. For external HTTPS, retain --transport external --public-url https://....
  • A required Gateway restart ends active OMP runtimes but preserves pairings and saved sessions. Finish active work before setup. To select a replacement explicitly, use pinkcollab setup --omp omp or pinkcollab setup --omp "/absolute/path/to/omp".
  • Android/Gateway Protocol 4 and the database schema are unchanged. Install the signed Android APK over the existing app; do not uninstall it.

Verification

  • Gateway CI passed on Windows, macOS, and Ubuntu, including formatting, strict Clippy, and the full test suite.
  • Windows CLI smoke confirmed that setup and doctor probe the failed case-variant launcher once, retain configuration, and do not create a database. This used an isolated fake launcher, not a real OMP installation or production service migration.
Assets 9
Loading