Merge pull request #4054 from swcurran/1.5.1rc0

1.5.1rc0

Author: swcurran

CHANGELOG.md

@@ -1,5 +1,40 @@
 # ACA-Py Changelog
 
+## 1.5.1rc0
+
+### February 20, 2026
+
+ACA-Py 1.5.1 is a clean up release primarily to address some follow-on issues related to the [1.5.0] release -- notably with the handling of AnonCreds revocation. There are some  convenience additions and a GitHub Actions pipeline fix.
+
+[1.5.0]: https://github.com/openwallet-foundation/acapy/releases/tag/1.5.0
+
+### 1.5.1 Breaking Changes
+
+There are no breaking changes in this release from [1.5.0]. Those upgrading from a version prior to [1.5.0] should review the [1.5.0] Breaking Changes section for details about the breaking changes introduced in [1.5.0].
+
+### 1.5.1 Deprecation Notices
+
+The `acapy_agent.revocation_anoncreds` package has been deprecated and relocated to `acapy_agent.anoncreds.revocation` for improved consistency across the codebase. The change should only affect [ACA-Py Plugins] that implement AnonCreds, but other developers should also take note.
+
+The `wallet-type` configuration value `askar` is now deprecated and all deployments still using that wallet type should migrate to either the `askar-anoncreds` or (ideally) `kanon-anoncreds` wallet types.
+
+AIP 1.0 protocols that were [previously announced as deprecated](#140-deprecation-notices) have now been removed from ACA-Py core. Implementers still using those protocols **MUST** adjust their configuration to load those protocols from the respective plugins, or better, upgrade to their AIP 2.0 equivalents.
+
+### 1.5.1 Categorized PR List
+
+- **Core Platform and Architecture**
+  - Enable outbound transport in `--no-transport` mode, only disable inbound [\#4050](https://github.com/openwallet-foundation/acapy/pull/4050) [PatStLouis](https://github.com/PatStLouis)
+  - feat: add list endpoint for out-of-band records [\#4046](https://github.com/openwallet-foundation/acapy/pull/4046) [kukgini](https://github.com/kukgini)
+- **AnonCreds, Revocation, and Wallet Migration**
+  - Fix revocation setup [\#4047](https://github.com/openwallet-foundation/acapy/pull/4047) [PatStLouis](https://github.com/PatStLouis)
+  - fix: handle revocation registry race conditions for BDD integration tests [\#4056](https://github.com/openwallet-foundation/acapy/pull/4056) [PatStLouis](https://github.com/PatStLouis)
+- **Testing, Logging, and Diagnostics**
+  - FIX BDD interop integration tests [\#4052](https://github.com/openwallet-foundation/acapy/pull/4052) [PatStLouis](https://github.com/PatStLouis)
+- **Dependabot PRs**
+  - [Link to list of Dependabot PRs in this release](https://github.com/openwallet-foundation/acapy/pulls?q=is%3Apr+is%3Amerged+merged%3A2025-01-29..2026-02-20+author%3Aapp%2Fdependabot+)
+- **Release management pull requests**:
+  - 1.5.1rc0 [\#4054](https://github.com/openwallet-foundation/acapy/pull/4054) [swcurran](https://github.com/swcurran)
+
 ## 1.5.0
 
 ### January 29, 2026

Managing-ACA-Py-Doc-Site.md

@@ -20,7 +20,7 @@ and mkdocs configuration.
 
 When the GitHub Action fires, it runs a container that carries out the following steps:
 
-- Checks out the triggering branch, either `main` or `docs-v<version>` (e.g `docs-v1.5.0`).
+- Checks out the triggering branch, either `main` or `docs-v<version>` (e.g `docs-v1.5.1`).
 - Runs the script [scripts/prepmkdocs.sh], which moves and updates some of the
   markdown files so that they fit into the generated site. See the comments in
   the scripts for details about the copying and editing done via the script. In
@@ -97,7 +97,7 @@ To delete the documentation version, do the following:
 - Check your `git status` and make sure there are no changes in the branch --
   e.g., new files that shouldn't be added to the `gh-pages` branch. If there are
   any -- delete the files so they are not added.
-- Remove the folder for the RC.  For example `rm -rf 1.5.0rc1`
+- Remove the folder for the RC.  For example `rm -rf 1.5.1rc0`
 - Edit the `versions.json` file and remove the reference to the RC release in
   the file.
 - Push the changes via a PR to the ACA-Py `gh-pages` branch (don't PR them into

PUBLISHING.md

@@ -6,7 +6,7 @@ a major, minor or patch release, per [semver](https://semver.org/) rules.
 
 Once ready to do a release, create a local branch that includes the following updates:
 
-1. Create a local PR branch from an updated `main` branch, e.g. "1.5.0".
+1. Create a local PR branch from an updated `main` branch, e.g. "1.5.1".
 
 2. See if there are any Document Site `mkdocs` changes needed. Run the script
    `./scripts/prepmkdocs.sh; mkdocs`. Watch the log, noting particularly if
@@ -146,15 +146,15 @@ For the build test, the RTD Sphinx theme needs to be added to the docker image,
 
    Published images are automatically tagged with multiple tags for flexibility:
 
-   - **Regular Releases** (e.g., `1.5.0`):
-     - `py3.12-1.5.0` - Python version specific tag
-     - `1.5.0` - Semantic version tag
+   - **Regular Releases** (e.g., `1.5.1`):
+     - `py3.12-1.5.1` - Python version specific tag
+     - `1.5.1` - Semantic version tag
      - `1.5` - Major.minor tag (moves to latest patch release)
      - `latest` - Only assigned if this is the highest semantic version
 
-   - **Release Candidates** (e.g., `1.5.0rc1`):
-     - `py3.12-1.5.0rc1` - Python version specific RC tag
-     - `1.5.0rc1` - Semantic version RC tag
+   - **Release Candidates** (e.g., `1.5.1rc0`):
+     - `py3.12-1.5.1rc0` - Python version specific RC tag
+     - `1.5.1rc0` - Semantic version RC tag
      - **Note**: RC releases do NOT receive major.minor (`1.5`) or `latest` tags
 
    The `latest` tag is explicitly managed by comparing semantic versions across all
@@ -179,7 +179,7 @@ For the build test, the RTD Sphinx theme needs to be added to the docker image,
 [publish.yml]: https://github.com/openwallet-foundation/acapy/blob/main/.github/workflows/publish.yml
 
 12. When a new release is tagged, create a new branch at the same commit with
-    the branch name in the format `docs-v<version>`, for example, `docs-v1.5.0`.
+    the branch name in the format `docs-v<version>`, for example, `docs-v1.5.1`.
     The creation of the branch triggers the execution of the [publish-docs]
     GitHub Action which generates the documentation for the new release,
     publishing it at [https://aca-py.org]. The GitHub Action also executes when

docs/deploying/ContainerImagesAndGithubActions.md

@@ -42,15 +42,15 @@ Click [here](https://github.com/openwallet-foundation/acapy/pkgs/container/acapy
 
 The following is the ACA-Py container images tagging format:
 
-**Regular Releases** (e.g., `1.5.0`):
- - `py3.12-1.5.0` - Python version specific tag
- - `1.5.0` - Semantic version tag
+**Regular Releases** (e.g., `1.5.1`):
+ - `py3.12-1.5.1` - Python version specific tag
+ - `1.5.1` - Semantic version tag
  - `1.5` - Major.minor tag (moves to latest patch release)
  - `latest` - Only assigned if this is the highest semantic version
 
-**Release Candidates** (e.g., `1.5.0rc1`):
- - `py3.12-1.5.0rc1` - Python version specific RC tag
- - `1.5.0rc1` - Semantic version RC tag
+**Release Candidates** (e.g., `1.5.1rc0`):
+ - `py3.12-1.5.1rc0` - Python version specific RC tag
+ - `1.5.1rc0` - Semantic version RC tag
  - **Note**: RC releases do NOT receive major.minor (`1.5`) or `latest` tags
 
 **Nightly Builds**: