smeb_y/0g-chain
1
0
Fork 0
mirror of https://github.com/0glabs/0g-chain.git synced 2024-11-20 15:05:21 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update dockerfile, ci, and migration instructions to go 1.17 (#1140)

Browse Source
This commit is contained in:
Nick DeLuca 2022-01-16 19:24:37 -07:00 committed by GitHub
parent e9a28cefd8
commit 4f300a040e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.circleci/config.yml
View File

@ -2,7 +2,7 @@ version: 2.1
executors:
golang:
docker:
- image: circleci/golang:1.16
- image: circleci/golang:1.17
commands:
make:

2
Dockerfile
View File

@ -1,4 +1,4 @@
FROM golang:1.16-alpine AS build-env
FROM golang:1.17-alpine AS build-env
# Set up dependencies
# bash, jq, curl for debugging

10
migrate/v0_16/migrate.md
View File

@ -4,13 +4,13 @@
- We will be upgrading from chain-id "kava-8" to chain-id "kava-9".
- The version of Kava for kava-9 is v0.16.0
- The kava-8 chain will be shutdown with a `SoftwareUpgradeProposal` that activates at block height __1803250__, which is approximately 14:00 UTC on January, 19 2022.
- The kava-8 chain will be shutdown with a `SoftwareUpgradeProposal` that activates at block height __1803250__, which is approximately 14:00 UTC on January, 19 2022.
- kava-9 genesis time is set to January 19, 2022 at 16:00 UTC
- The version of cosmos-sdk for kava-9 is v0.44.5
- The version of tendermint for kava-9 v0.34.14
- The minimum version of golang for kava-9 is __1.16+__.
- The minimum version of golang for kava-9 is __1.17+__.
__NOTE__: As part of the upgrade to kava-9, the `kvd` and `kvcli` binaries were combined into a single blockchain binary named `kava`. When restarting the chain, be sure to use `kava start` and not the deprecated `kvd start`.
__NOTE__: As part of the upgrade to kava-9, the `kvd` and `kvcli` binaries were combined into a single blockchain binary named `kava`. When restarting the chain, be sure to use `kava start` and not the deprecated `kvd start`.
### Risks
@ -30,7 +30,7 @@ In the event that the upgrade does not succeed, validators and operators must do
### Before the upgrade
Kava Labs has submitted a `SoftwareUpgradeProposal` that specifies block height __1803250__ as the final block height for kava-8. This height corresponds to approximately 14:00 UTC on January 19th. Once the proposal passes, the chain will shutdown automatically at the specified height and does not require manual intervention by validators.
Kava Labs has submitted a `SoftwareUpgradeProposal` that specifies block height __1803250__ as the final block height for kava-8. This height corresponds to approximately 14:00 UTC on January 19th. Once the proposal passes, the chain will shutdown automatically at the specified height and does not require manual intervention by validators.
### On the day of the upgrade
@ -41,7 +41,7 @@ Kava Labs has submitted a `SoftwareUpgradeProposal` that specifies block height
1. Export State (this **MUST** be done using **v0.15.x**)
```sh
# verify version before export:
# verify version before export:
kvd version --long
# name: kava
# server_name: kvd