Home > Article > Backend Development > Why Is My Go Version Command Stuck on an Old Version After Upgrading?
Go Version Command Stuck on Old Version After Upgrade
Despite successfully installing Go 1.8, the go version command continues to display the old version (1.7.5) for a user. They have double-checked the installation in /usr/local/go/bin and ruled out interference from external processes. Their Webstorm IDE correctly identifies 1.8 as the active version, and they cannot utilize the "NextResultSet()" SQL feature introduced in 1.8.
Suspecting a configuration error in their .bashrc file, the user has been unable to locate the cause.
Solution:
The user encountered a common issue where updating Go through the official website doesn't always update the command-line version. To resolve this, they should install or upgrade Go via Homebrew:
brew update brew upgrade golang
After running these commands, the go version command should accurately reflect the installed Go version.
The above is the detailed content of Why Is My Go Version Command Stuck on an Old Version After Upgrading?. For more information, please follow other related articles on the PHP Chinese website!