Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-17707

Failed to resolve go module with incompatible semantic version

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: 4 - Normal
    • Resolution: Deferred
    • Affects Version/s: 6.5.2
    • Fix Version/s: None
    • Component/s: Go
    • Severity:
      Medium

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              eliom Elio Marcolino
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Sync Status

                  Connection: RTFACT Sync
                  RTMID-17707 -
                  SYNCHRONIZED
                  • Last Sync Date: