Aries-cloudagent

Latest version: v0.12.1

Safety actively analyzes 631310 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 8

0.10.4

Not secure
- DID Handling and Connection Establishment Updates/Fixes
- fix: routing behind mediator [\2536](https://github.com/hyperledger/aries-cloudagent-python/pull/2536) [dbluhm](https://github.com/dbluhm)
- Release management pull requests
- 0.10.4 [\2539](https://github.com/hyperledger/aries-cloudagent-python/pull/2539) [swcurran](https://github.com/swcurran)

0.10.3

Not secure
- Credential Exchange (Issue, Present) Updates
- Feat: Upgrade from tags and fix issue with legacy IssuerRevRegRecords [<=v0.5.2] [\2486](https://github.com/hyperledger/aries-cloudagent-python/pull/2486) [shaangill025](https://github.com/shaangill025)
- Release management pull requests
- 0.10.3 [\2522](https://github.com/hyperledger/aries-cloudagent-python/pull/2522) [swcurran](https://github.com/swcurran)

0.10.2

Not secure

0.10.1

Not secure

0.10.0

Not secure
same name. We immediately released 0.10.1 as a replacement.

0.9.0

Not secure
on the now archived Hyperledger Ursa project to its updated, improved
replacement, [AnonCreds CL-Signatures]. This important change is ONLY available
when using [Aries Askar] as the wallet type, which brings in both [Indy VDR] and
the CL-Signatures via the latest version of [CredX from the indy-shared-rs
repository]. The update is **NOT** available to those that are using the [Indy
SDK]. All new deployments of ACA-Py SHOULD use [Aries Askar]. Further, we
**strongly** recommend that all deployments using the [Indy SDK] with ACA-Py
upgrade their installation to use [Aries Askar] and the related components using
the migration scripts available. An [Indy SDK to Askar migration document] added
to the [aca-py.org] documentation site, and a deprecation warning added to the
ACA-Py startup.

[AnonCreds CL-Signatures]: https://github.com/hyperledger/anoncreds-rs
[Aries Askar]: https://github.com/hyperledger/aries-askar
[CredX from the indy-shared-rs repository]: https://github.com/hyperledger/indy-shared-rs
[Indy SDK]: https://github.com/hyperledger/indy-sdk
[Indy SDK to Askar migration document]: https://aca-py.org/main/deploying/IndySDKtoAskarMigration/
[aca-py.org]: https://aca-py.org

The second big change in this release is that we have upgraded the primary
Python version from 3.6 to 3.9 (PR [\2247]). In this case, primary means that
Python 3.9 is used to run the unit and integration tests on all Pull Requests.
We also do nightly runs of the main branch using Python 3.10. As
of this release we have **dropped** Python 3.6, 3.7 and 3.8, and introduced new
dependencies that are not supported in those versions of Python. For those that
use the published ACA-Py container images, the upgrade should be easily handled.
If you are pulling ACA-Py into your own image, or a non-containerized
environment, this is a breaking change that you will need to address.

Please see the next section for all breaking changes, and the subsequent section
for a categorized list of all pull requests in this release.

Breaking Changes

In addition to the breaking Python 3.6 to 3.9 upgrade, there are two other
breaking changes that may impact some deployments.

[\2034] allows for additional flexibility in using public DIDs in invitations,
and adds a restriction that "implicit" invitations must be proactively enabled
using a flag (`--requests-through-public-did`). Previously, such requests
would always be accepted if `--auto-accept` was enabled, which could lead to
unexpected connections being established.

[\2170] is a change to improve message handling in the face of delivery errors
when using a persistent queue implementation such as the [ACA-Py Redis Plugin].
If you are using the Redis plugin, you **MUST** upgrade to [Redis Plugin Release

Page 2 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.