LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

docs: fix dead links in documentation (#25061)

Browse Source
This commit is contained in:
maradini77 2025-07-31 16:12:58 +02:00 committed by GitHub
parent e434dc7aab
commit 8230a73c03
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/README.md
View File

@ -22,7 +22,7 @@ It is built using the following stack:
## Docs Build Workflow
The docs are built and deployed automatically on GitHub Pages by a [GitHub Action workflow](../.github/workflows/deploy-docs.yml).
The docs are built and deployed automatically on GitHub Pages by a [GitHub Action workflow](../.github/workflows/build-docs.yml).
The workflow is triggered on every push to the `main` and `release/v**` branches, every time documentations or specs are modified.
### How It Works
@ -60,7 +60,7 @@ make build-docs
When a new major version of the SDK is released, the following steps should be taken:
* On the `release/vX.Y.Z` branch, remove the deploy action (`.github/workflows/deploy-docs.yml`), for avoiding deploying the docs from the release branches.
* On the `release/vX.Y.Z` branch, remove the deploy action (`.github/workflows/build-docs.yml`), for avoiding deploying the docs from the release branches.
* On the `release/vX.Y.Z` branch, update `docusaurus.config.js` and set the `lastVersion` to `current`, remove all other versions from the config.
* Each time a new version is released (on docusaurus), drop support from the oldest versions.
* If the old version is still running vuepress (v0.45, v0.46), remove its line from `vuepress_versions`

2
docs/architecture/adr-033-protobuf-inter-module-comm.md
View File

@ -20,7 +20,7 @@ service definitions defined in [ADR 021](./adr-021-protobuf-query-encoding.md) a
## Context
In the current Cosmos SDK documentation on the [Object-Capability Model](../../docs/learn/advanced/10-ocap.md), it is stated that:
In the current Cosmos SDK documentation on the [Object-Capability Model](../docs/learn/advanced/10-ocap.md), it is stated that:
> We assume that a thriving ecosystem of Cosmos SDK modules that are easy to compose into a blockchain application will contain faulty or malicious modules.

4
docs/docs/build/building-apps/01-app-go-di.md vendored
View File

@ -7,7 +7,7 @@ sidebar_position: 1
:::note Synopsis
The Cosmos SDK allows much easier wiring of an `app.go` thanks to [runtime](./00-runtime.md) and app wiring.
Learn more about the rationale of App Wiring in [ADR-057](../architecture/adr-057-app-wiring.md).
Learn more about the rationale of App Wiring in [ADR-057](../../../architecture/adr-057-app-wiring.md).
:::
@ -16,7 +16,7 @@ Learn more about the rationale of App Wiring in [ADR-057](../architecture/adr-05
* [What is `runtime`?](./00-runtime.md)
* [Depinject documentation](../packages/01-depinject.md)
* [Modules depinject-ready](../building-modules/15-depinject.md)
* [ADR 057: App Wiring](../architecture/adr-057-app-wiring.md)
* [ADR 057: App Wiring](../../../architecture/adr-057-app-wiring.md)
:::

2
docs/docs/build/building-modules/13-upgrade.md vendored
View File

@ -60,4 +60,4 @@ func (m Migrator) Migrate1to2(ctx sdk.Context) error {
}
```
To see example code of changes that were implemented in a migration of balance keys, check out [migrateBalanceKeys](https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/x/bank/migrations/v2/store.go#L55-L76). For context, this code introduced migrations of the bank store that updated addresses to be prefixed by their length in bytes as outlined in [ADR-028](../architecture/adr-028-public-key-addresses.md).
To see example code of changes that were implemented in a migration of balance keys, check out [migrateBalanceKeys](https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/x/bank/migrations/v2/store.go#L55-L76). For context, this code introduced migrations of the bank store that updated addresses to be prefixed by their length in bytes as outlined in [ADR-028](../../../architecture/adr-028-public-key-addresses.md).

4
docs/docs/learn/advanced/00-baseapp.md
View File

@ -166,7 +166,7 @@ which encodes and validates each transaction and from there the `AnteHandler` is
If successful, valid transactions are returned inclusive of the events, tags, and data generated
during the execution of the proposal.
The described behavior is that of the default handler, applications have the flexibility to define their own
[custom mempool handlers](https://docs.cosmos.network/main/building-apps/app-mempool#custom-mempool-handlers).
[custom mempool handlers](https://docs.cosmos.network/main/build/building-apps/app-mempool).
![ProcessProposal](./baseapp_state-prepareproposal.png)
@ -177,7 +177,7 @@ from the root store and is used to process a signed proposal received from a val
In this state, `runTx` is called and the `AnteHandler` is executed and the context used in this state is built with information
from the header and the main state, including the minimum gas prices, which are also set.
Again we want to highlight that the described behavior is that of the default handler and applications have the flexibility to define their own
[custom mempool handlers](https://docs.cosmos.network/main/building-apps/app-mempool#custom-mempool-handlers).
[custom mempool handlers](https://docs.cosmos.network/main/build/building-apps/app-mempool).
![ProcessProposal](./baseapp_state-processproposal.png)