Run Github Actions workflows using the latest two versions of Go

[nothub]

This changes the CI job to always use the Go version defined in the mod file. It also enables caching for module downloads.

[nothub]

Merged upstream to resolve conflicts.

[adrg]

Hi @nothub,

Thank you for the PR. I apologize for the late response.

I would rather not use the version of Go specified in the go.mod file for the workflows. The minimum version of Go required by the module is currently 1.19 and I would like to run the actions using a more recent version.

I think it might be a better idea to use go-version: 'stable' or go-version: 'oldstable', or perhaps both using the matrix section. In any case, I would always get a newer Go version this way.

Reference: https://github.com/actions/setup-go?tab=readme-ov-file#using-stableoldstable-aliases

[nothub]

Hi @adrg,

I changed the used go-version to stable and oldstable with matrix strategy.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (fdcc36e) to head (21d4306).

Additional details and impacted files

@@            Coverage Diff            @@
##            master       #74   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines          392       392           
=========================================
  Hits           392       392           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[adrg]

Hi @adrg,

I changed the used go-version to stable and oldstable with matrix strategy.

Thank you. Can you also change the golangci-lint binary version from v1.54 to latest in lint.yml? It seems Go 1.23 support was just added in version v1.60.1 of golangci-lint.

[nothub]

Yeah no problem 👍
The version of the golangci-lint step is now set to latest.

[adrg]

@nothub Merged the PR. Thanks again. I also added you to the contributors list in README.md.