Repository navigation
deps: bump ucantone (v1 DID context) and libforge (attested-sig fix) - #8
Merged
Merged
Conversation
Bump ucantone 7985ec0 -> a8f24fe (accepts the DID Core v1 `@context` alongside v1.1) and libforge eb26d871 -> 2b55dbcf (fil-forge/libforge#43, attested did:web signatures). Part of the cross-service rollout for the attested-signatures / UCAN Principal Clarification migration: any service that resolves did:web documents needs the ucantone bump to accept v1-context DID documents, and the libforge#43 verifier fix for attested did:web signatures. Dependency-only change: builds and vets clean. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017yUxrDH8gWAA4ufwzuq657
frrist
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bump the UCAN dependencies as part of the attested-signatures / UCAN Principal Clarification rollout:
7985ec0→a8f24fe— accepts the DID Core v1@context(https://www.w3.org/ns/did/v1) alongsidev1.1.eb26d871→2b55dbcf— fil-forge/libforge#43, verify attested signatures fromdid:webauthorities.Why
Any service that resolves
did:webdocuments needs the ucantone bump to acceptv1-context DID documents (the older ones some services still serve, e.g. the delegator), plus the libforge#43 verifier fix for attesteddid:websignatures. This mirrors the same bump applied to piri (fil-forge/piri) to unblock the smelt e2e (fil-forge/smelt#7).The indexer was not observed failing directly in the e2e run (piri failed first, before the index step), so this is a precautionary, consistency bump — but it is the same one-line dependency change and keeps the indexer aligned with the rest of the stack.
Testing
Dependency-only change (
go.mod/go.sum).go build ./...andgo vet ./...pass locally.🤖 Generated with Claude Code
https://claude.ai/code/session_017yUxrDH8gWAA4ufwzuq657
Generated by Claude Code