@theokit/gateway-matrix 0.2.0 → 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 (2) hide show
  1. package/CHANGELOG.md +43 -0
  2. package/package.json +4 -3
package/CHANGELOG.md CHANGED
@@ -1,5 +1,48 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.3.0
4
+
5
+ ### Minor Changes
6
+
7
+ - a2fb95e: Widen the platform SDK peer ranges, each major verified against the real platform.
8
+
9
+ `gateway-matrix` accepts `matrix-js-sdk ^32.0.0 || ^42.0.0`, and `gateway-line` accepts
10
+ `@line/bot-sdk ^9.0.0 || ^11.0.0`.
11
+
12
+ For Matrix this is a security fix for consumers rather than a convenience. The old `^32.0.0`
13
+ floor could not reach any version carrying the five advisories' fixes — including a HIGH, where
14
+ key history sharing could share keys to malicious devices, fixed in `>=34.8.0`. A consumer could
15
+ not patch it alone: raising their own dependency put them outside the range this package
16
+ declared.
17
+
18
+ Both majors of both ranges were exercised against the real platform, not only typechecked. The
19
+ Matrix live contracts pass 7/7 against a Synapse homeserver at 32.4.0 and at 42.2.0, with
20
+ per-test timings within 5ms of each other; the LINE live contracts pass 6/6 against the real
21
+ LINE API at 9.9.0 and at 11.2.0.
22
+
23
+ Each package now declares the SDK as an explicit devDependency. Until now neither did, so what
24
+ their suite ran against was whatever pnpm's peer auto-install happened to pick — the test target
25
+ was an accident rather than a decision.
26
+
27
+ ## 0.2.1
28
+
29
+ ### Patch Changes
30
+
31
+ - 1e215ab: The peer floor on `@theokit/gateway` is `>=0.9.0`, which is what these packages have needed since
32
+ they gained `deliver`.
33
+
34
+ `deliver` and `runHandler` arrived in the core at 0.9.0, and the previous release shipped these
35
+ adapters still declaring `>=0.6.0` — a floor `dep-check` had already proven false by building the
36
+ workspace against it: TS4113 on the override, TS2551 on `runHandler`, in all ten packages.
37
+
38
+ It could not be corrected in that release. `dep-check`'s install check packs an adapter and installs
39
+ it the way a consumer would, and until 0.9.0 was on npm no consumer could resolve a package asking
40
+ for it — the check was right about the world as it stood. The floor is raised here, against a
41
+ registry where the version it names exists.
42
+
43
+ Between the two releases a consumer installing against an older core got a build error rather than a
44
+ resolution error: the same failure, later and less clearly. That window is closed.
45
+
3
46
  ## 0.2.0
4
47
 
5
48
  ### Minor Changes
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@theokit/gateway-matrix",
3
- "version": "0.2.0",
3
+ "version": "0.3.0",
4
4
  "description": "Matrix protocol platform adapter for @theokit/gateway. ADRs D413-D421.",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -35,8 +35,8 @@
35
35
  "CHANGELOG.md"
36
36
  ],
37
37
  "peerDependencies": {
38
- "@theokit/gateway": ">=0.6.0 <1.0.0",
39
- "matrix-js-sdk": "^32.0.0"
38
+ "@theokit/gateway": ">=0.9.0 <1.0.0",
39
+ "matrix-js-sdk": "^32.0.0 || ^42.0.0"
40
40
  },
41
41
  "peerDependenciesMeta": {
42
42
  "matrix-js-sdk": {
@@ -47,6 +47,7 @@
47
47
  "@stryker-mutator/core": "10",
48
48
  "@stryker-mutator/vitest-runner": "10",
49
49
  "@theokit/sdk": "^4.62.0",
50
+ "matrix-js-sdk": "^42.2.0",
50
51
  "tsup": "^8.5.0",
51
52
  "typescript": "5.9.3",
52
53
  "vitest": "^4.1.11",