[dependabot]

Bumps @openvtc/trust-tasks from 0.28.1 to 0.28.8.

Changelog

Sourced from @​openvtc/trust-tasks's changelog.

0.28.19 — 2026-11-06

Added

• vtc/badges: Member badges — community badges backed by groups, awards accepted by the member, kudos, Open Badges credentials (vtc/badges/*/0.1) (#1052)

• feat(vtc/badges): member badges — community badges backed by groups, awards accepted by the member, kudos, Open Badges credentials (vtc/badges/*/0.1)

  A new family for the VTI Community Badges chapter (VTI-BDG-001 – 095): pictures with a name a member earns, holds and shows on their directory card.

  • A community badge is backed by a community group: create creates the group as vtc/groups/create does, its managers are the badge's owners, its members the holders; requests reuse vtc/groups/join and requests/decide, owners reuse managers/add and remove. The shared Group record gains an optional badgeId (additive).
  • An award is an offer until its recipient accepts (awards/offer → mine/accept or mine/decline); mine/accept issues the badge credential as the group's DID first and records the membership after. mine/accept states the credential profile: an Open Badges 3.0 OpenBadgeCredential with the community as the Achievement's creator and endorser, one evidence entry per award; short-lived with no status inside the community, long-lived with a slot in the community's own status set where holders may show it outside.
  • Hidden is portal-only (mine/hide, mine/show): walls, holders/list and counts leave a hidden holder out; awards/list shows owners the hidden mark.
  • Kudos badges (kudos/give, kudos/list): given by any member to any other within per-giver limits, each giving an award of its own; promote turns one into a community badge.
  • settings/show and settings/update hold the community's switches and limits.
  • images/upload and images/get mirror the directory's picture pipeline.

0.28.18 — 2026-11-05

Added

• vtn/registry: Check a party against the network's trust registry through the network, and the registry status for administrators (#1050)

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.

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).

• vta/collection: Settings/show and settings/set — collection by default per trust context, stored and changed at run time (#1049)

Collection by default was one operator setting, off unless enabled (VTI-NTF-093). The VTI specification withdraws that in favour of a setting of each trust context, enabled unless disabled there (VTI-NTF-094 – VTI-NTF-098):

• vta/collection/settings/show/0.1: a party with standing in a context reads

... (truncated)

Commits

• d26ef22 chore: release 11 packages (#1007)
• e60a7ba feat(vtc/rooms/community): archive, unarchive, remove and removal/cancel 0.1;...
• d3b054c chore: release 11 packages (#1003)
• 20d2b0e feat(voting): textReleaseThreshold may be as low as 1, disclosed below 10 (vo...
• 701f44c chore: release @​openvtc/trust-tasks 0.28.6 (#1000)
• 2951e0b ci(ts): an object type that only gains optional members is API-compatible (#995)
• 46c3f3e chore: release 11 packages (#999)
• 2205fb1 feat(vtc/elections/ballot-boxes/list): 0.1 reads the community's trusted ball...
• 66c2351 chore: release 11 packages (#991)
• 888b052 feat(vta/webvh/dids/update): 1.1 lists or removes an existing log's did:scid ...
• Additional commits viewable in compare view