Skip to content

deps: bump ucantone (v1 DID context) and libforge (attested-sig fix)#29

Merged
frrist merged 1 commit into
mainfrom
claude/smelt-pr7-fix-ks4g5s
Jul 2, 2026
Merged

deps: bump ucantone (v1 DID context) and libforge (attested-sig fix)#29
frrist merged 1 commit into
mainfrom
claude/smelt-pr7-fix-ks4g5s

Conversation

@Peeja

@Peeja Peeja commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Summary

Bump the UCAN dependencies to unblock the attested-signatures / UCAN Principal Clarification rollout:

  • ucantone 7985ec0a8f24fe — accepts the DID Core v1 @context (https://www.w3.org/ns/did/v1) alongside v1.1.
  • libforge eb26d8712b55dbcffil-forge/libforge#43, verify attested signatures from did:web authorities.

Why

With the attested-signature login fix (libforge#43) in place on the upload service, the smelt e2e suite got past guppy login but then failed on every upload at piri's /blob/accept:

publishing location commitment: unable to resolve "did:web:delegator":
parsing DID document JSON: @context must list ".../did/v1.1" first

The published piri:main image runs the older ucantone (7985ec0), which accepts a v1.1 @context only and therefore rejects the delegator's v1-context did:web document. ucantone a8f24fe adds v1 acceptance (intended backward-compat on input), which fixes the resolution. The delegator needs no change.

Once this merges and piri:main is rebuilt, the smelt e2e (see fil-forge/smelt#7) can go green.

Testing

Dependency-only change (go.mod/go.sum). go build ./..., go vet ./..., and the fx dependency-graph test (pkg/fx/app) all pass locally.

🤖 Generated with Claude Code

https://claude.ai/code/session_017yUxrDH8gWAA4ufwzuq657


Generated by Claude Code

Bump ucantone 7985ec0 -> a8f24fe (adds acceptance of the DID Core v1
`@context`, https://www.w3.org/ns/did/v1, alongside v1.1) and libforge
eb26d871 -> 2b55dbcf (fil-forge/libforge#43, attested did:web signatures).

Without the ucantone bump, piri rejects DID documents whose `@context`
is the older v1 form with:

  publishing location commitment: unable to resolve "did:web:delegator":
  parsing DID document JSON: @context must list ".../did/v1.1" first

This blocks /blob/accept (and therefore every upload) against services
that still serve a v1-context did:web document (e.g. the delegator),
which is what the smelt e2e suite hit once the attested-signature login
fix (libforge#43) was in place.

Dependency-only change: builds, vets, and the fx app graph validation
(pkg/fx/app) pass unchanged.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017yUxrDH8gWAA4ufwzuq657
@frrist frrist merged commit 6bf7299 into main Jul 2, 2026
8 checks passed
@frrist frrist deleted the claude/smelt-pr7-fix-ks4g5s branch July 2, 2026 22:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants