Failed to resolve go module with incompatible semantic version

When generating a module that does not follow the semantic versioning rules proposed by go modules, the suffix +incompatible is added to the version to show that upgrading to this can potentially break your application.

Users can still use the command go get module@version without the suffix, but it will be added to the version in the go.mod file and it will be used when publishing the module to Artifactory.

The issue is that, after publishing the module to Artifactory, I'm not able to resolve it without adding the suffix to the version manually. So the command below does not work:

frog rt go --server-id=go-central-devenv "get github.com/elioengcomp/go-module-example@v2.0.0" go-staging

Instead, I need to use:

frog rt go --server-id=go-central-devenv "get github.com/elioengcomp/go-module-example@v2.0.0+incompatible" go-staging

The former command works when resolving from GitHub.