Repository navigation
Conversation
divijg19
commented
Sep 29, 2026
divijg19
left a comment
divijg19
left a comment
Owner
Author
There was a problem hiding this comment.
v2.0.0: adopt /v2 module path so go install resolves the release
The v2.0.0 release published on 2026-09-28 was invisible to the Go module
system. The tag was hard-rejected by the module proxy:
invalid version: module contains a go.mod file, so module path must
match major version ("github.com/divijg19/Helm/v2")
This is a rejection, not a skip, so `go list -m -versions` stopped at v1.9.9
and `go install …@latest` fell back to it, failing on its `module helm`
declaration. The release looked healthy end to end — goreleaser succeeded,
assets downloaded, the curl installer worked — which is why it went unnoticed.
The `/v2` is a module-path suffix on the `module` line only. No `v2/`
directory is involved: the tree, the GoReleaser `main:` path, the archive
layout, and `go build -o helm ./cmd/helm` are all unchanged.
Applied in lockstep across the module line, all 17 internal imports, and
every `-X` ldflag target (GoReleaser plus the end-to-end test build, whose
golden files pin the injected version). Also folds in the README refactor
from main, with its heading levels corrected from #### to ###, hard-wrapped
prose unwrapped, and trailing whitespace removed; the prose content is
unchanged.
Note: 9940a94 is mislabelled "v0.2.0+". Left as-is rather than force-pushing
main to amend it.
Verified: gofmt, go vet, go build, go mod tidy (no drift), go test, go test
-race, staticcheck, golangci-lint, goreleaser check, and shellcheck all
clean. go install of this tree against a local module proxy installs and
runs clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v2.0.0 release published on 2026-09-28 was invisible to the Go module system. The tag was hard-rejected by the module proxy:
This is a rejection, not a skip, so
go list -m -versionsstopped at v1.9.9 andgo install …@latestfell back to it, failing on itsmodule helmdeclaration. The release looked healthy end to end — goreleaser succeeded, assets downloaded, the curl installer worked — which is why it went unnoticed.The
/v2is a module-path suffix on themoduleline only. Nov2/directory is involved: the tree, the GoReleasermain:path, the archive layout, andgo build -o helm ./cmd/helmare all unchanged.Applied in lockstep across the module line, all 17 internal imports, and every
-Xldflag target (GoReleaser plus the end-to-end test build, whose golden files pin the injected version). Also folds in the README refactor from main, with its heading levels corrected from #### to ###, hard-wrapped prose unwrapped, and trailing whitespace removed; the prose content is unchanged.Note: 9940a94 is mislabelled "v0.2.0+". Left as-is rather than force-pushing main to amend it.
Verified: gofmt, go vet, go build, go mod tidy (no drift), go test, go test -race, staticcheck, golangci-lint, goreleaser check, and shellcheck all clean. go install of this tree against a local module proxy installs and runs clean.