chore: update pydid #2527
Merged
chore: update pydid #2527
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
This update includes changes recently committed to the 0.10.X releases, correcting an issue that prevented mediators from handling `didcomm:transport/queue` as a service endpoint. Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
|
Kudos, SonarCloud Quality Gate passed!
|
|
Gentle nudge on this one; this is ready for review @swcurran / @usingtechnology |
swcurran
approved these changes
Oct 5, 2023
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.
This update includes changes recently committed to the 0.10.X releases, correcting an issue that prevented mediators from handling
didcomm:transport/queueas a service endpoint.A small but notable difference between this and the 0.10.X releases: in changes queued for the "next" release, we added
peerdid.peerdidalso depends on pydid. I had to backport fixes to the pydid 0.3.x line to workaround conflicts caused by using 0.4.0 of pydid with peerdid. I'm working with the SICPA team to resolve this. In the meantime, 0.3.9 will work exactly as we need anyways.