Pocket Deck 1.0.4
Pocket Deck 1.0.4
npm install -g @masadev/pocket-decknow verifies the Windows installer, installs for the current user and opens the desktop application. Global npm updates also update the desktop installation. Close Pocket Deck from the tray before updating; running processes are never forcibly stopped. Local npm installs and npx do not automatically install the desktop application.- The desktop application checks for stable releases at startup and offers Update / Later. Downloads and installation require approval. Updates can also be checked manually. Settings remain in the existing user data directory.
- Installer filenames, update metadata, licensing notices and installation/release documentation have been updated.
Validation
- npm: 11 tests passed. Desktop: 15 tests passed. Source checks passed.
- Disposable Windows Sandbox: verified installer checksum, silent installation of 1.0.4, backend startup, real electron-updater/NSIS update to a local test-only 1.0.5, unchanged configuration/user data and restarted backend.
- Integration tests substitute local release files and consent. Public release downloads, the native confirmation dialog and another PC/phone require separate validation. The test-only 1.0.5 is not a public release.
Notes
1.0.3 does not include an updater. Install 1.0.4 once using npm or the exe to enable future in-app updates. Windows x64 and Node.js 22.12+ are required for npm installation; npm install scripts must be allowed. Existing all-users installations should use the Windows installer.
The installer is unsigned. The phone connection remains an unauthenticated, non-HTTPS LAN MVP for trusted networks. The existing held-drag issue remains unresolved. npm uninstall removes the npm package; remove the desktop app separately through Windows Settings. MIT license.
Publication impact and recovery
Publishing includes the main-branch source, stable GitHub release v1.0.4 and npm @masadev/pocket-deck@1.0.4 with the latest tag. Global npm installation/update will now install/update and launch the Windows application, subject to enabled install scripts. It will not close a running application. Normal app startup checks stable releases but does not download or install without consent.
If a problem is found, deprecate the affected npm version and issue a higher-version corrective release. Published version numbers must not be reused. Removing a release does not undo installations already performed. The npm installer intentionally refuses automatic downgrades; a manual recovery requires exiting the app and using a known-good Windows installer while retaining user data.