Feature/336 upgrade to veramo 2 #396
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… custom test environment
…SDK into feature/336-upgrade-to-veramo-2
…grade-to-veramo-2
This was referenced Aug 5, 2024
Closed
sadiabbasi
reviewed
Aug 14, 2024
| debug(`Credential verified`, result.verified); | ||
| } | ||
|
|
||
| export async function veramo2() { |
There was a problem hiding this comment.
veramo and veramo2 name.. may be we can update this name?
|
🎉 This PR is included in version 0.21.0-development.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 0.22.0-development.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 0.22.0-rc.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 0.22.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
did-resolver,did-jwtanddid-jwt-vcpackages from DIF repo, instead of the outdated@tonomy/did-...bundles Upgrade to latest did-jwt #336antelope-did-resolverafter it was upgraded Upgrade all packages and migrate to using nobel for cryptography antelope-did-resolver#15jsdomandjsdom-urlpackage as not needed in latest jest. Added jsdom dependencies in./test/test.setup.tsand removed jest custom environmentjest.config.tsyarn run clialso using ESM bundlesveramo.tsand unit tests. to ensure we are ready for next tasks that depended on this upgrade Upgrade to use Veramo library #337 to be ready for Upgrade to use latest did-resolver, did-jwt and did-jwt-vc libraries Tonomy-ID#758did-jwk.tsand upgraded to usedid-key.tsinstead. this solves Reduce URL down to below recommended sizes #316APIandutilsbuilds and conditional exportsbase64.tshelper functions and unit testseslintto use the new configuration file and conventions. Also removing and updating config dependency packagesExternalUser.getIssuer()using the wrongkeyManager