Why is Total Commander "stuck" at version 10.0 on chocolatey?

[gobalius]

Total Commander package is "stuck" at version 10.0.0.20210903
I can see a discussion about the installation path and there was a bug, which got fixed, as far as I understand it. The package is automatically maintained (AU), the files in the repo get updated (they show 10.52 as the latest version), however, when doing choco upgrade totalcommander it says I already have the latest 10.0.0.20210903

[RedBaron2]

@gobalius
It would appear that something needs to be done to fix this being approved by the automated system for the chocolatey community feed.
Maybe @gep13, @AdmiringWorm, or @pauby might be able to find out why this package fails to be approved for the community feed.

[pauby]

@RedBaron2 @gobalius The package failed validation as can be seen from the (latest) failed version.

[gobalius]

The validation failing confuses me... it says binary files are included in the package, but I don't see any in the package folder in the repo...

[pauby]

@gobalius Can you point to where it says that so I can look?

[gobalius]

@pauby on the link you provided, it says, quote:

This package was rejected on 30 Nov 2022. The reviewer chocolatey-ops has listed the following reason(s):
Binary files (.exe, .msi, .zip) have been included. The reviewer will ensure the maintainers have distribution rights. More...

[gobalius]

Oh... it was an unfortunate scroll... the first line I copied and the second one are not supposed to be together... I got this totally wrong. I still don't exactly know what is wrong, but it's not what it seemed to me before.

[pauby]

It is failing Package Validator for this reason:

A quick check looks like it is likely this and maybe also this.

[TheCakeIsNaOH]

The reason behind the usage of $env:chocolateyInstallArguments is due to this bug: chocolatey/choco#2345