Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How does go module decide the version if the 3rd party repo doesn't have tag or releases? #35611

GingerMoon opened this issue Nov 15, 2019 · 1 comment


Copy link

@GingerMoon GingerMoon commented Nov 15, 2019

Hi guys,

We are migrating to go modules.
One of our dependency is, however, there is no tags or releases maintained for this repo.
After does go module decide the version of the crypto? v0.0.0-20191106202628-ed6320f186d4

Best Regards,


This comment has been minimized.

Copy link

@agnivade agnivade commented Nov 15, 2019

Please see -

For each named package or package pattern, get must decide which version of the corresponding module to use. By default, get looks up the latest tagged release version, such as v0.4.5 or v1.2.3. If there are no tagged release versions, get looks up the latest tagged pre-release version, such as v0.0.1-pre1. If there are no tagged versions at all, get looks up the latest known commit. If the module is not already required at a later version (for example, a pre-release newer than the latest release), get will use the version it looked up. Otherwise, get will use the currently required version.

I will close this issue, but if you have further questions, please feel free to ask it in any of these forums below:


@agnivade agnivade closed this Nov 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.