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_cloudagenttoacapy_agent, - the publication of the PyPi project under the new
acapy_agentname, and - the use of the OWF organizational GitHub Container Registry (GHCR) and
acapy_agentas 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
- Update MDs and release publishing files to reflect the repo move to OWF by @swcurran in #3270
- General repo updates post OWF move. by @jamshale in #3267
- Fix interop test fork location replacement by @jamshale in #3280
- Update interop fork location after AATH update by @jamshale in #3282
- 1.1.0rc0 by @swcurran in #3284
- Change pypi upload workflow to use pypa/gh-action-pypi-publish by @jamshale in #3291
- 1.1.0rc1 by @swcurran in #3292
- 1.1.0 by @swcurran in #3294
Full Changelog: 1.0.1...1.1.0
