consider automating go-versions availability (auto go-versions update when released are done by the go team)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.8k
- Forks
- 673
- Avg merge
- 6d 28m
- Merged PRs (30d)
- 4
Description
Description:
Trust the go team releases and have a minimal delay between the go team shipping a new patch release (e.g 1.20.6 to 1.20.7) and that patch becoming available with setup-go check latest actions - as in making go-versions update entirely automatic with no lag from humans
Justification:
Otherwise build break (in part because of govulncheck) or have to wait to release security fixed binaries
Are you willing to submit a PR?
I would but it's probably easier for someone familiar
There are a few hints on "how"
https://github.com/actions/setup-go/issues/405#issuecomment-1664433639
https://github.com/actions/setup-go/issues/405#issuecomment-1664747189
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the two linked comments on setup-go issue #405 and tracing how go-versions is currently updated and how setup-go checks the latest available version. No files or tests are named in the issue. Done means new Go patch releases become available with minimal human delay while preserving the existing version lookup behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, typescript
- Domain
- ci-cd, devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100