Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

Commit

Permalink
Merge pull request #122 from swcurran/1.0.0
Browse files Browse the repository at this point in the history
1.0.0rc4
  • Loading branch information
swcurran authored Jul 10, 2024
2 parents e2420a0 + bc3c751 commit fe4bd3a
Show file tree
Hide file tree
Showing 30 changed files with 122 additions and 122 deletions.
12 changes: 6 additions & 6 deletions docs/CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ Much progress has been made on `did:peer` support in this release, with the hand

[Qualified DIDs]: https://aca-py.org/latest/features/QualifiedDIDs/
[Credo-TS]: https://github.com/openwallet-foundation/credo-ts
[Aries Interop Profile v2.0]: https://github.com/hyperledger/aries-rfcs/tree/main/concepts/0302-aries-interop-profile#aries-interop-profile-version-20
[Aries Interop Profile v2.0]: https://github.com/hyperledger/aries-rfcs/tree/1.0.0rc4/concepts/0302-aries-interop-profile#aries-interop-profile-version-20

Work continues towards supporting ledger agnostic [AnonCreds], and the new [Hyperledger AnonCreds Rust] library. Some of that work is in this release, the rest will be in the next release.

Expand Down Expand Up @@ -1090,9 +1090,9 @@ those published to the [Hyperledger Package Repository under
aries-cloudagent-python].

[Hyperledger Package Repository under aries-cloudagent-python]: https://github.com/orgs/hyperledger/packages?repo_name=aries-cloudagent-python
[publish.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish.yml
[publish-indy.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish-indy.yml
[Container Images and Github Actions]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/ContainerImagesAndGithubActions.md
[publish.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/1.0.0rc4/.github/workflows/publish.yml
[publish-indy.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/1.0.0rc4/.github/workflows/publish-indy.yml
[Container Images and Github Actions]: https://github.com/hyperledger/aries-cloudagent-python/blob/1.0.0rc4/ContainerImagesAndGithubActions.md

### Breaking Changes and Upgrades

Expand All @@ -1106,7 +1106,7 @@ case is that an ACA-Py instance publishes a public DID on a ledger with a
DIDComm `service` in the DIDDoc. Other agents resolve that DID, and attempt to
establish a connection with the ACA-Py instance using the `service` endpoint.
This is called an "implicit" connection in [RFC 0023 DID
Exchange](https://github.com/hyperledger/aries-rfcs/blob/main/features/0023-did-exchange/README.md).
Exchange](https://github.com/hyperledger/aries-rfcs/blob/1.0.0rc4/features/0023-did-exchange/README.md).

#### PR [\#1913](https://github.com/hyperledger/aries-cloudagent-python/pull/1913) -- Unrevealed attributes in presentations

Expand Down Expand Up @@ -1552,7 +1552,7 @@ However, anyone else using an external queue should be aware of the impact of th
included in the release.

For those that have an existing deployment of ACA-Py with long-lasting connection records, an upgrade is needed to use
[RFC 434 Out of Band](https://github.com/hyperledger/aries-rfcs/tree/main/features/0434-outofband) and the "reuse connection" as the invitee. In PR #1453
[RFC 434 Out of Band](https://github.com/hyperledger/aries-rfcs/tree/1.0.0rc4/features/0434-outofband) and the "reuse connection" as the invitee. In PR #1453
(details below) a performance improvement was made when finding a connection for reuse. The new approach
(adding a tag to the connection to enable searching) applies only to connections made using this ACA-Py
release and later, and "as-is" connections made using earlier releases of ACA-Py will not be found as reuse
Expand Down
6 changes: 3 additions & 3 deletions docs/PUBLISHING.md
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,7 @@ Once you have the list of PRs:

9. Immediately after it is merged, create a new GitHub tag representing the
version. The tag name and title of the release should be the same as the
version in [pyproject.toml](https://github.com/hyperledger/aries-cloudagent-python/tree/main/pyproject.toml). Use
version in [pyproject.toml](https://github.com/hyperledger/aries-cloudagent-python/tree/1.0.0rc4/pyproject.toml). Use
the "Generate Release Notes" capability to get a sequential listing of the
PRs in the release, to complement the manually curated Changelog. Verify on
PyPi that the version is published.
Expand All @@ -144,8 +144,8 @@ Once you have the list of PRs:
Additional information about the container image publication process can be
found in the document [Container Images and Github Actions](./deploying/ContainerImagesAndGithubActions.md).

[publish.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish.yml
[publish-indy.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/.github/workflows/publish-indy.yml
[publish.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/1.0.0rc4/.github/workflows/publish.yml
[publish-indy.yml]: https://github.com/hyperledger/aries-cloudagent-python/blob/1.0.0rc4/.github/workflows/publish-indy.yml

11. Update the ACA-Py Read The Docs site by building the new "latest" (main
branch) and activating and building the new release. Appropriate permissions
Expand Down
Loading

0 comments on commit fe4bd3a

Please sign in to comment.