I am not sure how common this is, but I stumbled on this project where release assets have a tar.xz extension.
This the output:
2025/03/24 13:14:32 listening on :3000...
2025/03/24 13:15:04 fetching asset info for tursodatabase/libsql@latest
2025/03/24 13:15:04 fetched asset has unsupported file type: dist-manifest.json (ext '.json')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-aarch64-apple-darwin.tar.xz (ext '.tar.xz')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-aarch64-apple-darwin.tar.xz.sha256 (ext '.sha256')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-aarch64-unknown-linux-gnu.tar.xz (ext '.tar.xz')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-aarch64-unknown-linux-gnu.tar.xz.sha256 (ext '.sha256')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-installer.sh (ext '.sh')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-x86_64-apple-darwin.tar.xz (ext '.tar.xz')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-x86_64-apple-darwin.tar.xz.sha256 (ext '.sha256')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-x86_64-unknown-linux-gnu.tar.xz (ext '.tar.xz')
2025/03/24 13:15:04 fetched asset has unsupported file type: libsql-server-x86_64-unknown-linux-gnu.tar.xz.sha256 (ext '.sha256')
2025/03/24 13:15:04 fetched asset has unknown os: source.tar.gz
2025/03/24 13:15:04 fetched asset has unsupported file type: source.tar.gz.sha256 (ext '.sha256')
2025/03/24 13:15:04 fetched asset has unsupported file type: sqld.rb (ext '.rb')
I am not sure how common this is, but I stumbled on this project where release assets have a
tar.xzextension.This the output: