The go command uses semantic versioning of the standard form vX.Y.Z to describe the module version. When modules are versioned, an app can specify use of a module version they know will be compatible with the rest of their runtime.Ī Go module version is assigned by tagging its revision in the underlying source repository. The ability to version Go modules is a key feature, providing developers a way to make sure their applications use the dependencies they intend. We also offer some guidance on keeping your Go builds working as you upgrade to Go 1.13 and later. Let’s take a look at how pseudo-versions work, and what you can expect from those changes. JFrog GoCenter, the free repository of versioned Go modules, now includes some important updates that can help you stay on course. Managing module pseudo-versions can be difficult, especially with some of the latest changes to Go.
Go modules have helped bring order to Go development, but there’s been some disorder lurking. For more information on the sunsetting of the centers read the deprecation blog post UPDATE: As of – GoCenter central repository has been sunset and all features deprecated.
