1.3.0rc0 (openwallet-foundation#3604)

* 1.3.0rc0

Signed-off-by: Stephen Curran <swcurran@gmail.com>

* Additional Changelog notes

Signed-off-by: Stephen Curran <swcurran@gmail.com>

* Add PR to the list

Signed-off-by: Stephen Curran <swcurran@gmail.com>

* Adjustments to the API changes section

Signed-off-by: Stephen Curran <swcurran@gmail.com>

---------

Signed-off-by: Stephen Curran <swcurran@gmail.com>

Author: swcurran

CHANGELOG.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.2.1`).
+- Checks out the triggering branch, either `main` or `docs-v<version>` (e.g `docs-v1.3.0`).
 - 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.2.1rc0`
+- Remove the folder for the RC.  For example `rm -rf 1.3.0rc0`
 - 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

Managing-ACA-Py-Doc-Site.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.2.1".
+1. Create a local PR branch from an updated `main` branch, e.g. "1.3.0rc0".
 
 2. See if there are any Document Site `mkdocs` changes needed. Run the script
    `./scripts/prepmkdocs.sh; mkdocs`. Watch the log, noting particularly if
@@ -140,7 +140,7 @@ Once you have the list of PRs:
 [publish-indy.yml]: https://github.com/openwallet-foundation/acapy/blob/main/.github/workflows/publish-indy.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.2.1`.
+    the branch name in the format `docs-v<version>`, for example, `docs-v1.3.0rc0`.
     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

PUBLISHING.md

@@ -51,8 +51,8 @@ the [LTS strategy](./LTS-Strategy.md).
 
 Current LTS releases:
 
-- Release [1.2](https://github.com/openwallet-foundation/acapy/releases/tag/1.2.1) **Current LTS Release**
-- Release [0.12](https://github.com/openwallet-foundation/acapy/releases/tag/0.12.3) **End of Life: October 2025**
+- Release [1.2](https://github.com/openwallet-foundation/acapy/releases/tag/1.2.4) **Current LTS Release**
+- Release [0.12](https://github.com/openwallet-foundation/acapy/releases/tag/0.12.6) **End of Life: October 2025**
 
 Past LTS releases:
 

README.md

@@ -60,6 +60,8 @@
     "unflatten",
     "yaml",
     "uuid_utils",
+    "did_webvh",
+    "canonicaljson",
 ]
 
 #    "acapy_agent.tests.test_conductor",
@@ -72,7 +74,7 @@
 # -- Project information -----------------------------------------------------
 
 project = "ACA-Py"
-copyright = "2024, Province of British Columbia"
+copyright = "2025, Province of British Columbia"
 author = "Province of British Columbia"
 
 # The short X.Y version
@@ -226,7 +228,6 @@
         "ACA-Py",
         "ACA-Py Documentation",
         author,
-        "ACA-Py",
         "A Decentralized Trust Agent implemented in Python and\
         suitable for use in (almost) any non-mobile environment.",
         "Miscellaneous",

docs/conf.py

@@ -8,7 +8,7 @@ ACA-Py or the repository `main` branch. Reminders (and PRs!) to update this page
 welcome! If you have any questions, please contact us on the #aries channel on
 [OpenWallet Foundation Discord](https://discord.gg/openwallet-foundation) or through an issue in this repo.
 
-**Last Update**: 2025-01-21, Release 1.2.1
+**Last Update**: 2025-03-20, Release 1.3.0rc0
 
 > The checklist version of this document was created as a joint effort
 > between [Northern Block](https://northernblock.io/), [Animo Solutions](https://animo.id/) and the Ontario government, on behalf of the Ontario government.
@@ -21,7 +21,7 @@ ACA-Py and other decentralized trust Frameworks and Agents.
 
 | AIP Version | Supported | Notes |
 |  - | :-------: | -------- |
-| AIP 1.0     | :white_check_mark:  | Fully supported. Deprecation notices published|
+| AIP 1.0     | :white_check_mark:  | Partially supported. Deprecation notices published, Connections protocol moved into an [ACA-Py Plugin](https://plugins.aca-py.org/latest/connections/)|
 | AIP 2.0     | :white_check_mark:  | Fully supported. |
 
 A summary of the Aries Interop Profiles and Aries RFCs supported in ACA-Py can be found [later in this document](#supported-rfcs).
@@ -112,22 +112,22 @@ A summary of the Aries Interop Profiles and Aries RFCs supported in ACA-Py can b
 
 ### AIP 1.0
 
-All RFCs listed in [AIP
-1.0](https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0302-aries-interop-profile#aries-interop-profile-version-10)
+Most RFCs listed in [AIP
+1.0](https://identity.foundation/aries-rfcs/latest/concepts/0302-aries-interop-profile/#aries-interop-profile-version-10)
 are fully supported in ACA-Py, but deprecation and removal of some of the
 protocols has begun. The following table provides notes about the implementation
 of specific RFCs.
 
 | RFC | Supported | Notes |
 | --- | :--: | -- |
 | [0025-didcomm-transports](https://github.com/hyperledger/aries-rfcs/tree/b490ebe492985e1be9804fc0763119238b2e51ab/features/0025-didcomm-transports)      | :white_check_mark:        | ACA-Py currently supports HTTP and WebSockets for both inbound and outbound messaging. Transports are pluggable and an agent instance can use multiple inbound and outbound transports.|
-| [0160-connection-protocol](https://github.com/hyperledger/aries-rfcs/tree/9b0aaa39df7e8bd434126c4b33c097aae78d65bf/features/0160-connection-protocol)    | :white_check_mark:        | **DEPRECATED** In the next release, the protocol will be removed. The protocol will continue to be available as an [ACA-Py plugin], but those upgrading to that pending release and continuing to use this protocol will need to include the plugin in their deployment configuration. Users **SHOULD** upgrade to the equivalent [AIP 2.0] protocols as soon as possible. |
+| [0160-connection-protocol](https://github.com/hyperledger/aries-rfcs/tree/9b0aaa39df7e8bd434126c4b33c097aae78d65bf/features/0160-connection-protocol)    | :x:        | **MOVED TO PLUGIN** The protocol has been moved into the [ACA-Py plugin] repository. Those upgrading to Release 1.3.0 or later and continuing to use this protocol **MUST** include the [Connections plugin](https://plugins.aca-py.org/latest/connections/) in their deployment configuration. Users **SHOULD** upgrade to the equivalent [AIP 2.0] protocols as soon as possible. |
 | [0036-issue-credential-v1.0](https://github.com/hyperledger/aries-rfcs/tree/bb42a6c35e0d5543718fb36dd099551ab192f7b0/features/0036-issue-credential)    | :white_check_mark:        | **DEPRECATED** In the next release, the protocol will be removed. The protocol will continue to be available as an [ACA-Py plugin], but those upgrading to that pending release and continuing to use this protocol will need to include the plugin in their deployment configuration. Users **SHOULD** upgrade to the equivalent [AIP 2.0] protocols as soon as possible.  |
 | [0037-present-proof-v1.0](https://github.com/hyperledger/aries-rfcs/tree/4fae574c03f9f1013db30bf2c0c676b1122f7149/features/0037-present-proof)    | :white_check_mark:        | **DEPRECATED** In the next release, the protocol will be removed. It will continue to be available as an [ACA-Py plugin], but those upgrading to that pending release and continuing to use this protocol will need to include the plugin in their deployment configuration. Users **SHOULD** upgrade to the equivalent [AIP 2.0] protocols as soon as possible. |
 
 [ACA-Py plugin]: https://plugins.aca-py.org
 
-[AIP 2.0]: https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0302-aries-interop-profile#aries-interop-profile-version-20
+[AIP 2.0]: https://identity.foundation/aries-rfcs/latest/concepts/0302-aries-interop-profile/#aries-interop-profile-version-20
 
 ### AIP 2.0
 

docs/features/SupportedRFCs.md

@@ -29,7 +29,7 @@ drill into the modules, subpackages and submodules that make up ACA-Py.
 Developers that are interested in what DIDComm protocols are supported in ACA-Py
 should take a look at the `protocols <generated/acapy_agent.protocols.html>`_ package. 
 These should align with the corresponding
-`aries-rfcs protocols <https://github.com/hyperledger/aries-rfcs/tree/master/features>`_.
+`aries-rfcs protocols <https://github.com/decentralized-identity/aries-rfcs/tree/master/features>`_.
 Decorators defined in aries-rfcs and implemented in ACA-Py can be found
 `here <generated/acapy_agent.messaging.decorators.html>`_.
 Some general purpose subpackages that might be of interest include