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
We are migrating to go modules.
One of our dependency is golang.org/x/crypto, however, there is no tags or releases maintained for this repo.
After does go module decide the version of the crypto?
golang.org/x/crypto v0.0.0-20191106202628-ed6320f186d4
Best Regards,
The text was updated successfully, but these errors were encountered:
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:
Hi guys,
We are migrating to go modules.
One of our dependency is golang.org/x/crypto, however, there is no tags or releases maintained for this repo.
After does go module decide the version of the crypto?
golang.org/x/crypto v0.0.0-20191106202628-ed6320f186d4
Best Regards,
The text was updated successfully, but these errors were encountered: