@openvtc/trust-tasks 0.28.16 → 0.28.18
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 +43 -0
- package/dist/_shared/components.d.ts +26 -1
- package/dist/_shared/components.d.ts.map +1 -1
- package/dist/index.d.ts +15 -0
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +15 -0
- package/dist/index.js.map +1 -1
- package/dist/vta/collection/_shared/0.1/collection.d.ts +2 -2
- package/dist/vta/collection/_shared/0.1/collection.d.ts.map +1 -1
- package/dist/vta/collection/list/0.1/payload.d.ts +4 -4
- package/dist/vta/collection/list/0.1/payload.js +2 -2
- package/dist/vta/collection/list/0.1/payload.js.map +1 -1
- package/dist/vta/collection/settings/set/0.1/payload.d.ts +469 -0
- package/dist/vta/collection/settings/set/0.1/payload.d.ts.map +1 -0
- package/dist/vta/collection/settings/set/0.1/payload.js +275 -0
- package/dist/vta/collection/settings/set/0.1/payload.js.map +1 -0
- package/dist/vta/collection/settings/show/0.1/payload.d.ts +437 -0
- package/dist/vta/collection/settings/show/0.1/payload.d.ts.map +1 -0
- package/dist/vta/collection/settings/show/0.1/payload.js +260 -0
- package/dist/vta/collection/settings/show/0.1/payload.js.map +1 -0
- package/dist/vtc/networks/preview/0.1/payload.d.ts +696 -0
- package/dist/vtc/networks/preview/0.1/payload.d.ts.map +1 -0
- package/dist/vtc/networks/preview/0.1/payload.js +376 -0
- package/dist/vtc/networks/preview/0.1/payload.js.map +1 -0
- package/dist/vtn/registry/check/0.1/payload.d.ts +528 -0
- package/dist/vtn/registry/check/0.1/payload.d.ts.map +1 -0
- package/dist/vtn/registry/check/0.1/payload.js +282 -0
- package/dist/vtn/registry/check/0.1/payload.js.map +1 -0
- package/dist/vtn/registry/status/0.1/payload.d.ts +736 -0
- package/dist/vtn/registry/status/0.1/payload.d.ts.map +1 -0
- package/dist/vtn/registry/status/0.1/payload.js +421 -0
- package/dist/vtn/registry/status/0.1/payload.js.map +1 -0
- package/package.json +1 -1
- package/src/_shared/components.ts +26 -1
- package/src/index.ts +15 -0
- package/src/vta/collection/_shared/0.1/collection.ts +2 -2
- package/src/vta/collection/list/0.1/payload.ts +2 -2
- package/src/vta/collection/settings/set/0.1/payload.ts +319 -0
- package/src/vta/collection/settings/show/0.1/payload.ts +296 -0
- package/src/vtc/networks/preview/0.1/payload.ts +483 -0
- package/src/vtn/registry/check/0.1/payload.ts +365 -0
- package/src/vtn/registry/status/0.1/payload.ts +502 -0
package/CHANGELOG.md
CHANGED
|
@@ -11,6 +11,49 @@ 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.28.18 — 2026-11-05
|
|
15
|
+
|
|
16
|
+
|
|
17
|
+
### Added
|
|
18
|
+
|
|
19
|
+
- **vtn/registry**: Check a party against the network's trust registry through the network, and the registry status for administrators (#1050)
|
|
20
|
+
|
|
21
|
+
vtn/registry/check/0.1 lets anyone ask a network to ask its trust registry whether a party is published as its member, returning the registry's own signed answer verbatim, so a verifier with no DIDComm or TSP session (a browser, or a registry that serves no HTTPS) can still check the registry rather than take the network's word for it. Unreachable is indeterminate, never not a member.
|
|
22
|
+
|
|
23
|
+
vtn/registry/status/0.1 lets an administrator read the registry, the writer and whether it is connected, the last reconcile, and every record compared with what the entries project (ok, missing, stale, wrong).
|
|
24
|
+
|
|
25
|
+
- **vta/collection**: Settings/show and settings/set — collection by default per trust context, stored and changed at run time (#1049)
|
|
26
|
+
|
|
27
|
+
Collection by default was one operator setting, off unless enabled
|
|
28
|
+
(VTI-NTF-093). The VTI specification withdraws that in favour of a setting of
|
|
29
|
+
each trust context, enabled unless disabled there (VTI-NTF-094 – VTI-NTF-098):
|
|
30
|
+
|
|
31
|
+
- vta/collection/settings/show/0.1: a party with standing in a context reads
|
|
32
|
+
its setting, who last changed it and when, and whether the VTA's operator
|
|
33
|
+
has suspended collection by default everywhere (VTI-NTF-096).
|
|
34
|
+
- vta/collection/settings/set/0.1: a party with administrative authority over
|
|
35
|
+
the context (VTI-ACL-022) enables or disables it; stored, audited, applied
|
|
36
|
+
before the answer — disabling closes the VTA's connections first
|
|
37
|
+
(VTI-NTF-095). Answers the setting and whether it changed.
|
|
38
|
+
- _shared/0.1 gains a CollectionSetting definition (new $defs entry), and the
|
|
39
|
+
`disabled` reason is re-described: the context's own setting, or the
|
|
40
|
+
operator's suspension (VTI-NTF-097, VTI-NTF-098). No enum value changes.
|
|
41
|
+
- claim/list/release 0.1 prose and an error-code meaning now cite the
|
|
42
|
+
per-context setting instead of VTI-NTF-093 (description edits only).
|
|
43
|
+
|
|
44
|
+
The setting is not folded into list's response: it belongs to the context,
|
|
45
|
+
not an identifier, and an added member in that released response would be
|
|
46
|
+
refused by every existing client's additionalProperties: false.
|
|
47
|
+
|
|
48
|
+
Bindings regenerated (Rust, TS, Go, Dart).
|
|
49
|
+
|
|
50
|
+
## 0.28.17 — 2026-11-05
|
|
51
|
+
|
|
52
|
+
|
|
53
|
+
### Added
|
|
54
|
+
|
|
55
|
+
- **vtc/networks/preview**: Read a network before joining it — its profile, required roles, and whether it lists the community (#1047)
|
|
56
|
+
|
|
14
57
|
## 0.28.16 — 2026-11-05
|
|
15
58
|
|
|
16
59
|
|
|
@@ -1110,7 +1110,7 @@ export type NamespaceId = string;
|
|
|
1110
1110
|
*/
|
|
1111
1111
|
export type NodeKind = "network" | "community";
|
|
1112
1112
|
/**
|
|
1113
|
-
* Why nobody collects for an identifier the VTA would otherwise collect for: `limit`, the VTA is at the bound it states on the number of identifiers it collects for (VTI-NTF-088); `conflict`, another connection for the identifier kept closing the VTA's, and the VTA stopped after the bound it states until the conflict is resolved (VTI-NTF-085). `disabled`, the VTA's operator has
|
|
1113
|
+
* Why nobody collects for an identifier the VTA would otherwise collect for: `limit`, the VTA is at the bound it states on the number of identifiers it collects for (VTI-NTF-088); `conflict`, another connection for the identifier kept closing the VTA's, and the VTA stopped after the bound it states until the conflict is resolved (VTI-NTF-085). `disabled`, collection by default is disabled for the identifier's trust context — by the context's own setting, or because the VTA's operator has suspended it for every context — so the VTA collects for no identifier there that a client has not claimed (VTI-NTF-097, VTI-NTF-098); vta/collection/settings/show says which.
|
|
1114
1114
|
*/
|
|
1115
1115
|
export type NotCollectedReason = "limit" | "conflict" | "disabled";
|
|
1116
1116
|
/**
|
|
@@ -6324,6 +6324,31 @@ export interface CollectionEntry {
|
|
|
6324
6324
|
claim?: Claim;
|
|
6325
6325
|
notCollectedReason?: NotCollectedReason;
|
|
6326
6326
|
}
|
|
6327
|
+
/**
|
|
6328
|
+
* Whether the VTA collects by default for the identifiers of one trust context that no client has claimed (VTI-NTF-094 – VTI-NTF-098), and who last changed that. The VTA collects for them exactly when `collectByDefault` is true and `suspendedByOperator` is false. `changedBy` and `changedAt` are present together, and both absent while the setting has never been changed.
|
|
6329
|
+
*/
|
|
6330
|
+
export interface CollectionSetting {
|
|
6331
|
+
/**
|
|
6332
|
+
* The trust context the setting belongs to. It applies to that context's identifiers alone, not to its ancestors' or descendants' (VTI-NTF-094).
|
|
6333
|
+
*/
|
|
6334
|
+
contextId: ContextId_VtaCollectionV0_1;
|
|
6335
|
+
/**
|
|
6336
|
+
* The context's own setting: true unless a party with administrative authority over the context has disabled it (VTI-NTF-094, VTI-NTF-095). The VTA keeps it across restarts.
|
|
6337
|
+
*/
|
|
6338
|
+
collectByDefault: boolean;
|
|
6339
|
+
/**
|
|
6340
|
+
* Whether the VTA's operator has suspended collection by default for every context (VTI-NTF-098). While true, the VTA collects for no unclaimed identifier here whatever `collectByDefault` says, and does not change it; once lifted, `collectByDefault` applies again. Always false at a VTA that offers its operator no suspension.
|
|
6341
|
+
*/
|
|
6342
|
+
suspendedByOperator: boolean;
|
|
6343
|
+
/**
|
|
6344
|
+
* The subject of the access control entry that last changed `collectByDefault` (VTI-NTF-096).
|
|
6345
|
+
*/
|
|
6346
|
+
changedBy?: Did_NotificationsV0_1;
|
|
6347
|
+
/**
|
|
6348
|
+
* When `collectByDefault` was last changed.
|
|
6349
|
+
*/
|
|
6350
|
+
changedAt?: string;
|
|
6351
|
+
}
|
|
6327
6352
|
/**
|
|
6328
6353
|
* OPTIONAL. How the community asks to be shown to a prospective applicant: a name, an accent colour and a logo. Presentation only, self-asserted and unverified — `communityDid` identifies the community, never `branding`. Not part of any criterion, so not covered by a `requirementsDigest`. Every member is optional.
|
|
6329
6354
|
*/
|