bump opinit and cleanup github actions

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,24 @@
 ---
 name: Bug report
-about: Create a report to help us improve (use this for suspected bugs only, if not sure, open a regular issue below)
-title: ''
-labels: Bug
-assignees: ''
+about: Create a report to help us improve
+title: ""
+labels: ""
+assignees: ""
 ---
 
-<!-- This issue tracker is only for technical issues related to Initia.
+**Describe the bug**
+A clear and concise description of what the bug is.
 
-General initia questions and/or support requests are best directed to the initia support team. 
+**To Reproduce**
+Steps to reproduce the behavior:
 
--->
-
-<!-- Describe the issue -->
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
 
 **Expected behavior**
+A clear and concise description of what you expected to happen.
 
-<!--- What behavior did you expect? Describe what the software should do in response to a specific action or command.-->
-
-**Actual behavior**
-
-<!--- What did the software actually do when you performed the action or command? If you're unsure whether the issue is related to Initia, feel free to ask us for clarification."
- -->
-
-**To reproduce**
-
-<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
-
-**System information**
-
-<!-- What version of initia are you using, where did you get it (website, self-compiled, etc)? -->
-
-<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
-
-<!-- initia-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
-
-<!-- Any extra information that might be useful in the debugging process. -->
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,19 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: Feature
-assignees: ''
-
+title: ""
+labels: ""
+assignees: ""
 ---
 
 **Is your feature request related to a problem? Please describe.**
-<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
 **Describe the solution you'd like**
-<!-- A clear and concise description of what you want to happen. -->
+A clear and concise description of what you want to happen.
 
 **Describe alternatives you've considered**
-<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+A clear and concise description of any alternative solutions or features you've considered.
 
 **Additional context**
-<!-- Add any other context or screenshots about the feature request here. -->
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,32 +1,46 @@
-<!--
-*** Please remove the following help text before submitting: ***
-
-Pull requests without a rationale and clear improvement may be closed
-immediately.
-
--->
-
-<!--
-Please provide clear motivation for your patch and explain how it improves
-initia user experience or initia developer experience
-significantly:
-
-* Any test improvements or new tests that improve coverage are always welcome.
-* All other changes should have accompanying unit tests (see `src/test/`) or
-  functional tests (see `test/`). Contributors should note which tests cover
-  modified code. If no tests exist for a region of modified code, new tests
-  should accompany the change.
-* Bug fixes are most welcome when they come with steps to reproduce or an
-  explanation of the potential issue as well as reasoning for the way the bug
-  was fixed.
-* Features are welcome, but might be rejected due to design or scope issues.
-  If a feature is based on a lot of dependencies, contributors should first
-  consider building the system outside of initia, if possible.
--->
-
-<!--
-Initia has a thorough review process and even the most trivial change
-needs to pass a lot of eyes and requires non-zero or even substantial time
-effort to review. There is a huge lack of active reviewers on the project, so
-patches often sit for a long time.
--->
+# Description
+
+Closes: #XXXX
+
+<!-- Add a description of the changes that this PR introduces and the files that
+are the most critical to review. -->
+
+---
+
+## Author Checklist
+
+_All items are required. Please add a note to the item if the item is not applicable and
+please add links to any relevant follow up issues._
+
+I have...
+
+- [ ] included the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title, you can find examples of the prefixes below:
+<!-- * `feat`: A new feature
+* `fix`: A bug fix
+* `docs`: Documentation only changes
+* `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+* `refactor`: A code change that neither fixes a bug nor adds a feature
+* `perf`: A code change that improves performance
+* `test`: Adding missing tests or correcting existing tests
+* `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+* `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+* `chore`: Other changes that don't modify src or test files
+* `revert`: Reverts a previous commit -->
+- [ ] confirmed `!` in the type prefix if API or client breaking change
+- [ ] targeted the correct branch
+- [ ] provided a link to the relevant issue or specification
+- [ ] reviewed "Files changed" and left comments if necessary
+- [ ] included the necessary unit and integration tests
+- [ ] updated the relevant documentation or specification, including comments for [documenting Go code](https://blog.golang.org/godoc)
+- [ ] confirmed all CI checks have passed
+
+## Reviewers Checklist
+
+_All items are required. Please add a note if the item is not applicable and please add
+your handle next to the items reviewed if you only reviewed selected items._
+
+I have...
+
+- [ ] confirmed the correct [type prefix](https://github.com/commitizen/conventional-commit-types/blob/v3.0.0/index.json) in the PR title
+- [ ] confirmed all author checklist items have been addressed
+- [ ] reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

.github/workflows/build-darwin-amd64.yml

@@ -15,7 +15,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v4
         with:
-          go-version: '1.22.4'
+          go-version: "1.22.4"
 
       - name: Set environment variables
         run: |
@@ -31,7 +31,7 @@ jobs:
           echo "VERSION=${VERSION}" >> $GITHUB_ENV
           echo "ARCH_NAME=x86_64" >> $GITHUB_ENV
           WASMVM_VERSION=$(go list -m github.com/CosmWasm/wasmvm/v2 | awk '{print $2}')
-          echo "WASMVM_VERSION=${WASMVM_VERSION}" >> $GITHUB_ENV 
+          echo "WASMVM_VERSION=${WASMVM_VERSION}" >> $GITHUB_ENV
 
       - name: Ensure dependencies
         run: |
@@ -47,8 +47,6 @@ jobs:
           echo "WASMVM_VERSION=${WASMVM_VERSION}"
           echo "MINIWASM_NETWORK_NAME=${MINIWASM_NETWORK_NAME}"
 
-
-
       - name: Build and Package for Darwin ADM642
         run: |
           cd ../miniwasm \
@@ -59,10 +57,13 @@ jobs:
           && cp ~/go/pkg/mod/github.com/\!cosm\!wasm/wasmvm/v2@${WASMVM_VERSION}/internal/api/libwasmvm.dylib ./ \
           && tar -czvf miniwasm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz ./minitiad libwasmvm.dylib \
           && mv ./miniwasm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz $GITHUB_WORKSPACE/ \
-          && rm -rf ./libwasmvm.dylib ./minitiad   
+          && rm -rf ./libwasmvm.dylib ./minitiad
 
       - name: Release
         uses: softprops/action-gh-release@v2
         with:
           files: |
             miniwasm_${{ env.VERSION }}_Darwin_${{ env.ARCH_NAME }}.tar.gz
+        env:
+          VERSION: ${{ env.VERSION }}
+          ARCH_NAME: ${{ env.ARCH_NAME }}

.github/workflows/build-darwin-arm64.yml

@@ -1,4 +1,3 @@
-
 name: Build Darwin ARM64
 
 on:
@@ -15,7 +14,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v4
         with:
-          go-version: '1.22.4'
+          go-version: "1.22.4"
       - name: Set environment variables
         run: |
           MINIWASM_NETWORK_NAME="miniwasm-1"
@@ -31,12 +30,12 @@ jobs:
           fi
           echo "VERSION=${VERSION}" >> $GITHUB_ENV
           echo "ARCH_NAME=aarch64" >> $GITHUB_ENV
-          
+
       - name: Ensure dependencies
         run: |
           go mod tidy
           go get github.com/CosmWasm/wasmvm/v2@${WASMVM_VERSION}
-          
+
       - name: Print environment variables
         run: |
           echo "GOARCH=${GOARCH}"
@@ -55,10 +54,13 @@ jobs:
           && cp ~/go/pkg/mod/github.com/\!cosm\!wasm/wasmvm/v2@${WASMVM_VERSION}/internal/api/libwasmvm.dylib ./ \
           && tar -czvf miniwasm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz ./minitiad libwasmvm.dylib \
           && mv ./miniwasm_"$VERSION"_Darwin_"$ARCH_NAME".tar.gz $GITHUB_WORKSPACE/ \
-          && rm -rf ./libwasmvm.dylib ./minitiad   
-  
+          && rm -rf ./libwasmvm.dylib ./minitiad
+
       - name: Release
         uses: softprops/action-gh-release@v2
         with:
           files: |
             miniwasm_${{ env.VERSION }}_Darwin_${{ env.ARCH_NAME }}.tar.gz
+        env:
+          VERSION: ${{ env.VERSION }}
+          ARCH_NAME: ${{ env.ARCH_NAME }}

.github/workflows/build-linux-amd64.yml

@@ -1,8 +1,6 @@
-
 name: Build Linux AMD64
 
-on:
-  workflow_call
+on: workflow_call
 
 jobs:
   build:
@@ -14,7 +12,7 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v4
         with:
-          go-version: '1.22.4'
+          go-version: "1.22.4"
 
       - name: Set environment variables
         run: |
@@ -50,3 +48,6 @@ jobs:
         with:
           files: |
             ./build/miniwasm_${{ env.VERSION }}_Linux_${{ env.ARCH_NAME }}.tar.gz
+        env:
+          VERSION: ${{ env.VERSION }}
+          ARCH_NAME: ${{ env.ARCH_NAME }}