#How on earth do you upgrade a module

9 messages · Page 1 of 1 (latest)

pastel field
#

So I made an error in my code can be found here: https://github.com/jasric89/headfirstgo/tree/master/Chapter5/datafile I've rectified that error and re pushed to my repo. I then tried editing my mod file to be v1.2 as I have noticed my average program found here: https://github.com/jasric89/headfirstgo/tree/master/Chapter5/average is not pulling through the lastest change from my data file program. Even though Ive ran go get github.com/jasric89/headfirstgo/Chapter5/datafile@upgrade

Sooo how on earth do I update modules? I was following this: https://www.mend.io/free-developer-tools/blog/golang-dependency-management/ and this: https://go.dev/ref/mod again Go Docs are not helpful just a load of wish wash.

GitHub

This is a repo that I am using to learn go from the headfirst go book - jasric89/headfirstgo

GitHub

This is a repo that I am using to learn go from the headfirst go book - jasric89/headfirstgo

sharp egret
#

unless you bump the major version (e.g. v1 to v2), you don’t update a module by changing its path

#

you simply add a new git tag, e.g. a tag called v1.2.0

pastel field
#

ohhh

#

so it uses git tagging to update minor versions?

#

Do you have a site where someone has laid this out on how to do it because the stuff ive found is not helpful they all talk about majour upgrades which I think for a majour one I have to make a new file, then move the stuff to a new file and then append the mod to v2?

sharp egret
#

every version, including major ones. it’s just that major versions also change the path (since they have incompatible changes).

#

the link you included above isn’t really meant to be a narrative tutorial; it’s meant to include the precise technical information for everything in case you have a question about the specifics of how something works.