ci: give release/v0.13 its own release-PR branch prefix

Cargo.toml

@@ -20,9 +20,10 @@ exclude = ["py-ft", "molecular-annotation/python"]
 
 [workspace.dependencies]
 rust-htslib = "0.46"
-# hts-sys 2.2.1 changed bindings that rust-htslib 0.46 relies on (bam1_core_t
-# isize, bgzf write length), so a fresh resolution fails to compile. Pin until
-# rust-htslib is bumped. Cargo.lock already held 2.2.0.
+# hts-sys 2.2.1 regenerated its bindings with bindgen 0.72 over the same
+# htslib 1.19.1: bam1_core_t.isize became isize_ and size_t became usize.
+# rust-htslib 0.46 still uses the old names, so a fresh resolution fails to
+# compile. Pin until rust-htslib is bumped. Cargo.lock already held 2.2.0.
 hts-sys = "=2.2.0"
 # molecular-annotation is versioned independently of fibertools-rs and kept at
 # a low 0.0.x "internal crate" version (bump only when its code changes). The

release-plz.toml

@@ -10,19 +10,31 @@
 # releases on ANY commit (chore/docs/ci included, as a patch); this restricts it
 # to meaningful changes. Breaking changes use feat!/fix!, which still match.
 release_commits = "^(feat|fix)[(:!]"
+# release-plz finds "its" open release PR by head-branch prefix only, with no
+# base-branch filter (opened_prs in release_plz_core). main uses the default
+# "release-plz-", so a run on this branch would grab main's 0.14.x release PR
+# and force-push 0.13.x content onto it (that happened to #132 on 2026-09-18).
+# A prefix that does not start with "release-plz-" or "release-plz/" keeps the
+# two branches' release PRs apart in both directions.
+pr_branch_prefix = "release-v0.13-"
 # The release-plz action installs cargo-semver-checks, so the check runs unless
 # turned off here, and it must be set in this [workspace] table to apply to
 # every package. It builds both the current source and the published baseline
 # from a fresh registry resolution without any Cargo.lock. The baseline is
 # immutable, and the 0.13.0 crate no longer resolves to a buildable set (vergen
 # 9.1.0 vs vergen-git2 1.x), so the check can never pass again for that
-# baseline. Conventional-commit bumping is what we rely on.
+# baseline. Once 0.13.1 is the newest published version, the baseline resolves
+# fresh again and this can be turned back on. Conventional-commit bumping is
+# what we rely on meanwhile.
 semver_check = false
 
 [[package]]
 name = "fibertools-rs"
 git_tag_name = "v{{ version }}"          # keep v0.X.Y (matches existing tags + cargo-dist)
 git_release_draft = true                 # draft so cargo-dist attaches binaries, then un-drafts
+# A 0.13.x patch cut after 0.14.0 exists must not become GitHub's "latest":
+# the cargo-dist updater and releases/latest/download URLs follow that flag.
+git_release_latest = false
 features_always_increment_minor = true   # feat -> minor even on 0.x
 # Prepend an install section (the cargo-dist shell installer) to the changelog
 # in the GitHub release body. {{ version }} is the release version; the tag is