Prepare gaia alpha release for cosmoshub-4.6 upgrade

.github/workflows/sim-label.yml

@@ -25,7 +25,7 @@ jobs:
           path: ~/go/bin
           key: ${{ runner.os }}-go-runsim-binary
 
-  test-sim-nondeterminism:
+  test-sim-nondeterminism-labeled:
     if: ${{ github.event.label.name == 'sim' }}
     runs-on: ubuntu-latest
     needs: newbuild
@@ -34,18 +34,10 @@ jobs:
       - uses: actions/setup-go@v2.1.3
         with:
           go-version: 1.16
-      - uses: technote-space/get-diff-action@v4
-        with:
-          PATTERNS: |
-            **/**.go
-            go.mod
-            go.sum
       - uses: actions/cache@v1
         with:
           path: ~/go/bin
           key: ${{ runner.os }}-go-runsim-binary
-        if: "env.GIT_DIFF != ''"
       - name: test nondeterminism
         run: |
-          make test-sim-nondeterminism
-        if: "env.GIT_DIFF != ''"
+          make test-sim-nondeterminism

.github/workflows/sims.yml

@@ -18,7 +18,7 @@ jobs:
     steps:
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - name: Install runsim
         run: export GO111MODULE="on" && go get github.com/cosmos/tools/cmd/runsim@v1.0.0
       - uses: actions/cache@v1
@@ -33,7 +33,7 @@ jobs:
 #      - uses: actions/checkout@v2
 #      - uses: actions/setup-go@v2.1.3
 #        with:
-#          go-version: 1.15
+#          go-version: 1.16
 #      - uses: technote-space/get-diff-action@v4
 #        with:
 #          PATTERNS: |
@@ -63,7 +63,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - uses: actions/cache@v1
         with:
           path: ~/go/bin
@@ -80,7 +80,7 @@ jobs:
     steps:
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - uses: actions/checkout@v2
       - uses: technote-space/get-diff-action@v4
         with:
@@ -105,7 +105,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - uses: technote-space/get-diff-action@v4
         with:
           PATTERNS: |
@@ -130,7 +130,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - uses: technote-space/get-diff-action@v4
         with:
           PATTERNS: |

.github/workflows/test.yml

@@ -18,7 +18,7 @@ jobs:
     steps:
       - uses: actions/setup-go@v2.1.3
         with:
-          go-version: 1.15
+          go-version: 1.16
       - uses: actions/checkout@v2
       - uses: technote-space/get-diff-action@v4
         with:

CHANGELOG.md

@@ -37,6 +37,7 @@ Ref: https://keepachangelog.com/en/1.0.0/
 ## [Unreleased]
 
 * (tendermint) Bump Tendermint version to [v0.34.10](https://github.com/tendermint/tendermint/releases/tag/v0.34.10).
+* (golang) Bump golang prerequisite from 1.15 to 1.16.
 
 ## [v4.2.1] - 2021-04-08
 

CONTRIBUTING.md

@@ -62,15 +62,38 @@ Other notes:
   A convenience git `pre-commit` hook that runs the formatters automatically
   before each commit is available in the `contrib/githooks/` directory.
 
-## Pull Requests
+## Submissions
+
+Generally, when structuring a submission for the Cosmos ecosystem, the submission might span multiple layers
+of the technology stack, including the Cosmos SDK and Tendermint dependencies.
+
+### Structuring a submission
 
 To accommodate review process we suggest that PRs are categorically broken up.
 Ideally each PR addresses only a single issue. Additionally, as much as possible
 code refactoring and cleanup should be submitted as a separate PRs from bugfixes/feature-additions.
 
+In order to simplify reviewing large changes, submissions should have a created an issue
+with a description of the submission, a description tracking the changes and relevant discussions,
+and a checklist of changes and tasks to be done. 
+
+The issue can then be used to develop multiple well-scoped PRs that are easy to review.
+
+The following PR structuring checklist can be used when submitting changes to the Gaia repository for review:
+- [ ] Proto files: PR updating proto files. As a suggested next step, don't regenerate updated protobuf 
+   implementations using `protgen`, since this will break existing code.   
+- [ ] Broken code: If `protogen` is run, a PR disabling broken code
+- [ ] Validation: PR with validation of types
+- [ ] Functionality: PR integrating supporting functionality
+- [ ] Servers: PR for `msgserver` and `queryserver`
+- [ ] CLI: PR for CLI commands
+- [ ] Orchestrators: PR for any orchestrators
+- [ ] Genesis: PR for genesis
+- [ ] Upgrades: PR for upgrades
+
 ### Process for reviewing PRs
 
-All PRs require two Reviews before merge (except docs changes, or variable name-changes which only require one). When reviewing PRs please use the following review explanations:
+All PRs require at least one review before merge (except docs changes, or variable name-changes which only require one). When reviewing PRs please use the following review explanations:
 
 - `LGTM` without an explicit approval means that the changes look good, but you haven't pulled down the code, run tests locally and thoroughly reviewed it.
 - `Approval` through the GH UI means that you understand the code, documentation/spec is updated in the right places, you have pulled down and tested the code locally. In addition: