bach feed writes the small JSON file an installed app reads to learn about a newer version. bach build already writes it when your [updates] has github or a download_url. Use bach feed to write it again after signing, because signing changes the file and its SHA-256.
The feed
latest.json
versionis read from the setup file’s manifest.sha256is computed from the file on disk, so run the command on the final, signed file.sizeis the setup file’s size in bytes. The installed app uses it to check the disk has room before downloading.rolloutis only there with--rollout. Write the feed again without it to release to everybody.deltais only there with a patch:{ "from", "url", "sha256", "size" }.bach build --patch-fromadds it by itself when the patch is at least a fifth smaller than the full file.notesis left out when you do not pass--notesor--notes-file, and is cut at 4000 characters.
Errors
- Without
--urland without abach.tomlwith an[updates]download link, the command asks for the https link. - A link that is not
httpsis refused. - A file that is not a Bach setup file, or is an uninstaller, is refused with a sentence. So is an update patch given as
FILE: pass the full setup file and the patch with--patch. - A
--patchfile that is not an update patch is refused.