Skip to content

Releases

v0.53.0

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 15 Nov 06:54
f6ed815

Changed — the vta feature is back

  • affinidi-messaging-mediator depends on vta-sdk 0.90 again,
    released on the same line as this workspace (affinidi-messaging-sdk 0.47 /
    affinidi-tdk 0.45 / trust-tasks 0.39 / affinidi-crypto 0.3), so every
    affinidi-* and trust-tasks-* crate still resolves once.
  • vta (VTA-backed key management: operating secrets fetched from a
    Verifiable Trust Agent at boot, periodic refresh, mediator rotate-admin) is
    back in the mediator's default features, and enabling it no longer stops
    the build. Library consumers can still turn it off with
    default-features = false; self-hosted mediators never used it.
  • mediator-setup's vta feature is now real and on by default: the VTA step
    offers full setup, admin-only and offline export again, the deployment
    defaults pick a VTA-managed setup again, and --setup-key-out,
    --setup-key-file, use_vta = true recipes (sealed-mint, sealed-export,
    --bundle) and did_method = "vta" run instead of exiting 5. A self-hosted
    did:webvh document is rendered by vta-sdk's didcomm-mediator template
    again. A wizard built with --no-default-features and without vta keeps
    the previous release's behaviour (only "No VTA", VTA paths refused with exit
    5).
  • The build commands the wizard renders (Dockerfile, cargo install,
    cargo build) list the mediator's vta feature again.
  • The container image includes VTA integration again: the mediator's default
    features (with vta) and mediator-setup with its vta flows. A
    VTA-linked deployment that stayed on an earlier image can move to this one.

v0.53.0-rc.0

v0.53.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 15 Nov 06:16
25ba747

What's Changed

  • chore: bootstrap the mediator workspace at 0.42.0 by @stormer78 in #1
  • ci(publish): publish crates from the release environment by @stormer78 in #3
  • chore(release): cut release/0.42; main moves to 0.43.0 by @stormer78 in #2
  • fix(deps): rustls 0.23.46 for RUSTSEC-2026-0346 and -0347 by @stormer78 in #6
  • docs(release): 0.42.0 is GA by @stormer78 in #8
  • fix(release): cut-release.py prunes its worktrees after removing them by @stormer78 in #9
  • fix(store): close Fjall crash and race gaps in forwarding, expiry and sessions by @stormer78 in #11
  • fix(forwarding): live-notify the abandonment problem report by @stormer78 in #13
  • fix(mediator): publish live notification after the message is stored by @marat-affinidi in #10
  • fix(monitor): report a live delivery only once it is queued to the socket by @stormer78 in #14
  • chore(deps): affinidi-messaging-sdk 0.36.2 by @stormer78 in #15
  • fix(mediator): REST bodies over 2 MiB, and silent raw-TSP refusals by @stormer78 in #16
  • fix(mediator): a TSP-only build compiles and serves TSP clients by @stormer78 in #17
  • chore(deps)!: trust-tasks-rs 0.32, affinidi-messaging-sdk 0.37 by @stormer78 in #18
  • chore(release): cut release/0.43; main moves to 0.44.0 by @stormer78 in #19
  • ci(image): add swap on the image build runners by @stormer78 in #21
  • chore(deps): vta-sdk 0.72 — one trust-tasks-rs, affinidi-messaging-sdk and affinidi-tdk in the graph by @stormer78 in #23
  • chore(deps)!: trust-tasks-rs 0.33, affinidi-messaging-sdk 0.38 by @stormer78 in #25
  • chore(release): cut release/0.44; main moves to 0.45.0 by @stormer78 in #26
  • feat(mediator): did:scid accounts and a did:scid mediator identity by @stormer78 in #28
  • feat(mediator): did:scid version floors survive a restart (VTI-KEY-162) by @stormer78 in #29
  • chore(deps)!: TSP 1.0 — affinidi-tsp 0.3, affinidi-messaging-sdk 0.39 by @stormer78 in #30
  • chore(deps)!: trust-tasks-rs 0.34, affinidi-messaging-sdk 0.40 by @stormer78 in #32
  • chore(release): cut release/0.45; main moves to 0.46.0 by @stormer78 in #33
  • ci(release): tag, prep and backport with the release-bot app, not GITHUB_TOKEN by @stormer78 in #35
  • ci(release): the release-bot's tag triggers the image build; stop dispatching it too by @stormer78 in #36
  • chore(deps)!: trust-tasks-rs 0.35, affinidi-messaging-sdk 0.41 by @stormer78 in #37
  • feat!: serve the 0.2 Trust Tasks beside 0.1, with the task types generated at build time by @stormer78 in #40
  • chore(release): cut release/0.46; main moves to 0.47.0 by @stormer78 in #41
  • chore(deps)!: affinidi-messaging-sdk 0.43, so the admin console speaks the 0.2 tasks by @stormer78 in #42
  • fix(mediator): a relay leaves a remote recipient's access list to its own mediator by @marat-affinidi in #31
  • chore(release): cut release/0.47; main moves to 0.48.0 by @stormer78 in #43
  • chore(deps)!: trust-tasks-rs 0.36, affinidi-messaging-sdk 0.44, monitor/event 0.2 by @stormer78 in #46
  • chore(release): cut release/0.48; main moves to 0.49.0 by @stormer78 in #47
  • fix(mediator): honour X-Forwarded-For from trusted proxies for per-IP rate limiting by @yaroslava-kurash in #45
  • chore(deps)!: latest dependencies for 0.49 (vta-sdk 0.77, kube 5, aws-config 1.13) and a docs consistency pass by @stormer78 in #50
  • chore(release): cut release/0.49; main moves to 0.50.0 by @stormer78 in #51
  • docs(releases): 0.49 is GA; 0.48 is N-1 and 0.47 reaches end of life by @stormer78 in #53
  • chore(deps)!: trust-tasks-rs 0.37, affinidi-messaging-sdk 0.45; replay record to record_expiry by @stormer78 in #55
  • chore(release): cut release/0.50; main moves to 0.51.0 by @stormer78 in #56
  • docs(releases): 0.50 is GA; 0.49 is N-1 and 0.48 reaches end of life by @stormer78 in #58
  • fix(config): ship the send-queue limits the template documents by @yaroslava-kurash in #54
  • fix(mediator): refuse a self-managed queue limit of -1 by @yaroslava-kurash in #61
  • feat(mediator): resolve did:webs by @stormer78 in #62
  • feat(mux): one connection carries many DIDs (DID multiplexing) by @stormer78 in #63
  • chore(release): cut release/0.51; main moves to 0.52.0 by @stormer78 in #64
  • fix(mux): muxNonce is 32 random bytes as base64url, as the spec requires by @stormer78 in #66
  • docs(releases): 0.51 is GA; 0.50 is N-1 and 0.49 reaches end of life by @stormer78 in #67
  • fix(mux): REST delete accepts a mux member's messages by @stormer78 in #68
  • fix(mux): carry a newly stored grant on its principal's live connection by @stormer78 in #69
  • test(mux): drive DID multiplexing end to end through the SDK mux client by @stormer78 in #70
  • feat(mux): durable notices for suspended, revoked and present grants by @stormer78 in #71
  • feat(mux): unknown-key rule on direct authentication by key relationship; grantsExpiring by @stormer78 in #72
  • test(mux): consume durable notices through the SDK notice stream by @stormer78 in #73
  • fix(mux): unknown-key rule fails closed on direct authentication by @stormer78 in #74
  • feat(mux): apply grant changes across mediator instances via pub/sub by @stormer78 in #75
  • feat(mux): honour the send scope on the inbound path by @stormer78 in #76
  • feat(mux): per-member fair queuing on mux sockets by @stormer78 in #77
  • feat(mux): didcomm-mux subprotocol; report connectionFull; attachedNow; bounded login check by @stormer78 in #78
  • feat(mux): audit revocations, revoke-all and unknown-key suspensions by @stormer78 in #79
  • feat(mux): tsp-mux subprotocol for DID multiplexing on raw-TSP sockets by @stormer78 in #80
  • test(mux): drive tsp-mux through the SDK client (affinidi-messaging-sdk 0.45.4) by @stormer78 in #82
  • fix(mux): send a resync status only for members holding pickup by @stormer78 in #81
  • fix(store): count fetched messages in the global sent stats on Redis by @stormer78 in #83
  • feat: Implement Redis cluster mode support and related fixes by @oleksiipiliugin in #59
  • fix(mux): attached events for attaches and narrowed grants; affinidi-messaging-sdk 0.45.5 by @stormer78 in #84
  • fix(streaming): report delivered once the websocke...
