Skip to content

Cox v0.1.42

Choose a tag to compare

View all tags
@doublepi123 doublepi123 released this 06 Nov 06:12
· 22 commits to main since this release
v0.1.42
b55c7e8

Cox v0.1.42

Cox and the desktop client now have independent versions. Desktop installers are explicitly
named cox-desktop; combination filenames include both the client and Cox versions.

  • Add desktop-owned Cox installation and update management. Check the official stable npm
    package at startup, every six hours, or manually from Settings → About.
  • Verify npm SHA-512 integrity and runtime compatibility before staging an update. Activate
    on the next normal launch without interrupting active coding tasks.
  • Snapshot desktop userdata before activation and restore the matching data and previous
    backend if startup or migration fails.
  • Support client-only packages: download Cox on first launch, then reuse the verified local
    installation offline. Keep managed backends outside the signed application bundle.
  • Show desktop, installed Cox and bundled Cox versions separately, with a themed update dialog.
  • Add three subtle animated dots below Cox on the loading screen; respect reduced motion.
  • Build latest-Cox/latest-released-desktop combination installers after stable Cox publication.
    Desktop releases also produce separate client-only installers.

Validation

  • Release commit: b55c7e8bada869ec465c7bc0941b94d731269b50.

  • All four main CI jobs passed: Core, Server, Web and Distribution. The complete suites
    passed 15,458 tests, with 7 skipped: 5,655 Server, 5,095 Web, 3,363 shared packages,
    1,237 client-runtime and 108 root/desktop tests.

  • Workspace typechecks, production builds and isolated runtime/development checks passed.

  • The CI source archive passed SHA-256, version/commit checks and a fresh frozen-dependency
    installation, including local/password authentication, HTTP/WebSocket origin checks and
    actual development startup with isolated state.

  • Main CI

  • All six desktop pre-release CI jobs passed, covering bundled and client-only installers
    on macOS Apple Silicon, macOS Intel and Windows x64.

  • Client-only native checks exercise fresh first installation and a second offline launch.

  • macOS checks verify unpacked and DMG signatures, including the standalone Node binary.

  • Desktop tests cover owned backend cleanup, staged activation, matching data/code rollback
    and the macOS forced-shutdown process-group reaping race.

  • Desktop packaging preserves relative npm symlinks, keeping signed macOS bundles self-contained.

  • Desktop startup waits for asynchronously published ownership data with a cancellable deadline;
    delayed foreign owners and malformed descriptors still fail closed.

  • Desktop 0.2.3 pre-release CI

  • Desktop 0.2.3 native release builds

  • The public npm tarball matches the CI tarball byte-for-byte, passes SHA-512/SHA-1 checks,
    and includes the expected desktop compatibility metadata, licenses and all six platform bridges.
    Provenance source/ref and digest metadata match the release commit.

  • Fresh isolated npm installation passes local/password authentication and runtime smoke tests.

  • A real official-npm upgrade from Cox 0.1.41 to 0.1.42 stages without disturbing the running
    backend, activates on normal restart, preserves test data and retains a matching pre-upgrade
    SQLite snapshot. No live user service or application data was used.

Desktop downloads

The combination installers attached to this release use Desktop 0.2.3 + Cox 0.1.42.
macOS provides DMG only, with no duplicate ZIP application packages. Windows uses EXE.
Native dialogs and custom menu labels follow the OS language instead of showing bilingual copy.
Update-download dialogs distinguish progress, completion and errors rather than reporting
unfinished downloads as up to date.

Client-only installers are available in the separate
Desktop 0.2.3 release.

Install

npm install --global @doublepi123/cox@0.1.42

For the source archive with prebuilt assets, extract it, run
pnpm install --frozen-lockfile, then pnpm start using the pinned Node and pnpm versions.

Client-only installers require internet on first launch. macOS packages use ad-hoc signing,
without Developer ID notarization; Windows packages are not publisher-signed.

This release does not change or restart an existing local Cox deployment.

Assets 20
Loading