• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

archetech / archon / 23015720892 / 1
94%
main: 94%

Build:
DEFAULT BRANCH: main
Ran 12 Mar 2026 05:44PM UTC
Files 44
Run time 1s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

12 Mar 2026 05:42PM UTC coverage: 94.962% (+0.02%) from 94.942%
23015720892.1

push

github

web-flow
feat: Add change-registry command to change a DID's registry (#194)

* feat: Add changeRegistry to change a DID's registry after creation

Adds a `change-registry <id> <registry>` CLI command and supporting
`changeRegistry(id, registry)` method that updates didDocumentRegistration
to point to a new registry. Same-registry calls are a no-op. Gatekeeper
updateDID now queues the operation on the new registry when it differs
from the current one. Accepts any resolvable DID or alias.

Closes #153

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* test: Add unit and client tests for changeRegistry

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* test: Add changeRegistry unit and client tests

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* refactor: Move change-registry command to DID commands section

Relocate changeRegistry in keymaster.ts (after revokeDID), cli.ts (after revoke-did), and archon-cli.js (after revoke-did) to group it with DID operations rather than ID/wallet operations.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: Restore InvalidParameterError guard in changeRegistry

Guard was accidentally dropped during method relocation.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* fix: Queue registry-change operations on the old registry

Queuing on the new registry broke the confirmation check, which
validates that each event's confirming registry matches the DID's
current registry. This caused the entire DID history after the
first registry change to be permanently marked unconfirmed.

The fix: always queue on the current (old) registry. The new registry
is still validated for support upfront. Subsequent operations
naturally queue on the new registry once the doc is updated.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* feat: Add Migrate dialog to gatekeeper web client

Adds a shared Migrate dialog to KeymasterUI allowing users to change
the registry for any o... (continued)

1810 of 1990 branches covered (90.95%)

Branch coverage included in aggregate %.

7502 of 7816 relevant lines covered (95.98%)

588.79 hits per line

Source Files on job 23015720892.1
  • Tree
  • List 44
  • Changed 20
  • Source Changed 3
  • Coverage Changed 20
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Build 23015720892
  • 0d258def on github
  • Prev Job for on main (#22961272368.1)
  • Next Job for on main (#23020696961.1)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc