chore: improve Makefile and release docs

.github/workflows/codeql-analysis.yml

@@ -26,8 +26,7 @@ jobs:
       uses: actions/checkout@v4
     - uses: actions/setup-go@v5
       with:
-        go-version: "1.21"
-        check-latest: true
+        go-version-file: go.mod
 
    # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL

.github/workflows/lint.yml

@@ -16,8 +16,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: "1.21"
-          check-latest: true
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         id: git_diff
         with:
@@ -30,4 +29,4 @@ jobs:
       - name: run linting
         if: env.GIT_DIFF
         run: |
-          make lint
+          make lint

.github/workflows/nightly-tests.yml

@@ -21,8 +21,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: "1.21"
-          check-latest: true
+          go-version-file: go.mod
       - name: run-vulncheck
         id: vulncheck
         run: make vulncheck

.github/workflows/release-sims.yml

@@ -26,7 +26,7 @@ jobs:
     steps:
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - name: Install runsim
         run: go install github.com/cosmos/tools/cmd/[email protected]
       - uses: actions/[email protected]
@@ -65,7 +65,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         with:
           PATTERNS: |

.github/workflows/release.yml

@@ -19,20 +19,17 @@ jobs:
           fetch-depth: 0
       - run: git fetch --force --tags
 
-      - name: Set go version
-        run: echo "GO_VERSION=$(make print_required_go_version)" >> $GITHUB_ENV
-
       - uses: actions/setup-go@v5
         with:
-          go-version: "${{ env.GO_VERSION }}"
+          go-version-file: go.mod
 
       - name: Set Env
-        run: echo "TM_VERSION=$(go list -m github.com/cometbft/cometbft | sed 's:.* ::')" >> $GITHUB_ENV
+        run: echo "TM_VERSION=$(make print_tm_version)" >> $GITHUB_ENV
 
       - name: Release
         uses: goreleaser/goreleaser-action@v5
         with:
-          version: latest
+          version: v1.25.1
           args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/sim-label.yml

@@ -16,8 +16,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/setup-go@v5
-        with:
-          go-version: 1.21.x
       - name: Install runsim
         run: go install github.com/cosmos/tools/cmd/[email protected]
       - uses: actions/[email protected]
@@ -33,7 +31,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - uses: actions/[email protected]
         with:
           path: ~/go/bin

.github/workflows/sims.yml

@@ -20,8 +20,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/setup-go@v5
-        with:
-          go-version: 1.21.x
       - name: Install runsim
         run: go install github.com/cosmos/tools/cmd/[email protected]
       - uses: actions/[email protected]
@@ -36,7 +34,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         with:
           PATTERNS: |
@@ -60,7 +58,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - uses: technote-space/get-diff-action@v6
         with:
           PATTERNS: |
@@ -81,8 +79,6 @@ jobs:
       runs-on: ubuntu-latest
       steps:
         - uses: actions/setup-go@v5
-          with:
-            go-version: 1.21.x
         - name: Install runsim
           run: go install github.com/cosmos/tools/cmd/[email protected]
         - uses: actions/[email protected]
@@ -105,10 +101,10 @@ jobs:
     runs-on: ubuntu-latest
     needs: [build, install-runsim]
     steps:
+      - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
-      - uses: actions/checkout@v4
+          go-version-file: go.mod
       - uses: actions/[email protected]
         with:
           path: ~/go/bin

.github/workflows/test.yml

@@ -26,10 +26,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: "1.21"
-          check-latest: true
-          cache: true
-          cache-dependency-path: go.sum
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         id: git_diff
         with:
@@ -63,10 +60,10 @@ jobs:
     runs-on: ubuntu-latest
     timeout-minutes: 45
     steps:
+      - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
-      - uses: actions/checkout@v4
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         with:
           PATTERNS: |
@@ -112,7 +109,7 @@ jobs:
       - uses: actions/checkout@v4
       - uses: actions/setup-go@v5
         with:
-          go-version: 1.21.x
+          go-version-file: go.mod
       - uses: technote-space/[email protected]
         with:
           PATTERNS: |

.goreleaser.yml

@@ -1,22 +1,19 @@
 ---
 project_name: atomone
 
-env:
-  - GO111MODULE=on
-
 builds:
   - main: ./cmd/atomoned
     id: "atomoned"
     binary: atomoned
     mod_timestamp: "{{ .CommitTimestamp }}"
     flags:
-      - -tags=netgo ledger
+      - -tags=netgo
       - -trimpath
     env:
       - CGO_ENABLED=0
     ldflags:
       # .Env.TM_VERSION is provided in the workflow runner environment -> see .github/workflows/release.yml
-      - -X github.com/cosmos/cosmos-sdk/version.Name=atomone -X github.com/cosmos/cosmos-sdk/version.AppName=atomoned -X github.com/cosmos/cosmos-sdk/version.Version=v{{ .Version }} -X github.com/cosmos/cosmos-sdk/version.Commit={{ .Commit }} -X github.com/cosmos/cosmos-sdk/version.BuildTags=netgo,ledger -X github.com/cometbft/cometbft/version.TMCoreSemVer={{ .Env.TM_VERSION }} -w -s
+      - -X github.com/cosmos/cosmos-sdk/version.Name=atomone -X github.com/cosmos/cosmos-sdk/version.AppName=atomoned -X github.com/cosmos/cosmos-sdk/version.Version=v{{ .Version }} -X github.com/cosmos/cosmos-sdk/version.Commit={{ .Commit }} -X github.com/cosmos/cosmos-sdk/version.BuildTags=netgo -X github.com/cometbft/cometbft/version.TMCoreSemVer={{ .Env.TM_VERSION }} -w -s
     goos:
       - darwin
       - linux

CONTRIBUTING.md

@@ -61,10 +61,10 @@ chance of getting changes merged into the codebase.
 
 To ensure a smooth workflow for all contributors, a general procedure for contributing has been established.
 
-1. Start by browsing [existing issues](https://github.com/atomone-hub/atomone/issues) and [discussions](https://github.com/atomone-hub/atomone/discussions). If you are looking for something interesting or if you have something in your mind, there is a chance it had been discussed.
+1. Start by browsing [existing issues](https://github.com/atomone-hub/atomone/issues). If you are looking for something interesting or if you have something in your mind, there is a chance it had been discussed.
    * Looking for a good place to start contributing? How about checking out some [good first issues](https://github.com/atomone-hub/atomone/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22) or [bugs](https://github.com/atomone-hub/atomone/issues?q=is%3Aopen+is%3Aissue+label%3Abug)?
 2. Determine whether a GitHub issue or discussion is more appropriate for your needs:
-   1. If you want to propose something new that requires specification or an additional design, or you would like to change a process, start with a [new discussion](https://github.com/atomone-hub/atomone/discussions/new/choose). With discussions, we can better handle the design process using discussion threads. A discussion usually leads to one or more issues.
+   1. If you want to propose something new that requires specification or an additional design, or you would like to change a process, start with a [new issue](https://github.com/atomone-hub/atomone/issues/new/choose).
    2. If the issue you want addressed is a specific proposal or a bug, then open a [new issue](https://github.com/atomone-hub/atomone/issues/new/choose).
    3. Review existing [issues](https://github.com/atomone-hub/atomone/issues) to find an issue you'd like to help with.
 3. Participate in thoughtful discussion on that issue.
@@ -82,13 +82,9 @@ To ensure a smooth workflow for all contributors, a general procedure for contri
 For complex problems or features, please make sure to open an issue and provide context and problem description. 
 PRs opened before adequate design discussion has taken place in a GitHub issue have a high likelihood of being rejected without review.
 
-## Project Board
-
-We use self-organizing principles to coordinate and collaborate across organizations in structured "EPICs" that focus on specific problem domains or architectural components of AtomOne.
-
 ## Architecture Decision Records (ADR)
 
-When proposing an architecture decision for AtomOne, please start by opening an [issue](https://github.com/atomone-hub/atomone/issues/new/choose) or a [discussion](https://github.com/atomone-hub/atomone/discussions/new) with a summary of the proposal. Once the proposal has been discussed and there is rough alignment on a high-level approach to the design, you may either start development, or write an ADR.
+When proposing an architecture decision for AtomOne, please start by opening an [issue](https://github.com/atomone-hub/atomone/issues/new/choose) with a summary of the proposal. Once the proposal has been discussed and there is rough alignment on a high-level approach to the design, you may either start development, or write an ADR.
 
 If your architecture decision is a simple change, you may contribute directly without writing an ADR. However, if you are proposing a significant change, please include a corresponding ADR.