trust_tasks_https 0.1.9
trust_tasks_https: ^0.1.9 copied to clipboard
The Trust Tasks HTTPS transport binding for Dart: a typed client and a framework-agnostic server running the SPEC section 7.2 pipeline per request.
Changelog — trust_tasks_https #
All notable changes to the Dart HTTPS binding package.
The format follows Keep a Changelog. The package versions over its own API — what a consumer compiles against. Below 1.0 a breaking change bumps the leading non-zero component.
Publishing is triggered by the trust-tasks-dart-https-v<version> tag, because
pub.dev only accepts an automated publish from a tag-triggered workflow. See
RELEASING.md.
0.1.9 — 2026-11-10 #
Added #
- acl: Purpose of use on grants and on memory reads (AclEntry 0.3; vta/memory put/delete/list 0.3, get 0.2) (#1074)
-
feat(acl): purpose of use on grants and on memory reads (AclEntry 0.3; vta/memory put/delete/list 0.3, get 0.2)
An access-control entry says who may do what, where and until when, but not what for. An agent granted a read of its principal's memory can use the content for anything, and nothing records the use it intended. The VTI specification now requires the purpose (VTI-ACL-100 – 110, trustoverip/dtgwg-vti-spec#115); these are the wire shapes.
acl/_shared/0.3 — AclEntry 0.3 adds one REQUIRED axis,
purposes:{"scope": "any"}or{"scope": "listed", "purposes": [...]}with at least onePurpose— a lowerCamelCase name registered in the VTI purpose registry (personalisation, taskExecution, analytics, modelTraining) or an absolute IRI such as a DPV purpose.anynever grantsmodelTraining. Delegated purposes are a subset of the granter's. CONVENTIONS.md §8a maps a 0.2 entry onto 0.3 (any, the authority it already held, now stated) and §12 states the rules.acl tasks on AclEntry 0.3: grant/0.3, update/0.3, show/0.3, revoke/0.3, change-role/0.3, list/0.4. New errors on grant and update:
purposeOutsideDelegator(purposes wider than the granter's) andpurposeRefused(policy will not grant a purpose, refused by name, never dropped). update/0.3 replacespurposeswholesale; narrowing it is an audited privilege reduction.purposesis never redacted by show or list. Noextends: a REQUIRED member on the entry cannot be added to a version a 0.2 consumer still reads.vta/memory put/0.3, delete/0.3, list/0.3, get/0.2 (each
extendsits predecessor) add an optionalpurpose(MemoryPurpose, new in vta/_shared/0.1/memory-record, a reference to acl'sPurpose) and apurposeNotGrantederror that discloses nothing and is distinct fromcontextForbidden. A recall, and a listing with values, is purpose-bound: refused for a purpose the entry does not grant, or for none under an entry listing several, and audited with its purpose either way. A write is not purpose-bound, but a conflict that returnscurrentValueis: the value is withheld unless the request's purpose is granted.Data rooms (a room authority credential's
purposes, VTI-ACL-110) are a follow-up.Samples in other specs that named the superseded acl versions now name the new ones, with
purposeson every embedded entry; prose links were moved bynpm run fix-stale-references.
0.1.8 — 2026-11-04 #
Added #
- trust-task-discovery: Publish 0.4, a responder advertises the horizon up to which it honours a stated expiresAt (#1030)
SPEC §7.2 (Bounding the record) applies a consumer's maximum age only where a document states no expiresAt, and since trust-tasks-rs 0.37 (#1021) validate_freshness does so, honouring a stated expiry up to the policy's expiry_horizon. discovery 0.3 cannot describe that: its window "governs issuedAt only" and its responder refuses any document past issuedAt + maxAgeSeconds + clockSkewSeconds, whatever expiresAt it states. A responder that honours an expiry could only advertise a narrower window than it applies, and a producer could not learn that stating an expiry keeps a long delivery acceptable.
- specs/trust-task-discovery/0.4: acceptanceWindow gains an optional
expiryHorizonSeconds (whole seconds, at least 1), and the spec defines a
document's acceptance end: issuedAt + maxAgeSeconds without an expiresAt;
the earlier of expiresAt and issuedAt + expiryHorizonSeconds with one; and,
where the window carries no horizon, the earlier of expiresAt and
issuedAt + maxAgeSeconds, which is what a 0.3 window says.
- Responder: MUST NOT advertise a horizon wider than it applies, nor one at all if it applies its maximum age whatever expiresAt states.
- Discoverer: send bounds follow the acceptance end. MAY state an expiresAt within the horizon, no later than it will pursue delivery, instead of issuing a chain of new attempts; a new attempt carries it unchanged. Absent a horizon, it MUST assume the maximum age applies to every document.
- AcceptanceWindow is closed in 0.3, so an added optional member is a MINOR increment (§5.2): a new version, not an edit.
- Response-side invalid examples: a zero horizon, a duration string, and a fractional entry-level horizon.
- trust-tasks-rs: DiscoveryRegistry::respond_to_v0_4 is the current answer. acceptance_window_from reads the policy's expiry_horizon, and expiry_horizon() sets one by hand. respond_to_v0_3 moves to discovery/superseded.rs and states the window without the horizon (narrower than applied, which 0.3 permits).
- trust-tasks-https: enable_discovery answers 0.4, and 0.3 beside 0.2 and 0.1.
- trust-tasks-dart-https: enableDiscovery answers 0.4. Dart's FreshnessPolicy has no horizon, so its window states none, which says the maximum age applies to every document. 0.3 moves to the superseded block.
- Examples and tests that named the 0.3 types use 0.4.
- Bindings regenerated (Rust, TS, Go, Dart). 0.3 is superseded.
Follows from #1021 and trustoverip/dtgwg-vti-spec#96 (VTI-OPS-024, VTI-OPS-028, VTI-TRN-048), whose implementation in OpenVTC/verifiable-trust-infrastructure states delivery deadlines as expiresAt.
0.1.7 — 2026-10-27 #
Added #
- ts, go: Trust-task-error/0.6 and the unsupportedExtension and indeterminate standard codes (#961)
-
feat(ts)!: trust-task-error/0.6 and the unsupportedExtension and indeterminate standard codes
Framework 0.7.0 added unsupportedExtension to the standard codes, and the indeterminate ruling (SPEC §8.3) adds indeterminate: the recipient could not decide because something it needed and does not control could not be obtained or checked, which is neither a refusal nor a failed verification. Both live in the closed code list of the trust-task-error payload schema, so they need a new version.
- specs/trust-task-error/0.6: both codes appended to the enum, and extends: "0.5", which the build checks. References to 0.5 across the registry therefore stay current, and no other spec changes.
- All four libraries recognize both codes and emit 0.6: trust_task_error_type_uri(), TRUST_TASK_ERROR_TYPE_URI, TrustTaskErrorTypeURI and trustTaskErrorTypeUri move together. Rust's StandardCode is hand-written (trust-task-error is in SKIP_SLUGS) and gains UnsupportedExtension and Indeterminate, with indeterminate retryable by default as §8.3 gives it.
- The HTTPS binding's status table maps unsupportedExtension to 422 and indeterminate to 503, in the binding prose, trust-tasks-https and trust_tasks_https. The Dart package spells the new codes out so it still builds against a core that predates them.
Breaking for @openvtc/trust-tasks only: StandardCode is a closed union there, so an exhaustive switch over it stops compiling. Rust's StandardCode is #[non_exhaustive] and Go's and Dart's are open string types, so the change is additive for them.
Part of trustoverip/dtgwg-trust-tasks-spec#42.
0.1.6 — 2026-10-27 #
Added #
- The prebuilt specification modules are deprecated in all four libraries; generate the tasks you use (#954)
Milestone 5 of docs/design/consumer-side-generation.md. Every prebuilt module outside the framework's own specifications (trust-task-, trust-ceremony-, _framework/) is deprecated, so that an application is told to pin the tasks it uses with the trust-tasks CLI and generate them instead. Nothing is removed: the withdrawal batch that removes them is chosen later, at least 90 days after this ships.
Each library marks the prebuilt entry point where its toolchain reports a deprecation, never the module body, which is also what the consumer-side generators emit:
- Rust: #[deprecated] on each gated family module in trust-tasks-rs's specs/mod.rs (trust-tasks-codegen). It reaches every path and item under the module; framework modules and trust-tasks-build's output are unmarked.
- TypeScript: the root index re-exports each module as
import * as _X …; /** @deprecated … */ export import X = _X;, because TypeScript ignores @deprecated onexport * as. API compatibility against 0.27.8: nothing removed or changed. A deep import of a module file is not marked; TypeScript has no module-level deprecation. - Go: a
Deprecated:paragraph in each prebuilt package's doc, which gopls and staticcheck (SA1019) report on import. - Dart: @Deprecated on each prebuilt library's
librarydirective, which the analyzer reports on import from another package. This package's own tests use them, so analysis_options ignores the same-package diagnostic SDKs before 3.4 report.
The TS, Go and Dart equivalence tests mask exactly the mark; every consumer generator is still held to the prebuilt tree as before. Hand-written Rust that uses prebuilt modules on purpose — the acl-specimen test modules, the integration tests and the examples — carries #[allow(deprecated)]; none of the runtime does.
GETTING-STARTED, the four library READMEs, the design doc and CLAUDE.md say so, and point at each language's generator.
0.1.5 — 2026-10-26 #
0.1.4 — 2026-10-26 #
Added #
- codegen: Superseded and retired spec versions are deprecated in every library, and withdrawn ones leave them in a quarterly batch (#921)
-
feat(go): mark superseded and retired spec versions deprecated, and omit withdrawn ones
Every generated request package now exports
const Deprecation(empty for a current version, otherwise "superseded by
0.1.3 — 2026-10-23 #
Fixed #
- dart: The sibling packages require the current trust_tasks core (#895)
Every published sibling (trust_tasks_https, _proof, _didcomm, and the
unreleased _tsp and _capability_client) declared trust_tasks: ^0.1.0,
which pub reads as >=0.1.0 <0.2.0. A consumer therefore got core 0.1.19,
missing every fix since, and an app already on trust_tasks 0.9.x could not
add a sibling at all: the constraints conflict. tag-dart's release check
did not notice, because it verifies against the newest published core the
constraint admits. The floor is now ^0.9.3.
That core releases the replay claim itself when a handler throws (#876), so the HTTPS server and the DIDComm and TSP consumers no longer release it a second time. Their release also fired when the guard failed to record a response after the handler had run, freeing a document whose effect had already happened; the core keeps the claim in that case, and so do they now.
They also pass responseToJson (#878), so a persistent ReplayGuard caches
the success response as JSON and a resend is answered with it.