Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Releases require a manual navigation to the released package URL #499

Open
dblock opened this issue Apr 1, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@dblock
Copy link
Member

dblock commented Apr 1, 2024

What is the bug?

When releasing 3.1.0 I ran into #498 (comment).

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/[email protected] 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/[email protected] 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.

How can one reproduce the bug?

  1. Make a release per https://github.com/opensearch-project/opensearch-go/blob/main/RELEASING.md#releasing.
  2. Observe it not appearing on https://pkg.go.dev/github.com/opensearch-project/opensearch-go/v3

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

@dblock dblock added bug Something isn't working untriaged and removed untriaged labels Apr 1, 2024
@dblock dblock removed the untriaged label Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant