@openvtc/trust-tasks 0.23.9 → 0.24.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.
- package/CHANGELOG.md +26 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,32 @@ The package versions over **its own API** — what a consumer compiles against
|
|
|
11
11
|
not over `SPEC.md`. Below 1.0 a breaking change bumps the leading non-zero
|
|
12
12
|
component.
|
|
13
13
|
|
|
14
|
+
## 0.24.0 — 2026-10-11
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Specifications
|
|
18
|
+
|
|
19
|
+
- **rooms**: An unauthorized room request is refused with the standard permissionDenied (#743)
|
|
20
|
+
|
|
21
|
+
Thirteen rooms specifications (create, epoch/{commits,mint,prune},
|
|
22
|
+
keys/open, keys/present 0.1 and 0.2, owner/{claim,transfer},
|
|
23
|
+
records/{curate,get,list,put} 0.1) declared a task-specific
|
|
24
|
+
`<slug>:notAuthorized` for a failure the framework already names: an
|
|
25
|
+
authorization refusal is the standard `permissionDenied` (SPEC §7.2, §8.3).
|
|
26
|
+
The extended code shadowed it, so a consumer switching on
|
|
27
|
+
`permissionDenied` never matched it, and a party that did not recognise it
|
|
28
|
+
degraded it to `taskFailed` (§8.5), a worse signal than the code it
|
|
29
|
+
duplicated. The later rooms specifications (records/put 0.2 onward) already
|
|
30
|
+
use the standard code, as the reference room host does for every version.
|
|
31
|
+
|
|
32
|
+
Each withdrawn declaration's condition is kept as one sentence at the end of
|
|
33
|
+
the specification's Conformance section, naming `permissionDenied`. Same
|
|
34
|
+
correction as `vta/app-state:permissionDenied` in 0.11.3.
|
|
35
|
+
|
|
36
|
+
Breaking for trust-tasks-rs: the thirteen `error_codes::NOT_AUTHORIZED`
|
|
37
|
+
constants are removed from the generated rooms modules. A consumer emitting
|
|
38
|
+
one should emit `StandardCode::PermissionDenied` instead.
|
|
39
|
+
|
|
14
40
|
## 0.23.9 — 2026-10-10
|
|
15
41
|
|
|
16
42
|
|