externally configured Go version for automation support
See original GitHub issueI’ve got a GitHub Action I wrote to update the Go versions in my various configuration files[1]. Especially, for my security projects, I’d like an auditable but automated way to keep the Go versions I use up to date.
(Using a .x
version number isn’t enough because doing that wouldn’t kick off new builds when a new version is released and it’s difficult to audit when a new Go version was brought in.)
But, unfortunately (and totally understandably from a security perspective!), GitHub Actions can’t modify integration configs. So, I’ve got a plan to keep my Go versions in a file outside of my workflow configs, have my workflows read in that file and use it for go_version
, and then have my tool update that external file.
Would y’all be open to me posting a PR to make that an explicitly supported thing in setup-go? Say, reading a file in something like .github/versions/go.yml
or similar?
Issue Analytics
- State:
- Created 4 years ago
- Comments:18 (4 by maintainers)
Top GitHub Comments
I’m using this:
So I only have to maintain go.mod. Only works if you don’t need matrix builds ofc 😃
But it would be nice if this action could do that on its own, e.g. have a property
go-mod-path: go.mod
For reference my GitHub Action as seen on iron-go-project:
My file
.github/go/Dockerfile
:And keeping the file updated automatically in
.github/dependabot.yml
: