cmd/go: add better support for v0.YYYYMMDD.HHMMSS
versions
#35646
Labels
FrozenDueToAge
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
WaitingForInfo
Issue is not actionable because of missing required information, which needs to be provided.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
We recently switched to module versions of the form
v0.YYYYMMDD.HHMMSS
since we only care whether a module is more recent and we already had existing semver tags in the repo. Sov0.0.YYYYMMDDHHMMSS
would not work.This works fine until the timestamp starts with a
0
since then the patch version is outside the semver spec.go build
then fails butgo mod tidy
fetches the version but rewritesgo.mod
tov0.20191115.124623-0.20191117071016-50581b53fb34
. This does not happen after 10:00 obviously.We can switch to something like
v0.99.YYYYMMDD.HHMMSS
orv1.0.YYYYMMDDHHMMSS
but I'm wondering whether it would make sense to make the semver parser a bit more lenient to allow for this use-case.The text was updated successfully, but these errors were encountered: