Migrate github actions workflows to use actions/setup-go go-version-file input

[anGie44]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

• Across many of our workflows we setup the go version with following environment variable setup:

 # See also: https://github.com/actions/setup-go/pull/62
    - run: echo "GO_VERSION=$(cat .go-version)" >> $GITHUB_ENV
    - uses: actions/setup-go@v3
      with:
        go-version: ${{ env.GO_VERSION }}
    # See also: https://github.com/actions/setup-go/issues/54

But as of a recent release in actions-setup/go as suggested by @gdavison , this can be accomplished directly as seen in their github release of v3.1.0 e.g.

steps:
 - uses: actions/checkout@v3
 - uses: actions/setup-go@v3
   with:
     go-version-file: 'path/to/go.mod'
 - run: go version

References

• Add go-version-from-file option actions/setup-go#62

[anGie44]

Relates: hashicorp/terraform-plugin-log#65

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.