You are looking at file versioning, rather than taking the actual version the program itself lists in the system after installation. This causes the package to always show an available update when, in fact, that version has already been installed / updated to (see console output below).
The script needs to be modified to force override the build number to zero.
Yes, I agree it's not ideal that JetBrains themselves doesn't use the same version information in all places. Regardless, I've come to understand that generally the informational version that does match the version listed under installed programs in Windows is / should be used in the manifests to match.
PS C:\Users\Administrator> winget update
Name ID Version Verfügbar Quelle
--------------------------------------------------------------
JetBrains Toolbox JetBrains.Toolbox 3.3.0.0 3.3.0.74186 winget
1 update available.
You are looking at file versioning, rather than taking the actual version the program itself lists in the system after installation. This causes the package to always show an available update when, in fact, that version has already been installed / updated to (see console output below).
The script needs to be modified to force override the build number to zero.
Yes, I agree it's not ideal that JetBrains themselves doesn't use the same version information in all places. Regardless, I've come to understand that generally the informational version that does match the version listed under installed programs in Windows is / should be used in the manifests to match.