Skip to content

Releases: openwallet-foundation/acapy

1.2.0

08 Jan 17:44
@swcurran swcurran
1.2.0
7188b32
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.2.0 Latest
Latest

Release 1.2.0 is a minor update to ACA-Py that contains an update to the AnonCreds implementation to make it easier to deploy on other than Hyperledger Indy, and a lengthy list of adjustments, improvements and fixes, with a focus on removing technical debt. In addition to the AnonCreds updates, the most visible change is the removal of the "in-memory wallet" implementation in favour of using the SQLite in-memory wallet (sqlite://:memory:), including removing the logic for handling that extra wallet type. In removing the in-memory wallet, all of the unit and integration tests that used the in-memory wallet have been updated to use SQLite's in-memory wallet.

Release 1.2.x is the new current Long Term Support (LTS) for ACA-Py, as defined in the LTS Strategy document. With this release, the "end of life" for the previous "current LTS release" -- 0.12 -- is set for October 2025.

The first step to full support of did:webvh ("did:web + Verifiable History"-- formerly did:tdw) has been added to ACA-Py -- a resolver. We're working on improving the new DID Registration mechanism for it, Cheqd and other DID Methods, enabling ACA-Py to be used easily with a variety of DID Methods.

The move to the OpenWallet Foundation is now complete. If you haven't done so already, please update your ACA-Py deployment to use:

A significant testing capability was added in this release -- the ability to run an integration test that includes an ACA-Py upgrade in the middle. This allows us to test, for example starting an agent on one release, doing an upgrade (possibly including running a migration script), and then completing the test on the upgraded release. This is enable by adding a capability to restart Docker containers in the middle of tests. Nice work, @ianco!

What's Changed

Read more

Contributors

ryjones, swcurran, and 8 other contributors
Assets 2
Loading

1.2.0rc0

25 Dec 06:08
@swcurran swcurran
1.2.0rc0
4598b83
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.2.0rc0 Pre-release
Pre-release

Release 1.2.0 is a minor update to ACA-Py that contains an update to the AnonCreds implementation to make it easier to deploy on other than Hyperledger Indy, and a lengthy list of adjustments, improvements and fixes, with a focus on removing technical debt. In addition to the AnonCreds updates, the most visible change is the removal of the "in-memory wallet" implementation in favour of using the SQLite in-memory wallet (sqlite://:memory:), including removing the logic for handling that extra wallet type. In removing the in-memory wallet, all of the unit and integration tests that used the in-memory wallet have been updated to use SQLite's in-memory wallet.

The first step to full support of did:webvh ("did:web + Verifiable History"-- formerly did:tdw) has been added to ACA-Py -- a resolver. We're working on improving the new DID Registration mechanism for it, Cheqd and other DID Methods, enabling ACA-Py to be used easily with a variety of DID Methods.

The move to the OpenWallet Foundation is now complete. For up to date details on what the repo move means for ACA-Py users, including steps for updating deployments, please see latest in GitHub Issue #3250.

A significant testing capability was added in this release -- the ability to run an integration test that includes an ACA-Py upgrade in the middle. This allows us to test, for example starting an agent on one release, doing an upgrade (possibly including running a migration script), and then completing the test on the upgraded release. This is enable by adding a capability to restart Docker containers in the middle of tests. Nice work, @ianco!

1.2.0rc0 Deprecation Notices

The same deprecation notices from the 1.1.0 release about AIP 1.0 protocols still apply. The protocols remain in the 1.2.0 release, but will be moved out of the core and into plugins soon. Please review these notifications carefully!

1.2.0rc0 Breaking Changes

The removal of the "in-memory" wallet implementation might be break some test scripts. Rather than using the in-memory wallet, tests should be updated to use SQLite's special sqlite://:memory: database instead. This results in a better alignment between the Askar storage configuration in test environments and what is used in production.

A fix for a multi-tenancy bug in the holding of VC-LD credentials that resulted in the storing of such credentials in the base wallet versus the intended tenant wallet in included in this release. As part of that fix, PR #3391 impacts those using the GET /vc/credentials endpoint; the response is now an object with a single results attribute where it was previously a flat list.

What's Changed

Read more

Contributors

ryjones, swcurran, and 8 other contributors
Assets 2
Loading

0.12.3

17 Dec 20:21
@swcurran swcurran
0.12.3
24cf926
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.12.3

A patch release to add address a bug found in the Linked Data Verifiable Credential handling for multi-tenant holders. The bug was fixed in the main branch, PR 3391 - BREAKING: VCHolder multitenant binding, and with this release is backported to 0.12 Long Term Support branch. Prior to this release, holder credentials received into a tenant wallet were actually received into the multi-tenant admin wallet.

0.12.3 Breaking Changes

There are no breaking changes in this release.

What's Changed

Full Changelog: 0.12.2...0.12.3

Contributors

swcurran and jamshale
Assets 2
Loading

0.12.3rc0

17 Dec 17:00
@jamshale jamshale
0.12.3rc0
2747b42
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
0.12.3rc0 Pre-release
Pre-release

A patch release to add address a bug found in the Linked Data Verifiable Credential handling for multi-tenant holders. The bug was fixed in the main branch, PR 3391 - BREAKING: VCHolder multitenant binding, and with this release is backported to 0.12 Long Term Support branch. Prior to this release, holders credentials received into a tenant wallet were actually received into the multitenant admin wallet.

0.12.3rc0 Breaking Changes

There are no breaking changes in this release.

What's Changed

Full Changelog: 0.12.2...0.12.3rc0

Contributors

swcurran and jamshale
Assets 2
Loading

1.1.1rc0

04 Dec 00:19
@swcurran swcurran
1.1.1rc0
4559704
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.1.1rc0 Pre-release
Pre-release

Release 1.1.1 is a patch update to ACA-Py that contains a lengthy list of adjustments, improvements and fixes, with a focus on removing Technical Debt. The most visible change is the removal of the "in-memory wallet" implementation in favour of using the SQLite in-memory wallet (sqlite://:memory:), including removing the logic for handling that extra wallet type. While arguably a breaking change (and we mention it below), we're confident no one is using the in-memory wallet (right?!?) any where other than in tests. In removing the in-memory wallet, all of the unit and integration tests that used the in-memory wallet were updated to use SQLite's in-memory wallet.

The first step to full support of did:webvh (for "did:web + Verifiable History" -- formerly called did:tdw) has been added to ACA-Py -- a resolver. We're working on adding new DID Registration for it and other DID Methods, enabling ACA-Py to be used easily with a variety of DID Methods.

The move to the OpenWallet Foundation is now complete. For up to date details on what the repo move means for ACA-Py users, including steps for updating deployments, please see latest in GitHub Issue #3250.

1.1.1 Deprecation Notices

The same deprecation notices from the 1.1.0 release about AIP 1.0 protocols still apply. The protocols remain in the 1.1.1 release, but will be moved out of the core and into plugins soon. Please review these notifications carefully!

1.1.1 Breaking Changes

While there are no breaking changes in this release that might impact production deployments, the removal of the "in-memory" wallet implementation might be break some test scripts. Rather than using the in-memory wallet, tests should be updated to use SQLite's special sqlite://:memory: database instead. This results in a better alignment between tests and a production environment.

What's Changed

Full Changelog: 1.1.0...1.1.1rc0

Contributors

swcurran, esune, and 5 other contributors
Assets 2
Loading

1.1.0

15 Oct 19:42
@swcurran swcurran
1.1.0
3d1682c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.1.0

Release 1.1.0 is the first release of ACA-Py from the OpenWallet Foundation (OWF). The only reason for the release is to test out all of the release publishing actions now that we have moved the repo to its new home (https://github.com/openwallet-foundation/acapy). Almost all of the changes in the release are related to the move.

The move triggered some big changes for those with existing ACA-Py deployments resulting from the change in the GitHub organization (from Hyperledger to OWF) and source code name (from aries_cloudagent to acapy_agent). See the Release 1.1.0 breaking changes for the details.

For up to date details on what the repo move means for ACA-Py users, including steps for updating deployments, please follow the updates in GitHub Issue #3250. We'll keep you informed about the approach, timeline, and progress of the move. Stay tuned!

1.1.0 Deprecation Notices

The same deprecation notices from the 1.0.1 release about AIP 1.0 protocols still apply. The protocols remain in the 1.1.0 release, but will be moved out of the core and into plugins soon. Please review these notifications carefully!

1.1.0 Breaking Changes

The only (but significant) breaking changes in 1.1.0 are related to the GitHub organization and project name changes. Specific impacts are:

  • the renaming of the source code folder from aries_cloudagent to acapy_agent,
  • the publication of the PyPi project under the new acapy_agent name, and
  • the use of the OWF organizational GitHub Container Registry (GHCR) and acapy_agent as the name for release container image artifacts.
    • The patterns for the image tags remain the same as before. So, for example, the new nightly artifact can be found here: [docker pull ghcr.io/openwallet-foundation/acapy-agent:py3.12-nightly](docker pull ghcr.io/openwallet-foundation/acapy-agent:py3.12-nightly).

Anyone deploying ACA-Py should use this release to update their existing deployments. Since there are no other changes to ACA-Py, any issues found should relate back to those changes.

  • Deployments referencing the PyPi project (including those in custom plugins) MUST update their deployments to use the new name.
  • Deployments sourcing the ACA-Py published container image artifacts to GHCR must update their deployments to use the new URLs.

Please note that if and when the current LTS releases (0.11 and 0.12) have new releases, they will continue to use the aries_cloudagent source folder, the existing locations for the PyPi and GHCR container image artifacts.

What's Changed

Full Changelog: 1.0.1...1.1.0

Contributors

swcurran and jamshale
Assets 2
Loading

1.1.0rc1

15 Oct 17:13
@swcurran swcurran
1.1.0rc1
6e2e91e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.1.0rc1 Pre-release
Pre-release

Release 1.1.0 is the first release of ACA-Py from the OpenWallet Foundation (OWF). The only reason for the release is to test out all of the release publishing actions now that we have moved the repo to its new home (https://github.com/openwallet-foundation/acapy). Almost all of the changes in the release are related to the move.

The move triggered some big changes for those with existing ACA-Py deployments resulting from the change in the GitHub organization (from Hyperledger to OWF) and source code name (from aries_cloudagent to acapy_agent). See the Release 1.1.0 breaking changes for the details.

For up to date details on what the repo move means for ACA-Py users, including steps for updating deployments, please follow the updates in GitHub Issue #3250. We'll keep you informed about the approach, timeline, and progress of the move. Stay tuned!

1.1.0rc0 Deprecation Notices

The same deprecation notices from the 1.0.1 release about AIP 1.0 protocols still apply. The protocols remain in the 1.1.0 release, but will be moved out of the core and into plugins soon. Please review these notifications carefully!

1.1.0rc0 Breaking Changes

The only (but significant) breaking changes in 1.1.0 are related to the GitHub organization and project name changes. Specific impacts are:

  • the renaming of the source code folder from aries_cloudagent to acapy_agent,
  • the publication of the PyPi project under the new acapy_agent name, and
  • the use of the OWF organizational GitHub Container Registry (GHCR) and acapy_agent as the name for release container image artifacts.
    • The patterns for the image tags remain the same as before. So, for example, the new nightly artifact can be found here: [docker pull ghcr.io/openwallet-foundation/acapy-agent:py3.12-nightly](docker pull ghcr.io/openwallet-foundation/acapy-agent:py3.12-nightly).

Anyone deploying ACA-Py should use this release to update their existing deployments. Since there are no other changes to ACA-Py, any issues found should relate back to those changes.

  • Deployments referencing the PyPi project (including those in custom plugins) MUST update their deployments to use the new name.
  • Deployments sourcing the ACA-Py published container image artifacts to GHCR must update their deployments to use the new URLs.

Please note that if and when the current LTS releases (0.11 and 0.12) have new releases, they will continue to use the aries_cloudagent source folder, the existing locations for the PyPi and GHCR container image artifacts.

What's Changed

Full Changelog: 1.0.1...1.1.0rc1

Contributors

swcurran and jamshale
Assets 2
Loading

1.1.0rc0

11 Oct 21:21
@swcurran swcurran
1.1.0rc0
79fd911
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.1.0rc0 Pre-release
Pre-release

Release 1.1.0 is the first release of ACA-Py from the OpenWallet Foundation (OWF). The only reason for the release is to test out all of the release publishing actions now that we have moved the repo to its new home (https://github.com/openwallet-foundation/acapy). Almost all of the changes in the release are related to the move.

The move triggered some big changes for those with existing ACA-Py deployments resulting from the change in the GitHub organization (from Hyperledger to OWF) and source code name (from aries_cloudagent to acapy_agent). See the Release 1.1.0 breaking changes for the details.

For up to date details on what the repo move means for ACA-Py users, including steps for updating deployments, please follow the updates in GitHub Issue #3250. We'll keep you informed about the approach, timeline, and progress of the move. Stay tuned!

1.1.0rc0 Deprecation Notices

The same deprecation notices from the 1.0.1 release about AIP 1.0 protocols still apply. The protocols remain in the 1.1.0 release, but will be moved out of the core and into plugins soon. Please review these notifications carefully!

1.1.0rc0 Breaking Changes

The only (but significant) breaking changes in 1.1.0 are related to the GitHub organization and project name changes. Specific impacts are:

  • the renaming of the source code folder from aries_cloudagent to acapy_agent,
  • the publication of the PyPi project under the new acapy_agent name, and
  • the use of the OWF organizational GitHub Container Registry (GHCR) and acapy_agent as the name for release container image artifacts.
    • The patterns for the image tags remain the same as before. So, for example, the new nightly artifact can be pulled by: docker pull ghcr.io/openwallet-foundation/acapy-agent:py3.12-nightly.

Anyone deploying ACA-Py should use this release to update their existing deployments. Since there are no other changes to ACA-Py, any issues found should relate back to those changes.

  • Deployments referencing the PyPi project (including those in custom plugins) MUST update their deployments to use the new name.
  • Deployments sourcing the ACA-Py published container image artifacts to GHCR must update their deployments to use the new URLs.

Please note that if and when the current LTS releases (0.11 and 0.12) have new releases, they will continue to use the aries_cloudagent source folder, the existing locations for the PyPi and GHCR container image artifacts.

1.1.0rc0 Categorized List of Pull Requests

What's Changed

Full Changelog: 1.0.1...1.1.0rc0

Contributors

swcurran and jamshale
Assets 2
Loading

1.0.1

08 Oct 21:38
@swcurran swcurran
1.0.1
06d1cf8
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.0.1

Release 1.0.1 will be the last release of ACA-Py from the Hyperledger organization before the repository moves to the OpenWallet Foundation (OWF). Soon after this release, the ACA-Py project and this repository will move to the OWF's GitHub organization as the new "acapy" project.

For details on what this means for ACA-Py users, including steps for updating deployments, please follow the updates in GitHub Issue #3250. We'll keep you informed about the approach, timeline, and progress of the move. Stay tuned!

The 1.0.1 release contains mostly internal clean ups, technical debt elimination, and a revision to the integration testing approach, incorporating the Aries Agent Test Harness tests in the ACA-Py continuous integration testing process. There are substantial enhancements in the management of keys and their use with VC-DI proofs, and web-based DID methods like did:web. See the Wallet and Key Handling updates in the categorized PR list below.

There are several important deprecation notices in this release in preparation for the next ACA-Py release. Please review these notifications carefully!

In an attempt to shorten the categorized list of PRs in the release, rather than listing all of the dependabot PRs in the release, we've included a link to a list of those PRs.

Deprecation Notices

  • ACA-Py will soon be moved from the Hyperledger GitHub organization to that of the OpenWallet Foundation. As such, there will be changes in the names and locations of the artifacts produced -- the PyPi project and the container images in the GitHub Container Registry. We will retain the ability to publish LTS releases of ACA-Py for the current LTS versions (0.11, 0.12) in the current locations. For details, guidance, timing, and progress on the move, please monitor the description of GitHub Issue #3250 that will be maintained throughout the process.
  • In the next ACA-Py release, we will be dropping from the core ACA-Py repository the AIP 1.0 RFC 0160 Connections, [RFC 0037 Issue Credentials v1.0] and [RFC 0037 Present Proof v1.0] DIDComm protocols. Each of the protocols will be moved to the [ACA-Py Plugins] repo. All deployers that use those protocols SHOULD update to the AIP 2.0 versions of those protocols (RFC 0434 Out of Band+RFC 0023 DID Exchange, RFC 0453 Issue Credential v2.0 and RFC 0454 Present Proof v2.0, respectively). Once the protocols are removed from ACA-Py, anyone still using those protocols MUST adjust their configuration to load those protocols from the respective plugins.

1.0.1 Breaking Changes

There are no breaking changes in ACA-Py Release 1.0.1.

What's Changed

Read more

Contributors

rngadam, swcurran, and 10 other contributors
Assets 2
Loading

1.0.1rc1

01 Oct 20:21
@swcurran swcurran
1.0.1rc1
db5ead3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.
Compare
Choose a tag to compare
1.0.1rc1 Pre-release
Pre-release

Release 1.0.1 might be the last release of ACA-Py from the Hyperledger organization before the repository moves to the OpenWallet Foundation (OWF). As noted in the repository README.md, the ACA-Py project will soon be moving soon to the OWF's GitHub organization as the new "acapy" project.

For details on what this means for ACA-Py users, including steps for updating deployments, please follow the updates in GitHub Issue #3250. We'll keep you informed about the approach, timeline, and progress of the move. Stay tuned!

The release contains mostly internal clean ups, technical debt elimination, and a revision to the integration testing approach, incorporating the Aries Agent Test Harness tests in the ACA-Py continuous integration testing process. There are substantial enhancements in the management of keys and their use with VC-DI proofs, and web-based DID methods like did:web. See the Wallet and Key Handling updates in the categorized PR list below.

There are several important deprecation notices in this release in preparation for the next ACA-Py release. Please review these notifications carefully!

In an attempt to shorten the categorized list of PRs in the release, rather than listing all of the dependabot PRs in the release, we've included a link to a list of those PRs.

Deprecation Notices

  • ACA-Py will soon be moved from the Hyperledger GitHub organization to that of the OpenWallet Foundation. As such, there will be changes in the names and locations of the artifacts produced -- the PyPi project and the container images in the GitHub Container Registry. We will retain the ability to publish LTS releases of ACA-Py for the current LTS versions (0.11, 0.12) in the current locations. For details, guidance, timing, and progress on the move, please monitor the description of GitHub Issue #3250 that will be maintained throughout the process.
  • In the next ACA-Py release, we will be dropping from the core ACA-Py repository the AIP 1.0 RFC 0160 Connections, [RFC 0037 Issue Credentials v1.0] and [RFC 0037 Present Proof v1.0] DIDComm protocols. Each of the protocols will be moved to the [ACA-Py Plugins] repo. All deployers that use those protocols SHOULD update to the AIP 2.0 versions of those protocols (RFC 0434 Out of Band+RFC 0023 DID Exchange, RFC 0453 Issue Credential v2.0 and RFC 0454 Present Proof v2.0, respectively). Once the protocols are removed from ACA-Py, anyone still using those protocols must adjust their configuration to load those protocols from the respective plugins.

1.0.1rc1 Breaking Changes

There are no breaking changes in ACA-Py Release 1.0.1.

What's Changed

Read more

Contributors

rngadam, swcurran, and 9 other contributors
Assets 2
Loading