Oh, thanks. The very reason that I do that is to avoid the following situation:
for i in `jot 12`; do echo $i > f; git commit -am "$i"; git tag v0.0.$i; done $ git tag -l v0.0.1 v0.0.10 v0.0.11 v0.0.12 v0.0.2 v0.0.3 v0.0.4 v0.0.5 v0.0.6 v0.0.7 v0.0.8 v0.0.9 If no leading 0s allowed, how do you guys solve the above problem? On Sat, Aug 15, 2020 at 5:01 AM seank...@gmail.com <seankhl...@gmail.com> wrote: > > that's an invalid semver, no leading 0s allowed > > https://semver.org/#spec-item-2 : > A normal version number MUST take the form X.Y.Z where X, Y, and Z are > non-negative integers, and MUST NOT contain leading zeroes. X is the major > version, Y is the minor version, and Z is the patch version. Each element > MUST increase numerically. For instance: 1.9.0 -> 1.10.0 -> 1.11.0. > > On Saturday, August 15, 2020 at 4:08:06 AM UTC+2 sunto...@gmail.com wrote: >> >> How to force update the latest version of package in pkg.go.dev? >> >> My https://github.com/go-easygen/easygen/releases/tag/v5.1.01 has been >> release for over 10 days, but the >> https://pkg.go.dev/github.com/go-easygen/easygen?tab=versions is still >> showing an old version. >> >> From https://proxy.golang.org/ I saw >> >>> explicitly request that version via go get module@version. After one minute >>> for caches to expire, the go command will see that tagged version. If this >>> doesn't work for you, please file an issue. >> >> >> >> So I did: >> >> >> go get github.com/go-easygen/eas...@v5.1.01 >> >> go: downloading github.com/go-easygen/easygen >> v4.0.1-0.20200804033944-7bacacfacf6a+incompatible >> go: github.com/go-easygen/easygen v5.1.01 => >> v4.0.1-0.20200804033944-7bacacfacf6a+incompatible >> go: finding module for package gopkg.in/yaml.v2 >> . . . >> >> $ date >> Fri Aug 14 21:56:06 EDT 2020 >> >> $ lynx -dump -width=78 >> "https://pkg.go.dev/github.com/go-easygen/easygen?tab=versions";; date >> . . . >> v1 - github.com/go-easygen/easygen >> >> * [32]v4.1.0+incompatible - Jun 19, 2019 >> * [33]v4.0.0+incompatible - Mar 24, 2019 >> * [34]v3.0.0+incompatible - May 4, 2018 >> . . . >> Fri Aug 14 22:06:18 EDT 2020 >> >> >> So do I need to file an issue, or I've missed something? >> >> Thx >> >> > -- > You received this message because you are subscribed to a topic in the Google > Groups "golang-nuts" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/golang-nuts/ECa7ZlbLNW0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/golang-nuts/074b1e7d-7b1c-43c0-abc6-d20eb2625c7dn%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAMmz1OdXGXc5D86oMdC2ABZ%2BuSER_P8hb7piimNPac3enihjeA%40mail.gmail.com.
