Skip to content

Use the /v2 module path for the v2 release - #4

Merged
fschoell merged 1 commit into
mainfrom
fix/v2-module-path
Sep 10, 2026
Merged

fschoell merged 1 commit into
mainfrom
fix/v2-module-path

Conversation

@fschoell

Copy link
Copy Markdown
Contributor

Go rejects the v2.0.0 tag as it stands: a module whose go.mod lacks the /v2 suffix cannot be tagged v2 or higher, so go list -m -versions skips it on the v1 path and refuses it on the /v2 path. Nobody can depend on the release until the module path carries the major version.

Needs a new tag once merged; v2.0.0 already points at the old path.

Go rejects the v2.0.0 tag as it stands: a module whose go.mod lacks the
/v2 suffix cannot be tagged v2 or higher, so `go list -m -versions`
skips it on the v1 path and refuses it on the /v2 path. Nobody can
depend on the release until the module path carries the major version.

Needs a new tag once merged; v2.0.0 already points at the old path.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@fschoell
fschoell merged commit 92f19b0 into main Sep 10, 2026
1 check passed
@fschoell
fschoell deleted the fix/v2-module-path branch September 10, 2026 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant