certusone
/
cosmos-sdk
mirror of https://github.com/certusone/cosmos-sdk.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Update upgrade.md (#9822) 

Not sure if this fix works, but currently the link takes you to a 404 at https://docs.cosmos.network/v0.43/v0.42/migrations/chain-upgrade-guide-040.html.

Don't we have 404 link checkers in the build process?
Why don't they detect this one?
This commit is contained in:
billy rennekamp 2021-07-30 15:56:14 +02:00 committed by GitHub
parent cab727af0f
commit 32723400e0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/core/upgrade.md
View File

@ -12,7 +12,7 @@ Upgrade your app modules smoothly with custom in-place store migration logic. {s
The Cosmos SDK uses two methods to perform upgrades.
- Exporting the entire application state to a JSON file using the `export` CLI command, making changes, and then starting a new binary with the changed JSON file as the genesis file. See [Chain Upgrade Guide to v0.42](/v0.42/migrations/chain-upgrade-guide-040.html).
- Exporting the entire application state to a JSON file using the `export` CLI command, making changes, and then starting a new binary with the changed JSON file as the genesis file. See [Chain Upgrade Guide to v0.42](../v0.42/migrations/chain-upgrade-guide-040.html).
- Version v0.43 and later can perform upgrades in place to significantly decrease the upgrade time for chains with a larger state. Use the [Module Upgrade Guide](../building-modules/upgrade.md) to set up your application modules to take advantage of in-place upgrades.