Skip to content

feat: package version update w3c #120

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
rongquan1 merged 1 commit into from
Nov 11, 2025
Merged

feat: package version update w3c #120

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
62 changes: 31 additions & 31 deletions package-lock.json
View file
Open in desktop

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

10 changes: 5 additions & 5 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,11 +122,11 @@
"@tradetrust-tt/tradetrust": "^6.10.2",
"@tradetrust-tt/tradetrust-utils": "^2.4.4",
"@tradetrust-tt/tt-verify": "^9.6.0",
"@trustvc/w3c": "^1.3.0-alpha.17",
"@trustvc/w3c-context": "^1.3.0-alpha.12",
"@trustvc/w3c-credential-status": "^1.3.0-alpha.13",
"@trustvc/w3c-issuer": "^1.3.0-alpha.10",
"@trustvc/w3c-vc": "^1.3.0-alpha.17",
"@trustvc/w3c": "^2.0.0",
"@trustvc/w3c-context": "^2.0.0",
"@trustvc/w3c-credential-status": "^2.0.0",
"@trustvc/w3c-issuer": "^2.0.0",
"@trustvc/w3c-vc": "^2.0.0",
Comment on lines +125 to +129

@coderabbitai coderabbitai Bot Nov 11, 2025

Copy link
Copy Markdown
Contributor

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

Verify compatibility and breaking changes for W3C package upgrades.

All five W3C-related dependencies are consistently upgraded to ^2.0.0 (stable releases), which is a significant move from pre-release versions. While maintaining version alignment across these packages is good practice, we need to confirm that the upgrade doesn't introduce breaking changes to the codebase.

Before merging, please verify:

  1. Package availability: Confirm these versions exist on npm registry
  2. API compatibility: Check for breaking changes between pre-release and 2.0.0 (especially type definitions, since this is a TypeScript project)
  3. Integration testing: Run the full test suite (npm test) and e2e tests (npm run e2e:test) to catch integration issues early
  4. Type safety: Review any TypeScript compilation errors (npm run type-check)

If you haven't already, consider reviewing the changelogs or release notes for these packages to identify any deprecated APIs or required migration steps.

🌐 Web query:

What are the breaking changes in @trustvc/w3c 2.0.0 release?

💡 Result:

I couldn't find a published @trustvc/w3c v2.0.0 release. The npm package shows the latest published version is 1.2.17 (last publish June 2025). Therefore there are no documented breaking changes for a 2.0.0 release. [1]

Sources:

Revert W3C dependency versions to published releases—v2.0.0 does not exist on npm.

The specified versions ^2.0.0 for all five @TrustVC packages cannot be installed. The latest published version on npm is 1.2.17 (June 2025). This will cause your npm install to fail or pull unintended pre-release versions.

Update lines 125-129 to use the latest available version (1.2.17 or confirm the correct target version). If v2.0.0 is intentional (pre-release or private registry), document the registry configuration explicitly.

🤖 Prompt for AI Agents 
In package.json around lines 125 to 129, the five @trustvc dependencies are
pinned to ^2.0.0 which is not published on npm; change each dependency version
to the latest published release (1.2.17) or the intended valid version, save
package.json, and run npm install to verify; if 2.0.0 is intentional
(pre-release or from a private registry), instead restore a published version
and add clear documentation and registry configuration (or .npmrc) so installs
resolve correctly.

"ethers": "^5.8.0",
"ethersV6": "npm:ethers@^6.14.4",
"js-sha3": "^0.9.3",
Expand Down