Change did:tdw resolver naming to did:webvh#3429
Change did:tdw resolver naming to did:webvh#3429dbluhm merged 3 commits intoopenwallet-foundation:mainfrom
Conversation
642d514 to
e2a68c5
Compare
Signed-off-by: jamshale <jamiehalebc@gmail.com>
Signed-off-by: jamshale <jamiehalebc@gmail.com>
e2a68c5 to
4926b5b
Compare
|
|
A new release for did-tdw 0.2.2 is on pypi but did-webvh is still 0.2.1 With all that said - So @jamshale @swcurran @dbluhm I would like to propose reverting this PR, meaning the old did-tdw name will be used in the meantime, so that we can upgrade askar to the latest release instead. A side-effect is this will unblock #3173, which has been waiting 6 months for a new askar release (!) If it causes unnecessary work to revert this, and a new did-webvh release can be prepared in due time, then I'd say that's ok, and up to you whether we wait or not. I can pull all the upgrades into our acapy fork manually. I'm just looking forward to rebasing our fork being less of a headache 😄 since we're using #3173 and a bunch of other customized things. |
|
We should be able to get a new release of did_webvh out soon. I'd rather not revert this. I'm not sure what's taking so long to get a simple askar upgrade for did_webvh. This has been a bit more annoying than I thought, though. It might be better to completely remove the resolver from acapy and only have it in the plugin instead. |
|
Alright -- I see that decentralized-identity/didwebvh-py#19 has gotten a few approvals since I last looked yesterday, so hopefully a new did-webvh release is just around the corner |
|
I don't know why but the did_webvh 0.2.2 library publish failed. Just trying to get it published and then we can get askar upgraded. We don't need the big PR finished to move ahead on this. |



Changes the
tdwresolver to the newwebvhnaming.