pingcap / pingcap/tidb-operator
Optimize the way to bump go version
Open
Nobody has claimed this yet.
v2
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Now there are many go versions in scripts, Dockerfiles, go.mod, go.work etc..
We need a way to bump all go versions.
Contributor guide
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
Inspect the Go version references in the scripts, Dockerfiles, go.mod, and go.work files to understand how they currently diverge. Define what a consistent bump workflow should cover, then verify that the chosen approach updates all mentioned locations without leaving mismatched versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100