Skip to content

Update did-jwks library to latest #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
venables merged 1 commit into from
Feb 21, 2026
Merged

Update did-jwks library to latest #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/large-lines-wave.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"@agentcommercekit/did": patch
Copy link

@coderabbitai coderabbitai bot Feb 21, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

# Check the changeset file
cat .changeset/large-lines-wave.md

Repository: agentcommercekit/ack

Length of output: 128

🏁 Script executed:

# Check the did package.json to see the actual dependency change
cat packages/did/package.json | grep -A 20 -B 5 "jwks-did-resolver\|dependencies"

Repository: agentcommercekit/ack

Length of output: 757

🌐 Web query:

jwks-did-resolver npm package changelog 0.3.0 to 1.1.0 breaking changes

💡 Result:

jwks-did-resolver breaking changes from 0.3.0 → 1.1.0

Breaking change introduced in 1.1.0 (tagged Feb 21, 2026)

Path-based did:jwks identifiers resolve to different URLs than before. Root (no-path) DIDs are unchanged. [1][2]

Before (≤ 1.0.0, including 0.3.0): .well-known was placed under the DID path (RFC 8615-invalid), e.g.:

  • https://example.com/tenant/.well-known/jwks.json (and similar patterns)

Now (1.1.0): resolution is RFC 8615 / RFC 8414 compliant: [2]

  • Direct JWKS: https://example.com/tenant/jwks.json
  • OIDC discovery fallback: https://example.com/.well-known/openid-configuration/tenant

Impact: if you used path DIDs (e.g. did:jwks:example.com:tenant), the resolver will now call different endpoints, so servers configured for the old (non-compliant) paths may fail until updated. [2]

0.3.0 → 1.0.0

I didn’t find any documented API-level breaking change in the repo history between these tags—only a doc/spec tweak and the 1.0.0 version tag itself are visible in the comparison metadata GitHub renders. [3]

Sources

[1] GitHub tags list showing jwks-did-resolver@0.3.0, @1.0.0, @1.1.0 (catena-labs/did-jwks) (github.com)
[2] GitHub compare view containing the 1.1.0 change description (“RFC 8615/8414-compliant” path resolution and new URL chain) (github.com)
[3] GitHub compare view for jwks-did-resolver@0.3.0...@1.0.0 showing only high-level commit metadata (no explicit breaking notes) (github.com)

Citations:

Change bump type from patch to minor — jwks-did-resolver 1.1.0 contains a breaking change.

The jwks-did-resolver upgrade from 0.3.0 to 1.1.0 introduces a breaking change in how path-based did:jwks identifiers are resolved. In 1.1.0, the resolver now uses RFC 8615/8414-compliant URLs (e.g., https://example.com/tenant/jwks.json) instead of the old non-compliant paths (e.g., https://example.com/tenant/.well-known/jwks.json). If servers or clients in the ecosystem are configured for the old resolution paths, this upgrade will cause silent failures.

Semver requires that breaking changes trigger at least a minor bump (not patch). Additionally, update the changeset description to explicitly note the breaking change: "Upgrade jwks-did-resolver to 1.1.0 for RFC-compliant path-based DID resolution (breaking change: path resolution URLs have changed)".

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.changeset/large-lines-wave.md at line 2, Update the changeset for
"@agentcommercekit/did" in .changeset/large-lines-wave.md by changing the
release type from "patch" to "minor" and revise the changeset body to explicitly
note the breaking change; replace the existing description with: "Upgrade
jwks-did-resolver to 1.1.0 for RFC-compliant path-based DID resolution (breaking
change: path resolution URLs have changed)" so consumers know the path-based
did:jwks resolution URLs have changed and require attention.

---

Improve did:jwks support
2 changes: 1 addition & 1 deletion packages/did/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@
"@agentcommercekit/caip": "workspace:*",
"@agentcommercekit/keys": "workspace:*",
"did-resolver": "4.1.0",
"jwks-did-resolver": "0.3.0",
"jwks-did-resolver": "1.1.0",
"key-did-resolver": "4.0.0",
"valibot": "catalog:",
"varint": "6.0.0"
Expand Down
19 changes: 10 additions & 9 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.