signalk-container-helper 0.2.1 → 0.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/CHANGELOG.md +14 -0
  2. package/README.md +1 -1
  3. package/package.json +6 -6
package/CHANGELOG.md CHANGED
@@ -1,3 +1,17 @@
1
+ # v0.3.0
2
+
3
+ - **Node floor lowered to `>=22`** (was `>=24`) — nothing in the library ever required Node 24: the main entry imports no Node builtins at all, and the only runtime globals it touches (`fetch`, `AbortController`, a plain `setTimeout`-based timeout in `fetchWithTimeout`, `URL`, `globalThis`) predate Node 22 comfortably. There is no `AbortSignal.any()` / `AbortSignal.timeout()`, no `node:sqlite`, and the compiler targets ES2023. The old floor was a policy value that consumers — Signal K plugins, which inherit their host server's Node — had to satisfy for no technical reason. This is a **minor**, not a patch: it widens the supported range and takes nothing away, so Node 24 consumers are unaffected
4
+ - **The floor is now enforced rather than asserted** — CI builds, tests, and lints on a `["22", "24"]` matrix instead of Node 24 alone, and `@types/node` drops to `^22` so the typechecker fails on any Node 24-only API that gets introduced later. Previously the package claimed a floor that nothing verified
5
+
6
+ # v0.2.2
7
+
8
+ Maintenance release — dependency updates only, no changes to the library's public API or runtime behaviour.
9
+
10
+ - **TypeScript 6** — the dev toolchain moves from `^5.5.0` to `^6.0.3`; the emitted declarations and ESM output are unchanged, and the full build, 96-test suite, and lint chain pass under the new compiler
11
+ - **`signalk-container` type source bumped 1.23.2 → 1.25.2** — the contract test that pins this library's type mirror against `signalk-container/types` still passes, so the mirrored `ContainerManagerApi` / `ContainerConfig` / `UpdateServiceApi` surface has not drifted against the newer manager
12
+ - Dev-dependency refresh: `eslint` 10.7.0 → 10.8.0, `typescript-eslint` 8.65.0 → 8.66.0, `globals` 17.7.0 → 17.9.0, `@types/react` 19.2.17 → 19.2.18
13
+ - CI: `actions/checkout` and `actions/setup-node` bumped to v7 in the publish workflow
14
+
1
15
  # v0.2.1
2
16
 
3
17
  Docs-only release.
package/README.md CHANGED
@@ -35,7 +35,7 @@ versioning breaks npm semver ranges):
35
35
  }
36
36
  ```
37
37
 
38
- Requires **Node ≥ 24**. This library is published as an **ES module** (`import`, not
38
+ Requires **Node ≥ 22**. This library is published as an **ES module** (`import`, not
39
39
  `require`); consumers must be ESM too.
40
40
 
41
41
  At **runtime** it works with signalk-container ≥ 1.6.0 — newer manager features
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "signalk-container-helper",
3
- "version": "0.2.1",
3
+ "version": "0.3.0",
4
4
  "description": "Helper library for Signal K plugins that manage containers via the signalk-container plugin",
5
5
  "type": "module",
6
6
  "main": "dist/index.js",
@@ -55,7 +55,7 @@
55
55
  "author": "hoeken",
56
56
  "license": "Apache-2.0",
57
57
  "engines": {
58
- "node": ">=24"
58
+ "node": ">=22"
59
59
  },
60
60
  "peerDependencies": {
61
61
  "react": ">=17"
@@ -66,16 +66,16 @@
66
66
  }
67
67
  },
68
68
  "devDependencies": {
69
- "@types/react": "^19.0.0",
70
- "react": "^19.0.0",
71
69
  "@eslint/js": "^10.0.1",
72
- "@types/node": "^24.0.0",
70
+ "@types/node": "^22.20.1",
71
+ "@types/react": "^19.0.0",
73
72
  "eslint": "^10.2.0",
74
73
  "eslint-config-prettier": "^10.1.8",
75
74
  "globals": "^17.4.0",
76
75
  "prettier": "^3.8.1",
76
+ "react": "^19.0.0",
77
77
  "signalk-container": "^1.23.2",
78
- "typescript": "^5.5.0",
78
+ "typescript": "^6.0.3",
79
79
  "typescript-eslint": "^8.58.0",
80
80
  "vitest": "^4.1.10"
81
81
  }