Hi, DEV people! 😉 Sometimes, when you publish a new version of your Go package, pkg.go.dev may still give away an old version for a long time.
This also means, that if other people are using your package, not be able to update to the new version until the cache is updated.
Let's fix this! 👌
📝 Table of contents
A little story from real-life
That's what we did at Fiber Go web framework a few months ago.
After fixed a major bug, a new Fiber version could not be installed on users projects for about a couple of hours, because the cache was not updated. But the press release for the fix was already out (in official repository, Twitter, etc.) and users wanted to update and could not.
Worst-case scenario, isn't it? 😨
Save this command to a
Makefile (or a task manager you're using now):
# ... update-pkg-cache: GOPROXY=https://proxy.golang.org GO111MODULE=on \ go get github.com/$(USER)/$(PACKAGE)@v$(VERSION) # ...
And use it, like this:
make update-pkg-cache USER=gofiber PACKAGE=fiber VERSION=1.12.4
USERyour GitHub user or organization name
PACKAGEa name of your package to update cache
VERSIONa version number to update cache
It's that simple and clear!
If you want more articles like this on this blog, then post a comment below and subscribe to me. Thanks! 😘
And, of course, you can support me by donating at LiberaPay. Each donation will be used to write new articles and develop non-profit open-source projects for the community.
Top comments (1)
Hey Vic, nice write up. I've had the same problem earlier this year and came up with a Github Action that does pretty much the same every time a new package version is released: github.com/marketplace/actions/go-...