Skip to main content

Recompute every release's volume/chapter span and every series' `highest_volume` / `highest_chapter` mark from the stored file lists (titles as fallback). Network-free and idempotent. Unlike the incremental bump that runs when a release is linked, this is an authoritative pass: a series' marks are *replaced* with the MAX across its currently-linked releases, so it also corrects values an earlier, more eager parser over-counted and clears marks on series whose releases no longer parse to anything.

POST 

/api/v1/series/recompute-spans

Use it after changing the span-parsing logic, or to backfill a catalog whose releases predate span detection. Runs in-process against the same pool serve uses, so it is safe to trigger on a live instance (it shares the single SQLite writer rather than contending with a separate process).

Responses