jamshale
jamshale
Closing due to the fix being merged from our end via https://github.com/hyperledger/aries-cloudagent-python/pull/3050
One of the trickier things is the LTS. When we fork the `openwallet-foundation` repo back to `hyperledger` we'll need to change the name back to `aries-cloudagent-python` and adjust the github...
You can manually publish both the pypi package and the ghrc.io images. For pypi you need the publishing account username/password and for ghrc.io you need a repo PAT with package:read,write,delete...
Another thing to consider is changing the project and package name will change the references in plugins. For the managed plugin repo we can do this ourselves but in unmanaged...
I didn't describe this very well. The forking back will work yes if we do it before merging the PR's, but I'm pretty sure we lose the github secrets and...
I think this is a good approach. It makes things a lot simpler. We could possibly generate the 0.11.lts and 0.12.lts artifacts for the new package and image names as...
This is complete...
So many configs... Guess the flag wasn't tested. I'll wait and see if Emiliano knows an easy way to fix it.
I don't use, or really understand the need for the in-memory wallet so I'm all for removing the complexity.