4 ms·
v1, v2, v3 are not valid module versions in Go, so it requires a slightly different solution.
by pgwhalen 5y ago
v1, v2, v3 are not valid module versions in Go, so it requires a slightly different solution.
- paskozdilar 5y agoIf you're not distributing your Go package to others as a library, then you don't need to follow the Go module versions. They are only enforced user-side.
- pgwhalen 5y agoTrue, though if you have code in separate repositories you might want to stick to some versioning scheme to use the module tooling to your advantage.