-
Notifications
You must be signed in to change notification settings - Fork 635
Open
Labels
severity/p1This bug affects functionality or significantly affect uxThis bug affects functionality or significantly affect uxtype/bugThis issue is a bugThis issue is a bug
Description
Search before asking
- I had searched in the issues and found no similar issues.
What happened
The project has inconsistent Go version requirements across different configuration files:
- go.mod: Specifies Go 1.20
- Development tools in Makefile: Require Go 1.21+ (golangci-lint@latest, mockery v2.43.0, swag v1.16.1)
- .devcontainer/Dockerfile: Uses Go 1.22 base image
When trying to run make dep
or other Makefile targets with Go 1.20, users get prompted to upgrade to a higher Go version, causing confusion about which version is actually required.
What do you expect to happen
All Go version specifications should be consistent across the project. The go.mod file should reflect the actual minimum Go version required by the development toolchain.
How to reproduce
- Install Go 1.20
- Clone the repository
- Run
cd backend && make dep
- Observe that development tools request a higher Go version than what's specified in go.mod
Anything else
This inconsistency creates confusion for new contributors and can lead to build failures. The .devcontainer already uses Go 1.22, suggesting this is the intended version.
Suggested fix: Update go.mod to specify Go 1.22 to match the development environment and toolchain requirements.
Version
Latest main branch
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
dosubot
Metadata
Metadata
Assignees
Labels
severity/p1This bug affects functionality or significantly affect uxThis bug affects functionality or significantly affect uxtype/bugThis issue is a bugThis issue is a bug