Skip to content
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.

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

Update dependencies and add did:jwk test. #116

Merged
merged 1 commit into from
Oct 3, 2024
Merged

Update dependencies and add did:jwk test. #116

merged 1 commit into from
Oct 3, 2024

Conversation

dlongley
Copy link
Member

@dlongley dlongley commented Oct 3, 2024

No description provided.

@dlongley dlongley merged commit 6b90ac8 into main Oct 3, 2024
4 checks passed
@dlongley dlongley deleted the update-deps branch October 3, 2024 01:37
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.89%. Comparing base (ad25433) to head (fd65218).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #116   +/-   ##
=======================================
  Coverage   81.89%   81.89%           
=======================================
  Files          15       15           
  Lines        4274     4274           
=======================================
  Hits         3500     3500           
  Misses        774      774           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ad25433...fd65218. Read the comment docs.

@@ -16,7 +16,7 @@
"@bedrock/credentials-context": "^5.0.2",
"@bedrock/data-integrity-context": "^4.0.3",
"@bedrock/did-context": "^6.0.0",
"@bedrock/did-io": "^10.3.1",
"@bedrock/did-io": "10.4",
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this should be "^10.4.0"?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, I'll push a fix for that. That's weird -- I'm guessing there's an npm command I ran while trying to force it to update its cache that did that and I wasn't expecting it.

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