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
{{ message }}
This repository was archived by the owner on Mar 1, 2021. It is now read-only.
Currently if I change #tool "dotnet:https://api.nuget.org/v3/index.json?package=GitVersion.Tool&version=4.0.1-beta1-53"
to #tool "dotnet:https://api.nuget.org/v3/index.json?package=GitVersion.Tool&version=4.0.1-beta1-58"
It won't use the new version, and that's not what's expected when pinning a version.
Directory structure is
tools\.store\gitversion.tool\{version}
So if differs one should be able to run dotnet tool uninstall --tool-path .\tools\ GitVersion.Tool and then install.
dotnet tool uninstall --tool-path .\tools\ GitVersion.Tool
+ Tool 'gitversion.tool' (version '4.0.1-beta1-53') was successfully uninstalled.
dotnet tool install --tool-path .\tools\ --version="4.0.1-beta1-58" GitVersion.Tool
+ You can invoke the tool using the following command: dotnet-gitversion+ Tool 'gitversion.tool' (version '4.0.1-beta1-58') was successfully installed.
Previously, the Module wouldn't check to see what version of a Tool was
installed. As a result, when a tool was already installed, even if a
newer version was requested, it wouldn't be installed. This is really
down to the underlying tool and how it works, but smarts have now been
put into the module, to check installed version, against what is
requested, so that an uninstall is first executed, and then the requested
version is installed.
…ool version
Previously, the Module wouldn't check to see what version of a Tool was
installed. As a result, when a tool was already installed, even if a
newer version was requested, it wouldn't be installed. This is really
down to the underlying tool and how it works, but smarts have now been
put into the module, to check installed version, against what is
requested, so that an uninstall is first executed, and then the requested
version is installed.
…ool version
Previously, the Module wouldn't check to see what version of a Tool was
installed. As a result, when a tool was already installed, even if a
newer version was requested, it wouldn't be installed. This is really
down to the underlying tool and how it works, but smarts have now been
put into the module, to check installed version, against what is
requested, so that an uninstall is first executed, and then the requested
version is installed.
devlead
pushed a commit
to devlead/cake
that referenced
this issue
Feb 27, 2021
…ool version
Previously, the Module wouldn't check to see what version of a Tool was
installed. As a result, when a tool was already installed, even if a
newer version was requested, it wouldn't be installed. This is really
down to the underlying tool and how it works, but smarts have now been
put into the module, to check installed version, against what is
requested, so that an uninstall is first executed, and then the requested
version is installed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently if I change
#tool "dotnet:https://api.nuget.org/v3/index.json?package=GitVersion.Tool&version=4.0.1-beta1-53"
to
#tool "dotnet:https://api.nuget.org/v3/index.json?package=GitVersion.Tool&version=4.0.1-beta1-58"
It won't use the new version, and that's not what's expected when pinning a version.
Directory structure is
So if differs one should be able to run
dotnet tool uninstall --tool-path .\tools\ GitVersion.Tool
and then install.Code for reference:
Cake.DotNetTool.Module/Source/Cake.DotNetTool.Module/DotNetToolPackageInstaller.cs
Lines 114 to 117 in 1bbd2aa
The text was updated successfully, but these errors were encountered: