I have a project that depends on vault/api, and I’d like to use a feature in v1.11. Why does the
@latest version query point to
% go version go version go1.19.1 darwin/amd64 % cd $(mktemp -d) % go mod init tmp % go get github.com/hashicorp/vault/api@latest # ...snip... % grep vault/api go.mod github.com/hashicorp/vault/api v1.8.0 // indirect % go get email@example.com go: module firstname.lastname@example.org found (v1.11.4), but does not contain package github.com/hashicorp/vault/api
Is it because of this version constraint in the top-level go.mod? I see the PR that last changed that constraint here:
Does that mean the api module release cadence is different from the server and sdk releases? Is there documentation to that effect? Historically, I’ve been blissfully ignorant of go module resolution. In this case, though, I think I need to update my understanding.