-
-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(microsoft-windows-terminal) Package installs the pre-release version instead of the stable version #55
Comments
Moreover, I had the v1.0.1401.0 already installed and then I ran a chocolatey upgrade. This caused the start menu to have two entries for Microsoft Terminal.
This difference in Appx Package name would also render the chocoUninstall.ps1 script (https://github.com/mkevenaar/chocolatey-packages/blob/master/automatic/microsoft-windows-terminal/tools/chocolateyUninstall.ps1) useless since it would not actually remove the preview version from Windows. |
The link (https://api.github.com/repos/microsoft/terminal/releases) provides a JSON output of all the releases (stable and pre-release both). The boolean key
|
Thank you for creating this issue. I will have a look at it soon. |
@ptanmay143 I ended up changing the work into a Stream to have a pre-release and a stable stream automatically updating in Chocolatey. They released a pre-release and a stable release at the same time. You can see my changes in this commit: 8b14c50 |
I tried installing Windows terminal on another system using |
@ptanmay143 They have split the software into two separate parts. Could you run the following in an elevated powershell?
This will uninstall the package, the two separate packages for Microsoft Windows Terminal and then it should install the latest version of Terminal without a pre-release. Could you confirm that this is working for you so I can close this case again? |
The output of Chocolatey v0.10.15
Uninstalling the following packages:
microsoft-windows-terminal
microsoft-windows-terminal v1.1.1671.0
Skipping auto uninstaller - No registry snapshot.
microsoft-windows-terminal has been successfully uninstalled.
Chocolatey uninstalled 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). The outputs of Chocolatey v0.10.15
Installing the following packages:
microsoft-windows-terminal
By installing you accept licenses for the packages.
Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 0%
[...]
Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 99%
Progress: Downloading microsoft-windows-terminal 1.1.1671.0... 100%
microsoft-windows-terminal v1.1.1671.0 [Approved]
microsoft-windows-terminal package files install completed. Performing other installation steps.
The install of microsoft-windows-terminal was successful.
Software install location not explicitly set, could be in package or
default install location if installer.
Chocolatey installed 1/1 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). So, this still installs the |
@ptanmay143 I have pulled that version just now. Can you run the commands again? This should result in the installation of v1.0.1811.0 which should be the latest available release as of now. If you want the latest pre-release you'll need to specifically add https://chocolatey.org/packages/microsoft-windows-terminal/1.1.1812.0-beta |
PS C:\Users\ptanmay143> choco outdated
Chocolatey v0.10.15
Outdated Packages
Output is package name | current version | available version | pinned?
PS C:\Users\ptanmay143> choco list -lo
Chocolatey v0.10.15
[...]
microsoft-windows-terminal 1.1.1671.0
[...]
45 packages installed. PS C:\Users\ptanmay143> choco upgrade all
Chocolatey v0.10.15
Upgrading the following packages:
all
By upgrading you accept licenses for the packages.
[...]
microsoft-windows-terminal v1.1.1671.0 is newer than the most recent.
You must be smarter than the average bear...
[...]
Chocolatey upgraded 0/45 packages.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log). PS C:\Users\ptanmay143> choco search microsoft-windows-terminal
Chocolatey v0.10.15
microsoft-windows-terminal 1.1.1671.0 [Approved]
1 packages found. |
I also followed these steps:
And it removed both packages. The last step installed the correct version, but I am also lacking a start menu entry. Hence I cannot start the terminal since I do not know where the binary is. |
In the last command, you specified the |
Cheers! That fixed the issue and everything seems to work as expected now. No preview installed and the correct version of the Windows Terminal is installed (1.0.1811.0) |
I can confirm that this does install the correct version on my school computer as well as my personal computer. I'm closing this issue now. Thanks. |
Expected Behavior
The chocolatey package
microsoft-windows-terminal
should install the latest stable version of the terminal from the releases page. You can see the version v1.1.1671.0 is tagged as pre-release.Current Behavior
Currently, it disregards the GitHub releases tag and install the one on the top, no matter if it is the pre-release version or the stable release version.
Possible Solution
Relying on the tag of the GitHub release for getting the package would be a better option. The link (https://github.com/microsoft/terminal/releases/latest) should always point to the latest stable version (currently v1.0.1401.0) even if the upstream updates the package version.
Secondly, a different chocolatey package
microsoft-windows-terminal-beta
could be made that would track only the pre-release versions of this terminal.Steps to Reproduce (for bugs)
I'm not sure how to specify the steps to reproduce. I believe the explanation above is enough but if you think this step is absolutely necessary, please guide me on how would I properly write the steps to reproduce.
Context
As I plan to use the terminal very frequently, I would appreciate if it was running a stable version rather than a pre release version. I hope I am making sense here.
Your Environment
Notes
I would be happy to send a PR if you could guide me how the install scripts are built.
The text was updated successfully, but these errors were encountered: