[Bug] Inconsistent version reported by `scoop --version`

[kdeldycke]

Bug Report

Current Behavior

In a terminal, I'm looking for the Scoop version and get:

> scoop --version
Current Scoop version:
b588a06e (HEAD -> master, tag: v0.5.3, origin/master, origin/HEAD) Bump to version 0.5.3 (resync) (#6436)

'main' bucket:
46c50c6b0 (HEAD -> master, origin/master, origin/HEAD) aqua: fix arm64 version (#7071)

Expected Behavior

That looks new to me, as I used to have an output like that:

> scoop --version
Current Scoop version:
v0.5.3 - Released at 2025-08-11

'main' bucket:
46c50c6b0 (HEAD -> master, origin/master, origin/HEAD) aqua: fix arm64 version (#7071)

Additional context/output

I am expecting a clean version output as that is what I am relying on to detect the presence of a fresh Scoop CLI in my Meta Package Manager project.

For reference, my current implementation is based on regular expressions.

Possible Solution

I bypassed that issue by looking harder at a version string in the output produced by Git but that is too fragile.

My guess is the format of the CHANGELOG.md had a recent subtle change that made the regular expression not matching anymore:

Scoop/bin/scoop.ps1

Lines 22 to 29 in b588a06

	Write-Host 'Current Scoop version:'
	if (Test-GitAvailable -and (Test-Path "$PSScriptRoot\..\.git") -and (get_config SCOOP_BRANCH 'master') -ne 'master') {
	Invoke-Git -Path "$PSScriptRoot\.." -ArgumentList @('log', 'HEAD', '-1', '--oneline')
	} else {
	$version = Select-String -Pattern '^## \[(v[\d.]+)\].*?([\d-]+)$' -Path "$PSScriptRoot\..\CHANGELOG.md"
	Write-Host $version.Matches.Groups[1].Value -ForegroundColor Cyan -NoNewline
	Write-Host " - Released at $($version.Matches.Groups[2].Value)"
	}

Or maybe the logic needs to be tweaked a bit so that the official released version is returned if the commit is a tag.

System details

Windows version: 11 Pro

OS architecture: arm64

PowerShell version: 5.1.22000.2538

Additional software: Git v2.50.1.windows.1

Scoop Configuration

Default.

[kdeldycke]

Also, when run in a terminal, I get the following, as I mentioned above:

> scoop --version
Current Scoop version:
b588a06e (HEAD -> master, tag: v0.5.3, origin/master, origin/HEAD) Bump to version 0.5.3 (resync) (#6436)

'main' bucket:
46c50c6b0 (HEAD -> master, origin/master, origin/HEAD) aqua: fix arm64 version (#7071)

But if I run the scoop --version command in a Python subprocess, I get the following output instead:

> scoop --version
Current Scoop version:
b588a06e chore(release): Bump to version 0.5.3 (resync) (#6436)

'main' bucket:
46c50c6b0 aqua: fix arm64 version (#7071)

As you can see all the branches and tags information is lost: (HEAD -> master, tag: v0.5.3, origin/master, origin/HEAD) is not displayed.

I guess this is because running in a process, and not an interactive terminal, the Git CLI is stripped of all context and user-set configuration. Which means git is called as a bare command, and defaults to a non-verbose log output.

A solution would be to expand the git log HEAD -1 --oneline command and add the necessary parameters to make sure that the results adds branches and tags data.

This is related to #6270.

[z-Fng]

That looks new to me, as I used to have an output like that:

scoop --version
Current Scoop version:
v0.5.3 - Released at 2025-08-11
'main' bucket:
46c50c6b0 (HEAD -> master, origin/master, origin/HEAD) aqua: fix arm64 version (#7071)

It was introduced in 360daa7 (#5122). Missing brackets here for the Test-GitAvailable function:

Scoop/bin/scoop.ps1

Line 23 in b588a06

if (Test-GitAvailable -and (Test-Path "$PSScriptRoot\..\.git") -and (get_config SCOOP_BRANCH 'master') -ne 'master') {

A simple example:

function RetTrue() {return $True}
function RetFalse() {return $False}
Write-Host (RetTrue -and RetFalse)
Write-Host (RetTrue -and (RetFalse))
Write-Host ((RetTrue) -and (RetFalse))

[kdeldycke]

It was introduced in 360daa7 (#5122). Missing brackets here for the Test-GitAvailable function:

Good catch! And thanks for the PR! :)

[z-Fng]

I am expecting a clean version output as that is what I am relying on to detect the presence of a fresh Scoop CLI in my Meta Package Manager project.

Hi, I’m glad to let you know that PR #6463 has been merged into the develop branch. This fix will be included in the next release.

As you can see all the branches and tags information is lost: (HEAD -> master, tag: v0.5.3, origin/master, origin/HEAD) is not displayed.

However, as we discussed in #6463 (comment), to avoid breaking existing workflows, the absence of branch and tag information in non-terminal environments will likely remain unchanged for the foreseeable future.

The fix for issue #6270 is still underway.