Releases: sudoplatform-labs/sudo-di-cloud-agent-js
Releases · sudoplatform-labs/sudo-di-cloud-agent-js
0.6.4
- Pull SDK up to use version 0.700.400 of The Anonyome fork of Aries Cloud Agent Python (i.e. ACA-py V0.7.4 equivalent)
- Pull SDK up to use version 100.700.200 of Anonyome fork of the VON Network (i.e. VON-network V1.7.2 equivalent)
- This release also now requires Use of Docker Compose V2 in the running Docker Desktop (i.e. V1 to V2 of Docker Compose changed the naming scheme for containers replacing _ with -).
0.6.3
- Pull SDK up to use version 0.700.300 of The Anonyome fork of Aries Cloud Agent Python (i.e. ACA-py V0.7.3 equivalent)
- This release also resolves the CORs issue when using the x-api-key header from a web UI
0.6.2
- Pull SDK up to use version 0.700.200 of The Anonyome fork of Aries Cloud Agent Python (i.e. ACA-py V0.7.2 equivalent)
0.6.1
- Fix a packaging issue with acapy.json config file where the previous 0.5.4 docker images would be pulled by
di-env
0.6.0
- This minor release updates the di-env tool to work with Docker Desktop 4.1.x on MacOS. Primarily it fixes an issue where the genesis file contents produced by VON Network contains node addresses that were not reachable by the Cloud Agent running in a Docker Desktop 4.1.x environment on MacOS
0.5.4
- Update the devDependencies to latest versions to remove security vulnerability warning from dependant about set-value
0.5.3
- Minor change to allow di-env to get the cloud agent and von host address to be set by an environment variable so that it can be more easily used in gitlab docker-in-docker test environments.
0.5.2
- Fix issue where
di-env up
failed to pull correct version of sudo-di-cloud-agent from public repository
0.5.1
- Correct duplicate publish of sudo-di-cloud-agent image as sudo-di-tails-server image
- Correct pipeline issue which prevented wrappers from being published to npmjs
0.5.0
- Adds an indy-tails-server docker image to work with the aca-py agent and is automatically configured on `di-env up. This supports development of applications wanting to implement Indy Revocable Credentials.
- Now uses more docker-compose functionality instead of completely hand coded scripts to bring up the di-env development environment.
- Supports the ability to
stop
the development environment and laterstart
it which will maintain state (i.e. Ledger and Wallet data remains after thestop
start
sequence whereas thedown
command removes all state. - Now supports the extra
-v
option ondi-env up
which allows setting of logging levels in ACA-py and the Tails-Server - Supports new
di-env logs
command which will monitor and output the combined log messages from ACA-py and the Tails-server - NOTE: the
di-env start
command has becomedi-env up
. This is more consistent with the semantics of docker-compose which should be more familiar to people.