[Bug] scoop isn't updataing some of my packages even when the version has changed.

[ingenarel]

Bug Report

Current Behavior

i've made a scoop bucket that are -git packages.
they download the source code's git repository, then builds the tool
and when there's a new commit, the version gets updated.
the thing is, [glab-git] package's version is 1afccf0f2ff1519b8dd6d563de309288e0172237 it's the commit hash of the glab-cli's latest commit
i've updated my local buckets, but still i can't update the package

Expected Behavior

a package should be updated when a version has changed

Additional context/output

i've done everything i can, previously i used only 1 decoy file
a decoy file is just a small text decoy file i downloaded to get around scoop's url and hash problem. because i use git clone to actually install the source code.
i've tried package specific decoy files
i've even tried updating the decoy files, so both the version and the hash entry in the scoop manifest gets updated, possibly registering an update

Possible Solution

i don't know scoop is written, or how scoop works. but my guess is it's doing trying to see if a package has numbers, and which version has a bigger number, and the version that has the bigger number gets recognized as the latest version.
the current commit hash is 1afccf0f2ff1519b8dd6d563de309288e0172237
glab-git on my pc is stuck on 637e9ce1ac0de1f70a16bd20a12636c95ac42128

System details

Windows version: 10

OS architecture: 64 bit

PowerShell version: 5.1.19041.4894

Additional software: git

Scoop Configuration

{
    "last_update":  "2024-10-12T16:52:31.9285841+06:00",
    "scoop_repo":  "https://github.com/ScoopInstaller/Scoop",
    "scoop_branch":  "master"
}

[niheaven]

To forcefully update packages, you should specify scoop config force_update true; otherwise, Scoop may not recognize that the axxxx version is an update of the cxxxx version.

[Virakal]

To forcefully update packages, you should specify scoop config force_update true; otherwise, Scoop may not recognize that the axxxx version is an update of the cxxxx version.

I'm having the same issue and this fixed it for me. Is there anything we can do in the bucket to apply this on an individual package level?