@calebcall/camera-ui-notify 0.5.4 → 0.5.6

package/CHANGELOG.md

@@ -5,6 +5,59 @@ 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.6] - 2026-08-01
+
+### Changed
+
+- **`@camera.ui/cli` `~0.0.75`** (from `~0.0.74`) — picks up the fix for the bug this project reported
+  upstream as [cameraui/cli#31](https://github.com/cameraui/cli/issues/31) (tracked here as #16):
+  `cui bundle` was writing an `optionalDependencies` block into the plugin repo's own `package.json` on
+  every run, pinned to a version that does not exist on npm until the release publishes it — so
+  `package-lock.json` could never resolve it and `npm ci` failed, breaking the release workflow at its
+  "Install dependencies" step. 0.0.75 stops touching the repo's `package.json` entirely, which also
+  removes the merge-vs-replace inconsistency and the whole-file reformatting reported alongside it.
+  Verified: `package.json` is byte-identical before and after `npm run bundle`, and the published bundle
+  still carries all 8 platform `optionalDependencies` at the right version.
+- **`PUBLISHING.md`** — replaced the "Never commit the `optionalDependencies` block" workaround with a
+  short explanation of where that block legitimately comes from (`bundle/package.json`, regenerated from
+  the Go targets each run) and why it must not appear in the repo's own `package.json`, noting the CLI
+  versions affected and that 0.0.75 fixes it.
+
+No change to the plugin itself — this release is build tooling and documentation only, and the published
+artifact is functionally identical to 0.5.5. Every other dependency was already current: `@camera.ui/sdk`
+1.2.3, `github.com/cameraui/sdk/go` v1.2.6, `github.com/cameraui/rpc/go` v1.0.7, camera.ui floor 2.0.24.
+
+## [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

package/package.json

@@ -1,7 +1,7 @@
 {
   "displayName": "Notify",
   "name": "@calebcall/camera-ui-notify",
-  "version": "0.5.4",
+  "version": "0.5.6",
   "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.23",
+    "camera.ui": ">=2.0.24",
     "node": ">=22.0.0"
   },
   "homepage": "https://github.com/calebcall/camera-ui-notify/tree/main#readme",
@@ -44,19 +44,19 @@
   },
   "os": [],
   "cpu": [],
-  "optionalDependencies": {
-    "@calebcall/camera-ui-notify-darwin-arm64": "0.5.4",
-    "@calebcall/camera-ui-notify-darwin-amd64": "0.5.4",
-    "@calebcall/camera-ui-notify-linux-amd64": "0.5.4",
-    "@calebcall/camera-ui-notify-linux-arm64": "0.5.4",
-    "@calebcall/camera-ui-notify-windows-amd64": "0.5.4",
-    "@calebcall/camera-ui-notify-windows-arm64": "0.5.4",
-    "@calebcall/camera-ui-notify-linux-amd64-musl": "0.5.4",
-    "@calebcall/camera-ui-notify-linux-arm64-musl": "0.5.4"
-  },
   "cameraui": {
     "protocolLevel": 1
   },
+  "optionalDependencies": {
+    "@calebcall/camera-ui-notify-darwin-arm64": "0.5.6",
+    "@calebcall/camera-ui-notify-darwin-amd64": "0.5.6",
+    "@calebcall/camera-ui-notify-linux-amd64": "0.5.6",
+    "@calebcall/camera-ui-notify-linux-arm64": "0.5.6",
+    "@calebcall/camera-ui-notify-windows-amd64": "0.5.6",
+    "@calebcall/camera-ui-notify-windows-arm64": "0.5.6",
+    "@calebcall/camera-ui-notify-linux-amd64-musl": "0.5.6",
+    "@calebcall/camera-ui-notify-linux-arm64-musl": "0.5.6"
+  },
   "files": [
     "bundle.zip",
     "CHANGELOG.md"