[Bug]: nu is still at version 0.93.0 although 0.94.2 is the latest release
pfmoore opened this issue · comments
Paul Moore commented
Prerequisites
- I have written a descriptive issue title.
- I have searched all issues/PRs to ensure it has not already been reported or fixed.
- I have verified that I am using the latest version of Scoop and corresponding bucket.
Package Name
nu
Expected/Current Behaviour
The available version is 0.93.0, but 0.94.2 is available on the nushell github releases page.
Steps to Reproduce
❯ scoop info nu
Name : nu
Description : A modern shell written in Rust
Version : 0.93.0
Bucket : main
Website : https://www.nushell.sh
License : MIT
Updated at : 01/05/2024 22:10:34
Updated by : github-actions[bot]
Possible Solution
The autoupdate string in the bucket json file seems to be wrong:
"autoupdate": {
"architecture": {
"64bit": {
"url": "https://github.com/nushell/nushell/releases/download/$version/nu-$version-x86_64-windows-msvc-full.zip"
},
The correct URL is https://github.com/nushell/nushell/releases/download/$version/nu-$version-x86_64-pc-windows-msvc-full.zip. It looks like the format changed in 0.94.0.
Scoop and Buckets Version
❯ scoop --version
Current Scoop version:
d337bb1f (HEAD -> master, tag: v0.4.2, origin/master, origin/HEAD) chore(release): Bump to version 0.4.2 (#5964)
'main' bucket:
834f4d840 (HEAD -> master, origin/master, origin/HEAD) nodejs@22.2.0: Fix hash (Closes #5893)
'extras' bucket:
fd4932e97 (HEAD -> master, origin/master, origin/HEAD) stirling-pdf: Update to version 0.25.3
'versions' bucket:
7880a512c (HEAD -> master, origin/master, origin/HEAD) vscode-insiders: Update to version 1.91.0-insider+1717746651462
'java' bucket:
22628523 (HEAD -> master, origin/master, origin/HEAD) temurin17-nightly-jre: Update to version 17.0.12-5.0.ea
'enk' bucket:
964bf0f (HEAD -> master, origin/master, origin/HEAD) uv 0.2.9
Scoop Config
❯ scoop config
last_update scoop_repo scoop_branch
----------- ---------- ------------
07/06/2024 15:03:23 https://github.com/lukesampson/scoop master
PowerShell Version
Name Value
---- -----
PSVersion 7.4.2
PSEdition Core
GitCommitId 7.4.2
OS Microsoft Windows 10.0.22631
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Additional Softwares
No response
Paul Moore commented
Thanks, I hadn't spotted that when I did a search.
de-odex commented
i apologise if this is not proper etiquette when it comes to PRs, i just assumed the reason the other PR wasnt approved yet was because of the outdated version, so i made another PR with an updated version and hash
(also foolishly pr'd my own repo...)