Skip to content

[Bug][Backend] Go version inconsistency between go.mod (1.20) and development environment (1.22) #8584

@spenpal

Description

@spenpal

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:

  1. go.mod: Specifies Go 1.20
  2. Development tools in Makefile: Require Go 1.21+ (golangci-lint@latest, mockery v2.43.0, swag v1.16.1)
  3. .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

  1. Install Go 1.20
  2. Clone the repository
  3. Run cd backend && make dep
  4. 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

Metadata

Metadata

Assignees

Labels

severity/p1This bug affects functionality or significantly affect uxtype/bugThis issue is a bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions