why freeze the patch number of the go version
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 337
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
since the version of the golang is 1.21.0, if the version specified in the go.work is not 1.21.0, it will report some error like following:
level=error msg="Running error: context loading failed: failed to load packages: failed to load with go/packages: err: exit status 1: stderr: go: module .xxx listed in go.work file requires go >= 1.21.0, but go.work lists go 1.21;
can the version ignore the patch number?
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 reproducing the reported workspace-loading error with a go.work file using go 1.21 and a module requiring go 1.21.0. Trace where the Go version is read or compared; done means compatible patch-version forms no longer trigger the error, with regression coverage if the repository has relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100