Skip to content

fix: bump w3c vc version#26

Open
RishabhS7 wants to merge 1 commit intomasterfrom
fix/bump-w3c-vc-version
Open

fix: bump w3c vc version#26
RishabhS7 wants to merge 1 commit intomasterfrom
fix/bump-w3c-vc-version

Conversation

@RishabhS7
Copy link
Copy Markdown

@RishabhS7 RishabhS7 commented Aug 19, 2025

Summary

bump w3c vc version

Summary by CodeRabbit

  • Chores
    • Upgraded a core verifiable credentials library to the latest pre-release version, incorporating upstream fixes and enhancements.
    • Improves compatibility with recent ecosystem updates and may enhance stability and interoperability.
    • No direct user-facing changes are expected; existing functionality should continue to work as before.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Aug 19, 2025

Walkthrough

Updated dependency version in package.json: @trustvc/w3c-vc from ^1.2.17 to ^1.3.0-alpha.5.

Changes

Cohort / File(s) Summary
Dependency Version Bump
package.json
Updated dependency @trustvc/w3c-vc from ^1.2.17 to ^1.3.0-alpha.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled the leaves of versioned trees,
Plucked 1.3.0 with alpha breeze.
A hop, a bump, dependencies align—
Carrot-orange commits look fine.
Whiskers twitch: “Ship it, please!”

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/bump-w3c-vc-version

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (1)
package.json (1)

72-72: Avoid floating pre-release range; pin exact alpha to reduce CI/install drift

Using a caret with a pre-release (^1.3.0-alpha.5) can float to other alphas and eventually the stable 1.3.x, which may introduce untested changes over time. Prefer an exact pin for alphas to keep installs reproducible.

Apply this diff:

-    "@trustvc/w3c-vc": "^1.3.0-alpha.5",
+    "@trustvc/w3c-vc": "1.3.0-alpha.5",

If a stable 1.3.x is available and acceptable, consider bumping to that instead of an alpha.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between eed6abb and 606c5f2.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json (1 hunks)

Comment thread package.json
"dependencies": {
"@govtechsg/jsonld": "^0.1.1",
"@trustvc/w3c-vc": "^1.2.17",
"@trustvc/w3c-vc": "^1.3.0-alpha.5",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Verification agent

🧩 Analysis chain

Verify API/peer-deps compatibility and lockfile resolution after the bump

Sanity-check that our imports and any subpath imports still resolve, and inspect peerDependencies for 1.3.0-alpha.5 to avoid runtime surprises.

Run this script from the repo root:

If you want, I can help scan our code for specific API changes (constructors/functions/types) once you share release notes or breaking-change summaries for 1.3.x.


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Scan direct imports of @trustvc/w3c-vc =="
rg -nP -C2 --type=ts --type=tsx --type=js --type=jsx \
  '(from\s+["'\'']@trustvc/w3c-vc["'\'']|require\(\s*["'\'']@trustvc/w3c-vc["'\'']\s*\))' || true

echo "== Scan subpath imports of @trustvc/w3c-vc/* (may break across versions) =="
rg -nP -C2 --type=ts --type=tsx --type=js --type=jsx '@trustvc/w3c-vc\/[A-Za-z0-9_\-\/]+' || true

echo "== Detect lockfiles present =="
fd -H -t f --exact-depth 1 'package-lock.json' 'pnpm-lock.yaml' 'yarn.lock' 2>/dev/null || true

if [ -f package-lock.json ]; then
  echo "== package-lock.json entries for @trustvc/w3c-vc =="
  rg -nP -C1 '"@trustvc/w3c-vc"|^\s*"version":\s*"' package-lock.json | sed -n '1,200p' || true
fi
if [ -f pnpm-lock.yaml ]; then
  echo "== pnpm-lock.yaml entries for @trustvc/w3c-vc =="
  rg -nP -C2 '@trustvc/w3c-vc' pnpm-lock.yaml || true
fi
if [ -f yarn.lock ]; then
  echo "== yarn.lock entries for @trustvc/w3c-vc =="
  rg -nP -C2 '@trustvc/w3c-vc' yarn.lock || true
fi

echo "== Peer deps for 1.3.0-alpha.5 from npm registry =="
curl -s https://registry.npmjs.org/%40trustvc%2Fw3c-vc | jq '.versions["1.3.0-alpha.5"].peerDependencies // {}'

echo "== Runtime deps for 1.3.0-alpha.5 from npm registry =="
curl -s https://registry.npmjs.org/%40trustvc%2Fw3c-vc | jq '.versions["1.3.0-alpha.5"].dependencies // {}'

echo "Done. Review output for import breaks or new peer requirements."

Length of output: 12002


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== package.json entries including jsonld =="
rg -nP '"jsonld"\s*:' package.json || true

echo "== Direct imports of jsonld package =="
rg -nP -C2 --type=ts --type=js "(from\s+['\"]jsonld['\"]|require\(\s*['\"]jsonld['\"]\))" || true

echo "== Direct imports of @govtechsg/jsonld wrapper =="
rg -nP -C2 --type=ts --type=js "(from\s+['\"]@govtechsg/jsonld['\"]|require\(\s*['\"]@govtechsg/jsonld['\"]\))" || true

Length of output: 1128


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Locked @govtechsg/jsonld version =="
jq -r '.dependencies["@govtechsg/jsonld"].version' package-lock.json

echo "== @govtechsg/jsonld registry dependencies and peerDependencies =="
WRAPPER_VERSION=$(jq -r '.dependencies["@govtechsg/jsonld"].version' package-lock.json)
curl -s "https://registry.npmjs.org/%40govtechsg%2Fjsonld" \
  | jq '.versions["'"$WRAPPER_VERSION"'"] | {dependencies, peerDependencies}'

Length of output: 594


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "== Wrapper version in lockfile (v3 packages) =="
jq -r '.packages["node_modules/@govtechsg/jsonld"].version // "not found"' package-lock.json

echo "== Wrapper registry peerDependencies and dependencies =="
WRAPPER_VERSION=$(jq -r '.packages["node_modules/@govtechsg/jsonld"].version' package-lock.json)
curl -s "https://registry.npmjs.org/%40govtechsg%2Fjsonld" \
  | jq '.versions["'"$WRAPPER_VERSION"'"] | {dependencies, peerDependencies}'

Length of output: 744


Add jsonld peer dependency for @trustvc/w3c-vc bump

Our bump to @trustvc/w3c-vc@^1.3.0-alpha.5 pulls in a new peer dependency on jsonld@^6.0.0, which isn’t declared in our package.json. To avoid install‐time warnings and runtime surprises, please:

• Add "jsonld": "^6.0.0" to your dependencies in package.json.
• Verify no direct or subpath imports of @trustvc/w3c-vc exist (scan passed with no matches).
• Confirm package-lock.json has been updated to @trustvc/w3c-vc@^1.3.0-alpha.5 (it has).
• Note that our @govtechsg/jsonld@0.1.1 wrapper remains unchanged and continues to work as before.

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.

1 participant