You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting with major version 2, module paths must have a major version suffix like /v2 that matches the major version. For example, if a module has the path example.com/mod at v1.0.0, it must have the path example.com/mod/v2 at version v2.0.0.
To Reproduce 🚧
$ go get github.com/ctreminiom/go-atlassian
go: downloading github.com/ctreminiom/go-atlassian v1.6.1
go: added github.com/ctreminiom/go-atlassian v1.6.1
$ go get github.com/ctreminiom/[email protected]
go: github.com/ctreminiom/[email protected]: invalid version: module contains a go.mod file, so module path must match major version ("github.com/ctreminiom/go-atlassian/v2")
Expected behavior ✅
A version v2.1.1 should be downloaded
Screenshots 📄
None.
Additional context
None.
The text was updated successfully, but these errors were encountered:
go-atlassian version
v2.0.0
-v2.1.1
go-atlassian component
Describe the bug 🐛
Users are unable to use
v2.0.0+
versions of the library.The tagged version of the library
v2.0.0
-v2.1.1
does not match the go module definition.The Go module file should have
..../v2
at the end of the module name.Quote from the documentation (https://go.dev/ref/mod#major-version-suffixes):
To Reproduce 🚧
Expected behavior ✅
A version v2.1.1 should be downloaded
Screenshots 📄
None.
Additional context
None.
The text was updated successfully, but these errors were encountered: