Skip to content

chore(deps): Bump affinidi-messaging-test-mediator from 0.50.0 to 0.51.0 - #213

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/affinidi-messaging-test-mediator-0.51.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/affinidi-messaging-test-mediator-0.51.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 21, 2026

Copy link
Copy Markdown
Contributor

Bumps affinidi-messaging-test-mediator from 0.50.0 to 0.51.0.

Release notes

Sourced from affinidi-messaging-test-mediator's releases.

v0.51.0

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

... (truncated)

Changelog

Sourced from affinidi-messaging-test-mediator's changelog.

0.51.0 (release/0.51)

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

... (truncated)

Commits
  • 2f437bc chore(release): v0.51.0 (#65)
  • 8af96c2 chore(release): cut release/0.51 at 0.51.0-rc.0
  • 9668646 feat(mediator): resolve did:webs (#62)
  • 3ff96ba fix(mediator): refuse a self-managed queue limit of -1 (#61)
  • 137e192 fix(config): ship the send-queue limits the template documents (#54)
  • cb98171 docs(releases): 0.50 is GA; 0.49 is N-1 and 0.48 reaches end of life (#58)
  • d784669 chore(release): cut release/0.50; main moves to 0.51.0 (#56)
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [affinidi-messaging-test-mediator](https://github.com/affinidi/affinidi-messaging-mediator) from 0.50.0 to 0.51.0.
- [Release notes](https://github.com/affinidi/affinidi-messaging-mediator/releases)
- [Changelog](https://github.com/affinidi/affinidi-messaging-mediator/blob/main/CHANGELOG.md)
- [Commits](affinidi/affinidi-messaging-mediator@v0.50.0...v0.51.0)

---
updated-dependencies:
- dependency-name: affinidi-messaging-test-mediator
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner November 21, 2026 01:43
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Nov 21, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants