# appimage-tools These are pinned copies of the AppImage build tools for BlueGit CI, so a build doesn't depend on GitHub at run time. | File | Upstream | SHA-256 | |---|---|---| | `appimagetool-x86_64.AppImage` | AppImage/appimagetool release `1.9.1` | `ed4ce84f0d9caff66f50bcca6ff6f35aae54ce8135408b3fa33abfc3cb384eb0` | | `runtime-x86_64` | AppImage/type2-runtime release `20251108` | `2fca8b443c92510f1483a883f60061ad09b46b978b2631c807cd873a47ec260d` | Both checksums match the digests that GitHub publishes for those release assets. Both projects are MIT-licensed; the licence texts are in `licenses/`. A tag push runs the pipeline. It checks `tools/SHA256SUMS` and publishes the files as release assets of that tag: ``` https://git.timfalken.com/golden-age/appimage-tools/-/releases//assets/ ``` Current release: `appimagetool-1.9.1_runtime-20251108`. Use the runtime with `appimagetool --runtime-file runtime-x86_64`; without it, appimagetool downloads an unpinned runtime from GitHub. Consumers pin the SHA-256 values themselves (e.g. `golden-age/paperdoll-renderer` `scripts/package/appimage.sh`). For a new version: add the files, update `SHA256SUMS` and this table, then push a new tag. Existing tags and releases are never changed.