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
It is recommended to set the initial version of the goki module to 1.5+, of course, a reasonable setting is the maximum of all previous module versions. The reason for this doubt is that the go module database server has recorded the release version number of each module before, except for the new goki module, the rest of the modules will prompt the version error and fail when doing go mod tidy, settle the archive or delete the gi and other module repositories, they I guess that their old version numbers are still in the go module server and cannot be deleted. A long time ago, my practice was to never release a version, and even a stable version used the auto-generated version with the date.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It is recommended to set the initial version of the goki module to 1.5+, of course, a reasonable setting is the maximum of all previous module versions. The reason for this doubt is that the go module database server has recorded the release version number of each module before, except for the new goki module, the rest of the modules will prompt the version error and fail when doing go mod tidy, settle the archive or delete the gi and other module repositories, they I guess that their old version numbers are still in the go module server and cannot be deleted. A long time ago, my practice was to never release a version, and even a stable version used the auto-generated version with the date.
Beta Was this translation helpful? Give feedback.
All reactions