Skip to main content

trust_tasks_https 0.1.4 copy "trust_tasks_https: ^0.1.4" to clipboard
trust_tasks_https: ^0.1.4 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.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.

0.1.2 — 2026-10-23 #

0.1.1 — 2026-09-21 #

0.1.0 #

Added #

  • Initial release: HttpsClient and a framework-agnostic HttpsServer for the Trust Tasks HTTPS binding (bindings/https/0.2), with a dart:io adapter in package:trust_tasks_https/io.dart.
0
likes
0
points
545
downloads

Documentation

Documentation

Publisher

verified publishertrusttasks.org

Weekly Downloads

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.

Repository (GitHub)
View/report issues

License

unknown (license)

Dependencies

http, trust_tasks

More

Packages that depend on trust_tasks_https