Skip to content

fix: Add required /v2 module path suffix for v2.0.0 release - #25

Merged
eshaffer321 merged 1 commit into
mainfrom
fix/v2-module-suffix
Jul 1, 2026
Merged

eshaffer321 merged 1 commit into
mainfrom
fix/v2-module-suffix

Conversation

@eshaffer321

Copy link
Copy Markdown
Owner

Summary

  • Go requires the module path to end in /vN for any major version N >= 2 (declared go.mod path must match the tag), otherwise go get rejects the version with "invalid version: module contains a go.mod file, so module path must match major version"
  • The previous rebrand PR (chore!: Rebrand from MonarchMoney to Monarch (v2.0.0) #24) tagged v2.0.0 without this suffix and the tag had to be deleted
  • This updates the module path to github.com/eshaffer321/monarch-go/v2 and all internal imports, docs, and the mcp-server submodule's go.mod to match

Test plan

  • go build ./... passes (root module)
  • go vet ./... passes
  • go test ./pkg/monarch/... passes
  • go build ./... && go test ./... passes in cmd/mcp-server after go mod tidy
  • Swept for any remaining eshaffer321/monarch-go import paths missing the /v2 suffix

Go's module versioning rules require the module path to end in /vN for
any major version N >= 2 (go.mod's declared path must match the tag),
otherwise `go get` rejects the tag with "invalid version" errors. The
prior rebrand commit tagged v2.0.0 without the suffix; this updates the
module path to github.com/eshaffer321/monarch-go/v2 and all internal
imports/docs to match before re-tagging.
@eshaffer321
eshaffer321 merged commit 7b41520 into main Jul 1, 2026
11 checks passed
@eshaffer321
eshaffer321 deleted the fix/v2-module-suffix branch July 1, 2026 19:33
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