Provide checksums for GitHub release assets #10328

New issue

Open

opened 2026-02-21 20:42:05 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 20:42:05 -05:00

Owner

Originally created by @Piccirello on GitHub (Apr 30, 2020).

Checksums for Sourceforge releases are hosted at qbittorrent.org. No such checksums exist for the .zip and .tar.gz assets attached to each GitHub release.

Ideally, the changelog of each GitHub release (currently unused) can include the relevant checksums. This would result in the checksum being displayed inline directly on the Releases page. Alternatively, the checksums can be included in an additional checksums.txt release asset (example).

Originally created by @Piccirello on GitHub (Apr 30, 2020). Checksums for Sourceforge releases are hosted at qbittorrent.org. No such checksums exist for the `.zip` and `.tar.gz` assets attached to each GitHub release. Ideally, the changelog of each GitHub release (currently unused) can include the relevant checksums. This would result in the checksum being displayed inline directly on the Releases page. Alternatively, the checksums can be included in an additional `checksums.txt` release asset ([example](https://github.com/DopplerHQ/cli/releases)).

deekerman added the

Project management

label

2026-02-21 20:42:05 -05:00

deekerman commented

2026-02-21 20:42:08 -05:00

Author

Owner

@Piccirello commented on GitHub (Apr 30, 2020):

To provide a concrete use-case: I'm migrating from running qBittorrent in a VM to running it in a Docker container. During the build phase, when downloading the source, I'd like to have a SHA256 hash that the download can be compared against.

Btw, I've added the Project management label, though I'm not sure that's strictly correct.

@Piccirello commented on GitHub (Apr 30, 2020): To provide a concrete use-case: I'm migrating from running qBittorrent in a VM to running it in a Docker container. During the build phase, when downloading the source, I'd like to have a SHA256 hash that the download can be compared against. Btw, I've added the `Project management` label, though I'm not sure that's strictly correct.

deekerman commented

2026-02-21 20:42:11 -05:00

Author

Owner

@Piccirello commented on GitHub (May 1, 2020):

@sledgehammer999 forgive the ping, I believe you're the only person than can address this issue.

@Piccirello commented on GitHub (May 1, 2020): @sledgehammer999 forgive the ping, I believe you're the only person than can address this issue.

deekerman commented

2026-02-21 20:42:11 -05:00

Author

Owner

@FranciscoPombal commented on GitHub (May 1, 2020):

This can be done manually, but IMO ideally it is the sort of stuff that should be automated.
https://github.com/qbittorrent/qBittorrent/issues/12357 is a step in that direction, though right now the focus of that effort is on nightly builds using vcpkg to get the dependencies, which is currently deemed not suitable for the official release process.

This repository could benefit greatly from more usage of GitHub Actions and bots, but deployment of such tools is only possible at the maintainer's discretion.

@FranciscoPombal commented on GitHub (May 1, 2020): This can be done manually, but IMO ideally it is the sort of stuff that should be automated. https://github.com/qbittorrent/qBittorrent/issues/12357 is a step in that direction, though right now the focus of that effort is on nightly builds using vcpkg to get the dependencies, which is currently deemed not suitable for the official release process. This repository could benefit greatly from more usage of GitHub Actions and bots, but deployment of such tools is only possible at the maintainer's discretion.