feat: Allow legacy didcomm connection context#2679
Merged
genaris merged 2 commits intoopenwallet-foundation:mainfrom Mar 3, 2026
Merged
feat: Allow legacy didcomm connection context#2679genaris merged 2 commits intoopenwallet-foundation:mainfrom
genaris merged 2 commits intoopenwallet-foundation:mainfrom
Conversation
Signed-off-by: jamshale <jamiehalebc@gmail.com>
|
Contributor
|
Makes sense! |
genaris
approved these changes
Mar 3, 2026
This file contains hidden or 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
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.
At bc gov we have existing issuance/verification applications still on the legacy connections protocol. We are transitioning them off of it, but, would like to maintain backwards compatibility with the did_doc context which is in production.
This is a problem with bifold completing legacy connections when upgrading to credo 0.6.x