golang/go

cmd/go: reject unenforced 'go' versions (older than 1.6) in 'go.mod' files

Open

#36,319 opened on Dec 30, 2019

View on GitHub
 (7 comments) (0 reactions) (0 assignees)Go (19,008 forks)batch import
DocumentationGoCommandNeedsFixhelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

If I have a very simple Go package that doesn't depend on any language features added since the original Go 1 release, I naturally thought I could put in my go.mod file:

go 1

But that doesn't parse:

$ go install
go: errors parsing go.mod:
/home/me/proj/go.mod:3: usage: go 1.23

But go 1.0 is weird, because we never called it that. Is that correct? Docs don't say.

go 1.1 is also weird, because it implies that I'm depending on something that was added in Go 1.1, but I'm not.

So I guess go 1.11 for when modules were introduced?

/cc @ianlancetaylor @bcmills @jayconrod @dmitshur

Contributor guide

Research direction
Investigate the parsing of 'go' directives in go.mod files, specifically the version range validation. The issue is that versions like '1' or '1.0' are rejected. The minimum supported version should be 1.11 (or 1.6?) as per Go module conventions. The fix likely involves updating the parser to accept older versions or provide a better error message.
Tech stack
go
Domain
backendtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Gogo.mod
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70