Felix Krueger
04/19/2026, 4:32 PM--discard-untrimmed, JSON trimming report for MultiQC native parsing (once MultiQC is updated), MultiQC-compatible.
Install:
• crates.io: cargo install trim-galore --version 2.1.0-beta.1 (the --version flag is required — plain cargo install trim-galore still resolves to v2.0.0 until GA)
• Docker (tag): <http://ghcr.io/felixkrueger/trimgalore:v2.1.0-beta.1|ghcr.io/felixkrueger/trimgalore:v2.1.0-beta.1> — or :beta for the moving “latest beta”
• Docker (digest, deterministic): <http://ghcr.io/felixkrueger/trimgalore@sha256:3e5dd519ea992ce88eb6f01e8d051a33f356e9ecd2d45e79a9c9bd0ac05c5b77|ghcr.io/felixkrueger/trimgalore@sha256:3e5dd519ea992ce88eb6f01e8d051a33f356e9ecd2d45e79a9c9bd0ac05c5b77>
• Multi-arch: linux/amd64 + linux/arm64
nf-core/rnaseq integration: PR https://github.com/nf-core/rnaseq/pull/1789 is green on full matrix — x86 (40/40), arm64 (28/28), GPU (4/4). Pinned to image digest so runs are deterministic. No MD5 drift on reference outputs; MultiQC parses both report formats.
Release notes:
https://github.com/FelixKrueger/TrimGalore/releases/tag/v2.1.0-beta.1
GA-tracking PR:
https://github.com/FelixKrueger/TrimGalore/pull/214 (draft, do-not-merge-until-GA)
Announcement + feedback hub:
https://github.com/FelixKrueger/TrimGalore/discussions/215
I am aiming for a 2-week beta window (planned release ~2026-05-03), assuming no critical issues. I would be very happy for some stress-testing, and to hear any feedback. Many thanks! 🫶Felix Krueger
04/20/2026, 7:32 AMcargo install --git <https://github.com/FelixKrueger/TrimGalore> --branch optimus_prime trim-galore --force