-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consume web5-kt 1.1.0 #241
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #241 +/- ##
=======================================
Coverage 84.28% 84.28%
=======================================
Files 38 38
Lines 1107 1107
Branches 115 115
=======================================
Hits 933 933
Misses 122 122
Partials 52 52
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just 1 q about Pom.xml
@@ -17,7 +17,7 @@ | |||
the version "version.xyz.block.web5" set this web5-parent. When updating Web5, update both | |||
this version *and* the <version.xyz.block.web5> below in the <properties> section. | |||
--> | |||
<version>1.0.0</version> | |||
<version>1.1.0</version> | |||
</parent> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need to update this version number ourselves? @ALRubinger
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, if we're upgrading tbdex-kt
to web5-kt:1.1.0
, updating the version number in both places as this PR does is the right way.
Are the comments in the POM not describing that clearly enough? If not, let's update the comments!
This will consume web5-kt 1.0.0
This change has
credentialSchema
field in the vc data model