go get v0.1.2/v0.1.3 confusion about sqlite HOT 4 CLOSED

This is normal behavior for go modules when you update to an untagged commit that is after a tagged version.

from sqlite.

Is everything about the behavior I see expected to you?

How come that a v0.1.3 seems to exist (I guess it's existence from the version name when updating to master) but I cannot update to it?

from sqlite.

Is everything about the behavior I see expected to you?

Yes. The latest version tag is v0.1.2. The latest commit on master is past that point. When you run go get crawshaw.io/sqlite@master you are instructing it to fetch the latest commit on master. Go modules gives this commit a name in your go.mod file and part of that name includes what you might call a "pseudo" version, which is a minor version above the most recently published tagged version.

When you run go get crawshaw.io/[email protected] it fails because this tag does not actually exist. The v0.1.3 is just a placeholder for what go modules assumes the next version tag would be.

When you run go get crawshaw.io/sqlite it gets the latest tagged commit, which is v0.1.2.

All of this is normal behavior.

Sometime later today I will release a new minor version that includes bug fixes and a few extra features. This will be v0.2.0 so just look out for that sometime this week.

from sqlite.

Thank you for the thorough explanation. Now I understand.

I wasn't aware of the minor+1 pseudo commit. TIL :)

from sqlite.