Read more

v0.52.0

Choose a tag to compare

@stormer78 stormer78 released this 14 Nov 23:14
7d40f0c

The full notes for this release are longer than a GitHub Release allows; they are in CHANGELOG.md. Read the Breaking entries before upgrading.

Highlights: affinidi-messaging-sdk 0.47 / affinidi-tdk 0.45 / trust-tasks 0.39 / affinidi-crypto 0.3. The vta feature is unavailable in this release (vta-sdk returns once it is published on the new line); images from this release have no VTA integration.

Entries

  • Breaking — a forward is delivered only to a next hop that has an account
  • Breaking — affinidi-messaging-mediator-common API
  • Breaking — the console reads typed refusals; ConsoleError::Refused gains current_epoch (sdk 0.46.3)
  • Breaking — test mediator keeps private keys on their own side of the boundary
  • Breaking — dropping a TestMediatorHandle stops the mediator
  • Breaking — purge returns a report; one purge algorithm on every backend
  • Breaking — a session that no longer exists is answered 401
  • Breaking — A store failure is an error, never a success carrying it
  • Breaking — Deliveries are recorded once the reply is written
  • Breaking — Trust-ping answers with ping-response
  • Breaking — Forward edge cases are refused, not guessed at
  • Breaking — Message Pickup status and live delivery tell the truth
  • Breaking — configuration values are checked strictly; a config that booted on silent defaults now fails
  • Breaking — file:// and vault:// secret-backend URLs are checked strictly
  • Breaking — the encrypted file:// store writes format version 2
  • Breaking — mediator-setup: --non-interactive needs --did-method, and no longer defaults to a VTA DID it cannot mint
  • Breaking — mediator-setup: a plaintext file:// secret store outside a local deployment needs an explicit opt-in
  • Breaking — mediator-setup: production deployments default to a closed network
  • Breaking — mediator-setup: the admin choice is honoured in VTA flows
  • Breaking — mediator-setup: re-running into a provisioned backend is refused whatever the config path
  • Breaking — console engine: connection state, monitor feed drops, pinned purges (R3.6)
  • Breaking — one error-code scheme: Trust Task refusals carry Trust Task codes, overloaded numbers split
  • Breaking — mediator-common drops its duplicate DatabaseConfigRaw and parse_cluster_mode
  • Breaking — mediator-admin: a typed transport error, timeouts, and ConsoleError is #[non_exhaustive]
  • Breaking — mediator-tui: the console keeps the typed answers
  • Breaking — MediatorStore is split into capability traits, with no silent defaults
  • Breaking — a trust-ping asking for no response is a success, not a 500
  • Breaking — wake fields on ProcessorsConfig, ProcessorsConfigRaw and SharedData; two AuxiliaryStore methods
  • Breaking — the mediator's vta feature is no longer a default, and cannot be enabled in this release (R3.6)
  • Breaking — the setup wizard's VTA flows are unavailable in this release
  • Breaking — images built from this release have no VTA integration
  • Breaking — affinidi-messaging-sdk 0.47, affinidi-tdk 0.45, trust-tasks-rs 0.39, affinidi-crypto 0.3 (R3.6)
  • Changed — manual image runs publish only what their ref allows
  • Changed — DIDComm v1 keylist-update registers only keys the client is known to hold, up to a limit
  • Changed — live mux members and monitor subscriptions follow account changes
  • Changed — live mux members and monitor subscriptions follow account changes; revoke-all ends session attaches
  • Changed — account/add is admin-only and never replaces an existing account
  • Changed — access and refresh tokens are each accepted only where they belong (R3.6)
  • Changed — token refresh is bound to the session's DID and is single-use
  • Changed — accounts are registered after the challenge is answered
  • Changed — removing an account ends its sessions on every backend
  • Changed — forwarding delivers to endpoints concurrently, with per-endpoint backoff
  • Changed — mux frame decisions are counted; delivery reports hold no body
  • Changed — pickup-only mux members are told when mail waits
  • Changed — affinidi-messaging-sdk 0.45.5
  • Changed — affinidi-messaging-sdk 0.45.4
  • Changed — DID multiplexing across mediator instances
  • Changed — DID multiplexing connections (R3.6)
  • Changed — DID multiplexing connections (R3.6)
  • Changed — Redis storage, both modes
  • Changed — one set of role rules for account administration
  • Changed — requests to the mediator act for the session's own DID
  • Changed — embedded mediators get a generated JWT key by default
  • Changed — /readyz reuses its backend checks; /metrics has access control and a request bound
  • Changed — anonymous relay WebSockets are limited per address and metered
  • Changed — mediator-setup requires the digest to open a sealed bundle
  • Changed — the config template names no identity; release builds refuse the committed test identities
  • Changed — live WebSockets close with 1001 "mediator shutting down" on shutdown
  • Changed — messaging/mux/ack removes only a copy held for the connection
  • Changed — Cross-instance mux detaches keep the reason they were made with
  • Changed — TSP login signs a statement naming the mediator, the session and an expiry
  • Changed — the console's live monitor subscribes at monitor/subscribe 0.2
  • Changed — membership monitor events cross instances behind a shared Redis
  • Changed — Trust Task refusals change form for a client that asks (R3.6)
  • Changed — affinidi-messaging-sdk 0.46 and trust-tasks-rs 0.38 (R3.6)
  • Changed — messages on an authenticated WebSocket are rate limited
  • Changed — test mediator suite is one binary
  • Changed — a DIDComm message refused on a Binary WebSocket frame is answered with a problem report; an oversized frame closes with 1009
  • Changed — join waits for live WebSockets to close and background tasks to stop
  • Changed — the Redis stored-function library is built in and versioned
  • Changed — Redis start-up fails rather than waiting forever
  • Changed — backends agree on observable semantics
  • Changed — an unresolvable blocked-forwarding DID no longer stops startup
  • Changed — secret backend guidance
  • Changed — the HTTP server bounds slow, idle and excess connections
  • Changed — OOB invitation lookups answer with real HTTP status codes
  • Changed — /fetch takes its limit from limits.listed_messages
  • Changed — jwt_refresh_expiry is documented as what it does
  • Changed — The mediator image runs as UID:GID 10001:10001
  • Changed — Release profile tuned for throughput
  • Changed — console keys: Esc no longer quits; ? lists every key
  • Changed — Hot-path store, I/O and parsing costs cut (P12 perf)
  • Changed — one defaults table and one read per setting for mediator.toml
  • Changed — mediator-common depends on mediator-config, and takes its defaults from the table
  • Changed — mediator-setup: the wizard no longer writes the file-backend passphrase into its own environment
  • Changed — mediator-setup: internal restructuring
  • Changed — the console's code is split by concern
  • Changed — one local-delivery gate for DIDComm, TSP and DIDComm v1 (R3.6)
  • Changed — message processing and connection handling restructured
  • Changed — each release is supported for 90 days after its GA
  • Changed — mediator library docs show the supported API
  • Fixed — WebSocket relay to a next hop is time-bounded and dials the checked address
  • Fixed — DIDComm direct delivery answers the same way for every recipient it refuses
  • Fixed — live delivery across mediator instances (Redis)
  • Fixed — a live-delivery entry that goes missing is claimed back (Redis)
  • Fixed — mux notices reach a TSP principal, sealed for TSP
  • Fixed — raw-TSP sockets record only what they write, and never get a DIDComm frame
  • Fixed — a killed instance's DIDs are taken over by the instances still running (Redis)
  • Fixed — database URL credentials are hidden in debug output
  • Fixed — WebSocket connections release their resources on every exit
  • Fixed — a slow client no longer holds up live delivery for others
  • Fixed — narrowing away receive stops live pushes
  • Fixed — a held-back resync is sent when due
  • Fixed — a redelivery cut short tells the client
  • Fixed — delivered is reported once the frame is written
  • Fixed — attached events for attaches and narrowed grants
  • Fixed — global sent counters on Redis
  • Fixed — resync status honours the pickup scope
  • Fixed — DID multiplexing
  • Fixed — blocked_forwarding_dids and limits.to_keys_per_recipient take effect
  • Fixed — a Redis session read back after login is marked authenticated
  • Fixed — a challenge session is promoted once
  • Fixed — the access-list limit holds on Redis
  • Fixed — TSP empty-route delivery uses the hop's verified sender
  • Fixed — a WebSocket client that has gone away is closed within a set time
  • Fixed — a session error over HTTP returns a fixed message
  • Fixed — the answer to messaging/mux/ack on a DIDComm mux connection is not stored
  • Fixed — the same bytes stored for two recipients get a record each
  • Fixed — on a tsp-mux socket, one member's backlog no longer holds back another member's live frames
  • Fixed — a renewed monitor subscription keeps its filter
  • Fixed — the crates require the SDK release whose APIs they use
  • Fixed — a re-sent notice for a grant an administrator voided says admin
  • Fixed — limits.max_websocket_connections = 0 means unlimited
  • Fixed — inbox redelivery is paced to the socket, and raw-TSP sockets get one wake-up
  • Fixed — a socket that replaces another gets the redelivery already running for it
  • Fixed — a lagged streaming subscription raises every live client's resync
  • Fixed — mux member registration is idempotent, and a grant that gains receive starts live delivery
  • Fixed — a restart of the streaming task keeps its registered sockets
  • Fixed — mux member-change events are never dropped
  • Fixed — the Redis circuit breaker follows real command fail...
Read more

v0.52.0-rc.0

v0.52.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 14 Nov 22:15
7cb607c

What's Changed

  • chore: bootstrap the mediator workspace at 0.42.0 by @stormer78 in #1
  • ci(publish): publish crates from the release environment by @stormer78 in #3
  • chore(release): cut release/0.42; main moves to 0.43.0 by @stormer78 in #2
  • fix(deps): rustls 0.23.46 for RUSTSEC-2026-0346 and -0347 by @stormer78 in #6
  • docs(release): 0.42.0 is GA by @stormer78 in #8
  • fix(release): cut-release.py prunes its worktrees after removing them by @stormer78 in #9
  • fix(store): close Fjall crash and race gaps in forwarding, expiry and sessions by @stormer78 in #11
  • fix(forwarding): live-notify the abandonment problem report by @stormer78 in #13
  • fix(mediator): publish live notification after the message is stored by @marat-affinidi in #10
  • fix(monitor): report a live delivery only once it is queued to the socket by @stormer78 in #14
  • chore(deps): affinidi-messaging-sdk 0.36.2 by @stormer78 in #15
  • fix(mediator): REST bodies over 2 MiB, and silent raw-TSP refusals by @stormer78 in #16
  • fix(mediator): a TSP-only build compiles and serves TSP clients by @stormer78 in #17
  • chore(deps)!: trust-tasks-rs 0.32, affinidi-messaging-sdk 0.37 by @stormer78 in #18
  • chore(release): cut release/0.43; main moves to 0.44.0 by @stormer78 in #19
  • ci(image): add swap on the image build runners by @stormer78 in #21
  • chore(deps): vta-sdk 0.72 — one trust-tasks-rs, affinidi-messaging-sdk and affinidi-tdk in the graph by @stormer78 in #23
  • chore(deps)!: trust-tasks-rs 0.33, affinidi-messaging-sdk 0.38 by @stormer78 in #25
  • chore(release): cut release/0.44; main moves to 0.45.0 by @stormer78 in #26
  • feat(mediator): did:scid accounts and a did:scid mediator identity by @stormer78 in #28
  • feat(mediator): did:scid version floors survive a restart (VTI-KEY-162) by @stormer78 in #29
  • chore(deps)!: TSP 1.0 — affinidi-tsp 0.3, affinidi-messaging-sdk 0.39 by @stormer78 in #30
  • chore(deps)!: trust-tasks-rs 0.34, affinidi-messaging-sdk 0.40 by @stormer78 in #32
  • chore(release): cut release/0.45; main moves to 0.46.0 by @stormer78 in #33
  • ci(release): tag, prep and backport with the release-bot app, not GITHUB_TOKEN by @stormer78 in #35
  • ci(release): the release-bot's tag triggers the image build; stop dispatching it too by @stormer78 in #36
  • chore(deps)!: trust-tasks-rs 0.35, affinidi-messaging-sdk 0.41 by @stormer78 in #37
  • feat!: serve the 0.2 Trust Tasks beside 0.1, with the task types generated at build time by @stormer78 in #40
  • chore(release): cut release/0.46; main moves to 0.47.0 by @stormer78 in #41
  • chore(deps)!: affinidi-messaging-sdk 0.43, so the admin console speaks the 0.2 tasks by @stormer78 in #42
  • fix(mediator): a relay leaves a remote recipient's access list to its own mediator by @marat-affinidi in #31
  • chore(release): cut release/0.47; main moves to 0.48.0 by @stormer78 in #43
  • chore(deps)!: trust-tasks-rs 0.36, affinidi-messaging-sdk 0.44, monitor/event 0.2 by @stormer78 in #46
  • chore(release): cut release/0.48; main moves to 0.49.0 by @stormer78 in #47
  • fix(mediator): honour X-Forwarded-For from trusted proxies for per-IP rate limiting by @yaroslava-kurash in #45
  • chore(deps)!: latest dependencies for 0.49 (vta-sdk 0.77, kube 5, aws-config 1.13) and a docs consistency pass by @stormer78 in #50
  • chore(release): cut release/0.49; main moves to 0.50.0 by @stormer78 in #51
  • docs(releases): 0.49 is GA; 0.48 is N-1 and 0.47 reaches end of life by @stormer78 in #53
  • chore(deps)!: trust-tasks-rs 0.37, affinidi-messaging-sdk 0.45; replay record to record_expiry by @stormer78 in #55
  • chore(release): cut release/0.50; main moves to 0.51.0 by @stormer78 in #56
  • docs(releases): 0.50 is GA; 0.49 is N-1 and 0.48 reaches end of life by @stormer78 in #58
  • fix(config): ship the send-queue limits the template documents by @yaroslava-kurash in #54
  • fix(mediator): refuse a self-managed queue limit of -1 by @yaroslava-kurash in #61
  • feat(mediator): resolve did:webs by @stormer78 in #62
  • feat(mux): one connection carries many DIDs (DID multiplexing) by @stormer78 in #63
  • chore(release): cut release/0.51; main moves to 0.52.0 by @stormer78 in #64
  • fix(mux): muxNonce is 32 random bytes as base64url, as the spec requires by @stormer78 in #66
  • docs(releases): 0.51 is GA; 0.50 is N-1 and 0.49 reaches end of life by @stormer78 in #67
  • fix(mux): REST delete accepts a mux member's messages by @stormer78 in #68
  • fix(mux): carry a newly stored grant on its principal's live connection by @stormer78 in #69
  • test(mux): drive DID multiplexing end to end through the SDK mux client by @stormer78 in #70
  • feat(mux): durable notices for suspended, revoked and present grants by @stormer78 in #71
  • feat(mux): unknown-key rule on direct authentication by key relationship; grantsExpiring by @stormer78 in #72
  • test(mux): consume durable notices through the SDK notice stream by @stormer78 in #73
  • fix(mux): unknown-key rule fails closed on direct authentication by @stormer78 in #74
  • feat(mux): apply grant changes across mediator instances via pub/sub by @stormer78 in #75
  • feat(mux): honour the send scope on the inbound path by @stormer78 in #76
  • feat(mux): per-member fair queuing on mux sockets by @stormer78 in #77
  • feat(mux): didcomm-mux subprotocol; report connectionFull; attachedNow; bounded login check by @stormer78 in #78
  • feat(mux): audit revocations, revoke-all and unknown-key suspensions by @stormer78 in #79
  • feat(mux): tsp-mux subprotocol for DID multiplexing on raw-TSP sockets by @stormer78 in #80
  • test(mux): drive tsp-mux through the SDK client (affinidi-messaging-sdk 0.45.4) by @stormer78 in #82
  • fix(mux): send a resync status only for members holding pickup by @stormer78 in #81
  • fix(store): count fetched messages in the global sent stats on Redis by @stormer78 in #83
  • feat: Implement Redis cluster mode support and related fixes by @oleksiipiliugin in #59
  • fix(mux): attached events for attaches and narrowed grants; affinidi-messaging-sdk 0.45.5 by @stormer78 in #84
  • fix(streaming): report delivered once the websocke...
