v0.18.1

Fixed

• signal classify no longer aborts when a tRNA body happens to contain the
  junction motif (#298). The CCA|adapter junction was located by requiring
  CCAGGC to occur exactly once per reference record, and that check ran
  before the common-arm check that actually identifies the junction. But the
  motif is just CCA plus the adapter's opening bases, and a 6-mer collides over
  ~75 nt of tRNA body in ~1.5% of records -- 4 of 282 in hg38, 51 of 3315 in
  danRer11. One such record aborted the entire run for that sample, and
  dropping the offenders is not neutral: 48 of danRer11's 51 are Glu, so it
  would remove most of one amino-acid family from a charging analysis.
  Candidates are now filtered by the arm first and uniqueness required of what
  survives, which resolves every record of both references to exactly one
  junction at the correct position. Two genuinely broken cases -- no arm-backed
  match, and several -- now report distinctly instead of being conflated with
  this benign one.

---

Which artifact

Artifact	Linkage	--gpu
…-x86_64-unknown-linux-musl.tar.gz	static (musl)	no
…-aarch64-unknown-linux-musl.tar.gz	static (musl)	no
…-x86_64-unknown-linux-gnu-gpu.tar.gz	dynamic, glibc ≥ 2.28	yes
…-x86_64-apple-darwin.tar.gz	dynamic	no
…-aarch64-apple-darwin.tar.gz	dynamic	no

The musl builds are the portable default and the right thing for
an unattended installer to fetch. The GPU paths cannot be static —
they dlopen their runtimes — so they ship in the single dynamically
linked …-linux-gnu-gpu artifact instead, built against glibc 2.28
(RHEL/Rocky/Alma 8+, Ubuntu 20.04+).

What …-linux-gnu-gpu needs at run time

Only when --gpu is actually requested — otherwise it behaves
exactly like the musl one. It expects a CUDA 12 runtime and
cuDNN 9, with an NVIDIA driver ≥ 535 (the DTW kernels target the
CUDA 12.2 driver API), and a CUDA-enabled libonnxruntime matching
the ort 2.0.0-rc.13 it links.

Rather than assembling that by hand, see
GPU acceleration,
which covers the pixi environment that supplies it and how to
confirm the CUDA execution provider actually loaded.