From d291c46148a28f7df3720187cb9d25a606ed3e40 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 8 Jul 2024 16:50:17 +0200 Subject: [PATCH 1/2] chore(deps): bump JamesIves/github-pages-deploy-action (#6779) Bumps [JamesIves/github-pages-deploy-action](https://github.com/jamesives/github-pages-deploy-action) from 4.6.1 to 4.6.3. - [Release notes](https://github.com/jamesives/github-pages-deploy-action/releases) - [Commits](https://github.com/jamesives/github-pages-deploy-action/compare/v4.6.1...v4.6.3) --- updated-dependencies: - dependency-name: JamesIves/github-pages-deploy-action dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> --- .github/workflows/deploy-docs.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml index eee6de1c329..17eda64b9db 100644 --- a/.github/workflows/deploy-docs.yml +++ b/.github/workflows/deploy-docs.yml @@ -27,7 +27,7 @@ jobs: run: make build-docs - name: Deploy 🚀 - uses: JamesIves/github-pages-deploy-action@v4.6.1 + uses: JamesIves/github-pages-deploy-action@v4.6.3 with: branch: gh-pages folder: docs/build From b1ca4ef45f8015dff1a4f37aa5c0f5542cde09d4 Mon Sep 17 00:00:00 2001 From: healthyyyoung Date: Mon, 8 Jul 2024 22:51:10 +0800 Subject: [PATCH 2/2] doc: fix small spell check (#6780) * Update 13-v8-to-v9.md * Update 13-best-practices.md --- docs/docs/01-ibc/13-best-practices.md | 2 +- docs/docs/05-migrations/13-v8-to-v9.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/01-ibc/13-best-practices.md b/docs/docs/01-ibc/13-best-practices.md index 91093a1d984..cebaf9e435a 100644 --- a/docs/docs/01-ibc/13-best-practices.md +++ b/docs/docs/01-ibc/13-best-practices.md @@ -13,7 +13,7 @@ Identifying which channel to use can be difficult as it requires verifying infor Channels are based on a light client. A chain can be uniquely identified by its chain ID, validator set pairing. It is unsafe to rely only on the chain ID. Any user can create a client with any chain ID, but only the chain with correct validator set and chain ID can produce headers which would update that client. -Which channel to use is based on social consensus. The desired channel should have the following properities: +Which channel to use is based on social consensus. The desired channel should have the following properties: - based on a valid client (can only be updated by the chain it connects to) - has sizable activity diff --git a/docs/docs/05-migrations/13-v8-to-v9.md b/docs/docs/05-migrations/13-v8-to-v9.md index e3f681e9bd1..d7028f20fec 100644 --- a/docs/docs/05-migrations/13-v8-to-v9.md +++ b/docs/docs/05-migrations/13-v8-to-v9.md @@ -201,6 +201,6 @@ The `IterateConsensusMetadata` function has been removed. ### 09-localhost The `09-localhost` light client has been made stateless and will no longer update the client on every block. The `ClientState` is constructed on demand when required. -The `ClientState` itself is therefore no longer provable direcly with `VerifyMembership` or `VerifyNonMembership`. +The `ClientState` itself is therefore no longer provable directly with `VerifyMembership` or `VerifyNonMembership`. Previously stored client state data is pruned automatically on IBC module store migration from `ConsensusVersion` 6 to 7.