Read more

v0.51.0

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 09 Nov 07:01
2f437bc

Added — did:webs

  • The mediator resolves did:webs, so a did:webs client can authenticate and
    a did:webs recipient can be routed to. A did:webs resolves only when its
    KERI key event log verifies and the published did.json matches the
    verified key state, under the same default host policy as did:web and
    did:webvh: public hosts only, no redirects, no proxy. Requires
    affinidi-did-resolver-cache-sdk 0.8.47, which does not turn on
    serde_json's preserve_order for the whole build. A mediator configured to
    resolve through a DID resolver cache server needs one that resolves did:webs
    (affinidi-did-resolver-cache-server 0.9.16).

Changed — container send-queue limits

  • The published container image now ships queued_send_messages_soft = 2000
    and queued_send_messages_hard = 10000, matching the annotated template and
    the Rust defaults. It shipped 200 and 1000, so every deployment ran a send
    queue ten times tighter than the documented default while a code search
    reported 2000, which is a trap for anyone sizing a deployment or reading a
    queue_max_saturation_ratio against the wrong denominator. 200 is also tight
    in practice: a sender whose recipients stop deleting fills it in seconds.
    queued_receive_messages_soft and _hard are unchanged at 200 and 1000,
    because the receive limits bound total storage and the send limits do not;
    queued_send_messages_per_peer is unchanged at 50 and remains the gate that
    catches one sender flooding one recipient.

Fixed

  • A standard account can no longer switch its own queue limit off.
    SELF_MANAGE_SEND_QUEUE_LIMIT / SELF_MANAGE_RECEIVE_QUEUE_LIMIT let an
    account raise its own limit up to the mediator's hard maximum, enforced by
    clamping anything larger. -1 is not a larger number — it is the sentinel
    for no limit at all — so it slid past the clamp and was stored verbatim,
    after which the account's queue gate never refused it again, whatever its
    depth. Any deployment whose default ACL grants those flags — AMA's does,
    through GLOBAL_DEFAULT_ACL in cdk-atlas-lib; this repo's shipped
    global_acl_default does not — made one messaging/account/update/0.1
    enough, with no admin and no redeploy. Behaviour change (R3.6): a
    standard account requesting -1 (or any negative other than -2) for either
    queue limit now gets an authorization.queue_limit.admin_required problem
    report and a 403 instead of a success; a request it is allowed to make is
    unaffected, and values above the hard limit are still clamped rather than
    refused. An admin still sets -1 deliberately, and -2 still resets the
    account to the mediator default for standard accounts and admins alike.
    The queue_stream_maxlen doc comment in limits.rs described -2 as
    unlimited; it is a reset, and now says so.

  • A self-managed queue limit is no longer clamped against an unbounded hard
    limit.
    When the mediator is configured with queued_send_messages_hard or
    queued_receive_messages_hard of -1 (not bounded), the clamp compared
    against it as a number: 500 > -1 holds, so a standard account asking to be
    held to 500 was stored as -1 instead and ended up with no limit at all —
    reaching the state above by asking for something tighter. A negative hard
    limit is now read as "no ceiling" and the request stands, as
    queue_stream_maxlen already reads one. (queue_at_capacity and
    validate_peer_queue_limit test for -1 exactly, and are unbounded on any
    other negative only through the unsigned cast — the accident this change
    closes on the write path, not prior art to copy.) An unbounded mediator
    still does not hand out its own exemption: -1 from a standard account is
    refused either way.

  • A queue limit the account may not self-manage is now refused, not silently
    dropped.
    account/update ignored a send_queue_limit / receive_queue_limit
    from an account without the matching SELF_MANAGE_* flag and answered 200 with
    the account echoed, so the caller read the unchanged old value as the value it
    had just set. It now gets an authorization.queue_limit.not_self_manageable
    problem report and a 403, as acl already did for a capability the account may
    not change.

  • The two self-or-admin members of account/update now agree on who an admin
    is.
    The acl member tested Admin | RootAdmin, the queue limits tested
    "anything that is not Standard", so an account whose type did not decode
    (AccountType::Unknown) was gated on one member and waved through on the other.
    Both now use the handler's own is_admin.

  • account/update no longer applies part of a refused request. The handler
    guards every member before applying any of them, so that a member the caller
    may not set refuses the whole update; the queue-limit check above was added
    at the write instead, one step inside the apply phase. A single request
    carrying both an acl member and an unlimited queue limit therefore stored
    and audited the ACL change and then returned 403, leaving the account
    half-updated with no response document to say which half landed. The check
    now runs with the other guards, before the first write.

v0.51.0-rc.0

v0.51.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 09 Nov 06:39
8af96c2

What's Changed

  • chore: bootstrap the mediator workspace at 0.42.0 by @stormer78 in #1
  • ci(publish): publish crates from the release environment by @stormer78 in #3
  • chore(release): cut release/0.42; main moves to 0.43.0 by @stormer78 in #2
  • fix(deps): rustls 0.23.46 for RUSTSEC-2026-0346 and -0347 by @stormer78 in #6
  • docs(release): 0.42.0 is GA by @stormer78 in #8
  • fix(release): cut-release.py prunes its worktrees after removing them by @stormer78 in #9
  • fix(store): close Fjall crash and race gaps in forwarding, expiry and sessions by @stormer78 in #11
  • fix(forwarding): live-notify the abandonment problem report by @stormer78 in #13
  • fix(mediator): publish live notification after the message is stored by @marat-affinidi in #10
  • fix(monitor): report a live delivery only once it is queued to the socket by @stormer78 in #14
  • chore(deps): affinidi-messaging-sdk 0.36.2 by @stormer78 in #15
  • fix(mediator): REST bodies over 2 MiB, and silent raw-TSP refusals by @stormer78 in #16
  • fix(mediator): a TSP-only build compiles and serves TSP clients by @stormer78 in #17
  • chore(deps)!: trust-tasks-rs 0.32, affinidi-messaging-sdk 0.37 by @stormer78 in #18
  • chore(release): cut release/0.43; main moves to 0.44.0 by @stormer78 in #19
  • ci(image): add swap on the image build runners by @stormer78 in #21
  • chore(deps): vta-sdk 0.72 — one trust-tasks-rs, affinidi-messaging-sdk and affinidi-tdk in the graph by @stormer78 in #23
  • chore(deps)!: trust-tasks-rs 0.33, affinidi-messaging-sdk 0.38 by @stormer78 in #25
  • chore(release): cut release/0.44; main moves to 0.45.0 by @stormer78 in #26
  • feat(mediator): did:scid accounts and a did:scid mediator identity by @stormer78 in #28
  • feat(mediator): did:scid version floors survive a restart (VTI-KEY-162) by @stormer78 in #29
  • chore(deps)!: TSP 1.0 — affinidi-tsp 0.3, affinidi-messaging-sdk 0.39 by @stormer78 in #30
  • chore(deps)!: trust-tasks-rs 0.34, affinidi-messaging-sdk 0.40 by @stormer78 in #32
  • chore(release): cut release/0.45; main moves to 0.46.0 by @stormer78 in #33
  • ci(release): tag, prep and backport with the release-bot app, not GITHUB_TOKEN by @stormer78 in #35
  • ci(release): the release-bot's tag triggers the image build; stop dispatching it too by @stormer78 in #36
  • chore(deps)!: trust-tasks-rs 0.35, affinidi-messaging-sdk 0.41 by @stormer78 in #37
  • feat!: serve the 0.2 Trust Tasks beside 0.1, with the task types generated at build time by @stormer78 in #40
  • chore(release): cut release/0.46; main moves to 0.47.0 by @stormer78 in #41
  • chore(deps)!: affinidi-messaging-sdk 0.43, so the admin console speaks the 0.2 tasks by @stormer78 in #42
  • fix(mediator): a relay leaves a remote recipient's access list to its own mediator by @marat-affinidi in #31
  • chore(release): cut release/0.47; main moves to 0.48.0 by @stormer78 in #43
  • chore(deps)!: trust-tasks-rs 0.36, affinidi-messaging-sdk 0.44, monitor/event 0.2 by @stormer78 in #46
  • chore(release): cut release/0.48; main moves to 0.49.0 by @stormer78 in #47
  • fix(mediator): honour X-Forwarded-For from trusted proxies for per-IP rate limiting by @yaroslava-kurash in #45
  • chore(deps)!: latest dependencies for 0.49 (vta-sdk 0.77, kube 5, aws-config 1.13) and a docs consistency pass by @stormer78 in #50
  • chore(release): cut release/0.49; main moves to 0.50.0 by @stormer78 in #51
  • docs(releases): 0.49 is GA; 0.48 is N-1 and 0.47 reaches end of life by @stormer78 in #53
  • chore(deps)!: trust-tasks-rs 0.37, affinidi-messaging-sdk 0.45; replay record to record_expiry by @stormer78 in #55
  • chore(release): cut release/0.50; main moves to 0.51.0 by @stormer78 in #56
  • docs(releases): 0.50 is GA; 0.49 is N-1 and 0.48 reaches end of life by @stormer78 in #58
  • fix(config): ship the send-queue limits the template documents by @yaroslava-kurash in #54
  • fix(mediator): refuse a self-managed queue limit of -1 by @yaroslava-kurash in #61
  • feat(mediator): resolve did:webs by @stormer78 in #62

New Contributors

Full Changelog: https://github.com/affinidi/affinidi-messaging-mediator/commits/v0.51.0-rc.0

v0.50.0

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 04 Nov 03:46
34bbdea

Changed — trust-tasks-rs 0.37 (breaking)

  • trust-tasks-rs / trust-tasks-proof 0.37, affinidi-messaging-sdk
    0.45, affinidi-tdk 0.37, affinidi-messaging-didcomm-service 0.30.

    0.37 (trustoverip/dtgwg-trust-tasks-tf #1021) makes validate_freshness
    honour a stated expiresAt. Behaviour change: a consequential task
    that states an expiresAt is accepted until then, up to 30 days after its
    issuedAt, instead of being refused 5 minutes after issuedAt. A task
    without an expiresAt keeps the 5-minute window.

Fixed

  • The replay record now lasts as long as the document is acceptable. It
    was kept until issuedAt + 5 minutes + skew, or a sooner expiresAt. Under
    0.37 a document with a later expiresAt stays acceptable past that, so a
    replay of it after the record was dropped would have executed again.
    retention_end is now FreshnessPolicy::record_expiry, which the 30-day
    horizon bounds.
  • vta-sdk still resolves trust-tasks-rs 0.36 (with affinidi-messaging-sdk
    0.44 and affinidi-tdk 0.36) until the VTI moves to 0.37. No types cross
    between the two, and the next vta-sdk release removes the second copies.

v0.50.0-rc.0

v0.50.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 04 Nov 02:59
2996bcd

What's Changed

  • chore: bootstrap the mediator workspace at 0.42.0 by @stormer78 in #1
  • ci(publish): publish crates from the release environment by @stormer78 in #3
  • chore(release): cut release/0.42; main moves to 0.43.0 by @stormer78 in #2
  • fix(deps): rustls 0.23.46 for RUSTSEC-2026-0346 and -0347 by @stormer78 in #6
  • docs(release): 0.42.0 is GA by @stormer78 in #8
  • fix(release): cut-release.py prunes its worktrees after removing them by @stormer78 in #9
  • fix(store): close Fjall crash and race gaps in forwarding, expiry and sessions by @stormer78 in #11
  • fix(forwarding): live-notify the abandonment problem report by @stormer78 in #13
  • fix(mediator): publish live notification after the message is stored by @marat-affinidi in #10
  • fix(monitor): report a live delivery only once it is queued to the socket by @stormer78 in #14
  • chore(deps): affinidi-messaging-sdk 0.36.2 by @stormer78 in #15
  • fix(mediator): REST bodies over 2 MiB, and silent raw-TSP refusals by @stormer78 in #16
  • fix(mediator): a TSP-only build compiles and serves TSP clients by @stormer78 in #17
  • chore(deps)!: trust-tasks-rs 0.32, affinidi-messaging-sdk 0.37 by @stormer78 in #18
  • chore(release): cut release/0.43; main moves to 0.44.0 by @stormer78 in #19
  • ci(image): add swap on the image build runners by @stormer78 in #21
  • chore(deps): vta-sdk 0.72 — one trust-tasks-rs, affinidi-messaging-sdk and affinidi-tdk in the graph by @stormer78 in #23
  • chore(deps)!: trust-tasks-rs 0.33, affinidi-messaging-sdk 0.38 by @stormer78 in #25
  • chore(release): cut release/0.44; main moves to 0.45.0 by @stormer78 in #26
  • feat(mediator): did:scid accounts and a did:scid mediator identity by @stormer78 in #28
  • feat(mediator): did:scid version floors survive a restart (VTI-KEY-162) by @stormer78 in #29
  • chore(deps)!: TSP 1.0 — affinidi-tsp 0.3, affinidi-messaging-sdk 0.39 by @stormer78 in #30
  • chore(deps)!: trust-tasks-rs 0.34, affinidi-messaging-sdk 0.40 by @stormer78 in #32
  • chore(release): cut release/0.45; main moves to 0.46.0 by @stormer78 in #33
  • ci(release): tag, prep and backport with the release-bot app, not GITHUB_TOKEN by @stormer78 in #35
  • ci(release): the release-bot's tag triggers the image build; stop dispatching it too by @stormer78 in #36
  • chore(deps)!: trust-tasks-rs 0.35, affinidi-messaging-sdk 0.41 by @stormer78 in #37
  • feat!: serve the 0.2 Trust Tasks beside 0.1, with the task types generated at build time by @stormer78 in #40
  • chore(release): cut release/0.46; main moves to 0.47.0 by @stormer78 in #41
  • chore(deps)!: affinidi-messaging-sdk 0.43, so the admin console speaks the 0.2 tasks by @stormer78 in #42
  • fix(mediator): a relay leaves a remote recipient's access list to its own mediator by @marat-affinidi in #31
  • chore(release): cut release/0.47; main moves to 0.48.0 by @stormer78 in #43
  • chore(deps)!: trust-tasks-rs 0.36, affinidi-messaging-sdk 0.44, monitor/event 0.2 by @stormer78 in #46
  • chore(release): cut release/0.48; main moves to 0.49.0 by @stormer78 in #47
  • fix(mediator): honour X-Forwarded-For from trusted proxies for per-IP rate limiting by @yaroslava-kurash in #45
  • chore(deps)!: latest dependencies for 0.49 (vta-sdk 0.77, kube 5, aws-config 1.13) and a docs consistency pass by @stormer78 in #50
  • chore(release): cut release/0.49; main moves to 0.50.0 by @stormer78 in #51
  • docs(releases): 0.49 is GA; 0.48 is N-1 and 0.47 reaches end of life by @stormer78 in #53
  • chore(deps)!: trust-tasks-rs 0.37, affinidi-messaging-sdk 0.45; replay record to record_expiry by @stormer78 in #55

New Contributors

Full Changelog: https://github.com/affinidi/affinidi-messaging-mediator/commits/v0.50.0-rc.0

v0.49.0

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 02 Nov 04:32
8130824

Changed — dependencies to latest (breaking)

  • vta-sdk 0.77 (from 0.72; the mediator's default vta feature and
    mediator-setup). Breaking for VTA-linked deployments: from vta-sdk
    0.75 the SDK authenticates with auth/authenticate/0.3 and pages
    keys/list/0.2, and the VTA no longer serves the earlier versions. A
    mediator built with vta now needs a VTA from the same release line (vta-sdk
    0.75 or later); conversely, mediator 0.48 and earlier cannot authenticate to
    such a VTA. Upgrade the VTA and the mediator together. Self-hosted mediators
    (operating secrets from the unified secret backend) and builds without vta
    are unaffected. vta-sdk 0.77 also made VtaEvent, DiagStatus,
    AttemptResultKind and VtaIntegrationError #[non_exhaustive]; the
    mediator and wizard handle an unknown variant by skipping it or reporting it
    generically.
  • kube 5 / k8s-openapi 0.29 (from 4.2 / 0.28; secrets-k8s). The
    latest API feature now targets Kubernetes 1.37 (was 1.36); the
    backend's calls (core/v1 Secret get/create/replace) are unchanged.
  • aws-config 1.13, and the aws-smithy-types >=1.6.1, <1.7 resolver
    bound is removed. aws-config 1.13 is the first release off
    aws-smithy-json 0.63, whose break against aws-smithy-types 1.7 the bound
    existed to avoid; requiring 1.13 keeps a downstream resolve off the broken
    pair. aws-sdk-* move to their current releases.
  • Lockfile refreshed to the latest compatible versions throughout, including
    TDK patch releases (affinidi-did-common 0.4.5, affinidi-did-resolver-cache-sdk
    0.8.44, affinidi-messaging-didcomm 0.15.11), redis 1.8 and
    trust-tasks-rs 0.36.6. The second copies of affinidi-messaging-sdk
    (0.37), affinidi-tdk (0.27) and trust-tasks-rs (0.32) that vta-sdk 0.72
    pulled in are gone.

Fixed — configuration and documentation

  • LIMIT_QUEUED_SEND_MESSAGES_PER_PEER now overrides
    [limits] queued_send_messages_per_peer, as the shipped template's
    ### Env: label always said; it was silently ignored. A test now fails if
    any template ### Env: label has no override behind it.
  • Documentation brought in line with the code: the template lists the GCP,
    Azure, Vault and Kubernetes secret backends as available (not "coming soon")
    and names the secrets-* feature each needs; the quick start builds with
    the feature for the wizard's default keyring:// backend; the
    rate_limit_per_ip guidance and a new README section point load-balanced
    deployments at trust_xff_cidrs (also in the example setup recipe);
    version snippets say 0.49; links into affinidi-tdk-rs that broke when the
    mediator moved out are absolute; stale CI workflow names, feature lists and
    crate docs corrected; the release schedule shows 0.48 GA.

Changed — trusted-proxy rate-limit attribution

  • affinidi-rate-limit 0.1.3. The per-IP limiter can now charge clients
    behind a reverse proxy to themselves. New [server] trust_xff_cidrs (env
    TRUST_XFF_CIDRS, comma-separated; default [], which keeps today's
    behaviour of keying on the socket peer). When the socket peer is inside a
    listed range, the limiter walks X-Forwarded-For from the right, skips
    listed hops and charges the first address that is not one; a header from any
    other peer is never read. List only proxies that append to
    X-Forwarded-For (an ALB does), and make sure the mediator is reachable
    only through them.
  • Behaviour change: an unreadable X-Forwarded-For chain from a listed
    proxy (a hop from the client rightwards that is not an address, a non-ASCII
    header, more than 64 entries) is refused with 400 and x-rate-limit-source: mediator, body
    {"error":"invalid_forwarded_for","limiter":"mediator","message":…}, rather
    than charging the proxy's shared bucket. Entries left of the client are
    never parsed, so junk a client prepends is ignored (it still counts towards
    the 64-entry cap). Counted in the new
    rate_limit_attribution_failures_total{reason="invalid_forwarded_for"}
    (also reason="no_client_ip" for the existing 403).
  • Behaviour change: per-IP keys are canonical, so a dual-stack listener's
    ::ffff:a.b.c.d peer shares the IPv4 client's bucket instead of holding a
    second one. The 403 for a request with no client IP now also carries
    x-rate-limit-source: mediator.
  • A catch-all range (0.0.0.0/0, ::/0) in trust_xff_cidrs fails startup
    (and setup-wizard recipe loading): it would let any client choose its own
    rate-limit key. Startup logs which key the limiter uses and the trusted
    ranges, and warns when trust_xff_cidrs is set while per-IP limiting is
    disabled (rate_limit_per_ip = 0), since it then has no effect.
  • affinidi-messaging-mediator-setup now depends on
    affinidi-messaging-mediator-config (previously a dev-dependency) to apply
    the same checks to recipe values.

v0.49.0-rc.0

v0.49.0-rc.0 Pre-release
Pre-release

Choose a tag to compare

@affinidi-semantic-release affinidi-semantic-release released this 02 Nov 03:56
08d67c1

What's Changed

  • chore: bootstrap the mediator workspace at 0.42.0 by @stormer78 in #1
  • ci(publish): publish crates from the release environment by @stormer78 in #3
  • chore(release): cut release/0.42; main moves to 0.43.0 by @stormer78 in #2
  • fix(deps): rustls 0.23.46 for RUSTSEC-2026-0346 and -0347 by @stormer78 in #6
  • docs(release): 0.42.0 is GA by @stormer78 in #8
  • fix(release): cut-release.py prunes its worktrees after removing them by @stormer78 in #9
  • fix(store): close Fjall crash and race gaps in forwarding, expiry and sessions by @stormer78 in #11
  • fix(forwarding): live-notify the abandonment problem report by @stormer78 in #13
  • fix(mediator): publish live notification after the message is stored by @marat-affinidi in #10
  • fix(monitor): report a live delivery only once it is queued to the socket by @stormer78 in #14
  • chore(deps): affinidi-messaging-sdk 0.36.2 by @stormer78 in #15
  • fix(mediator): REST bodies over 2 MiB, and silent raw-TSP refusals by @stormer78 in #16
  • fix(mediator): a TSP-only build compiles and serves TSP clients by @stormer78 in #17
  • chore(deps)!: trust-tasks-rs 0.32, affinidi-messaging-sdk 0.37 by @stormer78 in #18
  • chore(release): cut release/0.43; main moves to 0.44.0 by @stormer78 in #19
  • ci(image): add swap on the image build runners by @stormer78 in #21
  • chore(deps): vta-sdk 0.72 — one trust-tasks-rs, affinidi-messaging-sdk and affinidi-tdk in the graph by @stormer78 in #23
  • chore(deps)!: trust-tasks-rs 0.33, affinidi-messaging-sdk 0.38 by @stormer78 in #25
  • chore(release): cut release/0.44; main moves to 0.45.0 by @stormer78 in #26
  • feat(mediator): did:scid accounts and a did:scid mediator identity by @stormer78 in #28
  • feat(mediator): did:scid version floors survive a restart (VTI-KEY-162) by @stormer78 in #29
  • chore(deps)!: TSP 1.0 — affinidi-tsp 0.3, affinidi-messaging-sdk 0.39 by @stormer78 in #30
  • chore(deps)!: trust-tasks-rs 0.34, affinidi-messaging-sdk 0.40 by @stormer78 in #32
  • chore(release): cut release/0.45; main moves to 0.46.0 by @stormer78 in #33
  • ci(release): tag, prep and backport with the release-bot app, not GITHUB_TOKEN by @stormer78 in #35
  • ci(release): the release-bot's tag triggers the image build; stop dispatching it too by @stormer78 in #36
  • chore(deps)!: trust-tasks-rs 0.35, affinidi-messaging-sdk 0.41 by @stormer78 in #37
  • feat!: serve the 0.2 Trust Tasks beside 0.1, with the task types generated at build time by @stormer78 in #40
  • chore(release): cut release/0.46; main moves to 0.47.0 by @stormer78 in #41
  • chore(deps)!: affinidi-messaging-sdk 0.43, so the admin console speaks the 0.2 tasks by @stormer78 in #42
  • fix(mediator): a relay leaves a remote recipient's access list to its own mediator by @marat-affinidi in #31
  • chore(release): cut release/0.47; main moves to 0.48.0 by @stormer78 in #43
  • chore(deps)!: trust-tasks-rs 0.36, affinidi-messaging-sdk 0.44, monitor/event 0.2 by @stormer78 in #46
  • chore(release): cut release/0.48; main moves to 0.49.0 by @stormer78 in #47
  • fix(mediator): honour X-Forwarded-For from trusted proxies for per-IP rate limiting by @yaroslava-kurash in #45
  • chore(deps)!: latest dependencies for 0.49 (vta-sdk 0.77, kube 5, aws-config 1.13) and a docs consistency pass by @stormer78 in #50

New Contributors

Full Changelog: https://github.com/affinidi/affinidi-messaging-mediator/commits/v0.49.0-rc.0