I read in https://go.dev/doc/modules/publishing and per instructions tried running GOPROXY=proxy.golang.org go list -m github.com/opensearch-project/opensearch-go@v3.1.0 but that fails with not found: ... invalid version: go.mod has post-v3 module path "github.com/opensearch-project/opensearch-go/v3" at revision v3.1.0.
a) A release needs to ping the go service and tell it there's a new release. Likely a new workflow that runs every time a release is made.
b) An update to RELEASING.md that says to go to the release URL
What is the bug?
When releasing 3.1.0 I ran into https://github.com/opensearch-project/opensearch-go/pull/498#issuecomment-2030597365.
The release was not appearing in https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3. A workaround was to navigate to https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3@v3.1.0 and hit "request".
I read in https://go.dev/doc/modules/publishing and per instructions tried running
GOPROXY=proxy.golang.org go list -m github.com/opensearch-project/opensearch-go@v3.1.0
but that fails withnot found: ... invalid version: go.mod has post-v3 module path "github.com/opensearch-project/opensearch-go/v3" at revision v3.1.0
.How can one reproduce the bug?
What is the expected behavior?
Release appears on https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3.
Solution
Either:
a) A release needs to ping the go service and tell it there's a new release. Likely a new workflow that runs every time a release is made. b) An update to RELEASING.md that says to go to the release URL