Description
Manifest consistency check is not performed after a real force update (running checkver.ps1).
It only ensures that the update runs successfully, but does not guarantee that the manifest remains the same before and after execution.
This can lead to situations where incorrect manifests go unnoticed, potentially causing installation or autoupdate issues.
Steps to Reproduce
For instance, create a PR which incorrectly modify autoupdate.hash without running checkver:
Related PRs
Description
Manifest consistency check is not performed after a real force update (running checkver.ps1).
It only ensures that the update runs successfully, but does not guarantee that the manifest remains the same before and after execution.
This can lead to situations where incorrect manifests go unnoticed, potentially causing installation or autoupdate issues.
Steps to Reproduce
For instance, create a PR which incorrectly modify autoupdate.hash without running checkver:
Related PRs
See: unigetui@3.3.5: Switch to ZIP package, add architecture field to support 64-bit only Extras#16054 (comment)
raspberry-pi-imager@1.9.5: Fix
autoupdate/urlto reflecturlchange. Extras#15767