@calebcall/camera-ui-notify 0.5.3 → 0.5.5

package/CHANGELOG.md

@@ -5,6 +5,83 @@ All notable changes to **Notify** are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.5] - 2026-08-01
+
+### Changed
+
+- **Go SDK pinned to `v1.2.6`** (from `v1.2.4`) — routine catch-up on two upstream patches. No source
+  change required; `go build`, `go test` and the full 8-target bundle all pass untouched.
+- **`@camera.ui/cli` `~0.0.74`** (from `~0.0.73`) — routine. Still writes an `optionalDependencies` block
+  into the repo's own `package.json` on every bundle, so the `PUBLISHING.md` guidance from #16 continues
+  to apply: discard that hunk, never commit it.
+- **Minimum camera.ui raised to `2.0.24`** (from `2.0.23`) — 2.0.24 carries three host-side fixes that
+  directly affect plugin settings: panels getting permanently stuck on "No configuration available" when
+  a settings request was superseded, a camera's plugin toggle deleting that plugin's stored per-camera
+  settings, and cleared settings becoming `undefined` instead of falling back to their default. The
+  plugin wire protocol is unchanged from 2.0.23 (`protocolLevel` is still 1), so this floor is about
+  guaranteeing Notify's own configuration behaves, not about protocol compatibility.
+- **`typescript` `7.0.2`** (from `5.9.3`) — moves off the 5.x line onto the native compiler. Safe here
+  because npm nests `typescript@5.9.3` under `@camera.ui/cli`'s copy of `ts-import`, which still declares
+  `peerDependencies: { typescript: "5" }`; the CLI's `cameraui.config.ts` loader therefore keeps running
+  on TS 5 while the repo's own pin moves to 7. Verified: `cui bundle` still bundles and validates the
+  contract, and `contract.ts`/`cameraui.config.ts` type-check clean under 7.0.2. Two consequences worth
+  knowing: `node_modules` now holds two TypeScript installs, and because TS 7 ships as a native binary
+  the lockfile gains 20 optional `@typescript/typescript-<platform>` packages (only the host's own is
+  installed). Nothing in the build consumes the root pin — there is no `tsconfig.json` and no `tsc` in
+  any script — so it serves ad-hoc type-checking only.
+
+### Fixed
+
+- **`package-lock.json` now records the correct version** — it still said `0.5.3` through the 0.5.4
+  release because the lockfile was last written before that version bump. Harmless (npm does not publish
+  from it) but misleading; regenerated here.
+
+## [0.5.4] - 2026-07-31
+
+### Changed
+
+- **Go SDK pinned to `v1.2.4`** (from `v1.1.18`) — this is the SDK half of camera.ui's standalone-sensor
+  refactor, released 30 minutes before `server-v2.0.23`. The diff rewrites `camera_device.go`, the whole
+  `sensor_*` family, `plugin_contract.go`, `plugin_notifier.go` and `plugin_interfaces.go`, and adds
+  `manager_sensor.go` and `observable.go`. Notify required **no source change**: it declares
+  `provides: []`/`consumes: []`, owns no cameras, and touches none of the camera-bound sensor
+  registration functions the refactor removed. `NotifierInterface`, `Notification` and `NotifierDevice`
+  remain compatible, and the detection-event types used by the diagnostics path still resolve.
+- **Minimum camera.ui raised to `2.0.23`** (from `2.0.15`) — `server-v2.0.23` is the release that landed
+  the new sensor system and, per its own notes, stops honouring plugins built against the old one. Since
+  this version of Notify ships an SDK v1.2.4 binary, a pre-2.0.23 server would be pairing a new plugin
+  wire protocol with a host that predates it. The server enforces this floor through
+  `checkEngineCompatibility` at install time, so affected users simply stay on 0.5.3 instead of
+  installing a build their host can't speak.
+- **`@camera.ui/cli` `~0.0.73`** (from `~0.0.65`) — the CLI now emits one npm package per platform target
+  under `bundle/platforms/` and records them as `optionalDependencies` in the published bundle. npm
+  installs only the entry matching the host's `os`/`cpu`/`libc` and the server executes that binary in
+  place, so nothing depends on an install-time lifecycle script — which npm v12 disables for
+  dependencies by default. `cui publish` publishes each platform package before the root one and keeps
+  the versions in lockstep. The set of published package names is unchanged, so the Trusted Publishing
+  setup in `PUBLISHING.md` still applies as written. Note that `npm run bundle` also writes that block
+  into the repo's own `package.json`; it must not be committed (it would break `npm ci`), see #16 and
+  the new section in `PUBLISHING.md`.
+- **`@camera.ui/sdk` `~1.2.3`** (from `~0.0.22`) — required, not optional: `@camera.ui/cli@0.0.73`
+  itself depends on `@camera.ui/sdk@~1.2.3`. Despite the major-version jump this is a no-op for
+  `contract.ts`; `PluginRole.Hub` (`'hub'`) and `PluginInterface.Notifier` (`'Notifier'`) keep their
+  identifiers and values, and the contract still type-checks and passes `cui bundle`'s validation.
+- **`@types/node` `^26.1.2`**, **`updates` `^17.20.2`** — routine. `cross-env` and `rimraf` were already
+  current.
+- **Transitive Go dependencies refreshed** — `github.com/cameraui/rpc/go` v1.0.7, `klauspost/compress`
+  v1.19.1, `nats-io/nkeys` v0.4.16, `golang.org/x/crypto` v0.54.0, `golang.org/x/sys` v0.47.0.
+
+### Notes
+
+- **`typescript` stays pinned at `5.9.3`** even though 7.0.2 is published. `@camera.ui/cli` loads
+  `cameraui.config.ts` through `ts-import@5.0.0-beta.1`, which declares `peerDependencies:
+  { typescript: "5" }`. 5.9.3 is the newest 5.x, so the existing exact pin is already correct and
+  deliberate; moving to 6 or 7 would break `cui bundle`.
+- Verified end to end: `go build ./src/...`, `go test ./...` (both packages pass), and `npm run bundle`
+  cross-compiling all 8 platform targets with contract validation. `staticcheck` (43 findings) and
+  `golangci-lint` (9 findings) return byte-identical counts before and after the upgrade — all
+  pre-existing, tracked in #14.
+
 ## [0.5.3] - 2026-07-29
 
 ### Changed

package/package.json

@@ -1,7 +1,7 @@
 {
   "displayName": "Notify",
   "name": "@calebcall/camera-ui-notify",
-  "version": "0.5.3",
+  "version": "0.5.5",
   "description": "A fully-local, multi-backend camera.ui notifier plugin: delivers notifications to ntfy, Gotify, or a generic webhook, entirely on your own hardware with no cloud dependency.",
   "author": "calebcall (https://github.com/calebcall/camera-ui-notify)",
   "main": "./main.go",
@@ -25,7 +25,7 @@
     "url": "https://github.com/calebcall/camera-ui-notify/issues"
   },
   "engines": {
-    "camera.ui": ">=2.0.15",
+    "camera.ui": ">=2.0.24",
     "node": ">=22.0.0"
   },
   "homepage": "https://github.com/calebcall/camera-ui-notify/tree/main#readme",
@@ -45,14 +45,17 @@
   "os": [],
   "cpu": [],
   "optionalDependencies": {
-    "@calebcall/camera-ui-notify-darwin-arm64": "0.5.3",
-    "@calebcall/camera-ui-notify-darwin-amd64": "0.5.3",
-    "@calebcall/camera-ui-notify-linux-amd64": "0.5.3",
-    "@calebcall/camera-ui-notify-linux-arm64": "0.5.3",
-    "@calebcall/camera-ui-notify-windows-amd64": "0.5.3",
-    "@calebcall/camera-ui-notify-windows-arm64": "0.5.3",
-    "@calebcall/camera-ui-notify-linux-amd64-musl": "0.5.3",
-    "@calebcall/camera-ui-notify-linux-arm64-musl": "0.5.3"
+    "@calebcall/camera-ui-notify-darwin-arm64": "0.5.5",
+    "@calebcall/camera-ui-notify-darwin-amd64": "0.5.5",
+    "@calebcall/camera-ui-notify-linux-amd64": "0.5.5",
+    "@calebcall/camera-ui-notify-linux-arm64": "0.5.5",
+    "@calebcall/camera-ui-notify-windows-amd64": "0.5.5",
+    "@calebcall/camera-ui-notify-windows-arm64": "0.5.5",
+    "@calebcall/camera-ui-notify-linux-amd64-musl": "0.5.5",
+    "@calebcall/camera-ui-notify-linux-arm64-musl": "0.5.5"
+  },
+  "cameraui": {
+    "protocolLevel": 1
   },
   "files": [
     "bundle.zip",